Review each investigation report and approve it or send it back
- Each claim with its record, or none
- A send-back drafted as numbered points
- The next draft read against those points
Deviation investigation report review that reads each claim against the eBR, process historian and maintenance work orders, marks what has no source, and turns the gaps into numbered points the next draft must answer.
Follow one report from its margin to the countersign ↓The QA approver reads a long investigation report against the SOP from memory. A line such as no other batches were affected looks exactly like a finding, and the only way to know whether it is one is to open the historian, the batch records and the shipments by hand.
Comments go back in the margin as free text. The investigator answers some, misses others, and the next draft is read again from the first page. At a CDMO the client's own reviewer then reads the same report, as the quality agreement allows, and sends it back too while the client's batches wait.
Built forQA investigation approversDeviation investigatorsQA headsProcess engineers
A sentence in an investigation report reads like a finding whether or not anyone opened the record behind it.
Opened by hand, claim by claim
Built-in controls
Investigation reports a client or an inspector can check claim by claim, because each claim carries its record or says it has none.
A QA investigation approver reviews the second draft of a granulation investigation whose scope section says no other batches were affected.
demoAll names, batches and equipment shown are sample data, as are the CDMO and its client.
Whoever wrote the report answers each point, and someone else approves it.
Review each investigation report and approve it or send it back
Write the investigation report and answer each send-back point
Countersign the larger reports and approve the rules reviews apply
Answer the technical questions an investigation sends them
Six agents, read-only in the plant's systems, each passing its work on to the next.
Splits each section of the report into claims, one sentence sometimes holding two.
Looks up the record for each claim in the eBR, historian, maintenance system, QMS, ERP and LIMS, and pins the passage.
Scores the site SOP and the regulation's lines with the sentence that decided each one, and recalls the approver's rulings.
Reads the report as an inspector would, then turns on the send-back the agents drafted.
Writes numbered points with section, change, record and reason code, applying the approved reviewer rules.
Reads the next draft against each point, shows what changed and scores the rubric again.
After the approval: the countersign, the client portal, the rules earlier send-backs produced, the queue and the trail of who read what.
demoSample data, from the working solution.
Deviation investigation report review is the QA check of an investigation report before it is approved. Here agents pin each claim in the deviation investigation report to its record or mark it no source, score the report against the SOP, ask an inspector's questions, and draft numbered send-back points the approver signs.
A description against the validated limits, the timeline, the investigation and its root cause, the impact on every batch in scope, other batches and products considered, CAPA linked to each cause, and a conclusion the evidence supports. The rubric scores each of these on substance, with the sentence that decided it.
Yes. FDA's production record review requirement says an investigation must extend to other batches of the same drug product and other drug products that may have been associated with the failure. The challenger asks for that list first, and a scope claim with no batch list is marked missing.
EU GMP Part I expects human error to be justified only once the investigation has checked it overlooked no cause in the process, a procedure or a system. A human-error claim stays missing until the report says what the operator could see and what the system allowed.
No. They read, pin, score, challenge and draft. The QA investigation approver signs each send-back and approval, the QA head countersigns where the SOP requires, and the deviation stays open until its CAPA actions are in place.
The answer is marked not compared, and no agent judges it. The approval panel counts typed answers beside the records, so the approver reads each as written before signing.
The quality council decides on recurrences it could not see before, every sentence sourced.
1-min demoBatch Release ForecastingClient ship dates you can plan on, because what blocks each batch is chased days before it is due.
1-min demoRaw Material Release & Identity TestingA wrong or mixed-up drum is stopped at the door, with every container's result on the record.
1-min demoSend one closed investigation report and the records it cites, and we will pin each claim or mark it no source.