1What has to be done before go-live.
Neither EU GMP Annex 11 nor FDA’s guidance sets a duration for implementing a LIMS. They set what has to be complete before the system is used for GMP work, and so the timeline is the time that work takes. The draft revision of Annex 11, consulted on in 2025 and not yet in force, puts the end point plainly: qualification and validation “should be successfully completed and reported prior to approval and taking a system into use”.¹²
| Step | What the rules expect |
|---|---|
| Requirements | User requirements describing the system’s required functions, based on documented risk assessment and GMP impact, and traceable through its life.³ |
| Supplier | The supplier assessed, an audit if risk calls for one, and a formal agreement stating the supplier’s responsibilities.³ |
| System description | For critical systems, an up-to-date description of the physical and logical arrangements, data flows, interfaces with other systems, prerequisites and security measures.³ |
| Configuration and installation | The chosen configuration documented in a controlled specification, and correct installation and configuration verified before testing starts.¹ |
| Instrument interfaces | Built-in checks on data exchanged electronically, with interfaces assessed during validation.³⁴ |
| Data migration | Checks that migrated data are “not altered in value and/or meaning”.³ |
| Validation | Documentation covering the relevant life cycle steps, with deviations reported, and backup and restore checked.³ |
| People and procedures | Close cooperation between process owner, system owner, Qualified Persons and IT, and users with the training for their tasks.³⁵ |
| Business continuity | Documented and tested arrangements to keep critical processes running if the system breaks down.³ |
2What makes it take longer.
Scope is the first driver. FDA’s data integrity guidance treats each CGMP workflow on a computer system as an intended use to be checked through validation, so every method, specification, sample type and report the LIMS will run adds configuration to verify.⁶ A laboratory that moves release testing, stability, environmental monitoring and incoming inspection at once validates all of them before the system goes live.
Customisation is the second. For bespoke or customised systems, Annex 11 expects a process for the formal assessment and reporting of quality and performance measures at every life cycle stage, on top of what a configured product needs.³
Interfaces and history are the third. The draft Annex 11 expects critical data to move from instruments to a LIMS through validated interfaces “rather than on manual transcriptions” where possible, and migration of a whole database from a retired system to follow a validated process that considers “the constraints on the sending and receiving side”.¹ PIC/S adds that data must stay readable in their original form: where old records cannot be converted, the old software may have to be kept, for example in a virtual environment, for as long as retention requirements call for.⁴ Each instrument and each legacy data set is its own piece of work.
3What shortens it without cutting corners.
The rules allow effort to follow risk. Annex 11 bases the extent of validation on “a justified and documented risk assessment”, and the draft says the validation strategy and effort should be determined by the system’s intended use and its risks to product quality, patient safety and data integrity.³¹
FDA’s guidance on computer software assurance, final in February 2026, is written for medical device manufacturers but sets out the methods plainly. It lets a manufacturer start from the developer’s own validation work and electronic information, use unscripted testing such as scenario or exploratory testing for functions that are not high process risk, and keep system logs and audit trails as evidence rather than “paper documentation, screenshots”.⁷ ISPE’s GAMP 5 Second Edition encourages leveraging supplier documentation and supports “iterative and incremental methods”.⁸ PIC/S sets the limit: companies should not place “sole reliance on vendor qualification packages”.⁴
Phasing follows from the same principle. Validation covers the intended uses you rely on, so a laboratory can take one workflow live and add others later, each as a controlled change to the system under a defined procedure.³¹ The draft also allows conditional approval to take a system into use when some acceptance criteria are not met or deviations remain open, if a documented assessment shows no impact on product quality, patient safety or data integrity and the condition is stated in the validation report.¹
4Going live starts the next phase.
A LIMS keeps changing after go-live: new methods, instruments, specifications and vendor releases. Annex 11 expects every change to the system, including its configuration, to be made under a defined procedure, and the system to be evaluated periodically to confirm it remains in a valid state.³ PIC/S asks that periodic evaluation consider the cumulative effect of changes since the last review, at a frequency based on risk.⁴ In FDA’s worked example of a cloud system, the vendor documents each automatic update’s changes and testing, and the manufacturer assesses their effect on its intended use and tests in proportion.⁷ Plan time for that change process as well as for the first release.
5How it runs in Seal.
In Seal you can start with one release test, incoming-inspection workflow or stability study, with representative data and one connected instrument source, alongside the LIMS you already run. The 48-hour evaluation turns that workflow into a working process with a validation pack to inspect; production timing then depends on scope, interfaces, migration and your release requirements, and existing systems can keep serving the work outside that scope. See the LIMS in Seal.
The validation and AI assurance guide sets out who owns what. Seal provides the platform controls and the supplier verification and release evidence; your team owns the intended use, requirements, risk acceptance and production approval, including qualification of integrations and migrated data. After go-live, each change in Seal runs its selected acceptance tests before publication; the LabWare comparison sets that beside LabWare’s impact assessment and, in most cases, requalification after a configuration update.
References
- 1Annex 11: Computerised Systems, draft for consultation, European Commission and PIC/S, July 2025. https:/
/ picscheme. org/ docview/ 9714 (read 6 November 2026) - 2Joint stakeholders consultation on the revision of Chapter 4, Annex 11 and the new Annex 22 of the PIC/S and EU GMP Guides, PIC/S, 7 July 2025. https:/
/ picscheme. org/ en/ news/ 131/ joint- stakeholders- consultation- on- the- revision- of- chapter- 4 (read 6 November 2026) - 3EudraLex Volume 4, Annex 11: Computerised Systems, revision 1, European Commission, January 2011. https:/
/ health. ec. europa. eu/ system/ files/ 2016- 11/ annex11_ 01- 2011_ en_ 0. pdf (read 6 November 2026) - 4PI 041-1, Good Practices for Data Management and Integrity in Regulated GMP/GDP Environments, PIC/S, 1 July 2021. https:/
/ picscheme. org/ docview/ 4234 (read 6 November 2026) - 521 CFR 11.10, Controls for closed systems, eCFR. https:/
/ www. ecfr. gov/ current/ title- 21/ chapter- I/ subchapter- A/ part- 11/ subpart- B/ section- 11. 10 (read 6 November 2026) - 6Data Integrity and Compliance With Drug CGMP: Questions and Answers, Guidance for Industry, FDA, December 2018. https:/
/ www. fda. gov/ media/ 119267/ download (read 6 November 2026) - 7Computer Software Assurance for Production and Quality Management System Software, Guidance for Industry and FDA Staff, FDA, February 2026. https:/
/ www. fda. gov/ regulatory- information/ search- fda- guidance- documents/ computer- software- assurance- production- and- quality- management- system- software (read 6 November 2026) - 8GAMP 5 Guide, 2nd Edition: A Risk-Based Approach to Compliant GxP Computerized Systems, ISPE, July 2022. https:/
/ ispe. org/ publications/ guidance- documents/ gamp- 5- guide- 2nd- edition (read 6 November 2026)
AQuestions and answers
Can a LIMS go live in phases?
Yes. Validation covers the intended uses you rely on, so you can take one workflow live, such as release testing for one product, and add others later. Each addition is a change to the system, made under change control and validated in proportion to its risk.
Do we have to migrate all our historical laboratory data?
Not necessarily, but the records must stay available and readable for their full retention period. If you migrate them, the migration is validated and checked for changes in value or meaning. If you leave them behind, the old system or an archive has to keep them retrievable, sometimes by keeping the old software running.
Who needs to be involved in a LIMS implementation?
EU GMP Annex 11 expects close cooperation between the process owner, the system owner, Qualified Persons and IT, with each person qualified for their role. The draft revision lists the process owner, system owner, users, subject matter experts, QA, QP, the internal IT department, vendors and service providers.
Does a cloud or SaaS LIMS take less time to validate?
It can, because the supplier runs the infrastructure and can supply evidence you may reuse after assessing it. You still own the requirements, configuration, interfaces, migrated data and the decision to go live, and each vendor release needs assessing for its effect on your intended use.
Does a LIMS have to be fully validated before anyone uses it?
Before it is used for GMP work, yes. The draft revision of Annex 11 says validation should be completed and reported before a system is taken into use, and allows conditional approval only with a documented assessment that open points will not affect product quality, patient safety or data integrity. Configuration, training and testing can run earlier, outside GMP use.