How do I run an SQF pre-audit before the real audit?

01Direct answer

Treat the pre-audit as a gap hunt.

To run an SQF pre-audit, pick the sections that apply to your site, collect the evidence for each section, score whether the evidence is current and complete, assign owners for gaps, and verify fixes before the real audit. The goal is not to create a pretty checklist. The goal is to find weak proof while there is still time to fix it.

Small teams often wait until audit week to gather records. That is too late. A strong pre-audit tests the system early: HACCP, supplier approval, allergen control, sanitation, training, traceability, recall, document control, calibration, and corrective actions.

02Pre-audit workflow

The five steps to run.

1. 01

   Scope the audit

   Choose the code areas, site, products, lines, date range, and people involved.

2. 02

   Pull evidence

   Collect procedures, logs, supplier records, training files, sanitation records, complaints, recalls, and internal audits.

3. 03

   Score gaps

   Mark each item as ready, weak, missing, expired, or unclear.

4. 04

   Assign owners

   Give each gap a person, due date, and expected proof.

5. 05

   Verify fixes

   Review the evidence again before the auditor does.

Use the interactive version

Run an audit-readiness check in HACCPlan

Score audit areas, stage evidence, assign corrective actions, and build the inspection packet from records your team already uses.

Use the free audit-readiness quiz first, then save the real gap list in the app.

03Why it breaks

Pre-audits fail when they only ask yes or no.

A checklist that says "training records complete" is not enough. Which roles were reviewed? Which employees were missing training? Which certificates expired? Was the fix verified? The same problem happens with sanitation, suppliers, calibration, and traceability.

The useful pre-audit asks for proof, not confidence. If the proof is weak, the page should tell the team what to fix next.

04What HACCPlan does

Turn pre-audit notes into corrective work.

HACCPlan connects audit readiness with the records behind the score. That means a gap can point to the missing supplier certificate, blank temperature log, expired training record, or weak mock recall report.

1. 01

   Evidence map

   See which records support each audit area.

2. 02

   Gap scoring

   Separate ready records from missing, expired, unclear, or unreviewed evidence.

3. 03

   Corrective action

   Assign the fix and keep the verification evidence beside the gap.

4. 04

   Audit packet

   Export the first records an auditor will ask for instead of building a packet from scratch.

05Next step

Start with the records most likely to embarrass you.

Pull one supplier file, one training file, one sanitation record, one temperature log, one corrective action, and one mock recall. If those six records are clean, the system is probably close. If they are messy, the pre-audit has already paid for itself.

Find the weak proof

Create an SQF pre-audit gap list

Use HACCPlan to turn audit questions into evidence checks, owners, due dates, and verified corrective actions.

Built for practical audit prep, not just a static checklist.

06Proof

The pre-audit should leave a trail.

A useful pre-audit produces more than a score. It leaves a list of gaps, the evidence that was reviewed, the owner for each fix, the due date, and the proof that the fix was verified. That record helps the team show progress and avoid repeating the same findings.

This is where HACCPlan's audit-readiness workflow is different from a paper checklist. The gap can point to the missing record, the corrective action can stay attached to the gap, and the final audit packet can show what changed before the real audit.

07Related

Use the quiz, then stage the packet.

Try the audit readiness quiz, then use audit readiness software and the inspection binder generator.

Andrew Langevin·CFIA-licensed facility, Brantford ON· Published 2026-06-05· 8 min read· Wikidata Q139112497