V5 Ultimate
Ultimate
PricingResourcesCompany
English (original)العربيةDeutschΕλληνικάEspañolFrançaisItalianoעברית日本語한국어NederlandsPolskiPortuguêsSvenska
Talk to us Log in Start free trial
Food & Beverage
  • Bakery & Confectionery
  • Food Processing
  • Ingredients & Dry Mixes
  • Sausage & Meat Products
  • Produce Packing
  • Pet Food & Pet Supplements
  • Dairy & Chilled Foods
  • Beverages & Liquid Manufacturing
  • Infant Formula
Pharma & Life Sciences
  • Radiopharmaceuticals
  • Pharmaceutical
  • Medical Devices
  • Veterinary Pharmaceuticals
  • Blood & Tissue
  • Diagnostics & IVD Kits
  • Reference Materials & Standards
  • OTC Topical Creams & Gels
Supplements & Personal Care
  • Dietary Supplements
  • Cosmetics & Personal Care
  • Cannabis & Hemp Manufacturing
  • Fragrances & Perfumery
  • Soaps & Personal Hygiene
  • Botanical Extracts & Essential Oils
Chemicals & Materials
  • Plastics & Resins
  • Agricultural Chemicals
  • Specialty & Industrial Chemicals
  • Printing Inks, Pigments & Construction Chemicals
  • Lubricants & Metalworking Fluids
  • Coatings, Adhesives & Sealants
Other Manufacturing
  • Consumer Products
  • Electronics & Electrical Assembly
  • Textiles & Nonwoven
  • Contract Manufacturing & Co-Packing
  • Packaging & Food-Contact Materials
  • Regulated Warehousing & Distribution
Explore all industries
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Why V5? Product & Features
Why V5?Product & Features
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Explore all industries
    • Bakery & Confectionery
    • Food Processing
    • Ingredients & Dry Mixes
    • Sausage & Meat Products
    • Produce Packing
    • Pet Food & Pet Supplements
    • Dairy & Chilled Foods
    • Beverages & Liquid Manufacturing
    • Infant Formula
    • Radiopharmaceuticals
    • Pharmaceutical
    • Medical Devices
    • Veterinary Pharmaceuticals
    • Blood & Tissue
    • Diagnostics & IVD Kits
    • Reference Materials & Standards
    • OTC Topical Creams & Gels
    • Dietary Supplements
    • Cosmetics & Personal Care
    • Cannabis & Hemp Manufacturing
    • Fragrances & Perfumery
    • Soaps & Personal Hygiene
    • Botanical Extracts & Essential Oils
    • Plastics & Resins
    • Agricultural Chemicals
    • Specialty & Industrial Chemicals
    • Printing Inks, Pigments & Construction Chemicals
    • Lubricants & Metalworking Fluids
    • Coatings, Adhesives & Sealants
    • Consumer Products
    • Electronics & Electrical Assembly
    • Textiles & Nonwoven
    • Contract Manufacturing & Co-Packing
    • Packaging & Food-Contact Materials
    • Regulated Warehousing & Distribution
PricingResourcesCompany
Start free trial Log in Talk to us
HomeGlossaryLIMS
Lab · The complete guide

LIMS (Laboratory Information Management System)

In short

Follow a sample through a LIMS to understand how laboratory evidence supports testing, investigation and human quality decisions.

4,047 words · ~19 min read
Laboratory information management: a lab technician in PPE scans a rack of barcoded sample tubes beside an analytical instrument
A LIMS tracks samples, tests and results through the laboratory.
On this page
  1. 01What a LIMS manages—and what it does not
  2. 02Regulatory scope: required records, not required software
  3. 03From sample receipt to a reviewed certificate
  4. 04LIMS, ELN, LES, CDS and SDMS compared
  5. 05The evidence behind a laboratory result
  6. 06Instrument transfers: preserve meaning and recover failures
  7. 07OOS handling without testing into compliance
  8. 08Stability and environmental monitoring need context
  9. 09Where laboratory evidence meets MES and ERP
  10. 10Implementation and review: test the evidence chain
  11. 11V5 Ultimate: laboratory evidence in the batch record
On this page · 11 sections
  1. 1What a LIMS manages—and what it does not
  2. 2Regulatory scope: required records, not required software
  3. 3From sample receipt to a reviewed certificate
  4. 4LIMS, ELN, LES, CDS and SDMS compared
  5. 5The evidence behind a laboratory result
  6. 6Instrument transfers: preserve meaning and recover failures
  7. 7OOS handling without testing into compliance
  8. 8Stability and environmental monitoring need context
  9. 9Where laboratory evidence meets MES and ERP
  10. 10Implementation and review: test the evidence chain
  11. 11V5 Ultimate: laboratory evidence in the batch record
AI · Explain it for MY operation

How does LIMS apply to your shop floor?

Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.

Your scale

01What a LIMS manages—and what it does not

LIMS (Laboratory Information Management System) is software that manages laboratory samples, assigned tests, specifications, results and their reviewable records. The aliases laboratory information management system, lab information system and QC LIMS appear in software selection and laboratory procedures. Here, they refer to manufacturing quality-control laboratories, not clinical diagnostics.

The organising question is practical: can a reviewer reconstruct which material was tested, against which instructions, with what evidence and subsequent decisions? A useful LIMS assessment starts with that reconstruction, rather than a feature count or a dashboard of passing results.

Four objects help frame the answer. A sample identifies the material submitted for examination; a test identifies the assigned examination; a result records its outcome; evidence supports how that outcome was produced and reviewed. These are connected, but not interchangeable. A passing number alone does not explain sample identity or the work behind it. The chain begins with a controlled sample login handoff.

This article follows laboratory work and its evidence, distinguishing binding requirements from official guidance and implementation practice. It then compares neighbouring laboratory systems and examines validation and review. Manufacturing execution and enterprise inventory are separate responsibilities; interface design belongs in MES–LIMS integration. Treat the functions described here as evaluation topics, not promises that every LIMS includes them.

02Regulatory scope: required records, not required software

For the provisions discussed here, the regulatory obligation is the laboratory record and its associated controls—not the purchase of software called LIMS. A LIMS may support those obligations, but its name does not establish that the required evidence exists. This distinction keeps software selection separate from the assessment of applicable requirements.

Binding US requirements: data and laboratory controls

21 CFR 211.194(a) requires laboratory records to include complete data from all tests necessary to assure compliance with established specifications and standards, including examinations and assays. The requirement concerns the evidence generated by testing, rather than a particular software category.

Under 21 CFR 211.160(a), specifications, standards, sampling plans, test procedures and other laboratory control mechanisms required by the subpart—including changes—must be drafted by the appropriate organizational unit and reviewed and approved by the quality control unit. The subpart’s requirements must be followed and documented at the time of performance. Deviations from those written controls must be recorded and justified. See the broader Part 211 laboratory-controls context when locating these provisions within pharmaceutical manufacturing requirements.

Guidance and product boundaries

The FDA OOS guidance background states that its Part 211 citations pertain to finished pharmaceuticals. That is the boundary used for this section’s Part 211 discussion; these obligations should not be transferred wholesale to supplements, food, devices or chemicals. The FDA document is guidance, not a new binding requirement: its introductory status statement identifies recommendations unless specific regulatory or statutory requirements are cited.

Jurisdiction and product contextSource categorySupported subjectLimits of this mapping
US finished pharmaceuticalsBinding regulation: supplied Part 211 passagesComplete laboratory data; approved controls; contemporaneous documentation; justified deviationsA focused laboratory-record mapping, not a complete regulatory assessment
US electronic recordsRegulation: Part 11 applicability questionWhether electronic-record controls apply to the intended useNo detailed Part 11 duties are mapped here
EU computerised systemsOfficial guidance: Annex 11 referenceSeparate assessment of computerised-system expectationsConfirm applicable scope and version before mapping individual provisions
Supplements, food, devices and chemicalsSector-specific applicable sourcesEach operation’s own records and controlsDo not substitute this pharmaceutical mapping for a sector-specific assessment

As implementation practice, build a requirements matrix that separates binding provisions, guidance recommendations and local operating choices. Record the product, jurisdiction, intended use and evidence supporting each entry. Treat workflow suggestions elsewhere in this article as practice unless tied explicitly to a cited requirement. Use the Part 11 reference to orient the electronic-record assessment, not as a blanket conclusion that every LIMS deployment has identical obligations.

03From sample receipt to a reviewed certificate

A typical manufacturing QC workflow connects collection, testing and reporting through one traceable sample identity. The sequence below is implementation practice; actual roles, sequencing and approval gates depend on the laboratory’s approved procedures.

  1. Collect and log in. Assign a unique sample identifier and link it to the source lot. At the sample login handoff, compare the container, label and request. Route insufficient quantity, damaged packaging or mismatched identity for resolution rather than silently advancing the sample.
  2. Track custody and subdivision. Record storage location and chain of custody, including sender, recipient and transfer time. Give aliquots identities linked to the parent sample. Resolve missing or conflicting handoff information before relying on the affected material.
  3. Assign testing. Select the applicable approved specification and method versions before testing, considering the material, product and testing purpose. An assigned test is planned work, not a result. Record preparation details against that assignment so measurements remain connected to the material actually tested.
  4. Capture and calculate. An observed value is the measurement obtained; a calculated reportable result applies the method’s calculation rules. Preserve both rather than replacing the observation with the final number. Route failed limits and other analytical exceptions to investigation.
  5. Review. Check identity, preparation, method version, calculations, applicable limits and exception decisions. An approved result is a result accepted through the designated review process—not merely a number that falls inside its acceptance interval.

For US drug laboratory records within Part 211’s scope, 21 CFR 211.194(a)(1) requires a sample description, source location, quantity, lot number or other distinctive code, collection date and receipt date. The login record should capture these specified elements; custody-transfer fields, storage locations and aliquot relationships are additional operational controls, not fields expressly listed in that provision.

Worked case: assume the approved method specifies a dimensionless dilution factor of 20, the diluted solution measures 4.90 mg/L, and no other correction is required. The original-solution result is 4.90 mg/L × 20 = 98.0 mg/L, within an assumed inclusive interval of 95.0–105.0 mg/L. These limits are illustrative, not regulatory. Retain the measured concentration, dilution factor, units, method version and calculated result.

Report selected approved results in a controlled certificate of analysis (CoA), linked to underlying evidence rather than substituting for it. A passing test, completed laboratory review, issued CoA and batch disposition are distinct events; authorised humans approve and release under applicable procedures.

Workflow: Collection → login/custody check → acceptable? No: resolve receipt/transfer exception or stop; yes: assign → prepare → capture/calculate → exception? Yes: investigate → documented decision; no: review → approve or return for resolution → controlled reporting.

QC Sample-to-Decision Workflow
  1. 1
    Log SampleIdentify the source lot, collection event and receipt.
  2. 2
    Assign testsEstablish applicable specification, method versions and reporting units.
  3. 3
    Prepare and testRecord aliquots, preparation details, analysts and instrument references.
  4. 4
    Capture resultsReconcile raw evidence, calculations and any transfer exceptions.
  5. 5
    Assess exceptionsRoute suspect results for documented assessment and investigation.
  6. 6
    Review evidenceAn authorised reviewer evaluates results and supporting records.
  7. 7
    Issue and Hand OffPublish the controlled CoA; route evidence for human disposition.
Typical handoffs; exception paths retain evidence and return to authorised review.

04LIMS, ELN, LES, CDS and SDMS compared

These laboratory software categories describe functional boundaries, not standardised legal definitions. Vendor implementations overlap: one product may cover several roles. Compare the evidence each system manages, rather than assuming its acronym defines its scope.

systemprimary objecttypical laboratory roleboundary to verify
LIMSSample and test assignmentQC status and resultsWhether execution and raw-data functions are included
ELN (electronic laboratory notebook)Experiment or notebook entryScientific observations and reasoningWhether structured QC routing is included
LES (laboratory execution system)Execution of a procedureGuided steps and contemporaneous observationsWhether sample and specification management is included
CDS (chromatography data system)Chromatographic sequence and analytical dataAcquisition and processingHow processed values and source evidence are linked
SDMS (scientific data management system)Scientific files and metadataCollection and retrievalWhether scientific interpretation or QC disposition is supported

For example, a LIMS assigns an assay, an LES guides sample preparation, a CDS processes chromatographic data, and an SDMS stores retrievable scientific files. An ELN might capture experimental reasoning during method development. This is an example architecture, not a required five-system stack; a combined platform may provide several functions.

For selection, follow one representative result and inspect ownership of the original record, version history and review action. Ask where the analyst records an observation, where a changed calculation remains visible, and precisely what the reviewer approves. For ELN and LES workflows, contemporaneous recording is a useful neighbouring concept: distinguish observations captured during work from summaries entered later.

05The evidence behind a laboratory result

A useful LIMS evidence model connects a reported value to the work that produced it. The following is an illustrative design, not a mandated database schema or a description of verified V5 fields.

For laboratory records within US drug CGMP scope, 21 CFR 211.194(a)(3) requires the weight or measure of sample used for each test, where appropriate. Received quantity is not a substitute: if a laboratory receives 100 g and uses 0.5 g for a test, the test-use record identifies 0.5 g.

The complete-data requirement in 21 CFR 211.194(a)(4) includes instrumentation graphs, charts and spectra. A final numeric result alone therefore cannot represent the complete test record. 21 CFR 211.194(b) also requires complete records of modifications to established testing methods; link those records to the affected method and tests.

Illustrative evidence links; arrows mean record references, not workflow gates: Sample → Assigned test → Result version → Source evidence Assigned test → Specification version + Method version → Method-modification record, if applicable Result version → Investigation, if applicable Result version → Review event → Controlled CoA snapshot

Attach analyst attribution and test-use quantity to the execution context. Preserve result units, calculation inputs, dilution factors, formula version and rounding context so a reviewer can reconstruct the value. Specification and method links should resolve to the versions used, not silently redirect to today's versions.

Keep an original observation distinguishable from a corrected or reprocessed result. Link each successor to its predecessor, source evidence and change rationale without overwriting the earlier record. A review event should identify the exact result version reviewed, reviewer and time. The controlled CoA snapshot discussed above can then reference those reviewed versions. For data-integrity implications of preserving interactive evidence rather than only a rendered report, see dynamic versus static records.

Logical Laboratory Evidence Model

Sample

Identity and physical-material lineage.

  • sample_id
  • lot_id
  • parent_sample_id
  • received_at

Test assignment

Versioned testing instruction for one sample.

  • test_id
  • sample_id
  • specification_version_id
  • method_version_id

Result

Recorded value and reporting context.

  • result_id
  • test_id
  • reported_value
  • unit

Evidence Asset

Resolvable source record, not merely an attachment.

  • evidence_id
  • result_id
  • source_record_uri
  • checksum

Investigation

Exception assessment and authorised outcome.

  • investigation_id
  • result_id
  • investigation_status
  • disposition

Review event

Who reviewed which record version.

  • review_event_id
  • record_version_id
  • reviewer_id
  • reviewed_at
Illustrative design fields, not a mandated schema or verified application structure.

06Instrument transfers: preserve meaning and recover failures

Treat instrument-to-LIMS transfer as a defined evidence handoff. As interface-control practice, define a transfer contract covering the source system and record identifier, sample and test identifiers, method or processing version, measured value, unit, precision, timestamp with time-zone context, and a resolvable source-data reference. Distinguish measurement time from transmission time. A successful file transfer establishes neither correct sample attribution nor scientific meaning: a number can arrive intact but belong to the wrong test.

Identify where reviewers can access chromatograms, spectra, processing history and other relevant source records. If that evidence remains in a CDS or another repository, test retrieval and review access using representative records. Do not assume a copied PDF or attachment preserves all evidence needed to understand the reported result.

  • Duplicate messages: use immutable transaction keys to prevent duplicate result creation.
  • Unmatched samples: quarantine rather than guess the destination.
  • Unrecognised units: apply controlled, verified mappings before acceptance.
  • Interrupted transfers: reconcile expected, received, accepted and quarantined records.
  • Expired source links: monitor retrieval and route failures for repair.

Worked case 2: reconcile messages, not just totals

Assume a run should supply 24 distinct results, measured in mg/L, and initially sends 26 messages. Two messages repeat already received immutable identifiers, leaving 26 − 2 = 24 distinct payloads. One payload has an unrecognised unit code: 23 results are accepted and one is quarantined. After source verification confirms mg/L and an approved mapping correction is applied, replay only the quarantined payload. The accepted total becomes 23 + 1 = 24 results, with no duplicate result records.

Assign laboratory ownership of the exception queue, with interface support responsible for technical repairs. Preserve rejected payloads, rejection reasons, replay identifiers and reconciliation evidence. Review transfer events and mapping changes through the audit trail, including who authorised correction and when replay occurred. Correcting interface configuration changes how a payload is interpreted; editing a scientific result changes the laboratory record. Keep those actions separately attributable, and retain the original payload rather than overwriting it during repair.

07OOS handling without testing into compliance

An out-of-specification (OOS) result falls outside its applicable acceptance criteria. It differs from an unusual but within-specification trend and from an unresolved analytical error: suspected error is not itself a demonstrated reason to invalidate a result. Classification follows approved laboratory procedures; see out-of-specification results for the terminology.

Preserve the assessment, not just the status

For pharmaceutical production, the FDA supervisor-assessment recommendation, step 7 is to fully document and preserve the laboratory assessment. This is guidance, not a requirement to purchase a LIMS. A practical implementation links the original result to an investigation record rather than treating investigation closure as an editable fail-to-pass status.

The assessment record should bring together original observations and preparations, method execution, calculations, instrument context, hypothesis checks, decisions and authorised follow-up. Record what each hypothesis predicts, what was checked and whether the evidence supports it. A suspected dilution error, for example, belongs beside the preparation evidence and check outcome—not merely in a closure comment.

As an implementation practice, keep the laboratory assessment, broader investigation and final disposition as connected but distinct records. Their links should expose unresolved questions and the evidence behind each conclusion. Where the event also enters deviation management, cross-reference the records rather than maintaining competing accounts; see OOS investigation and follow-up. The human-decision boundary remains as covered above.

Worked case: a passing retest mean

Assume an assay specification of 95.0–105.0% of label claim, inclusive. The initial result is 94.6%. Two retests authorised under a predefined protocol yield 97.1% and 98.3%; their mean is (97.1 + 98.3) / 2 = 97.7% of label claim. Assume no laboratory or calculation error has been identified.

The FDA retesting discussion says retest numbers should not change depending on results obtained. Predetermined retesting controls therefore belong in the approved procedure or protocol; a software workflow is not permission to keep testing until a pass appears.

Under that guidance, the passing 97.7% mean does not establish a scientific basis for discarding the original 94.6% result when no laboratory or calculation error has been identified. The investigation must address the original failure, not replace it with the more favourable summary. A useful LIMS view presents all three results with their assessment links, preserving the distinction between observations and conclusions.

08Stability and environmental monitoring need context

For stability and environmental monitoring, a LIMS needs more than a sample identifier and a result to support meaningful review. The following are operational design practices, not prescribed programme schedules, sampling frequencies or universal limits.

For stability testing, connect each result to the study identity, product and lot, packaging configuration, storage condition, scheduled time point, actual pull date, test date and applicable specification version. Scheduling a pull establishes intended work; it does not prove that a sample was removed from storage or tested. Keep planned milestones distinct from recorded events so reviewers can reconstruct the sample’s actual history.

For environmental monitoring, retain the location, collection method, collection time, sampled quantity with units, relevant operating context and approved assessment criteria. Operating context might distinguish sampling during production from sampling while an area is idle. A count without its sampled air volume or surface area may be unsuitable for comparison: identical numbers can represent different sampling exposures, and different collection methods may recover organisms differently.

Make overdue work, missing observations and method changes visible exceptions, rather than filling gaps with assumed dates or values. Preserve what is unknown alongside what was recorded. When methods, sampling volumes or specifications change, comparability becomes a scientific-review question—not something a continuous trend line establishes. Reviewers should assess whether results can be compared directly, require qualified interpretation or belong in separate series; no universal out-of-trend rule resolves those differences.

09Where laboratory evidence meets MES and ERP

In a typical manufacturing architecture, LIMS manages laboratory samples and test evidence, MES supplies production execution context, and ERP manages business or inventory transactions. These are practical boundaries, not universal assignments or a requirement to operate all three systems. A site's record-ownership model should identify the authoritative system and accountable people for each record type.

The shared-reference problem is that a laboratory sample identifier, manufacturing batch identifier and inventory lot identifier may differ. Govern their relationships explicitly rather than assuming matching text means matching material. For example, several samples may relate to one manufacturing batch. Document who maintains these mappings and controls corrections. A system receiving a test status does not thereby become the owner of the underlying laboratory record; it needs a traceable reference back to that evidence.

For message sequencing, integration architecture and manufacturing-side exception recovery, see MES to LIMS integration. Those interface decisions should follow the ownership model rather than define it accidentally.

10Implementation and review: test the evidence chain

Use this as a risk-based implementation and review checklist, not a quotation of Part 11 or Annex 11 requirements. Organise computerised-system validation around evidence that the configured LIMS supports the laboratory’s intended use.

Define use and responsibility

Identify product scope, laboratory activities, authoritative records, system boundaries, outsourced services and configuration ownership. Assign a named human owner to each exception type and its resolution. Supplier documentation can support assessment, but it is not a substitute for evidence that the site’s configuration works with its methods, interfaces and workflows. For hosted services, identify who supplies test evidence, manages changes, restores records and supports retrieval at service exit.

Demonstrate outcomes, including failures

  • Sample and method context: prove correct sample attribution and selection of effective specification and method versions. Change a specification while work is open; verify the intended version remains identifiable and any reassignment is controlled.
  • Results: check calculations, rounding and units against independently established expected values. Introduce a wrong unit and verify detection or controlled conversion rather than silent acceptance.
  • People and evidence: demonstrate attributable entry and correction, reviewer access to source evidence and permission boundaries. Attempt unauthorised approval. Where electronic signatures are used, test signer identity, record linkage and displayed meaning.
  • Reporting and recovery: verify controlled report generation and retrievable history. Interrupt a transfer and apply the earlier reconciliation example’s checks. Restore a representative record set from backup and demonstrate completeness, readability and usable evidence links.

For migration, compare source and destination populations, not just selected screenshots. Check completeness, original units, method context, time handling—including time zones—record-version relationships and source-evidence retrieval. Record discrepancies and their disposition before accepting the migrated evidence.

Keep the evidence current

Review unresolved interface exceptions, access changes, failed scheduled jobs, retrieval failures and configuration changes. Use requirements traceability during change control to identify affected tests and determine whether previous evidence still matches intended use. Give each review finding a named human owner, action and closure evidence; software status alone is not an acceptance decision. Set review frequency according to laboratory risk and change activity, with additional review after significant incidents or changes.

11V5 Ultimate: laboratory evidence in the batch record

V5 Ultimate assembles lab samples and QC check results into its batch record alongside manufacturing evidence: the work order, steps and step executions, dispensed bags and dispense variances, equipment used, checklists, electronic signatures and deviations. This places laboratory evidence alongside the batch execution history, rather than describing a separate laboratory-management capability. The human-decision boundary established above remains unchanged: authorised people approve and make batch release decisions.

Frequently asked questions

Q.Can a small QC laboratory use controlled paper records or spreadsheets instead of a LIMS?+

Yes, provided the chosen arrangement supports the laboratory’s applicable record and control obligations; sample volume alone is not a sufficient decision criterion. As a practical assessment, check sample identification, approved methods, calculation checks, review, retrieval and protection against undocumented changes. For spreadsheets, test formulas and control template versions and editing permissions. A hybrid record system also needs an explicit map of where original evidence resides and how reviewers reconcile paper worksheets with electronic results.

Q.What evidence should a contract laboratory return alongside its certificate of analysis?+

Define the evidence package in the service agreement: sample receipt and condition, identifiers, methods and versions, results with units, calculation basis, review status, and references to deviations or investigations. Agree how supporting raw data and metadata will be supplied or accessed. For pharmaceutical OOS cases, FDA guidance on retesting recommends reporting and considering passing and suspect results in batch release decisions. Include a chain-of-custody record where transport or transfers could affect interpretation.

Q.How should a result assigned to the wrong sample or lot be corrected?+

Treat the reassignment as a traceability correction, not a cosmetic edit. Preserve the original association and record the corrected association, reason, supporting evidence, person making the change and reviewer. Check both affected samples for downstream consequences, including calculations, investigations, certificates and disposition decisions. If identity cannot be established, flag the result as unresolved rather than guessing its destination. An audit trail should make the sequence reconstructable without requiring reviewers to compare unexplained database snapshots.

Q.What happens when a specification changes after a sample has been logged?+

Do not assume the newest specification automatically governs every open sample. Under the laboratory’s change-control procedure, determine applicability using the approved effective date, product and market context, lot status and any transition instructions. Preserve the specification version originally assigned, then document any approved reassignment and its effect on completed tests. If reassessment is needed, retain both evaluations with their respective limits. Controlled material master data helps separate the active specification from historical sample decisions.

Q.What evidence should a manufacturer request before adopting a hosted LIMS?+

Request evidence against intended use, not only a vendor demonstration: architecture and data flows, responsibility allocation, access controls, audit-trail behavior, backup restoration tests, incident handling, change notification and usable data export. Ask which validation evidence covers the supplied version and which workflows require local testing. Include outage operation, subcontractor dependencies and contract-exit arrangements in the assessment. A requirements traceability matrix can connect critical laboratory needs to vendor evidence, manufacturer tests and unresolved gaps before adoption.

Q.How can historical results be migrated without losing their original units or method context?+

Define a migration mapping that preserves original values, units, qualifiers, method versions, specification versions and sample identifiers. Keep converted or normalized values in separate fields with the conversion rule and provenance; do not overwrite the historical expression. Reconcile record counts and test representative edge cases, including detection-limit qualifiers, decimal precision and missing metadata. Where context cannot be recovered, label that limitation explicitly. Assess dynamic versus static records before substituting a report export for an interpretable source record.

Q.What should happen when a stability pull is missed or performed late?+

Record the planned pull date, actual pull date, storage history and reason for the departure. Distinguish late removal from late testing: they create different questions about exposure and sample handling. Have the responsible stability scientist assess interpretability against the protocol, including whether additional testing or revised trend evaluation is justified. Do not backdate the event or label an unqualified late result as on-time. A sample pull prompt supports scheduling, but missed-event assessment needs a documented scientific decision.

Q.When should a certificate of analysis be reissued rather than silently replaced?+

As a document-control practice, reissue an issued certificate when correcting information recipients may rely on, such as lot identity, a reported result, units, method reference or conformity statement. Give the revision a distinct identifier, explain the change, obtain approval and identify the superseded certificate. Assess who received the earlier version and communicate the correction accordingly. Preserve both versions and the supporting decision; use the electronic release record to connect the revised certificate with any affected disposition assessment.

Primary sources

  • 21 CFR 211.194 — Laboratory records
  • 21 CFR 211.160 — Laboratory controls: general requirements
  • FDA guidance: Investigating Out-of-Specification (OOS) Test Results for Pharmaceutical Production (2022)
Software that covers LIMS
V5 Ultimate Quality Control Software
In-process checks, sampling plans, spec limits, SPC trending, CoA generation and hold/release — enforced at the kiosk while the…
V5 Ultimate Supplier Quality Management Software
Keep why each supplier is approved, and for which materials, connected to the purchasing and receiving records that use them —…
V5 Ultimate LIMS
V5 includes laboratory information management alongside production and quality: sample plans, requests, lab queues and results…

Explore this topic

LIMS sits inside 2 overlapping topic clusters in our glossary. Every neighbour is one click away.

MES, WMS, ERP & QMS Layer
15 related entries

Where each shop-floor system fits and what it owns vs the ERP above it.

MESWMSQMSERPWORoutingBOMTraining RecordSOPRBACSSO / SAMLDocument controlAudit ManagementCMMSAsset Lifecycle Management
Lab & QC
14 related entries

Specifications, methods, instrument capability and the LIMS layer.

CoAOOSOOTUSPMSAGage R&RSPCCp / CpkIQ / OQ / PQPPQICH Q2ICH Q621 CFR 58ISO 8655
Talk to us about LIMS

Want to see how LIMS could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.

Start free
Back to glossary
Inside V5
  • → QC release — see what is open, then a person decides.
Example reports
V5Ultimate

Sample report

Certificate of Analysis (CoA)

Test & release

Certificate of Analysis (CoA)View on screen or print
→ All example reports
Related terms
  • → CoA
  • → OOS
  • → SPC
  • → MES
  • → WMS
  • → QMS
  • → ERP
  • → WO
  • → Routing
  • → BOM
  • → Training Record
  • → SOP
  • → RBAC
  • → SSO / SAML
  • → Document control
  • → Audit Management
  • → CMMS

Next Step

Try V5 with your own records, or ask a question first. Ask V5 opens with an editable question; nothing is sent until you choose to.

Start your free trial Browse All Features

Showing the site for the United States. Local spelling, dates and prices are applied automatically; change the language at the top of the page.

V5 Ultimate
Ultimate

Warehouse, quality and manufacturing software for regulated operations.

ProductIndustriesPricingResourcesSecurity & TrustCompanyLegal Centre

© S.G. Systems, LLC