Planning and Preparing for an FSMS Audit

Audits go wrong before the auditor arrives. Wrong scope, wrong team, no access to the night shift, and a plan that spends two hours on document control and twenty minutes on hazard control: each failure was decided during planning. Preparation is not administration. Preparation determines whether the audit can reach a reliable conclusion at all.

Planning work differs by audit type. Internal audits follow the organisation’s Clause 9.2 programme. Certification audits follow the certification body’s programme and scheme rules. Supplier audits follow the customer’s programme. Lead auditor responsibilities for defining objectives, scope, and criteria, selecting the team, and producing a workable plan apply in all three.

Define Objectives, Scope, and Criteria

Start by writing down three definitions and confirming them with the audit client.

• Objectives: what the audit must accomplish, for example determining conformity of the FSMS to ISO 22000, evaluating effectiveness in achieving food safety objectives, or following up previous findings.
• Scope: the extent and boundaries: sites, products, processes, shifts, outsourced processes, and any exclusions under Clause 4.3.
• Criteria: the reference set: ISO 22000 clauses, the organisation’s documented FSMS, and applicable statutory, regulatory, and customer requirements included in the system.

Ambiguity here causes disputes later. If a co-manufacturer packs product under the organisation’s label, is packing inside scope? If a new line was commissioned last month, is it included? Settle questions before travel is booked, and record answers in the audit plan.

Build the Team and the Programme Picture

Select auditors for competence and independence. Team members must collectively cover management system auditing, the food category, relevant hazards, and applicable regulation. Auditors must not audit their own work, a requirement stated explicitly for internal audits in Clause 9.2 and applied by independence principles in all audits. Declare conflicts of interest early: recent consultancy for the auditee, commercial relationships, or personal ties.

Place this audit inside its programme. Review previous audit reports, previous nonconformities and their corrective actions, complaints, withdrawals, verification trends, and changes since the last audit: new products, new equipment, new suppliers, organisational changes. Risk-based planning under ISO 19011 means those inputs decide where time goes. A site with repeated allergen incidents gets deep allergen sampling. A stable process with strong verification may need confirmation sampling rather than exhaustive review.

Document Review Before Arrival

Request documented information in advance: scope statement, food safety policy and objectives, organisational chart, process flow diagrams, hazard control plan, PRP summary, internal audit and management review records, and lists of products, sites, and shifts. Review for readiness and for audit design, not for final conformity judgements. Desk review can flag missing elements, outdated flow diagrams, or a hazard control plan that omits a process step you know exists. Each flag becomes a trail to test on site, not a finding written from the office.

Confirm logistics during preparation: access and safety induction requirements, photography rules, language and interpreter needs, guides for each area, availability of key staff including the food safety team leader, and arrangements to observe sanitation, start-up, changeover, and dispatch. Audits that miss critical operations because no one scheduled them waste the auditee’s fee and your credibility.

The Audit Plan and Opening Discipline

Produce a timed audit plan that assigns auditors to areas, processes, and clauses, sequences trails sensibly, and protects time for team consolidation, auditee feedback, and report drafting. Share the plan in advance. Build in flexibility: plans guide the day, but findings may require reallocation, and the lead auditor owns those decisions.

Checklists: Tool, Not Script

Prepare checklists from criteria and prior history to support memory and consistency. Strong checklists pose questions and evidence targets: which records, which lots, which shifts. Weak checklists invite yes-or-no answers from documents alone. Use checklists to support trails, never to replace observation and interviewing. If evidence contradicts the checklist expectation, follow evidence.

Prepare the opening meeting as part of planning: introductions, confirmation of objectives, scope and criteria, plan and timing, methods and grading, confidentiality, sampling explanation, and arrangements for communication during the audit. A disciplined opening prevents most closing-meeting disputes, because expectations were set before evidence was gathered.

End preparation with a team briefing. Align on trails, sampling sizes, note-taking standards, escalation for serious findings, and safety rules. An audit team that starts aligned stays consistent when the auditee challenges a conclusion.

Feasibility checks belong in preparation too. Confirm that the audit duration matches scope: number of sites, processes, shifts, product categories, and employees. A plan that allocates equal minutes to every clause regardless of risk signals poor preparation. Reallocate before arrival and explain changes to the client with reasons tied to previous performance, complaints, and operational complexity. Also confirm document language, record retention periods, and access to electronic systems, including read-only logins where records are digital. Auditors who discover on arrival that core records sit in a system they cannot access lose hours that technical trails needed.

Preparation ends with contingency thinking. Decide in advance how you will handle a serious finding, an absent food safety team leader, a production shutdown, or a refusal of access. Agreed escalation routes and scheme rules consulted early prevent improvised decisions under pressure on site.

Key points

• Confirm audit objectives, scope, and criteria in writing before planning sampling or travel.
• Select a competent, independent team and declare conflicts of interest early.
• Use previous results, complaints, verification trends, and changes to plan on a risk basis.
• Review key documents in advance to design on-site trails, not to pre-judge conformity.
• Issue a timed plan, prepare checklists as evidence guides, and brief the team before the opening meeting.