IT systems · Practical guide

LabWare LIMS validation: from sample receipt to approved result

For a LabWare LIMS result, trace the correct sample, applicable test specification, unit and authorisation from registration to report. Check the configured templates, any LIMS Basic customisations and actual integration paths. The examples help laboratory teams plan implementation and change tests. They are planning aids, not test results from a LabWare installation.

Table of contents

At a glance

What does LabWare LIMS validation involve in a GMP laboratory?

Demonstrate that the configured LabWare environment supports the intended laboratory process from sample assignment through testing, result processing, access, approval and retention, including interfaces. Define the scope from the requirements and risks of your intended use. Supplier tests and templates can provide evidence once you have assessed their relevance to your configuration, master data and working practices.

  • The evidence follows a sample through the entire laboratory process.
  • Labor batch, material batch, and result release serve distinct functions.
  • Templates, custom logic, and imported results require a clear distinction.
  • A successful test transport provides no assurance regarding the professional release of a change.

1. Define product scope, operating mode, and GMP relevance

LabWare describes LIMS functions for samples, tests, results, batches, and reports. The product page also differentiates between various operating modes, including on-premises and hosted environments. Therefore, assess your actual current status: application version, modules, templates, database, operating mode, interfaces, and custom enhancements.

This guide addresses the LIMS in a GMP laboratory. An attached chromatography data system, an ELN, or a QMS is considered only in relation to the relevant data flow. For each system, it should be clearly identifiable which records are critical and who is responsible for them.

Annex 11 covers computerised systems in GMP-controlled activities. The FDA applicability of Part 11 is determined by relevant recordkeeping obligations and their electronic implementation. The use of a LabWare product name or deployment in a general testing laboratory does not automatically constitute either. The following planning shall be aligned with this specifically defined scope of use.

Sources: [1] [5] [7]

2. Pharmaceutical master formula, configuration, and proprietary logic differ

The manufacturer's page for pharmaceutical laboratories outlines Pharmaceutical Templates. In the current training program, additional modules such as LIMS Basic, Visual Workflows, LabStation, and report generation are also covered. This highlights diverse configuration options; however, it neither demonstrates their actual implementation within your environment nor provides a general validation of all associated workflows.

Prepare an overview of relevant modifications. What inputs and status changes originate from a copied template? Where have rules been altered? Where is custom logic implemented? Which calculation is performed by a report instead of during result processing? For each relevant component, the intended use, responsible party, and source version should be clearly defined.

A useful internal questioning approach is: If tomorrow a different individual takes over responsibility for sample management, can they explain why a particular sample is subjected to those specific tests and why the report displays exactly those results? If such an explanation is absent, dependencies prior to test planning must be clarified. Simply distinguishing between standard and customized testing does not establish the required justification.

Sources: [2] [3] [4]

3. Map the sample pathway to result assignment

Start with a representative sample: a raw material sample, an in-process sample, or a stability sample. Describe sample identification, material reference, origin, test instruction, and result recipient. If sub-samples or repeat analyses are generated, the relationship to the original process sample must remain clearly traceable.

LabWare identifies Sample Login, Result Entry, Lot Management, and Batch Manager as separate functions. From this, the following assignment can be derived for internal review. The terms and control objectives serve as a reference guide; specific status names or menu paths depend on your configuration.

Process objects and validation questions for your LabWare configuration
Considered relationshipOwn control questionPossible evidence
Test and inspection instruction Is identity and required testing clearly defined? Registration, order entry, and sample identification
Laboratory batch Are the results of each associated sample properly attributable? Batch Compilation and Results Comparison
Batch Which samples and test results carry their assessment? Assignment of all relevant tests
Decision on the result Are incomplete or suspicious results visible? Test status, investigation and review
Certificate of Analysis or CoA Does the released edition reflect the correct current status? Report version and underlying results

Sources: [1] [5]

4. Specify, units, and rounding deliberately test

A correctly transmitted numerical value can be misjudged if unit, specification level or comparison rule does not fit. Let the method manager determine the accuracy of the decision and how to round it. Check missing values, limit values and values just outside the permitted range.

Example: For a test, a range including the current limits of 98.0 to 102.0 percent is predefined in advance. The decision shall be based on the unrounded numerical value; the report displays one decimal place. Thus, 97.96 falls outside the range, even though the displayed value is 98.0. The values 98.0 and 102.0 lie at the inclusive boundaries; 102.04 falls outside. This is a test specification, not an analytical or regulatory standard specification.

Run the example comparison in your test configuration and compare stored value, decision, and report. Add a missing value: it must not be treated as an actual measured zero value in the example. For real methods, the professionally approved rules—including the order of rounding and limit comparison—apply. This order is not derived from the numerical example.

Sources: [2] [5]

5. Verify LabStation and other data transfers along the actual pathway

LabWare describes several integration pathways, including device connectivity, file parsing, and connections to chromatography systems. The training material for LabStation explicitly mentions the development of parsing scripts. Therefore, use the documentation of the actually implemented import pathway, rather than assuming a single, standardized interface.

A dedicated test series should at least demonstrate the assignment of sample identifier, test, value, and unit. Additionally, provide an unknown identifier, an incomplete dataset, and the same message repeated. Prior to testing, define whether and how the system rejects, flags, or requests clarification for these cases. Verify the reverse path of a corrected transmission.

A LIMS result does not automatically replace the complete source data in the originating system. For example, chromatograms, analysis method, and processing history may still be required there. Document how a reviewer can trace from the reported result to the corresponding source dataset, and ensure this linkage is preserved during archiving.

Sources: [1] [3] [6]

Further reading:

6. Example: Flow test – Sample, abnormal result and Certificate of Analysis

The following example uses a pre-defined test assignment with a completed and an open review. The review role may only approve the report after the conditions specified in the example have been met. The expected responses are inherent system requirements and do not constitute commitments regarding LabWare default settings.

Perform the procedure using analyst and reviewer accounts. Document for each step the entry, expected behavior, and actual behavior observed. A screenshot alone is rarely sufficient to later associate the activity with the specific sample and configuration state.

Own test matrix for the complete laboratory workflow
SituationPre-defined expectationsWhat is documented
Probe receives testing assignment Materials, probe, and required tests are consistent. Identifiers and the template used
Result lies outside the example limit Atypicality remains visible prior to result determination. Value, Unit, Specification and Reaction
A required test is missing The process is not confirmed as fully reviewed. Open finding and blocked or restricted follow-up step
Analyst corrects an input error Origin, change, and rationale are traceable. Old and new statement together with history
Unauthorized user attempts release The action fails according to the established rights concept. Trial, intended use, and actual response
Inspector confirms; CoA is generated Release refers to the appropriate verified results. Report, correlation of results and confirmation

Sources: [5]

7. Cleanly separate results review, history and material sharing

Define which changes to the result evaluation are relevant: for example, a different value, a changed unit, a new specification, or a revised test assignment. Have a known test case reconstructed by a second person. This will reveal whether the required history, rationale, and result context are actually accessible.

An audit trail supports this review but does not provide professional assessment of the change. The presence of a technical entry does not automatically validate whether the new value is scientifically justified. Prescribed review timelines remain critical; additional system-wide evaluations are designed according to process and risk.

In addition, you should distinguish the confirmation of a laboratory result from a change in material status and a legally regulated batch certification if necessary. A CoA or a positive laboratory status does not alone prove that all the requirements of a later batch decision are met. If the LIMS directly triggers a follow-up decision in the ERP, this is exactly the transition to the scope of the test.

Sources: [5] [6]

Further reading:

8. Utilize existing evidence and plan for internal collaboration

LabWare describes its own testing and validation services, including configured objects, business processes, and master data strategy. Request the actual documentation available for your scope of supply. Align them with your requirements: what was tested at what stage, which prerequisites apply, and which deviations remain open?

For a small and medium-sized enterprise (SME), a clear assignment of responsibilities is more important than having a large number of document titles. The laboratory provides methods and representative sample cases. The system owner maintains configuration and responsibilities. Quality Assurance (QA) determines acceptance criteria and open issues. IT and external service providers clarify operational procedures, access controls, data transfer, and recovery processes.

The effort depends particularly on variants and starting conditions: different templates, custom LIMS basic logic, parsing scripts, report calculations, multiple sites, and evolving master data. Professional judgments regarding technical and operational decisions must be established prior to implementation. Therefore, a general manufacturer estimate of implementation duration cannot serve as a reliable project assessment for your validation.

Sources: [4] [3] [5]

9. Ensure changes, migration, and archive access during operational use

Evaluate a new validation rule, a modified parser, and a software upgrade based on their actual impact. For a simple report formatting change, alternative evidence may be appropriate compared to a modified result calculation. Document the affected requirements and which previous results remain valid.

Before commencing production transfer, it must be established which configuration—including its dependencies—is authorized. Compare the target state with the verified state. For data migrations, equal row counts alone are insufficient: units, references, histories, and meanings must remain accurate and intact in the selected transfer.

Select an older process with correction and release for archival or recovery testing. Can the team reconstruct the probe, applicable specification, result, and original report from that time? Also verify the required source systems. Possessing a current LIMS backup alone does not demonstrate that all distributed records remain accessible throughout the required retention period.

Sources: [5] [6]

10. Checklist for preparation of LabWare validation

This dedicated preparation aid links the laboratory process with the technical inventory review. Open items are recorded as tasks with assigned responsibility. Only from this can a suitable inspection plan be derived.

  • Capture application, modules, operating modes, and template versions.
  • Identify GxP-related sample types and result recipients.
  • Clarify specifications, units, rounding rules, and missing values.
  • Describe laboratory batches, material batches, and their relationships.
  • Assign individual logic, LabStation parser, and report customizations.
  • Set roles, review steps, correction paths and release limits.
  • Provide representative boundary, error, and recovery cases.
  • Evaluate supplier documentation, open deviations, and own additions.

Sources: [5]

Project experience and collaboration

Check whether the approved rules support the decision on a result

With laboratory and method owners, we establish known normal, boundary and failure cases for a selected test. We trace sample assignment, units, specification, rounding and review in the configured LabWare environment. A limited configuration may need focused local evidence. Complex calculations and interfaces warrant a broader selection of cases. We connect manufacturer records with independent expected results. The approved analytical method determines the applicable comparison rule.

Frequently asked questions about LabWare LIMS

Is LabWare LIMS automatically GxP-related?

The intended use determines the assessment. A system supporting GMP tests or decisions needs to be assessed for that use. A general research laboratory or unregulated test assignment presents a different case. Describe the processes and data use before mapping requirements.

Sources: [5] [7]

Is an existing pharmaceutical template sufficient as validation evidence?

A template can provide starting points and supplier certifications. However, it does not automatically verify that your master data, modifications, and equipment transfers are valid. Compare the delivered scope against your requirements and document any changes. This identifies which additional checks remain necessary.

Sources: [2] [4] [5]

Must every basic LIMS configuration change be equally extensively tested?

No. First describe the function, dependencies, and potential consequences of failures. Formatting and calculation for a quality decision have different implications. Select the appropriate evidence accordingly and include the complete workflow. A specific technical implementation alone neither justifies a full review nor constitutes a waiver.

Sources: [3] [5]

What is the difference between laboratory batch and material batch?

LabWare describes the Batch Manager as a tool to group samples or tests for laboratory processing. In contrast, the material batch refers to the material reference evaluated within the process. Its configuration must clearly maintain these relationships. Successful completion of a laboratory group does not automatically imply that all associated material batches have had their tests fully completed.

Sources: [1]

How do we verify a LabStation import?

Use real format variants of the established data pathway and define expected mappings, units, and error handling. Supplement missing samples, missing fields, and duplicate transfers. A correctly read numeric value is insufficient if it is erroneously assigned to the wrong test. The parser version used forms part of the validation evidence.

Sources: [3] [5]

Must every manual entry be verified by a second person?

Annex 11 calls for an additional accuracy check for critical data entered manually. This may be done by a second person or through validated electronic means. Assess the possible consequences to identify critical inputs. This does not require a second-person check for every non-critical free-text field.

Sources: [5]

Does the CoA serve as a complete laboratory record?

A CoA is a result presentation for a specific purpose. The complete record may additionally include raw data, processing steps, methods, and decisions. Define where these information items are located and how they remain interconnected. Simply archiving the CoA may obscure the required relationships.

Sources: [6]

What must our team contribute before project start?

Name contacts from Laboratory, QA, and IT, as well as a system owner. Provide templates, specifications, sample tasks, interface descriptions, and existing test records. Clarify open release criteria early. Different methods, custom logic, and disorganized master data drive greater effort than a simple user count.

Sources: [4] [5]

Must the entire LIMS be revalidated during an upgrade?

Assess changes and associated usage. Specifically evaluate relevant functions, interfaces, configurations, and historical data. Document which existing evidence remains valid and which regressions are required. Neither a new version label nor an unchanged product name alone addresses this question.

Sources: [5]

Who assumes responsibility for a hosted LabWare LIMS?

The operational model alters task delegation but does not eliminate the need for clear accountability. Specifically define operations, access rights, changes, backup procedures, recovery, and data release. The service provider may deliver services; your organization must assess its own laboratory process and the use of documentation. Verify the actually agreed-upon approach.

Sources: [1] [5]

Sources and review date

The basis is the public LabWare website pages with a source date of 6 October 2026 and regulatory primary sources. Product and training documentation illustrate functional areas, but do not specify standard settings for any version. Version-specific help, delivery contents, and configuration must be obtained for the specific environment. Tables and test cases are internal recommendations; the limit values are internal test specifications and apply only to the provided examples.

  1. LabWare: LIMS – Product Functions and Operating Modes
  2. LabWare: Pharmaceutical Laboratory Software
  3. LabWare: Current training offering for LIMS Basic, LabStation, Visual Workflows, and Reporting
  4. LabWare: Testing and Validation Services
  5. European Commission: EU GMP Annex 11, January 2011 revision
  6. FDA: Data Integrity and Compliance With Drug CGMP – Questions and Answers, December 2018
  7. FDA: Part 11, Electronic Records; Electronic Signatures – Scope and Application

Sources checked: .

Daniel Herrmann, Daniel Herrmann Consulting

Daniel Herrmann Consulting

Clarify your LabWare environment's open evidence of validation

Daniel Herrmann Consulting supports you in integrating laboratory procedures, system configuration, and existing documentation to establish a justified testing requirement.

  • Computer system validation →

    Bring your GxP systems into validated operation, from laboratory software, MES and eQMS to ERP. We define the scope, plan risk-based tests using GAMP 5 and hand the evidence to QA for release.

Send a project enquiry Customer testimonials →