A HACCP audit record checklist helps a team retrieve connected evidence and find gaps before a review. Start with one batch and follow its instruction, ingredient lots, monitoring records, exceptions and review decisions. This practical checklist supports preparation; the applicable audit program determines its complete scope and requirements.
Define the review scope
Identify the site, products, period and program being reviewed. Clarify whether the review concerns an internal procedure, customer requirement, certification scheme or regulatory program. Use the actual criteria to decide which records are needed.
Assign a record owner and retrieval location for each evidence type. Include records outside the production app, such as technical support, supplier documentation, training or instrument records, when relevant to the scope.
Choose a representative batch and an exception case. A review limited to the easiest completed run can miss the handoffs that create the most uncertainty. Include an unresolved example in your preparation exercise so the team practices documenting gaps.
Follow one batch through the evidence
| Record group | Retrieval check |
|---|---|
| Approved instructions | Correct procedure or recipe version for the run |
| Inputs | Actual ingredient-lot references, quantities and receiving evidence |
| Monitoring | Observations, relevant units, times and responsible people |
| Exceptions | Original issue, response, assessment and disposition evidence |
| Review | Defined review activity, responsible person and open questions |
| Supporting evidence | Relevant training, equipment or technical records within the scope |
Use the food manufacturing batch records guide to inspect field design and the ingredient lot traceability exercise to test input relationships. Record both a missing document and a broken link between documents: the file may exist but still be impossible to associate confidently with the selected batch.
Review exceptions without losing the original observation
Retrieve the first observation and its context before reviewing follow-up work. Identify the affected product or period as your procedure requires. Check who performed the immediate action and who made the assessment or disposition decision.
Look for unresolved questions, ambiguous acknowledgments and later observations that have been used to imply closure without an explanation. Ask whether the evidence supports the decision that was recorded. Do not silently reconstruct a missing decision during audit preparation.
The corrective action records guide provides practical prompts for this review. A complete response form can still require supporting evidence or approval elsewhere in the system.
Use an evidence-gap worksheet
| Fictional evidence item | Finding | Owner / next step |
|---|---|---|
| RUN-DEMO-31 monitoring record | Retrieved and linked to procedure version 4 | Reviewer A: retain reference |
| EX-DEMO-31 exception | Response recorded; disposition reference missing | Process owner: locate decision or document unresolved status |
| Input lot LOT-DEMO-6 | Receiving evidence retrieved | Record owner: reconcile quantity if required |
| Technical support TECH-DEMO | Applicability assessment not located | Food safety lead: assess required evidence |
These entries are fictional examples, not findings from a real facility. Keep the original records intact while investigating gaps. Add a dated follow-up and its responsible person rather than changing an incomplete historical record to make it appear complete.
Give each finding a clear next action and status. “Ask production” is less useful than “locate the referenced assessment for EX-DEMO-31 and record whether it resolves the question.” Use your own priority and escalation method.
Check retrieval and archive arrangements
Ask a reviewer to retrieve the packet using the identifier they would normally receive. Test permissions, search terms and access to supporting systems. Note any step that requires the original operator to explain an undocumented relationship.
Compare on-screen records with available exports. Check whether linked exceptions and sign-offs are included or need separate retrieval. Verify that dates, units and identifiers remain readable after export.
Apply retention and access requirements from your actual program. An exported file is not automatically a controlled archive. Identify how records are stored, backed up, retrieved and protected from inappropriate alteration.
Turn findings into implementation requirements
Use recurring retrieval problems to improve instructions, identifiers and review responsibilities. Separate missing operational evidence from missing technical support: they may need different owners and actions.
Validation versus verification helps classify those activities. If you are moving from paper, use the paper-to-digital migration guide. If you are choosing software, run the same packet through the HACCP software trial checklist.
Keep this worksheet with the applicable audit criteria. It helps organize a preparation review but does not guarantee an audit outcome or establish that every required record has been covered.