WorkflowQuality Operations & CAPA

Deviation Reporting & Classification

Deviation reporting that starts with the operator's own words at the press, holds the product before anyone classifies it, and keeps the class for a QA signature.

See one broken punch tip go from the press to a signed Major ↓
Watch with transcript →
The problem

A punch tip broke mid-run, and the missing piece could be in any drum

When something goes wrong on a GMP floor, the operator stops the press, writes a few words in the logbook and fills in a deviation form at the end of the task or the shift. The words are written for the logbook. QA phones the line for the batch, the equipment, the window at risk and what was done, and often classifies a day later from a thin record.

Meanwhile the batch can move on to coating, because containment depends on who is on shift. Two specialists give the same event different classes, and a broken tip described three ways on three presses never meets in a keyword search, so a repeat is handled as a first.

Built forQA deviation specialistsProduction operatorsShift supervisorsQA heads

The Problem Today

Operators report late and in few words, so QA chases the facts by phone while the batch moves on.

164
211.192 investigation citations on FDA drug inspections, FY2025 published

Pieced together after the shift

  • Logbook
  • Paper form
  • Phone calls
  • Keywords
  • A repeat looks like a firstEach plant searches its own records by keyword
  • One event, two classesMinor to one specialist, Major to the next

The Solution

  1. Reported in plain wordsOn the line tablet, with a logbook photo; only the missing facts are asked
  2. Held before anyone classifiesBatch on production hold, drums at risk set aside, press tagged out
  3. Repeats found by meaningThe same punch set chipped weeks earlier, and on another plant's press
  4. QA signs, a second QA checksClass, clause and reason signed; the plant's QA head countersigns a Major

Built-in controls

  • Only QA lifts a hold, with two signatures
  • The operator's words are kept exactly as written
  • Anything found outside the plant is set aside unread

What You Get

Every report reaches QA complete and contained, and each event is checked against every plant's history.

  • Operators heard at the lineReports in the operator's own language, with no form of codes
  • One press's lesson, every plantA rule learned from a QA ruling applies after the QA head's approval
  • Trending that counts alikeBatch, equipment, window and actions arrive sourced on every report
Features

Deviation reporting features, from a broken punch tip to a signed Major

An operator, a shift supervisor and QA follow one tablet press stopped mid-run, with a piece of an upper punch tip missing and the batch still on the line.

demoThe plant, its clients, people, batches, presses and records are sample data.

  1. 01Line report

    Deviation reporting in the operator's own words on the line tablet

    • Plain words, in the operator's language. The operator types what happened the way they would say it at the press, and the agent reads it instead of asking for a form of codes.
    • Each field shows its source. Equipment, batch, tooling set and last good check come from the MES, the eBR and the maintenance system, so QA knows which fact came from whom.
    • Logbook page photographed at the press. The lines the agent read are highlighted on the photo, so the record behind the window is attached before anyone asks for it.
  2. 02Missing questions

    Deviation intake that asks only what an investigator will need

    • Questions drawn from the gaps. The agent asks where the missing piece could be and what was done at once, because the plant's records already hold the rest.
    • Window at risk from the last good check. The operator's word that tooling was fine at the last check, agreed by the eBR, bounds which drums are at risk.
  3. 03Containment

    Containment first: batch hold, set-aside and tag-out proposed at once

    • The safe proposal comes first. Holding the batch, setting the drums aside and tagging the press out only make things safer, so they apply the moment the operator taps.
    • Loosening waits for QA. QA confirms the production hold as a QA hold when it reads the event, and only two QA signatures lift it.
    • Metal check after a fresh challenge test. Drums in the window and the detector's rejects go back through the detector once it passes its test pieces, so the fragment is looked for in product.
  4. 04Proposed class

    Deviation classification proposed with the SOP clause and a confidence

    • The clause and its revision cited. The proposal names the procedure, its revision and the clause, letting the specialist confirm it rests on the procedure in force.
    • What would change the answer. The classifier says which class it weighed and dropped and which fact would move it, so QA rules on the open question.
    • Routed on a one-business-day clock. The deviation opens with the triager on duty named, and the client notice the quality agreement requires is drafted for later.
  5. 05Triage workspace

    QA deviation triage with the operator's words, logbook and agents' trail

    • Words kept as written. The specialist reads what the operator said, with the agent's reading kept apart in the trail, before deciding anything.
    • Records opened before the signature. Signing stays locked while the operator's words, the logbook page or the earlier case is still unopened.
  6. 06Recurrence

    Recurring deviations found by meaning across plants, side by side

    • Alike by meaning, worded differently. A small nick on the tip edge and a broken tip meet, though no keyword links the two reports.
    • What is the same and what differs. The piece was recovered last time and is missing now, which is why the same failure can earn a different class.
  7. 07Signature

    Classification e-signature carrying its reason code and plain meaning

    • Reason code from the plant's procedure. The specialist picks the clause that decided the class, so trending later counts reasons that mean the same thing in every plant.
    • Meaning, name, time and session recorded. Each signature carries the printed name, date and time and meaning that Part 11 asks of an electronic signature.
    • A second QA person countersigns. Nobody countersigns their own ruling, and the plant's QA head countersigns a Major or a Critical.
  8. 08Learned rules

    Rules learned from QA rulings, waiting for the QA head's approval

    • Today's ruling turned into a draft rule. Today's ruling, that a broken tip with the piece not recovered is at least Major, is offered to the classifier for the next event.
    • Nothing applies before approval. Each learned rule stays parked until the QA head approves it, so one specialist's view never becomes the plant's rule alone.
  9. 09Holds in effect

    Containment board of holds, set-asides and tag-outs across plants

    • What each hold blocks. The supervisor sees that the batch cannot go to coating and the press cannot run until its tooling is inspected.
    • Release only with two QA signatures. A hold comes off with two signatures and a reason, after the deviation's product impact is assessed.

The operator applies the hold, and only two QA signatures take it off

The floor reports and holds, QA classifies and countersigns, and the QA head approves what the agents learn.

QA deviation specialists

Read each new event, classify it and assign it within one business day

  • The operator's words with the facts sourced
  • Earlier cases set side by side
  • Their own past rulings shown at the next one
Production operators

Run the press, do the in-process checks and report what went wrong

  • Plain questions instead of a form
  • Containment applied with one tap
  • Their own language at the line
Shift supervisors

Confirm containment on the floor and keep the other lines running

  • What is held and what can still run
  • Floor actions listed to confirm
  • Each hold's reason in plain words
QA heads

Countersign events classed Major or Critical; approve rules, settings and lifting holds

  • Countersignatures after the evidence is read
  • Agent-learned rules parked until approved
  • Holds lifted only on two signatures

The intake agent asks three questions, and the plant's records answer the rest

Each reads the plant's records without changing them and shows the source of what it says.

Intake agent

Reads the operator's words and the logbook photo, asks only the questions an investigator will need and fills each field with its source.

  • Changes no word the operator wrote
Containment agent

Proposes the safe immediate actions from the plant's containment rules: hold, set aside, tag out and re-check.

  • Releases nothing
  • Applies no action without a person's tap
Duplicate and planned-deviation checker

Compares the report with open reports on the same batch, equipment and window, and with approved planned deviations.

  • Closes no report as a duplicate by itself
Recurrence finder

Finds earlier events alike by meaning in every plant and shows what is the same and what differs.

  • Links no records without showing the difference
  • Raises no class on a repeat by itself
Classifier

Proposes a class, from Critical down to not a deviation, with the clause, its revision, a confidence and what would move it.

  • Sets no class
  • Counts as no signature
Router

Opens the deviation, starts the one-business-day clock, names the triager on duty and drafts the notice the client's quality agreement requires.

  • Sends no notice itself: QA sends it after the countersignature
More screens

An embossed punch tip edge broke away three times in two plants

What QA sees before and after a ruling, and what the agents did while the operator was still at the press.

Each new event on its own clockQA sees each new event with its proposed class, its containment, a repeat flag and the hours left to classify, filtered by plant, client or proposal.
The agents' run, step by stepEach agent shows its plan, the records it opened, its conclusion and the next agent it passed to, while the containment already stands.
The logbook page the agent readThe equipment logbook photo opens with the last good tooling check and the stop highlighted, so the window at risk is plain to see.
Signed, then held for the plant's QA head to countersignAfter the specialist signs, the event shows who classified it and when, and names the plant's QA head who countersigns before the class stands.
Repeats grouped by what happenedEvents found alike by meaning are grouped with what is the same and what differs, and QA adds a cluster to the investigation scope.
The trail behind the signed classEach step by a person or an agent, timed and with its reason, the plain meaning of each signature and its session; a CSV evidence file exports it all.

demoSample data, from the working solution.

Closing a report as a duplicate takes two signatures, like lifting a hold

The class of a deviationThe QA deviation specialist signs it under a reason code; a second QA person countersigns, the plant's QA head for a Major or a Critical.
Applying containmentThe operator taps to apply it and the shift supervisor confirms the floor actions; the agent only proposes.
Lifting a holdA hold comes off only with two QA signatures and a reason, and stays on while the deviation is open.
Closing a report as a duplicate or not a deviationAnything that loosens waits for two signatures; the checker only proposes.
Whether a held batch may move onThe plant's QA head decides on the held batch, and release to market belongs to the client's qualified person; the assistant names who decides and answers no release question.

The floor and quality records each report is completed from

Logbook photosThe equipment logbook page the operator photographs at the press, with the lines the agent used marked.
Manufacturing execution systemBatch, product and equipment status, and the production hold a person places.
Electronic batch recordIn-process checks that confirm when the tooling was last seen intact.
Maintenance systemTooling sets, punch replacements and inspections from the CMMS.
Quality management systemOpen deviations, approved planned deviations and earlier events in every plant.
Procedures and quality agreementsThe classification procedure in force, and what each client must be told and by when.

What QA heads ask about deviation reporting and classification

What is deviation reporting and classification?

Deviation reporting is how an operator tells QA that something went wrong, and classification is QA's decision on how serious it is. Here the operator reports in plain words at the line, agents complete the record and propose containment at once, and a QA specialist signs the class.

Does an agent classify the deviation?

No. The classifier proposes a class with the clause, its revision and a confidence. The decision and the signature belong to the QA deviation specialist, and a second QA person countersigns.

Why does containment come before the class?

Holding the batch, setting drums aside and tagging the press out only make things safer, so they apply when the operator taps. Anything that loosens a hold waits for two QA signatures.

How are repeats found when operators describe them differently?

The recurrence finder reads earlier events by meaning in every plant rather than by keyword, and sets what is the same and what differs beside the new event.

What goes on a deviation reporting form?

Here the operator fills no form of codes. They type what happened in plain words at the line tablet and photograph the logbook page. The intake agent fills equipment, batch, tooling set and last good check from the MES, the eBR and the maintenance system, shows the source of each field, and asks only what an investigator will need.

How does a CDMO's client hear about a deviation on its product?

The router drafts the notice the client's quality agreement requires for a Major or a Critical on its product, and QA sends it after the countersignature.

Send us the report that
arrived as four words.

Send a month of one line's deviation reports and logbook pages, and we will show each one completed, contained and proposed for QA.