WorkflowQuality Operations & CAPA

Deviation Impact Assessment

A deviation impact assessment that follows a suspected cause through the same equipment, shared lots, sister machines and shipped batches, with the record behind every mark.

See one deviation traced ring by ring ↓
Watch with transcript →
The problem

The binder lot in the failed batch also went into another client's tablets

Once an investigation records a suspected cause, the GMP rule is plain: the investigation reaches other batches and products the failure may be associated with, shipped or not. In most plants the impact section is still written by hand from the historian, the maintenance system, change control, lot usage and the shipment list, and it covers the batch that failed.

So a sister granulator with the same software change goes unread, a raw material lot shared with another client's product stays in use, and a released batch waits in the warehouse with its shipment booked. The client learns of the deviation from its own release review.

Built forQA deviation specialistsHeads of qualityProduction supervisorsRegulatory CMC specialists

The Problem Today

Impact checks end at the batch that failed, while sister machines, shared lots and shipped batches wait for someone to think of them.

164
FY2025 FDA citations of 211.192, unexplained discrepancies published

Read one system at a time

  • Historian
  • Maintenance
  • Lot usage
  • Shipments
  • Released batches keep shippingA batch already released leaves the warehouse while the trace waits
  • The client finds it firstIts own release review turns up the deviation before any notice

The Solution

  1. Traced outward ring by ringSame equipment, shared lots, sister machines, shipped batches and the filing
  2. Held while evidence comes inBatches that share the cause and have not left go on hold at once
  3. An inspector attacks the draftIt asks for the machine the plan left out, before anyone signs
  4. The QA head classifiesClass signed on the cited evidence, and each client notice under its clause

Built-in controls

  • A release from hold waits for the plant's QA head
  • The specialist proposes; only the QA head classifies
  • No learned rule applies until the QA head approves

What You Get

Each client hears from the plant first, with the record behind every batch, and keeps trusting the plant that told it.

  • New specialists trace like veteransThe inspector's questions run inside every trace
  • One machine's fix reaches its sistersMachines that shared a change are found by the change itself
  • Clean batches leave hold soonerEach one cleared with its record, never held just in case
Features

Deviation impact assessment features, from suspected cause to signed report

The QA deviation specialist, the QA head, QC and regulatory CMC use them to answer one question: what else does this cause touch? They follow one granulation deviation.

demoSample data throughout: the contract manufacturer, its clients and people, the batches and the numbers.

  1. 01Impact map

    Deviation impact assessment run as an impact map, ring by ring from the cause

    • Six rings planned from the root cause. Same equipment, shared lots, sister machines, batches made since, validation and stability, and the registered process are each read, so the assessment no longer ends at the failed batch.
    • Nothing marked before an agent reads it. A ring fills only when its agent has read the records, so the specialist never inherits a conclusion nobody checked.
    • Plan, sources and hand-offs in plain view. The specialist sees which record an agent read and who it passed the work to, and opens any of them before relying on a mark.
  2. 02Shared lot

    Material lot genealogy across clients, from one binder lot to its batches

    • Each batch that used the same lot. A raw material shared with another client's product is found in the same trace, before that client's batch is released.
    • Needs data, never a guess. A batch the records cannot clear stays flagged with its open request, and leftover stock of the lot is quarantined meanwhile.
  3. 03Record behind a mark

    Historian torque trace read against the validated range, batch by batch

    • The validated range from the approved report. A batch is cleared only against the range its validation report states, so the reviewer can defend each not impacted mark.
    • Excursions found where no alarm sounded. Batches that ran outside the range under a mis-set alarm limit are found by reading the trace, the way an inspector would.
  4. 04Inspector's challenge

    An inspector agent attacks the impact assessment before anyone signs it

    • The questions an inspector asks, asked first. A sister machine left out of the plan, or a root cause that cleared a material on a certificate alone, is raised in-house.
    • No agent closes its own challenge. A point is answered with a record or sent to a person, so a weak answer cannot slip into the report.
    • Why batch record review missed it. When released batches carried excursions nobody saw, the gap in review itself is named and proposed for the CAPA.
  5. 05Steered trace

    Sister equipment added mid-run so the investigation reaches other batches

    • Plain-words instructions to the running trace. The specialist adds a machine without starting over, and the plan, the counts and the log change in view.
    • Sister machines found by their shared change. A fault found on one granulator is checked on each machine that received the same configuration, in any plant.
  6. 06Holds

    Batch holds placed at once, with the shipment or order each one blocks

    • What a hold blocks, by order and shipment. Production and logistics plan around a hold the moment it lands, instead of meeting it at the dock.
    • Precautionary holds labeled as precautionary. A batch held while a retest is pending says so, with the rule that requires the retest, so nobody reads it as a finding.
  7. 07Classification

    Deviation classification against the SOP's critical, major and minor criteria

    • Each criterion beside the evidence for it. The QA head sees why a class is proposed and what would have made it critical, in the SOP's own words.
    • The triage class confirmed once scope is known. A provisional class set on one batch is confirmed or changed after the trace, with both kept on the record.
  8. 08Client notices

    Client deviation notices drafted against each quality agreement clause

    • Clause and due date quoted in each letter. A client is told within the time its own quality agreement sets, with the batches named and the evidence in hand.
    • Edited text flagged for a second reader. Words a person types into a letter are marked as not compared, so the QA head reads exactly what changed.
  9. 09Impact report

    Impact report written into the investigation, ring by ring with its records

    • Scope, rings, actions and class in one record. The investigation carries the deviation impact assessment it relied on, ready for the annual review and the next inspection.
    • Reopening clears the signatures. A changed report is signed again before export, so the file never shows a signature over different content.

Four people own one deviation's impact, and only one of them classifies

The specialist builds it, the QA head decides it, production plans around it, regulatory CMC answers for the filing.

QA deviation specialists

Write the impact section of each deviation and steer the trace

  • Each ring traced with the record behind it
  • An inspector's questions before signing
  • Holds placed while the evidence comes in
Heads of quality

Classify each deviation, release holds and sign each client notice

  • The proposed class beside the SOP's criteria
  • Each hold's reason to read once it lands
  • Past rulings offered back as rules to approve
Production supervisors

Raise the deviation and plan each shift around the holds

  • Which orders a hold blocks, and why
  • Released batches stopped before they ship
  • Equipment facts added straight into the trace
Regulatory CMC specialists

Decide whether an event departs from the client's registered process

  • The registered wording beside the event
  • A structured question sent to the client
  • Their filing assessment signed in the record

Seven agents trace, hold and draft, and none of them classifies or releases

Each agent names who gets its result next: another agent, or the person who decides.

Trace planner

Reads the deviation and the approved root cause, plans the six rings and applies the rules the QA head approved.

  • Changes no scope without logging it
Equipment history agent

Reads maintenance, calibration and configuration records, then each batch's historian trace against its validated range.

  • Clears no trace without the approved validated range
Genealogy agent

Finds each batch that used a material lot, in any client's product, and the stock left.

  • Links no lot to a batch without an ERP issue record
Batch status agent

Reads where each batch is, from in process to shipped, and places holds under the setting the QA head signed.

  • Releases no hold
  • Blocks a shipment only through a hold
Filing and validation agent

Reads the validation report, the stability protocol and the client's registered process for each batch in scope.

  • Decides no filing impact: regulatory CMC and the client do
Inspector

Attacks the draft as an inspector would, including the agents' own plan and the approved root cause.

  • Answers none of its own points
  • Closes no point itself
Notice drafter

Drafts each client notice against its quality agreement clause, and the impact report for the investigation.

  • Sends nothing: the QA head signs each notice
More screens

The queue, the requests, the client's portal and the record behind it all

Before a trace, the queue shows what waits in each plant; after it, QC, regulatory and the client answer in fields.

Deviations waiting across the plantsOpen deviations from four plants and three clients with their impact clocks; repeat events are routed to the QA head, never to bulk sign-off.
Questions with an owner and fixed answersA needs-data node becomes a request to QC, regulatory, production or the client, and only the named person can answer it.
What the client seesThe client's quality liaison sees only that client's items: the signed notice arrives here, with the request for its market status beside it.
Past rulings turned into rulesA ruling by the QA head becomes a proposed rule, such as tracing each machine a software change reached; it applies only once approved.
Who did what, and what each signature meantActions by people and agents with time, reason, signature meaning and session, exported as a file.
Settings that tighten at onceHold power, the impact clock, the trace window, bulk sampling, plants in scope and retention; loosening takes the QA head's signature.

demoSample data, from the working solution.

Four signatures on one impact assessment, and none of them an agent's

A signature carries its meaning, and nobody checks their own work.

QA deviation specialist
Sees
The impact map with each ring marked and its record
Signs
The proposed class and the impact report, as preparer
Plant QA head
Sees
The evidence behind each criterion and each hold's reason
Signs
The class, a release from hold and each client notice
QC analyst
Sees
The retained sample, the method and the question asked
Signs
The retest result that clears or confirms a material
Regulatory CMC specialist
Sees
The registered process wording beside the event
Signs
The filing assessment, with the client's answer

The calls that stay with the quality unit and the client

Classifying the deviationThe agents propose a class against the SOP; the QA head confirms it with the evidence open.
Releasing a batch from holdThe specialist requests the release with the result, and the QA head approves it after reading both.
Deciding a filing impactRegulatory CMC and the client decide whether a batch departed from the registered process.
Signing a client noticeThe notice drafter writes it against the client's quality agreement; the QA head signs it before it goes out.

What QA teams ask about deviation impact assessment

What is deviation impact assessment?

Deviation impact assessment is the part of a deviation record that says what else the event touches: other batches and products, shipped batches, validation and stability batches, and the client's registered process. Here agents trace each one and cite the record behind each mark, and the QA head classifies.

Which batches must a deviation investigation reach?

Under the GMP rule on production record review, an unexplained discrepancy is investigated whether or not the batch was distributed. The investigation extends to other batches and products associated with the failure; here that means the same equipment since its last change, shared lots, sister equipment and shipped batches.

Can the agents put a batch on hold?

Yes, and that is the only step they take on their own. Under a setting the QA head signed, a batch that shares the suspected cause and has not left goes on hold at once, and the QA head reads each reason afterwards.

How is a deviation classified as critical, major or minor?

Triage sets a provisional class on the first batch. After the trace, the agents set each criterion of the site's classification SOP beside its evidence and propose a final class. The specialist proposes it; the QA head opens the cited records, then confirms the class or returns it with a reason code.

How are clients told about a deviation at a contract manufacturer?

The notice drafter writes each notice against that client's quality agreement clause and due date, and the QA head signs it before it goes out through the client portal. The client answers structured requests in fixed fields.

Does it decide whether the registered process or a filing is affected?

No. It sets the client's registered process beside the event, such as whether a parameter is registered at all, and asks the client in fixed fields. Regulatory CMC and the client decide the filing impact.

Where does impact assessment sit in GMP deviation management?

After triage sets a provisional class and the investigation records a suspected cause, and before the final class and the CAPA. Here agents trace each ring out from that cause, and the QA head confirms the class.

Trace a deviation
you already closed.

Bring one closed deviation with its batch records, lot usage and shipments, and we will trace its impact ring by ring against them.