AI GxP validation for regulated life sciences
Test Automation

When Not to Automate a Validation Protocol

The honest counterweight to every automation pitch. Six situations where a scripted manual execution is the better answer, and how to say so in a way that survives review.

Cybroscape Technologies4 min read

Key takeaway

The honest counterweight to every automation pitch. Six situations where a scripted manual execution is the better answer, and how to say so in a way that survives review.

Every automation pitch has a slide about what to automate. The more useful slide is the other one, and it rarely gets made.

Automating the wrong protocol does not just waste the build effort. It leaves you maintaining a fragile test forever, and it tends to produce weaker evidence than the manual execution it replaced.

Six cases where manual is the better answer

  • You will run it once. A one-off migration verification, a decommissioning check. Automation pays back over repetition; with no repetition there is nothing to pay it back.
  • The test requires judgement. "The report is legible and the layout is suitable for the intended user" is a real acceptance criterion and a machine cannot assess it. Automate the numbers in the report; let a person judge the report.
  • The interface is about to change. Automating against a UI that is mid-redesign buys you a maintenance commitment and no stability.
  • Setting up the state costs more than the test. Some tests need a specific, elaborate data condition. If building that state reliably is most of the work, the automation is mostly a fixture, and fixtures rot.
  • It is a physical or environmental check. Cabling, labelling, temperature, the location of a machine. Somebody has to look.
  • The system is out of support or leaving. Effort spent automating a system you are retiring in a year is effort not spent on its replacement.

The honest arithmetic

A simple frame that survives challenge: automation is worth it when build cost plus lifetime maintenance is less than manual execution cost times the number of executions you will actually perform.

Two numbers get under-estimated in that comparison, reliably. Maintenance is the first — an automated test is code, and code needs updating whenever the system changes. The second is the number of executions, which people set optimistically at the point of maximum enthusiasm.

A practical rule of thumb: if you cannot name at least five future executions with a straight face, write it as a scripted manual protocol and move on.

Saying no in a way that survives review

The risk of declining to automate is that it reads as a shortcut. It does not have to, provided the reasoning is written down at the time rather than defended afterwards.

In the validation plan, record which protocols are automated and which are not, with a reason for each. "Executed manually; single execution expected as part of decommissioning" is a complete justification. So is "executed manually; acceptance criteria require assessment of report legibility".

What does not survive review is silence — a plan where some things happen to be automated and others happen not to be, with nothing recording why.

The middle ground people forget

It is not binary. A great deal of the value in automation comes from partial application, which the all-or-nothing framing tends to obscure:

  • Automate the setup, execute by hand. Get the system into the required state reliably, then let a person perform the test and judge the result.
  • Automate the evidence capture. A person drives; the tool records timestamps, versions and screenshots consistently. This removes the transcription errors without touching the judgement.
  • Automate the repeatable subset. Most protocols have a handful of steps that are pure assertion and a few that need a person. Split them rather than forcing the whole protocol one way.

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.

High riskFailure could affect patient safety or product quality
Scripted testingWritten steps, expected results, an independent reviewer
Step-by-step results, screenshots and signatures
Medium riskFailure is noticed and contained
Unscripted testingExploratory or ad-hoc testing against the intended use
A record of what was tested, by whom, and the result
Low riskStandard function, supplier-tested
Supplier evidenceThe vendor’s own testing, assessed and accepted
The assessment and the reason it is enough
Computer Software Assurance in one picture: test effort follows the risk of each requirement. Based on FDA’s Computer Software Assurance guidance.
See it on your own systemBring a URS or a system. We run GxP Copilot against it live on the call.
when not to automate testingmanual vs automated validationtest automation roi gxpautomation decision criteriarisk based testing

Keep reading

All articles
Document ManagementGxP Document Management: How to Choose, Validate, and Run a DMS That Survives AuditA GxP document management system controls SOPs, batch records and other regulated documents through their lifecycle, with audit trails, Part 11 signatures and controlled distribution. What it must do, how to run it in the cloud, how to share documents safely, and the findings inspectors write. · 7 min readQuality ManagementGxP Quality Management System: Architecture, Vendor Landscape, and Validation Requirements in 2026Everything a QA leader needs to select and validate a GxP QMS: the regulatory expectations, the architecture a modern QMS must support, and a scored comparison of Veeva, MasterControl, Qualio, ETQ, and Dot Compliance. · 5 min readGxP SoftwareGxP Software for Biotech Startups: What to Buy First, What Can Wait, and What to SkipThe GxP software buying guide for seed-to-Series-B biotech companies: which systems to prioritise, how to validate them without a dedicated QA team, and how to avoid the enterprise-software trap. · 5 min readGxP SoftwareGxP Software Validation Checklist: Every Step From URS to Go-Live Under GAMP 5 and CSAA step-by-step checklist for validating any GxP software system (URS, risk assessment, vendor qualification, IQ/OQ/PQ, traceability matrix, and Validation Summary Report) with CSA and GAMP 5 alignment. · 5 min readTrainingGxP Training Requirements: What Regulators Expect, How to Document It, and Where Most Teams FailThe complete guide to GxP training: regulatory basis (FDA, EMA, ICH Q10), training matrix design, SOP curriculum, competency assessment, and the documentation structure that satisfies inspectors. · 5 min readBuyer GuidesHow to Choose a Computer System Validation Platform in 2026: a Buyer's GuideA decision framework for shortlisting validation platforms: scoring matrix, weighted criteria, and the ten questions every finalist must answer. · 4 min readRegulatoryICH Q12 in practice: why uptake is slow and where it pays offICH Q12 lets companies agree established conditions with regulators and manage other changes in their own quality system. It pays off most for long-lived products with frequent changes, but needs strong, structured process data. · 3 min readRegulatoryICH Q9(R1): the four changes inspectors now use to challenge risk assessmentsICH Q9(R1), revised in 2023, targets four habits: subjective risk scores, the wrong level of formality, risk assessments that change no decisions, and ignoring product availability. · 3 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.