HACCP News
Food safety asks what could go wrong by accident. Food defense asks what could go wrong on purpose – someone deliberately contaminating product, tampering with a shipment, or walking out with labels and packaging. FSIS expects establishments to have a food defense plan, and inspectors ask about it. Most plants have one. Far fewer can show it was reassessed this year, by whom, and what they did about the gaps they found.
What a Food Defense Plan Has to Cover
The FSIS model organizes it into four areas, and a real plan has to address all of them – not just the fence line:
- Outside security – plant boundaries, secured entrances, perimeter monitoring, shipping and receiving, and mail handling.
- Inside security – restricted areas, processing floor access, storage, water and ice systems, chemical and hazardous material control, and access to sensitive information like site plans.
- Personnel security – identifying employees on site, background checks, restrictions on what comes in and out, visitor and contractor logs, and periodic security awareness training.
- Incident response – how a security concern gets investigated, who gets called, and where the emergency contacts live.
Where Food Defense Plans Usually Fall Down
The plan itself is rarely the problem. The problems are almost always the same four:
- It was written once, years ago, and nobody has walked the plant against it since.
- It lives in a binder or a shared drive, and finding it during an inspection takes longer than answering the question would have.
- There is no record of who assessed what, or when – so “we review it annually” is a claim with nothing behind it.
- Gaps got identified and then quietly went nowhere, because nothing tracked them to a corrective action.
How HACCP Builder Handles Food Defense
Food defense needs two things that usually live in different places: a written plan describing your security measures, and evidence you actually reassess it. HACCP Builder covers both, and keeps them together.
The Written Plan, Already Structured
A Food Defense Plan template ships as part of the Sub Plan library – not a blank form, but a real starting document covering facility description, outside security, inside security, personnel security, and incident response, with an acknowledgment block for sign-off. You adapt it to your facility and activate it.
The FSIS Self-Assessment, Built In
Alongside the plan, the FSIS food defense self-assessment is included – 83 questions across 16 security areas, from plant boundaries and mail handling through processing-floor access, water and ice systems, chemical control, visitor logs, and security training. It is already written. You are not building a questionnaire from scratch.
Corporate Sets It, Facilities Answer It
Corporate controls the questionnaire and assigns it to the facilities it applies to. At the facility it can be answered but not rewritten, so every site is assessed against the same standard and no single plant can quietly soften a question it would rather not fail. Across multiple locations, that is the difference between one food defense program and a dozen unrelated ones. Same corporate control model used throughout the system.
An Answer and a Reason, Not Just a Box
Most of the assessment is Yes/No, and every question also takes an open comment – because “No” is only useful if someone wrote down why. Where a gap should drive action rather than sit there, corrective actions can be turned on for that question, so the response comes from options you defined rather than free text.
Reassessment History, Not One Static Document
Each completed assessment is saved and dated, and prior submissions stay visible. That turns “we review our food defense plan periodically” from an assertion into a list with dates on it – which is what an inspector asking the question is really after. Plan edits carry the same document control and audit trail as the rest of your program.
Answered Where the Work Happens
The assessment is available on the same mobile access your team already uses for logs and checklists, so walking the plant and answering as you go is one pass – not a walk-through followed by an evening of transcription.
An Honest Note on Scope
The four-area structure above follows the FSIS food defense model, which is aimed at meat and poultry establishments under FSIS inspection. The FDA’s Intentional Adulteration rule is a separate regulation with its own required elements, including vulnerability assessments and mitigation strategies at specific process steps. The discipline is similar and the work overlaps, but they are not the same requirement. If you are not certain which applies to your operation, that is worth settling before you buy any software – ours or anyone else’s.
One Program, Not a Separate Binder
Food defense belongs with your HACCP plan, your logs, and your recall procedures – reviewed on the same rhythm and retrievable in the same place. For establishments already using HACCP Builder for meat and poultry compliance, it is part of the same program, not another system to maintain.
If you want to see how HACCP Builder would handle food defense against your own plant and your own security measures, contact HACCP Builder and we will walk you through it.
We can be reached at (866) 577-4030 ext. 800 or via email at [email protected]. Leave us a message or book a free demo today!
