Skills

Batch records: collect the evidence during production, not the week the auditor arrives

Batch records: collect the evidence during production, not the week the auditor arrives

A pharmaceutical or medical device manufacturer keeps batch documentation across paper and spreadsheets. An audit is scheduled, and somebody spends a week assembling it. The cost is not the week. The cost is that a documentation gap created in March is discovered in September, when nothing can be done about it.

The use case

The agent assembles the documentation as production happens and flags gaps when they occur, not when the auditor is at the door. A missing signature surfaces the same day, while the person who should have signed is still in the building and still remembers the batch.

What it is worth to the business

You walk into an audit prepared. That is worth something on its own. But the real value is upstream of the audit: a gap found on the day it is created is a five minute fix, and the same gap found six months later is an investigation.

Four decisions you have to make

  1. Does the agent read only, or also write to the controlled record. This is a regulatory decision before it is a technical one, and it should be made with your QA lead in the room, not reported to them afterwards.
  2. Who signs off a gap. QA or production. Getting this wrong creates a queue that nobody clears, and a flagged gap that nobody clears is worse than no flag at all.
  3. One line or the whole plant. One line. Every time. The regulatory surface of a single line is something you can actually reason about.
  4. Who owns the tool in front of the regulator. When an inspector asks how the system works, one named person answers. Decide who before you need them.

Where to start

Read and alert only. No writes to the controlled record in phase one. That constraint is not timidity, it is what makes the project approvable, and it still delivers the entire early-detection benefit.

Technical footnote

Caution is genuinely warranted here in a way it is not in the other four use cases. Everything runs inside your environment, the controlled record stays the system of record, and the agent's output is an alert with a citation rather than an assertion. If it cannot point at the document it is reasoning from, it does not raise the flag.

Field notes from the factory floor. Five use cases drawn from the same research pass: shift handover · frontline onboarding · field crew reporting · quote turnaround · batch records.

Assembling batch documentation the week before the audit?

Book a call
← Back to the blog