WorkflowQuality Operations & CAPA

Deviation Investigation Report Review

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 ↓
Watch with transcript →
The problem

No other batches were affected, says the report, with nothing behind it

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

The Problem Today

A sentence in an investigation report reads like a finding whether or not anyone opened the record behind it.

164
FDA inspection observations citing 211.192 in fiscal year 2025 published

Opened by hand, claim by claim

  • eBR
  • Historian
  • Change log
  • Shipments
  • Every round starts at page oneFree-text comments mean each new draft is read again in full
  • Human error closes the sectionNobody asks what the operator's screen could actually show

The Solution

  1. Each claim beside its recordBatch record, historian, work order and change record pinned in the margin
  2. Gaps left as no sourceA claim with no record keeps an empty margin and says so
  3. Asked as an inspector wouldThe challenger wants the batches that shared the equipment
  4. Numbered send-back, then re-readThe approver signs; the next draft is read only against those points

Built-in controls

  • Nobody approves a report they wrote
  • Signers open the cited records before they sign
  • Reviewer rules take effect once the QA head signs them

What You Get

Investigation reports a client or an inspector can check claim by claim, because each claim carries its record or says it has none.

  • New investigators write sound reportsEach margin and rule shows what a report must prove
  • One approver's ruling, every plantSigned rulings become rules for all plants' reports
  • Scope gaps found before an inspectorBatches the report missed are listed while it can still change
Features

Deviation investigation report features, from draft two to approval

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.

  1. 01Margin proof

    Deviation investigation report as printed, each claim's record in the margin

    • The report as the QMS prints it. The approver reviews the same pages an inspector will read, section by section, with nothing rewritten by the agents.
    • Each sentence split into claims. A sentence that holds two statements gets two checks, so a true half cannot carry a false one.
    • Agents at work, in view. Each agent's plan, sources opened and hand-off stay in view while the review runs.
  2. 02Proof

    The record passage behind a claim, opened from the margin in one click

    • The exact passage the agents pinned. The approver reads the historian line or batch record step itself, and checks whether it says what the report claims.
    • Opening counts as reading. Each open is written to the trail under the signer's name, and the approval later rests on those opens.
  3. 03No source

    Claims with nothing behind them marked no source before anyone signs

    • An empty margin says no source. The weakest line in a report stops looking like a finding the moment the approver opens it.
    • No source never means false. The agents say no record was found behind the words, and leave the judgment on the claim to a person.
    • Weak proof marked apart. A binder excluded on the supplier's certificate alone shows as weak, so the approver asks for the plant's own test.
  4. 04Rubric

    Investigation report rubric scored against the SOP and 21 CFR 211.192

    • Each line with its deciding sentence. The approver sees why a line is weak or missing and can disagree with the score on the evidence.
    • Format and content checked on substance. A heading present with nothing under it scores missing, so a report cannot pass a template check alone.
    • Past rulings recalled. When the same gap was sent back before, the run quotes that ruling, so the approver judges alike each time.
  5. 05Challenger

    Other batches and products in scope, found from the historian before QA signs

    • Questions an inspection would ask. The challenger reads the report as an FDA investigator would and asks which other batches shared the equipment.
    • Answered from the historian. Earlier batches that ran above range without an alarm are found while the report can still name them.
    • Points only a person can settle. A retest still open in the lab, or what an excursion means for a shipped batch, is handed to a named person.
  6. 06Self-check

    Challenger catches the agents' own send-back draft scoped too narrowly

    • The agents' draft challenged too. A send-back point limited to one product is caught before the approver signs it and widened to all products.
    • Corrections accepted by the approver. The approver accepts or rejects each answer, so nothing the challenger finds changes the send-back on its own.
  7. 07Send-back

    Numbered send-back points with record and reason code, signed by QA

    • Section, change, record and code. The investigator knows exactly what to rewrite and which record to use, with no comment left to interpret.
    • A primary reason code on the round. Send-backs can be counted by reason across plants, so the quality unit sees which gaps recur.
    • Signed by the approver alone. The agents draft the points; the QA investigation approver edits them and signs with a stated meaning.
  8. 08Answers

    Send-back points answered from records or in the investigator's own words

    • Each point a task with records. The investigator answers in one pass from the suggested records instead of searching five systems again.
    • Engineer's answer in fixed fields. The process engineer answers whether the screen showed the validated range, so human error is justified or withdrawn.
    • Typed answers kept apart. Words an investigator types carry a not-compared mark, and the approver reads them exactly as written.
  9. 09Re-read

    Next draft re-read only against the send-back points, rubric scored again

    • Old and new text side by side. The approver reads what changed for each point instead of reading a longer report again from its first page.
    • No line met by default. A line whose claim still stands unchanged is scored as it reads, and a missing line blocks approval.
  10. 10Approval

    QA approval of deviation investigations after each record is opened

    • Cited records opened first. Approve stays disabled until the approver has opened every record an answer cites, with tables open long enough to read.
    • Countersign when shipped batches are in scope. The SOP's countersign rule is applied from the scope itself, so the larger decisions carry a second signature.

The engineer's answer decides whether human error stays in the report

Whoever wrote the report answers each point, and someone else approves it.

QA investigation approvers

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 investigators

Write the investigation report and answer each send-back point

  • Each change named with the record to use
  • Records suggested for each point
  • Rules that show what a sound report proves
QA heads

Countersign the larger reports and approve the rules reviews apply

  • A countersign triggered by the scope itself
  • One review method across plants and clients
  • No rule in force without their signature
Process engineers

Answer the technical questions an investigation sends them

  • One plain question with fixed answer fields
  • The record to open before answering
  • An answer that reaches the report unchanged

The record finder writes no source where it found nothing, and never false

Six agents, read-only in the plant's systems, each passing its work on to the next.

Claim reader

Splits each section of the report into claims, one sentence sometimes holding two.

  • Never judges a claim
  • Never rewrites the author's words
Record finder

Looks up the record for each claim in the eBR, historian, maintenance system, QMS, ERP and LIMS, and pins the passage.

  • Never pins a record it did not open
  • Never reads no record found as false
Rubric scorer

Scores the site SOP and the regulation's lines with the sentence that decided each one, and recalls the approver's rulings.

  • Never passes a line on a heading alone
Challenger

Reads the report as an inspector would, then turns on the send-back the agents drafted.

  • Never answers or closes its own points
Send-back drafter

Writes numbered points with section, change, record and reason code, applying the approved reviewer rules.

  • Never sends or signs a send-back
Re-reader

Reads the next draft against each point, shows what changed and scores the rubric again.

  • Never approves a report
  • Never compares typed answers
More screens

The client's reviewer checks the same margin and sees no other client's batch

After the approval: the countersign, the client portal, the rules earlier send-backs produced, the queue and the trail of who read what.

A countersign the scope itself asks forShipped batches in scope call for a countersign; the QA head opens the impact assessment and both shipment records first.
The client reviews the margin under its agreementThe client's quality liaison reads the final report with each claim's record and answers with fixed codes; the plant reads any typed note before the review counts.
Past send-backs that became reviewer rulesThree earlier send-backs became rules on human error, CAPA linked to a cause and scope; a fourth, drawn from this review, is still unsigned.
Reports in review across four plants27 reports with author, class, draft round, due date and pre-read rubric; 2.4 review rounds per report this year in the sample.
The engineer's fixed-field answer sits on the trail beside the countersignWho acted, why, what each signature meant and in which session, from the engineer's fixed-field answer to the client review.

demoSample data, from the working solution.

A missing rubric line keeps Approve shut until the report goes back again

Whether a claim is trueThe agents say where a record backs a claim and where none was found; the QA investigation approver judges the claim.
Approving the investigationThe QA investigation approver alone approves, once the cited records are open, and no author approves their own report.
Countersigning the larger decisionsCritical deviations, and any report whose scope reaches a shipped batch, need the QA head's countersign.
What happens to the batches in scopeThe plant's QA decides each hold and disposition, and release to market stays with the client's QP.
Rules and looser settingsA reviewer rule, or a setting that loosens review, takes effect once the QA head has signed it.

Shipment records show which in-scope batches have already left the plant

Investigation report draftsEach draft from the QMS, laid out as printed, with its sections and page count.
Batch records and historianeBR steps, process historian traces and the alarm journal for the equipment in question.
Maintenance and change controlWork orders, seal and calibration history, and the change records behind an alarm limit.
ERP lots, holds and shipmentsWhich batches used a material lot, which are on hold and which have left the plant.
LIMS resultsRetests and certificates of analysis, including a retained-sample test the report relies on.
SOP, rulings and quality agreementsThe site's investigation SOP, the approver's past rulings and each client's review clause.

What QA approvers ask about deviation investigation report review

What is deviation investigation report review?

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.

What should a deviation investigation report contain?

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.

Must an investigation reach other batches and other products?

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.

How does the review treat human error?

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.

Can the agents approve or close an investigation?

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.

What happens when an investigator answers a point in their own words?

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.

Bring the report that
came back a third time.

Send one closed investigation report and the records it cites, and we will pin each claim or mark it no source.