1.0 The problem
“Notify Quality” is a placeholder, not a plan
Most reaction columns say some version of the same three words, repeated down every row. It survives document review because it looks like an answer. It fails on the floor because it leaves every real decision unmade: does the machine keep running, what happens to the parts already in the bin, who decides, how far back does suspicion extend, and what has to be true before production restarts.
The cost of that vagueness is not the nonconformance itself. It is the size of the containment two weeks later, when nobody can establish which parts were made before the condition started, and the answer becomes “everything since the last known-good check” — which, if that check was a week ago, is a large number of parts.
What a written reaction plan is actually protecting
Three things, in order: the customer, from receiving nonconforming product; the company, from an escape that becomes a corrective action and a supplier rating hit; and the operator, from having to invent a response and be second-guessed for it afterwards.
Where reaction detail lives
Not everything fits in a Control Plan cell. AiroQue can write a short, specific reaction in the plan itself, a referenced reaction sheet for characteristics that need more, or a per-defect response document for parts with a known failure history — whichever suits how your documents are used.
- Deliverable
- Written reaction plans at Control Plan row level, or as referenced reaction documentation
- Typical inputs
- Control Plan, nonconformance procedure, escalation and authority structure, shift pattern, nonconformance history
- Formats
- In-cell text, referenced reaction sheets, or a defect-based response document
- Starting price
- Quoted with Control Plan work, or standalone by scope
- Scales with
- Number of characteristics, number of distinct failure conditions, authority complexity
- Depends on
- Your nonconformance procedure and disposition authority
- Revision support
- Updated when roles, systems or escalation requirements change
2.0 Anatomy
The twelve moves a complete reaction covers
Not every characteristic needs all twelve. Every characteristic needs a deliberate decision about which apply.
Stop production
With the stop authority named. If the operator cannot stop the machine, the plan has to say who can and how fast they are reachable.
Identify affected product
Which parts, at which operations, in which containers — including product already moved to the next cell.
Segregate suspect material
Physical containment and identification, using your plant's hold tags, quarantine locations and system status.
Establish last known good
The last verified acceptable point, which is what bounds the suspect population. Frequency decisions upstream determine how expensive this step is.
Determine affected quantity
Including product downstream, in stores, at an outside processor, or already shipped — each of which has a different retrieval path.
Notify personnel
Named roles with escalation, written for every shift rather than assuming day-shift staffing.
Initiate nonconformance
Raised in your system, with the information the record actually requires captured while the evidence is still in front of someone.
Evaluate disposition
Through your established authority and any customer approval required before rework, repair or use-as-is.
Correct the process
Addressing the condition at its source, not just sorting the parts — and recording what was changed.
Verify the correction
Objective evidence that the process is back inside limits, specified as a check rather than an opinion.
Document the response
Records that satisfy your quality system and any customer notification obligation in the contract.
Resume under authorization
Restart requires a named approval. Without it, restart happens by default and nobody owns it.
3.0 Tailoring
Written for your roles, your systems, your shifts
A reaction plan that names a job title you do not have, or a system you replaced, is worse than none — it produces hesitation at exactly the wrong moment.
Specific to your building
AiroQue asks who is actually on the floor at 2am, who can authorize a stop, who dispositions, and what your nonconformance record is called. The plan is written in those terms.
Roles and authority
Uses your actual titles and the authority your quality system grants them. Where authority differs by shift, the plan states the alternate path rather than assuming someone is available.
System and form names
Your nonconformance record, hold tag, quarantine location and software are named as your people know them, so no translation is needed under pressure.
Escalation and notification
Internal escalation thresholds, and customer notification requirements where the contract imposes them — including the time limits some programs specify.
Level of detail
Concise text inside the Control Plan cell, or a referenced reaction sheet with a fuller sequence for high-severity characteristics.
Language and reading level
Written plainly for the person who will act on it, and bilingual where your workforce needs it.
Defect-based response documents
For parts with a known failure history, a response document organized by defect — what it looks like, where it is caught, what to do, who to tell — rather than by characteristic.
4.0 Adjacent services
Related work
Reaction column saying the same thing on every row?
Send the Control Plan and your nonconformance procedure. AiroQue will rewrite the reactions so they name authority, containment and verification that exist in your building.