AI GxP validation for regulated life sciences
AI Validation

How to Write an Intended Use Statement for an AI System

Every part of validating an AI depends on one short document. What to put in an AI intended use statement, what to leave out, how it sets your GAMP category and risk, and the vague wording that causes trouble later.

Cybroscape Technologies6 min read

Key takeaway

Every part of validating an AI depends on one short document. What to put in an AI intended use statement, what to leave out, how it sets your GAMP category and risk, and the vague wording that causes trouble later.

If you only get one document right when you validate an AI system, make it this one. The intended use statement is short — often a page — but everything else hangs off it. Your risk assessment, your GAMP category, your test set, your acceptance criteria, even what the inspector asks you first. Get it vague and every document after it inherits the vagueness.

We see the same pattern a lot. A team is excited about what the AI can do, so they write down everything it could do. That's the wrong way round. An intended use statement is about what you will actually rely on it for — and, just as important, what you won't.

What goes in it

Keep it plain. Someone outside your team should understand it in two minutes.

  • The task. One sentence. "Drafts first versions of OQ test scripts from an approved requirements list." Not "supports validation" — that could mean anything.
  • The inputs. What goes in, where it comes from, what format. If it only works on your template, say so.
  • The output. What comes out and who receives it.
  • The human step. Who reviews the output, what they check, and who approves. This line matters more than any other.
  • The decision it feeds. What happens because of this output? A draft that a person rewrites is very different from a classification that goes straight into a record.
  • The limits. What it must not be used for. Out-of-scope inputs. What happens when it isn't sure.

The 'must not' section is the one people skip

Honestly, this is where most statements fall short. Teams describe the happy path and stop. But an inspector — and your own QA — will want to know where the edges are.

Write it down plainly: it does not approve anything. It does not decide GAMP category, only proposes one. It is not used on batch release decisions. It is not used on documents in languages it wasn't tested on. Each of those sentences removes a question you'd otherwise have to answer on the spot.

There's a regulatory reason too. Under the draft EU GMP Annex 22, generative and continuously learning models are not expected in critical GMP decisions — where they're used in lower-risk work, a qualified person reviewing the output is the control. Your intended use statement is where you show which side of that line you're on. (Annex 22 was still a draft at the time of writing, so check its current status.)

How it sets your risk and GAMP category

Once the intended use is clear, the risk assessment almost writes itself. Ask two questions. If the output is wrong, what's the worst realistic outcome? And would a person catch it before it mattered? A draft that a trained reviewer checks line by line is lower risk than a score nobody looks at twice. See GxP risk assessment.

GAMP category follows the same logic. An off-the-shelf AI feature you configure but don't change is usually treated like other configured software, around Category 4. A model you trained or tuned on your own data behaves much more like custom software and is usually treated as Category 5, with the extra evidence that brings. Don't argue about the category in the abstract — let the intended use and how much you've changed the model settle it.

Wording that causes trouble later

  • "Assists" or "supports". Assists how? These words hide the one thing you need to state — who decides.
  • "Reviewed as needed". Reviewed by whom, every time or sometimes? If it's sometimes, say how you choose.
  • "High accuracy". Leave numbers out of the intended use. They belong in the acceptance criteria, where you can justify them. See acceptance criteria for AI.
  • A list of future uses. If you plan to extend it later, that's a change, and it goes through change control when it happens. Don't pre-validate a wish list.

Our approach is simple: write it, then hand it to someone in QA who wasn't in the project and ask them what the AI is allowed to do. If their answer doesn't match yours, the statement isn't finished. Next step: building the test set. The wider picture is in GxP AI.

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 AI — the regulatory framework, validation expectations and platform landscape. For the detail on this specifically, see GxP AI validation.

1Bounded intended useWhat the model does, and what it must not be used for
2A frozen evaluation setHeld-out data, version-controlled, agreed before testing
3A release gate that holdsAcceptance criteria set in advance, results recorded
4A person decides what mattersConsequential calls are made and signed by a named person
5Drift monitoring in productionInputs, outputs and overrides watched, with authority to suspend
6A fallback that actually runsThe process continues with the AI switched off
Annex 22 · consultation draft
The six parts of validating an AI system for GxP use. They map onto what the EU’s draft Annex 22 asks for. Annex 22 is still a consultation draft, not yet in force.
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.

ai intended use statementurs for ai systemai validation intended usegamp category for aihow to validate an ai system
FAQ

Frequently Asked Questions

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

What is an intended use statement for an AI system?

A short plain-language document stating exactly what the AI does, what goes in and comes out, who reviews and approves the output, which decision it feeds, and what it must not be used for. Every later validation document — risk assessment, GAMP category, test set, acceptance criteria — depends on it.

What should an AI intended use statement not include?

Accuracy figures, which belong in the acceptance criteria where they can be justified; vague verbs like 'assists' or 'supports' that hide who decides; and lists of possible future uses. Extending the use later is a change and goes through change control when it happens.

What GAMP category is an AI system?

It depends on how much you change the model. An off-the-shelf AI feature you configure but do not modify is usually treated like other configured software, around Category 4. A model trained or tuned on your own data behaves more like custom software and is usually treated as Category 5. Let the intended use and the degree of modification decide.

Why does the 'must not' section matter?

Because inspectors and QA need to know the edges, not just the happy path. Stating plainly that the AI does not approve anything, does not decide classifications, and is not used on certain decisions or inputs removes questions you would otherwise answer on the spot — and shows where you sit relative to Annex 22.

How do you know an intended use statement is finished?

Give it to someone in QA who was not on the project and ask what the AI is allowed to do. If their answer matches yours, it is clear enough. If not, keep editing.

Keep reading

All articles
AI ValidationHow to Validate an AI System for GxP Use, Step by StepA practical guide to validating AI for GxP use: what regulators expect from the FDA, EU Annex 22 and GAMP, how AI validation differs from classic CSV, an eight-step method, the deliverables, and the mistakes that fail inspections. · 9 min readAI ValidationFDA's AI credibility framework: seven steps and one idea worth borrowingFDA’s 2025 draft guidance asks for a seven-step, risk-based credibility assessment of AI that supports regulatory decisions, with risk set by model influence and decision consequence. · 3 min readAI ValidationHuman-in-the-loop is not a footnote: designing HITL that actually worksQuorum, segregation of duties, escalation, override auditing: HITL patterns that hold up under inspection. · 6 min readAI ValidationHow Good Is Good Enough? Acceptance Criteria for AI in GxPSetting acceptance criteria for an AI system without picking a number out of the air: linking accuracy to the cost of an error, comparing against today's manual process, and counting the right kind of mistake. · 5 min readAI ValidationYour validation software uses AI. What do you need to validate?If your validation software uses AI, the key question is whether its output is a draft a person reviews or a decision nobody checks. Test that review is enforced, recorded and visible in the audit trail. · 3 min readAI ValidationWhen the AI Model Changes: Change Control and RevalidationA validated AI stays validated only while it stays the same. Which changes need revalidation, which do not, how to size the retest, and what to do when your vendor updates the model without asking you. · 5 min readAI ValidationWhy AI Should Draft Your Tests, Not Run ThemUsing AI for test execution in GxP is where teams get into trouble. A simpler pattern: AI drafts the steps, a person approves them, and a fixed non-AI engine runs exactly what was approved, so the evidence holds up. · 6 min readAI ValidationBuilding the Test Set: How to Validate an AI With Your Own DataYour test set decides whether an AI validation means anything. How to choose real, messy examples, agree the right answers, keep test data apart from training data, and avoid the shortcuts that make results look better than they are. · 5 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.