AI GxP validation for regulated life sciences
AI Validation

What an Audit Trail Must Record When AI Helps Make a GxP Record

Part 11 and Annex 11 audit trails record what people did. When an AI drafted the content, the trail must also show what it was given, what it produced and what the reviewer changed.

Cybroscape Technologies4 min read

Key takeaway

Part 11 and Annex 11 audit trails record what people did. When an AI drafted the content, the trail must also show what it was given, what it produced and what the reviewer changed.

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.

21 CFR Part 11 asks for secure, computer-generated, time-stamped audit trails that record who created, changed or deleted an electronic record and when, without hiding what was there before. EU GMP Annex 11 asks for a record of GMP-relevant changes and deletions, with the reason. Neither was written with AI in mind, but both apply the moment an AI helps produce a GxP record.

The difficulty is that a standard audit trail records what a person did. When an AI drafted the content and a person approved it, the trail also needs to show what the AI contributed, or nobody can reconstruct how the record came to say what it says. This is one of the controls behind GxP AI validation.

What to record for each AI-assisted step

These are our recommendations rather than a regulatory list, but each one answers a question an inspector can reasonably ask:

  • The inputs: which records and documents the AI was given, by reference and version.
  • The model and its configuration: model version, prompt version and relevant settings.
  • The output as generated: kept unchanged, before any human edit.
  • The human action: who reviewed it, what they changed, and whether they accepted, edited or rejected it.
  • The time of each step, from a trusted system clock.

Keep the AI output separate from the approved record

If the approved document simply overwrites the draft, you lose the ability to show what the reviewer changed. Keeping both lets you show that review actually happened, and it gives you the data to measure how often reviewers correct the AI, which is your early warning that its quality is slipping.

The signature still belongs to a person

An AI cannot sign. The electronic signature on an AI-assisted record is the reviewer's, with the meaning of the signature recorded as Part 11 requires. If the system lets a record be approved without a named person signing it, the audit trail is the least of the problems.

For how reviewers can sign with genuine confidence, see automation bias and how to stop rubber-stamping AI output. The draft EU GMP Annex 22 also expects records of changes to AI models and their configuration; see prompt change control.

Where to go next

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

See it on your own systemBring a URS or a system. We run GxP Copilot against it live on the call.
ai audit trail part 11audit trail ai generated recordspart 11 aiannex 11 audit trail aiai record traceability
FAQ

Frequently Asked Questions

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

Does Part 11 apply to AI-generated records?

Yes. Once an AI helps produce an electronic record used for GxP purposes, Part 11 audit trail and signature requirements apply to that record, as Annex 11 does in the EU.

What should an audit trail record for AI-assisted work?

The inputs given to the AI, the model and prompt version, the output exactly as generated, who reviewed it and what they changed, and the time of each step.

Keep reading

All articles
AI ValidationWhat Goes in an AI Validation Plan: The Sections, in OrderThe plan that decides, before testing starts, what the AI is for, how good it must be, how you will prove it and how you will keep it that way. Six sections, in the order the work happens. · 5 min readAI ValidationTesting an LLM for Hallucinations Before It Touches GxP WorkYou cannot remove the risk of a confident, unsupported sentence, so measure it. How to define a hallucination for your use, test claim by claim, set a limit in advance and keep measuring in use. · 5 min readAI ValidationPrompt Change Control: When Editing a Prompt Needs RevalidationIn an LLM tool the prompt is part of the system, yet it is often edited with no record. How to version prompts like configuration, which edits need retesting, and how to catch changes you did not make. · 4 min readAI ValidationAutomation Bias: Stopping Reviewers From Rubber-Stamping AI OutputWhen AI is usually right, people stop checking it. Why better models make this worse, how to design a review that is easy to do properly, and how to measure whether review is real. · 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 ValidationHow to Write an Intended Use Statement for an AI SystemEvery 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. · 6 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 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

Book a demo

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

Your details stay private. We never share them.