Food Safety

FSSC 22000 mistakes we see and how to avoid them

11/19/2026

FSSC 22000 mistakes we see and how to avoid them

You’ve mapped the processes, drafted the procedures and trained the team—yet the system still feels fragile. We see this a lot when organisations rush to meet customer timelines or lift a template off the internet. The standard isn’t the problem. It’s the way it’s put together.

Whether you’re preparing for your first audit or shoring up a re-certification, avoiding a handful of common mistakes will save time and embarrassment. If you’re aiming for FSSC 22000 certification, here’s what trips up otherwise competent sites—and how to steer clear.

Get the scope and leadership right from day one

Mistake: Fuzzy scope and passive leadership

We often arrive to find a scope that doesn’t match reality—co-packing left out, a seasonal line ignored, or outsourced cold storage conveniently forgotten. Leadership has signed the policy, but can’t explain objectives or risks. That disconnect erodes credibility with auditors and, more importantly, with your own team.

How to avoid it

  • Define scope around products, processes and sites exactly as they operate today.
  • Map outsourced processes and show how you control them contractually and operationally.
  • Set a small set of measurable objectives with owners, baselines and due dates.
  • Have top management lead a short briefing on policy, objectives and responsibilities.

A beverage co-packer I audited had excluded returns processing because “it’s not production.” Returns are a food safety risk if rework is allowed. Once included, their mass balance and rework controls made sense and the team felt clearer on expectations.

Strengthen hazard analysis and control selection

Mistake: Weak hazard analysis and CCP/OPRP confusion

Cut-and-paste HACCP plans are still surprisingly common. Teams list generic hazards and jump straight to CCPs because “that’s what customers want.” Then we find over-controlled CCPs and under-managed OPRPs, or controls chosen without validation.

How to avoid it

  • Build a product and process-specific hazard analysis using credible data and shop-floor input.
  • Use a decision tree consistently to distinguish CCPs from OPRPs and justify choices.
  • Validate control measures with evidence such as challenge tests, supplier data or literature.
  • Keep monitoring simple, trained and timely with clear reaction plans for deviations.

In a chilled ready-meals site, metal detection was treated as the only CCP while allergen cross-contact during changeovers was managed by a vague instruction to “clean thoroughly.” When swab validation and switchover timing were formalised as an OPRP, complaint rates dropped and audits were calmer.

Make PRPs real on the shop floor

Mistake: PRPs look good on paper but don’t match practice

FSSC 22000 leans heavily on prerequisite programmes aligned with ISO/TS 22002-x. Common failures are invisible to office-based planning: dirty compressed air used in direct contact, makeshift wood in maintenance jobs, glass registers not maintained, or water potability checks forgotten.

How to avoid it

  • Walk the site with the PRP list and verify each control at point of use, not at a desk.
  • Control utilities such as compressed air, steam and water with point-of-use filtration and testing.
  • Tidy up temporary fixes and enforce hygienic design standards on repairs and new equipment.
  • Trend PRP data (cleaning, glass, pest, environmental monitoring) and act on patterns.

One bakery had immaculate SOPs but used unfiltered compressed air to blow crumbs off conveyors. A cheap point-of-use sterile filter and a maintenance check sheet closed the gap. Another had glass breakage procedures, yet replacement light covers were routinely left off after service. A simple sign-off step for maintenance reduced repeat findings.

Tighten supplier approval, food fraud and defence

Mistake: File-heavy supplier approval with little risk thinking

We often see supplier lists with expired certificates, unassessed brokers and specification gaps. Food fraud (VACCP) and food defence (TACCP) risk assessments are done once with generic conclusions, then shelved.

How to avoid it

  • Risk-rank materials and services, then scale approval activities accordingly and keep evidence live.
  • Assess brokers and agents with the same rigour as manufacturers and verify traceability.
  • Make VACCP and TACCP site-specific with credible threats, controls and testing of effectiveness.
  • Build quick-check dashboards for expiries, performance and incident alerts to avoid surprises.

A herb supplier with a glowing questionnaire later failed a mass balance during an incident because the site never verified lot-level traceability. A short remote verification and a first-delivery check avoided a repeat. On TACCP, a produce packer had a generic corporate plan, yet their site’s boundary fence was easily climbed. A modest investment in lighting and CCTV, plus visitor routing, addressed the real risks.

Prove you can trace, balance and recall

Mistake: Traceability tests that stop at the paperwork

On the day, many teams can follow a lot forward and back. Fewer can demonstrate a defensible mass balance, include rework, or do it within the time the standard expects. Electronic records help, but only if data integrity is sound.

How to avoid it

  • Define traceability units clearly and link them to production, warehousing and despatch records.
  • Include rework, returns and work-in-progress in your trace and mass balance scenarios.
  • Test the full recall and withdrawal process at least annually with timed drills and after-action reviews.
  • Protect electronic records with access control, audit trails and regular back-ups.

During one audit, a sauce manufacturer achieved a 99.5% mass balance—until we asked about the two pallets of rework held off-site. They were tracked in a separate spreadsheet no one had opened for months. Integrating rework into the ERP and rehearsing a time-limited drill made their next audit straightforward.

Build competence, not just training records

Mistake: One-off induction and laminated SOPs

Training matrices look complete, yet operators cannot explain critical limits or what to do when a check fails. Supervisors rotate and assumptions take root. Verification suffers when people don’t grasp why controls matter.

How to avoid it

  • Define competence by role and assess it practically, not just with signatures and PowerPoints.
  • Coach on the job and refresh high-risk competencies more often than general hygiene.
  • Use short toolbox talks on recent issues and near misses to keep it real and relevant.
  • Cross-train key roles so holidays or illness don’t halt monitoring and verification.

At a dairy, allergen changeovers failed weekly until operators helped redesign the clean-down checklist and swab points. Empowering the team halved downtime and improved verification pass rates without buying new kit.

Audit to learn, and fix causes not symptoms

Mistake: Internal audits that tick boxes, and CARs that chase tails

Internal audits sometimes mirror certification checklists rather than process risks. Findings are raised, then closed with retraining or an update to a procedure. Weeks later, the same issues return because the cause was never understood.

How to avoid it

  • Plan audits by process and risk, then follow evidence across departments end to end.
  • Use simple root cause tools (5 Whys, fishbone) and test that the cause explains the symptom.
  • Prioritise a few high-impact actions over many low-value fixes and assign owners and dates.
  • Feed themes into management review and adjust resources rather than blame individuals.

A site struggled with out-of-calibration scales despite repeated reminders. The root cause turned out to be an awkward location and missed maintenance windows. Moving the scales and aligning calibration with planned downtime solved it, and complaints dropped.

Practical trade-offs that pay off

Implementing FSSC 22000 is as much about sensible choices as it is about compliance. Some investments save more than they cost; others can wait. A few examples we’ve seen work:

  • Spend modestly on hygienic design where cleaning is slow or inconsistent to reduce risk and labour time.
  • Consolidate documents and forms that duplicate effort, then make the survivors easy to use on the floor.
  • Automate data capture for critical checks if manual recording is error-prone or routinely late.
  • Pilot changes on one line before rolling out site-wide to prove benefit and refine training.

Be honest about constraints. If seasonal peaks limit verification, plan extra checks in quieter weeks and communicate the rationale to your auditor. If validation evidence is thin in your sector, document your reasoning and commit to strengthen it as data emerges. Auditors aren’t looking for perfection; they’re looking for control that stands up to scrutiny.

If you avoid the traps above, your FSSC 22000 system will feel calmer and more useful. The standard expects a living management system—not a binder that gathers dust. If you’d like a sounding board before your audit, or a pragmatic view on where to focus, the UKCTL team is happy to talk through options and timelines. Get in touch and let’s see what would help most.