Laboratory Testing, LIMS & Release in Regulated Manufacturing — From Samples to Lot Disposition

This topic is part of the SG Systems Global regulatory & operations glossary.

Updated November 2025 • lab testing in manufacturing, LIMS, ISO/IEC 17025, QC release, COAs, ELN, test method validation, OOS/OOT, sampling & review, GxP data integrity • Pharma, Biologics, Medical Devices, Dietary Supplements, Food & Beverage, Meat, Bakery, Cosmetics, Chemicals

Laboratory testing and LIMS sit at the choke point of regulated manufacturing. Ingredients cannot be released for use, batches cannot be released to customers and complaints cannot be closed without lab evidence. But in many plants, lab data lives in its own silo—printed chromatograms, home-grown LIMS, spreadsheets—loosely connected to MES, WMS and QMS.

When things go wrong, that separation is exactly what hurts: QA is stuck stitching together where samples came from, whether methods were valid, who reviewed results and which lots were actually released against which specifications.

“If you can’t trace each lab result back to its sample, method, instrument, analyst, batch and lot—and forward to the release decision—you don’t have a QC lab. You have a collection of tests.”

1) Lab expectations in regulated manufacturing — more than “good science”

Whether or not a site seeks formal ISO/IEC 17025 accreditation, the core expectations are similar:

• Competence & impartiality. Labs must have qualified staff, controlled methods and a structure that avoids undue influence on results.
• Validated methods. Test methods are validated (or verified) for their intended use; performance characteristics and uncertainties are understood.
• Traceability of results. Each result is traceable to a sample, method, instrument, calibration status and analyst.
• Control of records. Raw data and processed results are captured, stored and reviewed under data-integrity expectations (ALCOA+).

Layer pharma-/device-specific expectations (e.g., USP chapters, ICH guidance) and food lab expectations (micro, contaminants, label claims) on top, and you end up with a lab that must think like a GxP system, not just as a scientific service.

2) LIMS & ELN — getting lab data out of notebooks and into systems

Two system types typically underpin lab informatics:

• LIMS — Laboratory Information Management System. LIMS manages samples, tests, worksheets, results, approvals, reference data (methods, specs, instruments) and reporting.
• ELN — Electronic Laboratory Notebook. ELN captures more free-form experimental work, R&D studies, method development and exploratory work.

In a regulated manufacturing context, LIMS is usually the primary system for release testing and in-process controls; ELN may be used for development and validation studies. Key questions:

• Can you trace every reported result back to a sample, LIMS record and raw data?
• Does LIMS know which batch/lot the sample came from and what specification applies?
• Do LIMS and MES/WMS talk, or are you re-keying identifiers by hand?

Until those questions are answered, “LIMS” is just another silo, not part of an integrated quality system.

3) Sampling, testing and review — who does what, when

Your lab analyses & review glossary entry outlines the basic lifecycle of a test:

• Sampling. Samples are taken according to defined plans (e.g., per lot, per batch step, per time interval). Sampling points are defined by risk and regulatory expectations.
• Testing. Lab staff perform tests per validated methods using calibrated instruments.
• Review & approval. Results are reviewed by a second person or designated reviewer; calculations are checked; anomalies are investigated.
• Release or action. Results are compared to specifications; lots, batches or processes are held, released, adjusted or rejected accordingly.

For that to work reliably, sampling triggers must be linked to MES (events in the process), LIMS (sample registration) and WMS (lot/batch identity). V5’s job is to be the execution side of that linkage: creating sample requests at defined triggers and consuming LIMS results into lot and batch status.

4) Methods, instruments and validation — TMV, HPLC, UV-Vis, Karl Fischer

Test results are only as good as the methods and instruments behind them. Your glossaries cover several key pieces:

• Test method validation (TMV). TMV ensures that methods are suitable for their intended purpose, evaluating accuracy, precision, specificity, linearity, range, robustness and detection/quantitation limits.
• HPLC, UV-Vis, Karl Fischer & others. Entries like HPLC, UV-Vis, Karl Fischer titration and others describe key instrument types and their role in QC.
• Calibration & maintenance. Instruments must be under calibration status and maintenance control, with events recorded and linked to methods and results.

From a systems perspective, this means LIMS and QMS must know:

• Which method and version was used for each test.
• Which instrument was used and what its status was.
• Where raw data lives (instrument software, ELN, attached files) and how it is linked to the reported result.

V5 does not replace LIMS or instrument software; it must integrate with them and treat lab data as part of the same traceability and release story as process data.

5) QC testing & release — from results to lot disposition

QC testing & release evidence is where lab work affects production, inventory and customers. Key components:

• Specifications. Each material, intermediate and product has defined specifications: tests, methods and acceptance criteria.
• Lot/batch status. Lots and batches are held, released, rejected or regraded based on lab results and QA/QP decision-making, tracked in WMS and MES via release status.
• Certificates of Analysis (CoA). CoAs summarise test results and specifications for customers and regulators.

In a V5 environment, QC results should flow from LIMS into V5, which then gates lot and batch statuses for MES and WMS: you literally cannot consume or ship material unless its status allows it. That turns “QC release” from an email plus spreadsheet into a system-enforced constraint.

6) OOS, OOT and data integrity — not all numbers are equal

Two glossary entries point to where labs often struggle most:

• Out-of-specification (OOS). OOS results are those that fall outside predefined acceptance criteria.
• Out-of-trend (OOT). OOT results may meet spec but deviate from historical trends; they can be early warning signs.

Handling OOS/OOT correctly requires:

• Clear SOPs, integrated with QMS, for OOS/OOT detection, confirmation, root-cause analysis and impact assessment.
• Robust data integrity controls: no backdating, no unlogged reprocessing of chromatograms, full audit trails in LIMS and instrument systems.
• Integration with batch and lot records so QA/QP can see the full context and decide on rework, rejection or further testing.

V5 QMS can be used to manage OOS/OOT investigations, linking them to specific batches, lab runs, methods and CAPA items. V5 MES/WMS then ensure that affected lots cannot be released or used until investigations are done.

7) LIMS–MES–WMS–QMS integration — one story rather than four

In many plants, these systems evolved independently:

• MES knows about batches and steps.
• WMS knows about lots and locations.
• LIMS knows about samples and tests.
• QMS knows about deviations and CAPA.

But regulators and customers expect one coherent story. Integration patterns V5 supports:

• Sample triggers from MES. MES events (e.g., end of mix, start of fill, end of cure) generate structured sample requests in LIMS.
• Lot/batch metadata into LIMS. LIMS gets the correct batch/lot IDs, materials, steps and specs automatically, not by re-keying.
• Result status back to MES/WMS. Once LIMS results are approved, V5 updates lot/batch status and moves material from hold to released (or rejected), enforcing decisions.
• QMS linking investigations. Deviations, OOS/OOT investigations and CAPA reside in QMS but are linked to specific LIMS runs, MES batches and WMS lots.

This is where V5 can act as the central orchestration layer, even when a separate third-party LIMS is in place.

8) How V5 Traceability supports lab testing, LIMS integration and release

V5 Traceability is not a LIMS, but it is the system that has to use lab results to control manufacturing and inventory:

• Sampling points in V5 MES. Recipes and batch workflows in V5 MES can define sampling events and generate unique sample IDs tied to batches, process steps and materials.
• LIMS integration via V5 Connect API. The V5 Connect API allows sample IDs, test orders and results to flow between V5 and external LIMS in a controlled way.
• Lot & batch status in V5 WMS/MES. V5 updates lot and batch statuses based on lab results, locking or releasing material across MES and WMS.
• QMS for investigations & CAPA. V5 QMS handles OOS/OOT investigations, lab deviations, method changes and CAPA, all linked to the underlying data.

The aim is straightforward: ensure that “tested and released” is something the system enforces, rather than something people try to remember.

FAQ — Laboratory Testing, LIMS & Release in Regulated Manufacturing

Q1. Do we need ISO/IEC 17025 accreditation for our QC lab?
Not always. Some sectors and customers require it; others are satisfied if you follow ISO/IEC 17025 principles without formal accreditation. Either way, regulators will expect ISO/IEC 17025-like controls over competence, methods, traceability and records. Accreditation is one way to prove that maturity; it is not the only way.

Q2. What’s the difference between LIMS and ELN?
LIMS (Laboratory Information Management System) focuses on structured, routine testing: samples, tests, specs, results, approvals, reports. ELN (Electronic Laboratory Notebook) focuses on flexible, free-form experimental work (method development, research). In regulated manufacturing, LIMS is usually the primary system for QC release; ELN plays a supporting role for development and validation.

Q3. How does lab data fit into batch records and traceability?
Lab data should be linked to batches and lots through sample IDs and LIMS–MES integration. Release decisions, CoAs, OOS/OOT investigations and specification changes all rely on being able to map lab results to specific batches and lots. In V5, this means lab results influence lot status in WMS and batch closure in MES.

Q4. How can we prevent transcription errors between lab instruments, LIMS and MES?
Minimise manual re-keying. Integrate instruments with LIMS where possible; integrate LIMS with MES/WMS via APIs; use barcodes and IDs instead of free-typed text. Ensure audit trails record any edits or overrides in LIMS, and that reported results can be traced back to raw data.

Q5. What’s the minimum viable LIMS/MES integration?
At minimum: MES generates unique sample IDs with batch/lot context; LIMS receives those IDs and returns results with a clear pass/fail status per specification; MES/WMS update lot/batch status based on those results. More advanced integration can add automated sample registration, method selection, instrument data and CPV analytics.

Q6. Where should we start if our lab is mostly paper-based?
Start by mapping your critical tests, specs and sampling points. Digitise sample registration and result reporting (simple LIMS or structured spreadsheets), then integrate that with lot and batch IDs in MES/WMS. Once that basic chain is working, invest in instrument integration, ELN for method development and tighter QMS linkage for OOS/OOT and CAPA.

Related Reading (Glossary)
• Lab & Methods: ISO/IEC 17025 Testing & Calibration Labs | United States Pharmacopeia (USP) | LIMS | ELN | Test Method Validation (TMV)
• Testing & Release: Tests, Laboratory Analyses & Review | QC Testing & Release Evidence | Certificate of Analysis (CoA) | Out-of-Specification (OOS) | Out-of-Trend (OOT)
• Data Integrity & Systems: Data Integrity | Audit Trail (GxP) | MES | WMS | QMS
• V5 Platform & LIMS Integration: V5 Solution Overview | V5 MES | V5 QMS | V5 WMS | V5 Connect API