AI GxP validation for regulated life sciences
Validation Practice

The Most Expensive Mistake in Validation Is Made in the First Week

Over-categorising a system can double the document set and add months, and it is usually caution rather than analysis. How categorisation errors happen in both directions, and what they cost.

Cybroscape Technologies5 min read

Key takeaway

Over-categorising a system can double the document set and add months, and it is usually caution rather than analysis. How categorisation errors happen in both directions, and what they cost.

The most expensive decision in a validation project is usually made in its first week, by someone who is not certain, under no particular pressure, and without anybody reviewing it afterwards.

It is the software categorisation. Get it wrong upward and you spend months you did not need. Get it wrong downward and you produce a thin package that looks efficient until somebody reads it properly.

What the categories decide

GAMP 5 categorises software as 1 (infrastructure), 3 (non-configured products used as supplied), 4 (configured commercial products) or 5 (custom applications). Category 2 was retired and no longer exists, which still catches people working from old templates.

The category determines which deliverables apply. A Category 4 system needs a configuration specification and testing of the configuration you applied. A Category 5 system adds design specification and code review. The difference between them, across a full package, is months.

Why it goes wrong upward

Caution. Nobody is ever criticised for validating too much, and arguing for a lower category means writing a rationale you might have to defend. Writing "Category 5" requires no justification from anyone.

So a configured commercial product with a few integrations gets treated as custom development, and the project produces design specifications for software it did not design and code reviews for code it does not own. The documents are real. They demonstrate nothing, because they describe a build that never happened.

This is the single most common avoidable cost we see, and it is the cheapest to fix — it costs nothing but a defensible written rationale.

Why it goes wrong downward

Optimism, usually under schedule pressure. A heavily configured platform labelled Category 3 because "we are using it as supplied" — when fourteen workflows, a custom report set and three integrations say otherwise.

The package comes together quickly and looks efficient. Then an inspector asks why the configuration was never specified or tested, and there is no answer, because the category said it did not need to be.

This error is rarer and considerably worse. Over-categorisation wastes money; under-categorisation produces a validated state you do not actually have.

The third error: treating everything as software

An HPLC is not a GAMP category. A bioreactor is not a GAMP category. Pushing instruments and equipment through a software lifecycle produces documents that do not match what a qualification auditor expects to see.

Analytical instruments are classified by USP <1058> group and qualified accordingly. Equipment is assessed against EU GMP Annex 15 criticality, with factory and site acceptance and critical process parameters. Where an instrument has a software component — an HPLC with a chromatography data system — the software is categorised under GAMP 5 and the instrument is not.

Mixed assets are categorised by component, not forced under one label. That distinction is the one most likely to be missed by a team whose entire experience is application software.

How to decide it properly

Categorise from facts about the asset rather than from a feeling about it, write the rationale down at the time, and have someone who was not involved read it. Where a system is genuinely mixed, categorise its components separately rather than arguing about which single label is least wrong.

Then revisit it if the facts change. A categorisation that was right at intake and wrong by the time the configuration was finished is common, and the only thing worse than fixing it late is not fixing it at all.

Our GAMP 5 Second Edition consulting work frequently begins by rechecking this one decision, because it is the cheapest place to recover months. Cybroscape GxP Copilot computes the classification from confirmed facts and re-derives the document set when a fact is corrected, so the decision stays visible rather than being buried in the plan.

Where to go next

Explore Cybroscape GxP Copilot for AI-native validation, Cybroscape TraceDraft for source-traceable clinical documentation, or book a demo to see either on your own data.

Part of our guide to GxP software — categories, evaluation criteria and how the platforms compare.

Validation planReported inValidation summary report
User requirements (URS)verified byPerformance qualification (PQ)
Functional specification (FS)verified byOperational qualification (OQ)
Design specification (DS)verified byInstallation qualification (IQ)
Build and configure the system
Risk assessment at every stageTraceability matrix links each row
The V-model under GAMP 5: each specification on the left is verified by the qualification on the right, and the traceability matrix links every row. Risk assessment runs through all of it.
See it on your own systemBring a URS or a system. We run GxP Copilot against it live on the call.

Sources

Primary documents referred to on this page, from their official publishers.

gamp 5 categorisationgamp category 4 vs 5over categorisation validationgamp software category mistakesvalidation scoping error
FAQ

Frequently Asked Questions

Prefer to talk first? Chat with us on WhatsApp or book a call with an expert.

What are the GAMP 5 software categories?

Category 1 is infrastructure software, Category 3 is non-configured products used as supplied, Category 4 is commercial products configured to your process, and Category 5 is custom applications. Category 2 was retired in GAMP 5 and no longer exists, which still catches teams working from older templates.

What does over-categorisation cost?

A configured commercial product treated as a custom application can double the document set and add months, producing design specifications for software you did not design and code reviews for code you do not own. It is the most common avoidable cost in validation and the cheapest to fix — it costs nothing but a defensible written rationale.

Why is under-categorisation worse than over-categorisation?

Over-categorisation wastes money; under-categorisation produces a validated state you do not actually have. A heavily configured platform labelled Category 3 yields a package that comes together quickly and looks efficient until an inspector asks why the configuration was never specified or tested — and there is no answer.

How are instruments and equipment categorised?

Not by GAMP category. Analytical instruments are classified by USP <1058> group and qualified accordingly. Equipment is assessed against EU GMP Annex 15 criticality, including factory and site acceptance and critical process parameters. Where an instrument has a software component, the software is categorised under GAMP 5 and the instrument is not.

Keep reading

All articles
Validation PracticeValidation Debt: The Cost You Are Already CarryingValidation debt is the gap between what your documentation says a system is and what it actually is. Where it comes from, what it costs, and how to pay it down without a remediation project. · 6 min readValidation PracticeWhy Validation Projects Overrun, and Which Causes Are Actually FixableValidation projects rarely overrun because the regulatory thinking was hard. Five recurring causes, ranked by how much time they actually cost and how fixable each one is. · 6 min readValidation PracticeWhen a test step fails: handling incidents during validation executionWhen a test step fails, first classify it: system defect, script error, tester error or environment problem. Record it at the step, assess impact for real defects, and close or justify every incident before sign-off. · 3 min readAudit ReadinessThe Retrieval Drill: A 15-Minute Test of Whether You Are Actually Audit ReadyAudit readiness is a retrieval problem before it is a documentation problem. A simple unannounced drill that tells you the truth about your estate in fifteen minutes. · 5 min readTest AutomationAutomated Execution in an Inspection: The Questions You Will Be AskedInspectors are not opposed to automation. They are opposed to evidence they cannot follow. The questions that come up, and what a good answer looks like with the record open in front of you. · 4 min readTest AutomationWhen an Automated Test Fails: From Red Result to DeviationA failing automated test is the moment automation either proves itself or embarrasses you. What the run has to capture, when a failure becomes a deviation, and why a re-run that passes is not an explanation. · 4 min readAI SoftwareAutomated Validation in Life Sciences: What AI Can and Can't ReplaceAn honest assessment of validation automation: which activities AI handles well, which still require human judgment, the human-in-the-loop model, and the real ROI of automating validation work. · 8 min readTest AutomationAutomating IQ: Verifying an Installation When There Is No User InterfaceOQ and PQ automation gets all the attention because there is a screen to click. IQ is mostly files, versions, services and permissions, which is why it is still done by hand. It does not have to be. · 4 min read

Bring a system. We'll show you the package.

Book a demo, or ask a validation lead a quick question on WhatsApp.

  • We reply within one business day
  • We run your URS live on the call
  • You get a clear plan for your system
Chat on WhatsApp

Book a demo

Four fields. The right specialist replies within one business day.

Your details stay private. We never share them.