Home › Use Cases › Classify a plant's deviation reports by severity
Use caseUC0134

Classify a plant's deviation reports by severity

A deviation report is written in a hurry, in one person's own words, at the end of a shift. This app reads what actually happened and gives it the class the facts call for, not the class the wording suggests.

For the quality teamChemicals · Manufacturing & CPG · Cross-domain

Why it matters

Today's manual process, and the same job with the app

A quality team at a chemical or manufacturing plant, triaging deviation reports as they come in.

✕Today's manual process

1Read every deviation report as it comes in, in the reporter's own words.
2Judge the severity from the tone and detail of the writing, not just the facts.
3Decide the class critical, major or minor, and hope the register isn't misleading.
4One misread report means a contamination case gets treated as routine housekeeping.
Every report judged by its wording

✓With the app

1The report is read in full, the same way every time.
2The class follows the facts, not the words the reporter reached for.
3The routing is worked out investigation depth, close-out days, release hold, regulator notice.
4A person still decides, with the reasoning and the source sentence in front of them.
Every report judged by what happened

See it work

One real case: what the app found and decided

A batch that was already released, with a decisive field in the paperwork left blank.

Classify a plant's deviation reports by severityReference appBuilt to be shaped to your process
  1. 1What the app decided critical, the most serious class there is.
  2. 2Why because a released or distributed batch was affected.
  3. 3The line it read the exact sentence saying that batch had already been released.
  4. 4What the form leaves blank foreign material contact and batch status were left blank.
  5. 5What happens next Further release blocked, investigation opens, and the regulator is told within three working days.

For engineers

How it is built, and how we measured it

All fourteen steps of the build are written up, from the business case to running it in your own environment.

Kit overview →
49 of 50reports classified correctlymeasured in 06 Evals →
13 of 14critical reports correctly caughtmeasured in 06 Evals →
0 of 36non-critical reports wrongly flagged criticalmeasured in 06 Evals →
14.4¢to classify all 50 reportsmeasured in 07 Unit cost →

The build, step by step

14 steps

Make it yours

What you see is a reference app. We shape it to how you work.

Every part of it is built to change, and none of it means starting over.

Your rulesYour own thresholds for critical, major and minor, and how long each has to close.
Your recordsYour own deviation reports, batch records and specifications, in the format your site already keeps them.
Your systemsConnects to your quality system, so a class becomes a real record, not a suggestion.
Your screensThe fields and wording your quality team already uses, not a generic form.

Want this for your team?

Talk to us

We can run this on your own deviation reports, inside your own quality system, on your terms.

Talk to us →
A living map of modern AI — kept current every morning