GxP training compliance that answers the inspector's training question with cited records in minutes
An inspector's training question answered with cited records in minutes
See one case, screen by screen ↓Software that proves each person doing GMP work was trained and qualified for it. A learning system records assignments and completions; GxP Training Compliance answers the inspector's actual question by joining the batch record — who did each step, when — to the SOP revision in effect at that moment and to each person's completion date, with anyone trained late listed first.
How to choose AI solutions for life sciences →
Updated
During an inspection the question sounds simple: show me that everyone who touched this batch was trained on the SOP versions in effect when they did the work. Answering it means reading the executed batch record for who performed and verified each step, finding the procedure revision effective on each date in the document system, pulling every transcript from the learning system and every media fill, gowning and Knapp result from the qualification register. By hand that is three to four hours across four systems while the inspector waits.
The real cost is the surprise. A read-and-understand completed a day after the work, or an operator inside a media fill grace window, is often first seen when the inspector reads the transcript — and then the deviation already on file looks like an afterthought. Training gaps are cited under 21 CFR 211.25(a) and EU GMP Chapter 2.
Estimated split of the 3–4 hours one batch training request takes by hand, and with the solution. The time QA spends deciding and signing comes on top.
Six agents read the inspector's question, the batch record, each SOP revision and every training record, and list anyone trained late first; the QA lead decides each gap and signs.
Day 2 of 4 of an agency inspection at Northwind Bio, Plant 2 — Westport, where Fill Line 2 fills Veltrimab 150 mg/mL vials. At 10:31 the lead inspector asks about batch VB-26-0917. Here is what happens next, screen by screen, in the working solution.
Sam Patel, the scribe, logs Ruth Calder's request R-14 in the front room. Grace's screen asks one thing: “What did the inspector ask?” Three requests are waiting, each with its clock, and the inspection request log sits beside them with R-14 highlighted, word for word.
R-14 · Ruth Calder: “Show me that everyone who touched batch VB-26-0917 was trained on the SOP versions in effect when they did the work.”
The request reader sets the scope: batch VB-26-0917, Sep 16 – Sep 18, 2026, everyone who performed or verified a step. The batch record reader reads 24 pages — 9 steps, 8 people, names joined by employee number. The SOP version resolver finds 9 procedures and notes that SOP-MFG-0262 rev 7 took effect 9 days before. The checker runs 18 training and 8 qualification checks.
“read-only · nothing is changed in the source systems”
The evidence pack opens with what QA must see first: 24 of 26 checks passed, and two items under “Found before the inspector”. Below, everyone on the batch record, one row per person, with a chip for each SOP revision and qualification — green when completed before the work, amber inside a window, red after. Lucas Moreau's training transcript opens on the right.
Lucas Moreau, aseptic operator, capped vials at 14:20 on Sep 17. SOP-MFG-0262 rev 7, which changed the cap torque check from every 60 to every 30 minutes, took effect on Sep 8. He completed it on Sep 18 — assigned Sep 1, due Oct 8. Each statement carries a numbered citation to the batch record page, the version history and the transcript row.
Rule: “training on the revision in effect is complete before the person performs or verifies the step.”
Lena Ortiz raised DEV-2026-0398 on Sep 22 for this event; Omar Haddad closed it on Oct 2. The torque checks on the batch were done every 30 minutes as rev 7 requires and verified by Aoife Byrne, trained on rev 7 on Sep 4 — no impact on product quality. Root cause: the training due date was set 30 days after the effective date. CAPA-2026-0151 makes the batch record refuse a signature until training on the effective revision is complete.
The gap explainer proposes; it never removes a gap from the pack.
The trace links each batch step to the people who did it and the revision or qualification that applied. Ciarán Doyle entered Grade A on Sep 16; his last media fill was Mar 4, so the 6-month date was Sep 4. He was on leave for the Aug 26 run and is booked for Oct 14 — day 12 of the 30-day grace window in SOP-QA-0150 §6.2. “C. Doyle” in the batch record is matched to “Ciaran Doyle” in the learning system by employee number 40417.
The evidence matrix lists every performer and verifier by step, with the procedure or qualification, the revision in effect, the completion date and the result — “Trained before”, “Qualified”, “Grace window”. Each row opens the batch record page, the transcript, the version history or the qualification register entry it rests on.
Grace chooses “Disclose with DEV-2026-0398” for Lucas Moreau and “Confirm — inside the grace window” for Ciarán Doyle; each decision shows her name and the time. She signs with the meaning “QA approved — release to the inspector” and her password.
“You are signing R-14 — 26 checks, 2 gaps with your decision: Disclose with DEV-2026-0398 · Confirm — inside the grace window. The pack becomes read-only.”
The response letter answers the question in its first lines, discloses Lucas Moreau's late completion with DEV-2026-0398 and CAPA-2026-0151, notes Ciarán Doyle's grace window, and lists every person, step, procedure and completion date. It is signed by Grace at 10:47 and handed to Dana Okafor, the inspection host, for the front room.
“Short answer. 7 of 8 people completed training on the procedure revision in effect before the work. Lucas Moreau did not — see the disclosure below.”
R-14 is with the inspector in 17 minutes, 2 explained. R-16, on gowning rev 9, waits for a QA check with 2 to explain and its clock past target; R-15 on lyophiliser LY-02 is still with the agents. Every request from this inspection is here, as the scribe logged it.
The same request, seen by the four people who carry it — what an inspection day looked like, and what it looks like now.
Six agents read the inspector's question, the batch record, each SOP revision and every training record, and list anyone trained late first; the QA lead decides each gap and signs.
Reads the inspector's request as the scribe logged it and sets the scope — batch, equipment, procedure or person — with the dates and the people to check, by default everyone who performed or verified a step.
Reads the executed batch record or logbook and lists every step with who performed and who verified it, the time, the page and the procedure the step names.
Finds the revision of each procedure that was in effect at the moment of each step, and flags revisions that took effect within 30 days before the work.
Checks that each person completed the revision in effect before the step, and their media fill, gowning or Knapp qualification at that moment, using the rules in Settings.
For every gap, searches deviations, CAPA, leave and access records for the explanation already on file, and proposes how QA should present it: disclose with the record, confirm inside a window, or hold and investigate.
Builds the evidence pack — person × step × revision × completion date, with every source extract stamped with its print time — and a short response letter that answers the question in its first sentence.
Decides each gap and signs. The agents propose; a named person decides.
Ask in plain words about a gap, a deviation or anyone's training on a date. Every answer points to the record it rests on.
Why is Lucas Moreau a gap?
SOP-MFG-0262 rev 7 took effect on Sep 8 and changed the cap torque check from every 60 to every 30 minutes. Lucas capped batch VB-26-0917 at 14:20 on Sep 17 and completed rev 7 on Sep 18 — it was assigned Sep 1 with a due date of Oct 8. The torque checks were still done every 30 minutes, verified by Aoife Byrne, who was trained on rev 7.
What does DEV-2026-0398 say?
Raised by Lena Ortiz on Sep 22, closed Oct 2 by Omar Haddad. Impact: none on the product; torque checks were done at the rev 7 frequency. Root cause: the training due date was set 30 days after the effective date. CAPA-2026-0151: the batch record will refuse a signature until training on the effective revision is complete, live Oct 26.
Was Ciarán Doyle qualified for Grade A?
Yes, inside the grace window. His last media fill was Mar 4, so the 6-month date was Sep 4; he missed the Aug 26 run while on leave and is booked for Oct 14. SOP-QA-0150 §6.2 allows 30 days, so on Sep 16 he was on day 12 of the window. The name “C. Doyle” in the batch record was matched to “Ciaran Doyle” in the learning system by employee number 40417.
Who was trained on capping rev 7 on Sep 17?
On Sep 17, rev 7 of SOP-MFG-0262 was in effect. Trained: Aoife Byrne (Sep 4) and Tomás Reilly (Sep 3). Not yet: Lucas Moreau — completed Sep 18.
13 screens from the working solution, on its sample data. Pick one to see it large.
The check rules every pack is measured against are versioned, and every open pack re-checks when one changes. Who approves and where the records come from are set here too.
| Setting | Default | Choose from |
|---|---|---|
| Response target | 30 min | 15 to 60 min, in 5-minute steps, from the time the scribe logs the request |
| Media fill grace window | 30 days (SOP-QA-0150 §6.2) | 0 · 15 · 30 · 45 days after the 6-month media fill date |
| Include verifiers | On | On · Off — check the second person who verified a step as well as the performer |
| Match names by employee number | On | On · Off — initials joined to the learning system through the HR employee number |
| QA check | Grace Mensah | Grace Mensah · Priya Raman |
| Release to the inspector | Grace Mensah | Grace Mensah · Omar Haddad |
| A gap disclosed without a deviation | Second approval: Omar Haddad | Omar Haddad · Grace Mensah |
| Add a rule | Described in one sentence | e.g. flag training completed within 24 hours of the work — approved before it runs |
Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.
“demo” = seen in the working solution, on its sample inspection data · “target” = the design goal, measured in the live solution · “estimated” = our estimate (3–4 hours by hand per batch request) · Regulations named as context: 21 CFR 211.25(a); EU GMP Chapter 2 and Annex 1. People, companies, products, batches and records named on this page are fictional — characters and sample data in the working solution.
Software that proves each person doing GMP work was trained and qualified for it. A learning system records assignments and completions; GxP Training Compliance answers the inspector's actual question by joining the batch record — who did each step, when — to the SOP revision in effect at that moment and to each person's completion date, with anyone trained late listed first.
The SOP version resolver takes the procedure each batch step names and returns the latest revision whose effective date is on or before the step date — the effective date, never the approval date. It flags revisions that took effect within 30 days before the work and cites the version history row.
No. A check passes only when the learning system shows completion of the revision in effect on or before the step date. Assigned or overdue does not count, and an operator trained the day after the work is listed as a gap.
Yes. For Grade A/B steps the checker looks at the media fill (every 6 months, plus the grace window your procedure allows) and gowning qualification at the moment of the step; for visual inspection it checks the Knapp test. EU GMP Annex 1 expects aseptic operators to take part in media fills and be requalified periodically. The grace window is a setting.
The gap is listed first in the pack. The gap explainer searches deviations, CAPA, leave and access records for the explanation already on file and proposes how to present it. QA decides — disclose with the record, confirm inside a window, or hold and investigate — and a gap is never removed from the pack.
No. The learning system, batch record, document system, qualification register and quality system stay the records of truth and are read only; the HR system provides only employee number and name. The pack is a read-only extract in which every line opens its source entry.
Yes. The agents propose; the QA lead decides each gap and releases the pack with an electronic signature recording name, meaning and time. A gap disclosed without a deviation needs a second approval from the head of site quality, and every step and decision is in the audit trail.
The Agentic Solution Engine builds and deploys it from your requirements and documents — your training and qualification procedures, a sample of executed batch records and access to your learning, document and quality systems — and it goes live once every quality gate has passed. We will walk you through it on your own batches first.
Only the people a change touches retrain, all before it takes effect
1-min demoHR Policy Self-ServicePolicy answers for each employee's own country in seconds, clause quoted.
1-min demoEU Pay Transparency ComplianceEvery pay-information request answered within the legal deadline.
1-min demoWe'll run GxP Training Compliance on one of your own executed batch records and its training records.