HACCP corrective action records should explain the deviation, the affected product, the response and the responsible person’s decision. A note saying “fixed” is difficult to evaluate later because it leaves the reader guessing which batch was involved and whether the action addressed the problem.
Design the record so a reviewer can follow the event from the original observation to its outcome. Keep a link to the monitoring result and the production batch, rather than making the corrective action an isolated form.
Published by HACCPEasy. Sources checked October 4, 2026. Examples below are fictional and show record design; your approved food safety procedures determine the actual checks and responses.
What a corrective action record needs to explain
FDA’s HACCP principles guidance describes corrective actions in terms of addressing the cause, determining what happens to non-compliant product and documenting the action. It recommends identifying responsibility in the plan. Use that guidance alongside the rules that apply to your operation.
For facilities subject to the relevant preventive-controls provisions, 21 CFR 117.150 addresses written corrective-action procedures, evaluation of affected food and documentation. It distinguishes corrective actions from certain corrections. Those provisions are not a universal checklist for every HACCP-regulated business.
| Field | What the reviewer needs |
|---|---|
| Event identity | Unique deviation ID linked to batch and process step |
| Observation | Actual result, unit, time and equipment or method reference |
| Expected condition | Relevant limit or requirement and procedure version |
| Product scope | Lots, quantities and production interval potentially affected |
| Immediate response | What was done, when and by whom |
| Evaluation and disposition | Authorized decision about affected product, with supporting references |
| Follow-up | Investigation, recurrence-prevention action and review status |
These fields are an operational design recommendation. Your team should adapt them to the specific records required by your program, including any signatures, review deadlines and supporting evidence.
A filled example: a deviation remains unresolved
The following is a fictional example with no processing limits. It deliberately leaves the final disposition open so an incomplete decision cannot be mistaken for a release.
| Field | Illustrative entry |
|---|---|
| Deviation | DEV-DEMO-01 |
| Batch / step | B-DEMO-01 / approved process check |
| Observation | Result outside the limit in procedure P-DEMO, revision 3; original result linked |
| Scope | All product associated with B-DEMO-01 pending assessment |
| Immediate action | Operator A notified Quality Reviewer B and recorded the event time |
| Evaluation | Supporting monitoring record and equipment check requested |
| Disposition | Not yet determined by the authorized reviewer |
| Follow-up | Investigation assigned; event remains open |
The value of this record is the distinction between the operator’s response and the reviewer’s product decision. Logging a notification does not establish that product was evaluated, and a repeat reading does not by itself explain the status of the original batch.
Design the workflow around responsibility
Start with your approved response, then map it into the form. Identify who can document a deviation, who can assess the affected product and who can close the event. If these roles differ, make that difference visible to the operator.
- Keep the original observation linked to the action record.
- Ask for the affected batch and product scope before closing the event.
- Use explicit statuses such as open, under evaluation and reviewed.
- Record supporting evidence without treating an attachment as an explanation.
- Capture the reviewer’s decision separately from the operator’s initial response.
If software can restrict progression or require a second verification, configure and test that behavior. HACCPEasy’s published workflow features include If-Then rules and second-user verification. Confirm your configuration with a demonstration deviation before using it in production.
Review the record before closing it
Give the record to someone who was not present at the event. Ask them to identify the affected batch, the original observation, the response and the current product decision. Any question they cannot answer points to a field, link or explanation that needs improvement.
Also check whether the investigation produced a follow-up task with an owner. Closing the form without resolving an assigned action can leave a gap between the event record and recurrence prevention. Review both the event and the follow-up process.
For the wider production record, see food manufacturing batch records. To compare software approaches, use our FoodReady comparison.
Start your 30-day HACCPEasy trial and evaluate this workflow with demonstration data. No credit card required.
Frequently asked questions
Can a corrective action record replace the monitoring record?
Keep both connected. The monitoring record explains what was observed; the corrective action record explains the response and decision. A summary should not erase the original observation.
Should every event be marked complete immediately?
Use the status that reflects the actual work. If product evaluation or a required review is pending, the record should show that rather than imply the event is resolved.
Is this example an approved HACCP form?
No. It is an illustrative design example. Your responsible food safety team determines the fields, procedures and review requirements for your operation.