Validation

Computer system validation assurance for business systems

Computer system validation is where regulated programmes most often lose time late. We assess readiness and effort early and assure the validation of your ERP, LIMS, MES, eQMS and CMMS from the client side, so go live dates hold.

19 yrssenior systems delivery
7finance platforms delivered
39 daysearly on an Oracle to Dynamics migration
22m+assets in the National Grid separation

Delivered for and alongside

ShellBPCapitaBaringaOfgemSmart DCCInsightsFlui TechnologiesExxonMobilVodafoneConstellation SoftwareDeloittePwCEYNational GridElexon

The rules that apply, and what is changing

Computerised system validation rests on a small set of texts, and two of them are moving.

EU GMP Annex 11. The text in force dates from 2011 and runs to about five pages. A joint EU and PIC/S draft published on 7 July 2025 expands it to 19 pages under 17 headings, with new sections on supplier and service management, alarms, identity and access management, audit trails, periodic review, security, backup and archiving. Consultation closed on 7 October 2025; reports in October 2026 put the EMA's target for handing a final text to the Commission at the fourth quarter of 2026, with no date of application yet. A new Annex 22 on artificial intelligence and a revised Chapter 4 on documentation were consulted on alongside it.

21 CFR Part 11 governs electronic records and signatures for the US market: validation, secure time stamped audit trails, operational and authority checks, and signatures showing the signer's name, date, time and meaning.

GAMP 5 second edition, published by ISPE in July 2022, keeps the life cycle model but calls for critical thinking, treats electronic records in validated tools as evidence in place of paper deliverables, and encourages use of supplier documentation.

FDA computer software assurance guidance was finalised in September 2025 and reissued in February 2026 to match the amended Part 820 quality management system regulation. It is written for medical device production and quality system software, but its thinking is shaping practice well beyond devices.

MHRA data integrity guidance of March 2018 sets out ALCOA plus and a risk based approach to audit trail review.

For a UK manufacturer supplying Europe and the US, all five usually apply at once.

Settled texts and moving ones

EU GMP Annex 112011Text in force, about 5pages7 Jul 2025Draft: 19 pages, 17headings7 Oct 2025Consultation closedQ4 2026Final text target,reportedFDAPart 11Electronic records andsignaturesSep 2025Software assuranceguidance finalFeb 2026Reissued with amendedPart 820Industry and UKMar 2018MHRA data integrity,ALCOA plusJul 2022GAMP 5 second edition For a UK manufacturer supplying Europe and the US, all five usually apply at once.

Risk based validation in practice

Good validation starts with intended use. For each system, and each function within it, you decide whether it touches GxP data or decisions and how badly a failure could affect product quality, patient safety or data integrity. An ERP may need validating only for batch and material status, supplier approval and shelf life; a CMMS for calibration and maintenance records on GMP equipment; an MES, LIMS or eQMS for most of what it does.

From there the work follows a familiar sequence: user requirements written to be testable, a supplier assessment that looks at the vendor's quality system, development practice, release process and certifications, a risk assessment, then verification proportionate to the risk.

The traditional IQ, OQ and PQ structure still has a place, particularly for on premise infrastructure and equipment linked systems. But FDA's assurance guidance points to scripted, traceable testing for high process risk functions and lighter unscripted methods, such as scenario, exploratory or error guessing tests, for the rest. It also prefers digital evidence, such as system logs and audit trails, over screenshots. On a cloud product, the supplier's own qualification and release documentation can carry much of the load, leaving you to test your configuration, interfaces and roles.

Validation does not end at go live. Periodic review, change control, release assessment on SaaS platforms and a risk based review of audit trails keep the system in a validated state. Data migration needs its own verification, and our data migration consultancy covers the reconciliation side.

Proportionate, from intended use onwards

Intended useTestable userrequirementsSupplierassessmentRisk assessment Verificationproportionate to the risk High process risk functionsScripted, traceable testingDigital evidence, logs and audit trailsrather than screenshots Everything elseLighter unscripted methods: scenario,exploratory or error guessing testsOn cloud: lean on supplier evidence AFTER GO LIVE, TO STAY VALIDATED Periodic reviewChange controlSaaS release assessmentAudit trail review

How validation effort is estimated

Most programme plans underestimate validation because they size it as a percentage of build. We estimate it bottom up from the drivers that actually move it:

  • GxP footprint: the number of functions judged high risk once intended use is mapped, not the number of modules licensed
  • Configuration depth: standard workflows tested by the vendor need far less of your own evidence than custom forms, scripts and extensions
  • Interfaces: each GxP relevant interface needs testing at both ends, and between instruments, control systems and ERP there may be dozens
  • Migrated data: volumes of legacy records, the checks needed to prove completeness and accuracy, and whether audit trails come across
  • Supplier evidence: how complete, current and usable the vendor's validation package is
  • Release rhythm: a SaaS platform updating three or four times a year creates a recurring assessment workload for the life of the contract
  • Tooling: paper protocols or a digital validation tool, and how electronic signatures are handled

We turn that into hours, roles and calendar time, then test it against your quality unit's actual capacity, which is usually the real constraint. The output is a readiness view your steering group can act on: what is missing, what it will take and where the critical path runs. Programmes that skip this step tend to find out during test execution, when every slipped week is expensive. Our testing and go live work is built on the same estimate.

A bottom up estimate

GxP footprintConfiguration depthInterfacesMigrated dataSupplier evidenceRelease rhythmPaper or digital tool Hours, roles andcalendar time Tested against yourquality unit's capacity Readiness viewgaps and critical path Not a percentage of build. Programmes that skip this find out during test execution.
Inputs

GxP footprint, configuration depth, interfaces, migrated data, supplier evidence, release rhythm, paper or digital tool

Hours, roles and calendar time

Built from those inputs

Tested against your quality unit's capacity
Readiness view

Gaps and critical path

Not a percentage of build. Programmes that skip this find out during test execution

Assurance on the client side, not execution

We are clear about our role. We assess validation readiness and effort, review strategies, plans, requirements and supplier assessments, check that risk decisions are defensible, and assure the work as it happens. We do not write and execute formal validation protocols or sign them off; that stays with your quality unit and the specialist validation resources you or your integrator appoint. Keeping assurance separate from execution is what makes the assurance worth having.

We are independent of every software vendor and validation provider, with no referral or reseller arrangements. Our team includes consultants who have led and examined system decisions before, during and after migration and implementation, across finance, quality and operational systems. When one programme spans several of these systems at once, it helps that our team has led programmes as large as £13bn and knows how validation planning has to join up with everything else.

Part A is independent assurance alongside your team and systems integrator or vendor partner, including validation readiness reviews at each stage gate. Part B is delivery of the wider programme led by our practitioners, with formal validation still executed by your quality and validation specialists. Clients take either or both. See our LIMS, MES and eQMS selection pages, and our pricing page, where fees are shown plainly.

Assurance kept separate from execution

PEF assures Validation readiness and effortStrategies, plans and requirementsSupplier assessmentsRisk decisions are defensibleThe work, as it happens Your quality unit executes Writes the formal protocolsExecutes themSigns them offWith the validation specialistsyou or your integrator appoint

What we have delivered

22m+assets, National Grid separation

Ran the procurement of every software provider on the National Grid separation, more than 22 million assets, through to implementation including Oracle to SAP S/4HANA.

£25msaving at BP Pulse, 39 days early

Delivered the Oracle to Microsoft Dynamics migration at BP Pulse 39 days ahead of forecast, with a £25m saving, the largest on a programme where PEF held the main contract.

£9bnEnergy Bills Support Scheme

Delivered the £9bn Energy Bills Support Scheme for Ofgem, BEIS and HMRC.

19 yrsfinance systems delivery

Implemented and delivered most major finance systems over 19 years: Oracle, Microsoft Dynamics, NetSuite, Sage, SAP S/4HANA, Unit4 and Access.

ERP and CRMpre, mid and post migration

A suite of consultants who have led and analysed pre, mid and post migration decisions and implementations across ERP and CRM platforms, independent of every vendor.

Questions we are asked

What is computer system validation?

Computer system validation is documented evidence that a computerised system does what it is meant to do, consistently, for its intended use in a regulated process. It covers requirements, supplier assessment, risk assessment, testing and ongoing control through change management and periodic review. In GMP manufacturing and laboratories it applies to any system that creates, holds or decides on GxP data.

What is the difference between CSV and CSA?

Computer software assurance is FDA's risk based approach for medical device production and quality system software, finalised in September 2025. It does not replace validation; it changes how effort is spent, putting rigorous scripted testing on high process risk functions and allowing lighter unscripted testing elsewhere. GAMP 5 second edition takes a similar line, so the ideas are spreading across pharma too.

Does an ERP system need to be validated?

Only the parts used for GxP purposes, but in a regulated manufacturer those parts matter. Batch and material status, quality holds, supplier approval, shelf life and expiry, and anything feeding batch release usually fall in scope. Finance, sales and most purchasing functions usually do not. A documented intended use assessment draws the line and keeps validation effort proportionate.

What is changing in the new Annex 11?

The July 2025 draft expands Annex 11 from about five pages to 19, with detailed sections on supplier and service management, identity and access management, audit trails, alarms, electronic signatures, periodic review, security, backup and archiving. It was consulted on until October 2025 and has not yet been finalised. Firms should review supplier oversight and access control now rather than wait.

How long does computer system validation take?

It depends on the GxP footprint, configuration depth, number of interfaces, migrated data and the quality of supplier evidence, so there is no reliable rule of thumb. The bigger risk is late planning. Estimate effort bottom up during selection, confirm your quality unit's capacity, and schedule validation alongside build rather than after it.

Is your validation plan realistic?

Ask us for an independent readiness and effort review before your test phase starts, while there is still time to adjust.

Book a conversation