What Documents Do You Need for IFS/BRCGS Food Safety Certification?

If you're a food manufacturer preparing for your first IFS or BRCGS audit — or renewing an existing certification — the sheer volume of required documentation can feel overwhelming. Auditors aren't just checking that food is made safely; they're checking that you can prove it, consistently, with paper trails going back months.

Here's a breakdown of what auditors actually expect to see, organized by category.

The Foundation: Your Food Safety & Quality Manual

This is the master document that ties everything else together — your food safety policy, scope, organizational structure, and a map of every other document in your system. Auditors typically start here to understand how your system is organized before diving into specifics.

The Core: Your HACCP Plan

This is the document auditors scrutinize most closely, and for good reason — it's supposed to represent your actual, site-specific hazard analysis, not a generic template. It needs to show your real process flow, a genuine hazard analysis at every step, clearly justified Critical Control Points, monitoring procedures with defined critical limits, and — critically — validation evidence showing your critical limits are scientifically sound, not just assumed.

The Prerequisite Programs

These are the standard operating procedures covering everything that supports food safety outside the HACCP plan itself:

• Supplier Approval & Raw Material Control — how you vet and monitor suppliers
• Allergen Management — your allergen matrix and cross-contact controls
• Foreign Body Control — glass/hard plastic registers, metal detection verification
• Pest Control — your contracted program and inspection records
• Cleaning & Sanitation — schedules, verification, and allergen changeover procedures
• Personal Hygiene — staff facilities, handwashing, fitness-to-work policy
• Traceability & Recall — batch coding and your ability to trace product quickly

Auditors don't just want to see these procedures exist on paper — they want to see records proving they're actually followed, week after week, not just written the month before the audit.

The System-Level Documents

Beyond day-to-day operations, auditors also check that you're managing the system itself: an internal audit program that actually covers your whole operation over a cycle, a corrective action process that addresses root causes rather than just symptoms, a training program with real competency evidence (not just attendance sheets), and calibration records for anything measuring a Critical Control Point.

The Records That Prove It's Real

This is where many businesses stumble — not because their procedures are wrong, but because their records don't demonstrate a genuine operating history. Auditors are trained to spot documentation created the week before an audit versus records that show consistent, months-long operation. Starting your record-keeping early, well before your audit date, matters as much as the procedures themselves.

A Word of Caution

None of this is a substitute for a real HACCP team and, ideally, a qualified food safety consultant reviewing your finalized system before your audit. IFS and BRCGS are proprietary, version-specific standards (the current versions being IFS Food v8 and BRCGS Food Safety Issue 9 at time of writing) — always verify your documentation against the current official standard, since requirements are periodically updated.

A Starting Framework, Not a Blank Page

Building this entire system from a blank document is where most first-time certification efforts stall out. Our Food Safety Management System Bundle gives you a structured starting point covering everything above — a Quality Manual, HACCP Plan template, all ten core prerequisite program SOPs, and a Forms & Records pack — so you're customizing an already-organized system instead of building the structure from scratch.

Common Documentation Mistakes During Audits

A few gaps come up repeatedly during IFS/BRCGS audits. HACCP plans that were clearly copied from a template and never actually validated against real process data. Cleaning schedules that exist on paper but have gaps in the sign-off sheets around the exact dates an auditor happens to check. Traceability tests that were never actually run, only documented as a procedure. And perhaps the most common: a system that was assembled in the final weeks before the audit, leaving no genuine operating history to demonstrate — auditors are specifically trained to notice this pattern.

The Bottom Line

IFS/BRCGS documentation isn't about paperwork for its own sake — a well-organized system genuinely makes your operation safer and easier to run, audit aside. Start with a solid structural framework, make it genuinely yours through real hazard analysis and consistent records, and get it reviewed by a qualified professional before your audit date.