LIMS
Laboratory Information Management System
A LIMS is the system of record for the laboratory's work: the sample that was logged in, the tests assigned to it against a specification, the results entered or captured, the review and approval that made a value reportable, and the certificate of analysis assembled from it. It manages the sample's whole chain of custody — receipt, storage location, aliquoting, distribution to analysts, and disposal — and it is the place where a result meets its specification limit and is judged in or out. QC laboratories in GMP manufacturing are the archetypal deployment, but the same class serves GLP test facilities and clinical laboratories operating to GCLP.
What this page does not claim
A system class is not a product. SPEQ describes what a CTMS or a LIMS is; the vendor directory at /tools lists the products that implement one, and a GAMP category is a property of an implementation, not of a class.
What a LIMS actually is
A LIMS is the system of record for the laboratory's work: the sample that was logged in, the tests assigned to it against a specification, the results entered or captured, the review and approval that made a value reportable, and the certificate of analysis assembled from it. It manages the sample's whole chain of custody — receipt, storage location, aliquoting, distribution to analysts, and disposal — and it is the place where a result meets its specification limit and is judged in or out. QC laboratories in GMP manufacturing are the archetypal deployment, but the same class serves GLP test facilities and clinical laboratories operating to GCLP.
The distinction that matters is between the reportable result and the raw data behind it. In most architectures the raw data — the chromatogram, the balance printout, the spectral file — is generated and stored in the instrument system that produced it, and the LIMS holds the processed, reviewed value together with the calculation that derived it. The LIMS is also where specification management lives: versioned specifications and test methods are master data, the system compares each result against the registered limit, and an out-of-specification result is flagged at entry rather than discovered at review. Stability programmes run on the same backbone — protocols, pull schedules, and interval testing.
Because results decide whether product is released and whether a study conclusion stands, a LIMS is squarely a 21 CFR Part 11 and EU GMP Annex 11 system: review and approval are electronic signatures with regulatory weight, the audit trail must capture result changes and reprocessing, and access must distinguish the analyst who entered a result from the reviewer who approved it. The highest-leverage data in the system is the static master data. A transposed digit in a specification limit is not one wrong record — it is silently applied to every result tested against it until someone notices.
The commercial market is mature, so most deployments are configured platforms rather than bespoke builds — the pattern GAMP 5 Second Edition (2022) describes as Category 4, with custom calculations and interfaces pushing specific elements further. Implementation effort concentrates less in the software than in the content: building and verifying the specification and method master data, mapping the laboratory's actual workflow onto the system's, and interfacing instruments so results arrive without transcription. A LIMS that mirrors the paper process it replaced, manual entry included, has automated the filing cabinet and kept the transcription risk.
WHERE THE BOUNDARY ACTUALLY SITS
Not the raw-data system. The chromatogram and its integration live in the chromatography data system; the LIMS holds the reportable result derived from them.
Lab Instruments & CDS owns it →Not an electronic laboratory notebook. An ELN captures the narrative of experimental work — method development, investigations, non-routine science; the LIMS runs the routine, specification-driven testing workflow.
Not where the OOS investigation lives. The LIMS flags the out-of-specification result; the investigation, its root cause, and any CAPA are quality records in the eQMS.
eQMS owns it →Not the inventory system. The LIMS tracks samples and reagents for testing purposes; material stock, batch status, and warehouse movements are ERP records.
ERP & Warehouse Management owns it →WHAT IT HOLDS, AND WHAT CROSSES ITS BOUNDARY
CORE RECORDS
- Sample login, chain-of-custody, and disposal records
- Versioned specifications and test-method master data, with the limits results are judged against
- Results with their calculations, units, significant figures, and entry/capture provenance
- Review and approval records — who verified, who approved, and what changed between entry and approval
- OOS and OOT flags, and the disposition each received before any result was reported
- Stability study protocols, pull schedules, and interval results
- Certificates of analysis and the result set each one drew from
DATA FLOWS OUT
Sample identities, test assignments, and worklists pushed to instruments and the chromatography data system for acquisition
Out-of-specification and out-of-trend results escalated into a formal laboratory investigation
Approved release-testing results and certificate-of-analysis data feeding batch record review and disposition
Usage decisions and testing status that move a material or batch between quarantine and released in the inventory system
HOW THIS CLASS IS USUALLY VALIDATED
- SPEQ synthesis: most LIMS deployments are configured commercial platforms — GAMP 5 Second Edition (2022) Category 4 — with custom result calculations and bespoke instrument interfaces pushing those specific elements toward Category 5. The category is a property of the implementation, not the product, and a single deployment routinely spans several.
- Custom calculations are the highest-risk configuration: a wrong formula produces a plausible reportable value with no error, so calculation verification against independently worked examples warrants scripted evidence even under a CSA-leaned approach.
- Specification and method master data is part of the validated scope. A limit entered wrongly propagates to every result tested against it, so master-data build deserves the same verification rigour as the workflow configuration.
- Instrument and CDS interfaces are verified end to end — the value that leaves the source system must be the value the LIMS stores, including units, rounding, and significant figures, not merely a successful transmission.
SPEQ synthesis, not a rating. This is SPEQ’s reading of how this system class is commonly approached, offered to help you scope your own work. A GAMP category is a property of a specific implementation, not of a product class, and one deployment routinely spans several. It is not a classification service and does not replace your own documented risk assessment.
- Stage 1 · Reactive
Testing runs on paper worksheets and spreadsheets; the LIMS, where one exists, is a login register. Results are transcribed by hand, specifications live in documents, and answering "show me every result for this batch" means assembling folders.
- Stage 2 · Defined
Samples, tests, and specifications are managed in the system and results are entered against registered limits with electronic review. But entry is manual from instrument printouts, and OOS flagging depends on the reviewer noticing.
- Stage 3 · Controlled
Specifications are versioned master data, OOS results are flagged automatically at entry, instruments feed results through validated interfaces, and audit-trail review of result changes is scheduled and evidenced. Stability pulls are system-driven, not diary-driven.
- Stage 4 · Predictive
Laboratory data is trended, not just judged: out-of-trend detection runs against historical results, method and analyst performance are monitored, and recurring aberrant results surface as signals before they become OOS events.
- Stage 5 · Adaptive
The LIMS operates as part of a connected data architecture — results flow to batch disposition and annual product review without manual assembly, trending feeds control-strategy decisions, and review effort concentrates where the data says the risk is.
SPEQ’s shared five-stage progression, labelled synthesis. It is not the FDA QMM rating scale and not the scored maturity-assessment domains — assess your quality system for those.
WHAT AN INSPECTION PROBES, AND WHERE IT GOES WRONG
INSPECTION SIGNALS
- How aberrant results were handled before they were flagged — invalidating a result without an investigation, or retesting into compliance, is the classic laboratory data-integrity finding.
- Whether the specification versions in the LIMS match the currently registered specifications, and who can change a limit.
- Whether audit-trail review covers result modifications and reprocessing against specific records, not just a periodic statement that review occurred.
- Segregation of duties: whether an analyst can approve their own result, and whether shared logins make entry and review unattributable.
- Orphan samples and unreported results — samples logged and tested whose results never reached a reportable record.
COMMON RISKS
- Specification master data entered wrongly at build or at change, silently misjudging every subsequent result against the wrong limit.
- Manual transcription from instrument printouts surviving the implementation, keeping the exact error mode the system was bought to remove.
- Custom calculations changed without reverification, so the formula in production no longer matches the validated one.
- Legacy result migration that drops metadata or the original audit trail, breaking the link between a historical result and its provenance.
- Configuring the review workflow so the flagged status of an OOS result can be cleared without a recorded disposition.
WHO WORKS IN IT, AND WHERE IT IS SHAPED
ROLES
- QC analyst
- QC reviewer / second-person verifier
- LIMS master-data administrator
- Laboratory supervisor
- Stability coordinator
- CSV analyst
DELIVERY-LIFECYCLE PHASES
[ POSITION IN THE FRAMEWORK ]
6 OF 7 DIMENSIONS · 27 LINKSThe laboratory's system of record for samples, specifications, and results — from login through review to the reportable value a batch decision rests on; where a result meets its specification limit and is judged in or out.
06 · QUALITY MATURITY — LIMS, REACTIVE TO ADAPTIVE
Testing runs on paper worksheets and spreadsheets; the LIMS, where one exists, is a login register. Results are transcribed by hand, specifications live in documents, and answering "show me every result for this batch" means assembling folders.
Samples, tests, and specifications are managed in the system and results are entered against registered limits with electronic review. But entry is manual from instrument printouts, and OOS flagging depends on the reviewer noticing.
Specifications are versioned master data, OOS results are flagged automatically at entry, instruments feed results through validated interfaces, and audit-trail review of result changes is scheduled and evidenced. Stability pulls are system-driven, not diary-driven.
Laboratory data is trended, not just judged: out-of-trend detection runs against historical results, method and analyst performance are monitored, and recurring aberrant results surface as signals before they become OOS events.
The LIMS operates as part of a connected data architecture — results flow to batch disposition and annual product review without manual assembly, trending feeds control-strategy decisions, and review effort concentrates where the data says the risk is.
SPEQ’s shared five-stage progression, labelled synthesis — not the FDA QMM rating scale. Where does your organization sit? Score your quality system →
07 · REGULATORY & EVIDENCE
GOVERNING STANDARDS · 9
Derived from the 9 standards SPEQ maps to this subject, across 7 regulatory bodies: FDA, EMA, ISPE, OECD, MHRA, PIC/S, ISO.
RECORDS & OBJECTIVE EVIDENCE
- Sample login, chain-of-custody, and disposal records
- Versioned specifications and test-method master data, with the limits results are judged against
- Results with their calculations, units, significant figures, and entry/capture provenance
- Review and approval records — who verified, who approved, and what changed between entry and approval
- OOS and OOT flags, and the disposition each received before any result was reported
COMMON INSPECTION FINDINGS
- Aberrant results invalidated without investigation, or retesting into compliance
- Specification versions in the LIMS not matching the currently registered specifications
- Audit-trail review not covering result modifications and reprocessing against specific records
- An analyst able to approve their own result, or shared logins making entry and review unattributable
- Specification master data entered wrongly, silently misjudging every result against the wrong limit
Choosing, validating, and living with LIMS
SPEQ curates the software directory and does not endorse, certify, or rank any vendor. Listing is not a recommendation, and this catalog describes the system class, not the product.
FREQUENTLY ASKED
What is the difference between a LIMS and an ELN?
A LIMS runs structured, specification-driven testing: samples are logged, assigned predefined tests, and judged against registered limits through a fixed workflow of entry, review, and approval. An ELN captures unstructured experimental work — method development, investigations, research — where the record is a narrative of what the scientist did rather than a result against a limit. QC release testing belongs in a LIMS; the laboratory investigation that follows an unexpected result often starts in an ELN. Many organisations run both, and the boundary between them should be defined in procedure, not left to analyst preference.
Does a LIMS hold raw data?
Usually not, and the distinction matters for data integrity. Raw data — the chromatogram, the spectral file, the balance output — is generated and normally retained in the instrument system that produced it, and MHRA's 2018 GxP data integrity guidance expects the complete data, including metadata and audit trails, to be preserved where it was created. The LIMS holds the processed, reviewed, reportable result and the calculation behind it. An inspector reconstructing a result will walk from the LIMS value back to the raw data, so the link between the two systems must be unambiguous in both directions.
What GAMP 5 category does a LIMS fall into?
Most commercial LIMS deployments are approached as GAMP 5 Category 4 — configured commercial software — because the organisation configures workflows, specifications, and screens without writing application code. Custom result calculations, bespoke instrument interfaces, and scripted extensions push those specific elements toward Category 5. GAMP 5 Second Edition (2022) is explicit that the category describes the implementation rather than the product, that a single system commonly spans categories, and it retired the former Category 2 entirely. This framing is SPEQ synthesis to aid scoping, not a classification service.
Is a LIMS required by regulation?
No regulation mandates a LIMS. 21 CFR Part 211 and EU GMP require laboratory controls, complete records, and specification-based release decisions — a paper laboratory can meet them, and some small facilities still do. What the regulations do require becomes materially harder at scale on paper: contemporaneous recording, second-person verification, trend evaluation, and reconstructable data lineage. Once records are electronic, 21 CFR Part 11 and Annex 11 apply in full. The honest framing is that a LIMS is how a laboratory of any size meets existing requirements reliably, not a requirement in itself.