What this is
What is a process deviation report?
What is a process deviation report?
A process deviation report is the record of a process parameter, such as a set point, running outside its defined limits for some duration, whether or not the product made during that time turns out to be affected. It captures the parameter, the limits, how long it was out, how the deviation was detected, and what happened to the product made while it ran.
Is a report needed if the product still passed testing?
Yes. The deviation is the process running outside its intended state, which is a separate fact from whether the product it produced happened to meet specification. A parameter drifting repeatedly and being caught by downstream testing every time is exactly the pattern this record exists to surface before it stops being caught.
How is this different from a critical control point deviation?
A CCP deviation is asked about directly on this form, because a critical control point exceedance follows the HACCP corrective procedure and its own log, not the general process this record covers. Answering yes routes the case there instead of completing the rest of this record as a standard deviation.
Scope
When is a process deviation report required?
This record is one step in the Nonconformance and Complaints programme, raised the moment a process parameter runs outside its limits. Using it for product already found out of specification, rather than the process condition that produced it, produces a record that duplicates rather than complements the ones that follow it.
Use this template when
- A monitored parameter, a set point with upper and lower limits, has run outside those limits for any duration during production
- The deviation is being raised at or near the time it happened, on the line, rather than reconstructed afterward
- Product made during the excursion needs its effect assessed and, if affected, routed to a hold decision
- A downstream case, an RCA or a CAPA, needs a deviation record to link back to as its originating event
- The deviation needs to be distinguished early from a critical control point exceedance, which follows a different procedure entirely
Do not use it for
- Product Nonconformance Report, which records product already found not to meet specification, rather than a process condition
- Hold and Release Record, which places suspect product on hold and records the release, rework or scrap decision once this record has identified it
- Rework Authorization, which authorises and specifies rework on nonconforming product once a disposition decision has been made
- A critical control point exceedance, which follows the HACCP corrective procedure and its own log, not this record
- Anything outside KnowQuality, which belongs in the workspace that owns that process
Compliance mapping
Which ISO 9001 cl.8.5.1 requirements does this satisfy?
ISO 9001 clause 8.5.1 requires production to be carried out under controlled conditions, which includes monitoring and measurement against defined parameters. This record is the evidence that a departure from those conditions was caught, assessed for its effect on product, and corrected, which is what clauses 8.7 and 10.2 then require of the response.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 9001 cl.8.5.1 | Production carried out under controlled conditions, including monitoring and measurement against defined parameters | The deviation |
| ISO 9001 cl.9.1.1 | Monitoring and measurement methods determined, and results evaluated | The deviation |
| ISO 9001 cl.8.7.1 | Nonconforming outputs identified and controlled to prevent unintended use or delivery | Product effect |
| ISO 9001 cl.8.7.1(d) | Suspect output verified against requirements before release where conformity cannot otherwise be confirmed | Product effect |
| ISO 9001 cl.10.2.1(a) | React to the nonconformity, take action to control and correct it | Response |
| ISO 9001 cl.10.2.1(b)-(c) | Evaluate the need for, and implement, action to eliminate the cause | Response |
| ISO 9001 cl.7.5 | Documented information retained as evidence of the deviation, the assessment and the response | Header |
What it does not cover
- Product Nonconformance Report, which records product already found not to meet specification.
- Hold and Release Record, which records the disposition decision on product this record has flagged as affected.
- Rework Authorization, which specifies the rework once a disposition has been decided.
- The HACCP corrective procedure and CCP log, which a critical control point exceedance must follow instead of this record.
- Root Cause Analysis, which this record links to but does not itself perform, once an investigation is required.
Global
Process Deviation Report requirements by country
The duty to keep a process within its own controlled conditions is close to universal in food and regulated manufacturing. What differs is how prescriptively regulators treat a deviation that stayed within a critical control point's own tolerance versus one that did not.
FDA Preventive Controls rule, 21 CFR 117 (food); FSMA
Preventive controls must be monitored, and a deviation from a critical parameter requires documented corrective action; other process deviations are managed under the facility's own food safety plan.
A CCP deviation carries a specific regulatory expectation; a routine deviation is governed by the plan the facility itself commits to, which is what this record evidences.
Food Safety Act 1990; retained HACCP requirements under Regulation (EC) 852/2004
Food business operators must maintain HACCP-based procedures and keep documentation showing limits are monitored and deviations acted on.
Enforcement officers examining a HACCP system expect non-CCP process deviations recorded and trended, not only the critical control point log.
ISO 9001 cl.8.5.1, cl.8.7, cl.10.2; Codex Alimentarius HACCP principles
Controlled production conditions, control of nonconforming output, and corrective action are certifiable requirements; Codex sets the CCP monitoring and deviation model most HACCP plans follow.
Auditors examine this record as evidence the facility monitors its own process, not only the parameters a regulator designated critical.
How to complete it
How to complete a process deviation report, step by step
The fields that make this record useful are the ones that separate the process fact from the product fact, and the ones that force the CCP question before anything else is decided.
The record exists to catch drift before it turns into rejected product, which only works if it is completed while the parameter, the duration, and the detection method are still fresh. A deviation reconstructed at end of shift loses precisely the detail, exact duration outside limits, that trend analysis depends on.
Is This A Critical Control Point should be answered before the rest of the record is completed, because a yes routes the case to the HACCP corrective procedure and its own log rather than continuing here. Completing a full deviation record for what is actually a CCP exceedance produces two records for one event and neither one is the authoritative log.
Product Made During Deviation and Product Affected are two different questions. Product can be made during a deviation and still not be affected, and the record should carry both answers rather than collapsing them into a single pass or fail judgement about the batch.
The field help is explicit that this is set by potential outcome, not actual outcome. A deviation that produced no detectable defect this time but would have on a different product, batch or duration still warrants the level appropriate to that potential, not to a clean test result.
What auditors find
Most common process deviation report findings
Deviation findings tend to concern which record the event actually belonged in, and whether the process fact and the product fact were kept separate.
| Finding | Clause | What fixes it |
|---|---|---|
| Deviation reconstructed after the shift instead of raised at the time it happened. | ISO 9001 cl.8.5.1 | Raise the record from the line, at the point the alarm or check flags the excursion. |
| Critical control point exceedance processed as a standard deviation instead of routed to the HACCP procedure. | ISO 9001 cl.8.7.1 | Confirm the CCP question is answered first, and route a yes to the CCP log and corrective procedure. |
| Product made during the deviation not assessed for effect before it moved on or was released. | ISO 9001 cl.8.7.1(d) | Hold product made during any deviation until Product Affected and Product Tested are both completed. |
| Investigation Level set by what actually happened rather than by what the deviation could have caused. | ISO 9001 cl.10.2.1(b) | Set the level from the potential severity of the parameter and duration, before the test result is known. |
| Action Required marked yes with no CAPA ID ever entered against the case. | ISO 9001 cl.10.2.1(c) | Require a CAPA ID before the deviation can move to Closed once Action Required is yes. |
| Detection method repeatedly recorded as customer or final inspection with no escalation of the underlying monitoring. | ISO 9001 cl.9.1.1 | Trend detection method by line and parameter; a pattern of late detection is itself a finding against the monitoring, not just the process. |
Case in point
Case in point: the deviation that always tested clean
A dairy line logged eleven process deviations on cooling temperature over four months, each caught by the routine check, each showing product tested Pass, each closed with Process Corrected marked yes, immediately. Investigation Level was set to none required each time, because no batch had ever come back affected.
The twelfth excursion ran longer overnight, past the point routine checks caught it, and was found only when a customer complaint arrived weeks later. The investigation traced eleven prior deviations on the same parameter, all logged, all closed, none escalated above none required, because each had been judged by its own clean test result rather than as part of a pattern on the same line.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
4 sections
- Reference
- QUA-002
- Archetype
- Record
- Record ID
- CASE-2026-000
- Scoring
- Deviation band
- Direction
- High is bad
- Singleton
- No
- Basis
- ISO 9001 cl.8.5.1
- Links
- Feeds RCA, CAPA
- Tags
- Quality, Process
- Sections
- 4
- Fields
- 47
- Follow up fields
- 11
- Repeating sections
- 0
- Links out
- 8
Header
14 fieldsCase ID*
Auto sequence. Format CASE-2026-00000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Date and Time*
Raised By*
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Line*
Shift*
Line Lead
Batch Number*
Numeric key joining to your ERP batch record.
Links to External system reference
Product*
Production Date*
Asset
Asset ID
Format AST-0000.
Links to FDN-002 Asset ID
The deviation
10 fieldsParameter*
Temperature, time, pressure, pH, speed, concentration or weight.
Set Point*
Actual Value*
Upper Limit
Lower Limit
Duration Outside Limits*
Control Plan Reference
Links to QUA-057 Plan ID
Is This A Critical Control Point*
A CCP deviation follows the HACCP corrective procedure, not this one.
CCP Log ID
Links to QUA-048 Log ID
How It Was Detected*
- Automated alarm3 pts
- Routine check3 pts
- Operator noticed2 pts
- Found at final inspection1 pt
- Found by customer0 pts
Product effect
7 fieldsProduct Made During Deviation*
- No3 pts
- Yes0 pts
Product Affected*
- No3 pts
- Yes0 pts
Quantity Affected
Hold ID
Raise the hold record, then enter its reference.
Links to QUA-003 Hold ID
Product Location
Where the affected product physically is right now.
Product Tested*
- Yes3 pts
- Not required3 pts
- No0 pts
Test Result
Response
16 fieldsProcess Corrected*
- Yes, immediately3 pts
- Yes, delayed1 pt
- No0 pts
Time Corrected
Line Stopped*
Equipment Fault Suspected*
- No3 pts
- Yes0 pts
Work Order ID
Links to MNT-002 Work Order ID
Investigation Required*
Set by potential outcome, not by what actually happened.
- No3 pts
- Yes0 pts
Investigation Level
RCA ID
Format RCA-2026-00000.
Links to FDN-013 RCA ID
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Quality*
Signature*
Production*
Second Signature*
QUA-002 · record IDs look like CASE-2026-000 · Feeds RCA, CAPA
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The deviation itself is easy to log. What slips is the pattern across many clean-tested deviations on the same parameter, the CCP question answered on autopilot, and the CAPA that was flagged but never actually raised.
Trends deviations by line, parameter and detection method, and flags a cluster of clean-tested deviations on the same parameter before it produces a failure.
Picks up Equipment Fault Suspected and the linked work order, so a deviation traced to equipment reaches the maintenance record rather than staying a quality note.
Connects an investigation level result to the training or procedure change it implies, where the cause turns out to be method rather than machine.

Checks a CCP deviation was routed to its own log, that Action Required carries a real CAPA ID, and holds every write for approval before it touches a record.
This template lives in KnowQuality — quality and food safety. HACCP, nonconformance, traceability, laboratory and customer complaints.
Meet KnowQuality→Glossary
Process Deviation Report definitions and key terms
- Set point
- The intended value of a monitored parameter, against which the actual reading is compared to determine whether the process is in or out of limits.
- Critical control point
- A step in a HACCP plan where control is essential to prevent or eliminate a food safety hazard; a deviation here follows its own corrective procedure and log.
- Duration outside limits
- How long the parameter stayed outside its upper or lower limit, which drives both the severity assessment and the trend value of the record.
- Disposition
- The decision made about product affected by a deviation: released, held, reworked or scrapped, recorded on the Hold and Release Record this deviation feeds.
- Investigation level
- How far the response goes beyond correcting the immediate deviation, from no further action through a quick debrief to a full or cross-functional root cause analysis.
FAQ
Frequently asked questions about process deviation report
Do we need a deviation report if the product still passed?+
Yes. The deviation is a fact about the process, independent of whether the product it produced happened to meet specification. Recording it even when the product passes is what lets a pattern on the same parameter and line be seen before it stops testing clean.
What if the deviation is at a critical control point?+
Answer the CCP question first. A yes routes the case to the HACCP corrective procedure and its own log, which carries its own regulatory expectations, rather than continuing through the rest of this record as a standard process deviation.
Who completes this record?+
The operator or supervisor running the line at the time, because the record depends on detail, the exact duration outside limits, the detection method, that is only reliably available at the moment the deviation happens rather than reconstructed later.
How is Investigation Level decided?+
By the potential severity of the excursion, not by whether this particular batch tested clean. The field help is explicit that it is set by potential outcome, which is why a deviation with a clean test result can still warrant a full root cause analysis.
What is the difference between this and a Product Nonconformance Report?+
This record is about the process condition, a parameter running outside its limits; the nonconformance report is about product already found not to meet specification. A deviation can occur with no nonconformance if the product tests clean, and a nonconformance can occur without a deviation if the process ran normally and the product still failed.
Does closing the deviation close the case?+
No. Process Corrected and Line Stopped close the immediate event; a linked CAPA, an RCA, or a hold and disposition decision on affected product are separate records that may still be open once this one is complete.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Nonconformance and Complaints
Root Cause Analysis
Finds out why something happened rather than who was involved
Corrective and Preventive Action
The single action record used everywhere
Product Nonconformance Report
Records product that does not meet specification
Hold and Release Record
Places suspect product on hold and records the decision to release, rework or scrap it
Rework Authorization
Authorises rework on nonconforming product and sets out exactly what will be done
Scrap Record
Records product written off, with quantity, reason and cost
More in Nonconformance
Product Nonconformance Report
Records product that does not meet specification
Hold and Release Record
Places suspect product on hold and records the decision to release, rework or scrap it
Rework Authorization
Authorises rework on nonconforming product and sets out exactly what will be done
Scrap Record
Records product written off, with quantity, reason and cost
Concession Request
Requests permission to use or ship product that does not fully meet specification
Material Rejection Report
Rejects incoming material that fails inspection

Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 9001:2015 clause 8.5.1, Control of production and service provision
- ISO 9001:2015 clause 8.7, Control of nonconforming outputs
- ISO 9001:2015 clause 10.2, Nonconformity and corrective action
- Codex Alimentarius, General Principles of Food Hygiene and HACCP Annex
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.