Building a client’s HACCP plan in 30 days
A four-week workflow that follows the 12 Codex steps, shows what the client does each week, and ends with a plan the site actually owns.
Follow the 12 Codex steps in four weekly blocks: scope and flow diagram, hazard analysis and CCPs, monitoring and corrective actions, then validation and handover. Write the plan with the client’s team, not for them, because auditors check that on-site staff understand it. And plan the records from day one: a plan is only proven by the records it produces.
Four weeks, twelve steps
Our suggested schedule for a small or medium manufacturer with a few product lines.
| Week | Codex steps | You do | Client does |
|---|---|---|---|
| 1: Scope | 1–5: team, product description, intended use, flow diagram, on-site check | Run the kick-off, draft product descriptions and flow diagrams | Names the HACCP team, walks the process with you, corrects the flow diagram |
| 2: Hazards | Principles 1–3: hazard analysis, CCPs, critical limits | Lead the hazard analysis, apply a decision tree, propose limits with their basis | Supplies process data, specifications and supplier information; challenges what doesn’t match reality |
| 3: Controls | Principles 4–5: monitoring, corrective actions | Write monitoring procedures and corrective action plans for each CCP | Checks every procedure can be done on the floor, by the people on shift |
| 4: Prove it | Principles 6–7: verification, records | Set verification, design records, validate limits, train the team | Starts keeping records, signs off the plan, takes ownership |
The prerequisite programs sit underneath the plan. If they’re weak, fix them alongside week 1. See the prerequisite programs explained.
Four ways a good plan fails at audit
It’s a template, not this site
Generic hazards, someone else’s flow diagram. Auditors spot a plan that doesn’t match the floor within minutes.
Limits with no basis
A critical limit needs a reason: a standard, a scientific reference or validation data. Write the basis next to the limit.
Corrective actions that say “notify supervisor”
Each CCP needs a real plan: stop, hold product back to the last good check, restore control, decide, record. See CCP deviations.
Nobody on site can explain it
If only the consultant understands the plan, it fails the first time an auditor asks an operator what their CCP is.
Build it so the client owns it
- Hold the hazard analysis as a workshop with the client’s team, not as a document you email.
- Name a person, not a role, for every monitoring task, with a trained back-up.
- Write procedures in the words the floor uses, and test each one on shift before signing off.
- Have the client’s senior manager sign the plan. It’s their plan and their responsibility.
If you also work as an auditor, keep the roles apart. In Victoria, an approved auditor can’t audit premises whose food safety program they wrote or helped prepare.
Build it once, keep it live
Build the client’s HACCP plan and prerequisite programs inside EthicalHub, and they stay live and versioned instead of living in a Word file. Monitoring records are set up from the plan, so the client starts logging in week 4, and you see their records in the Consultant Dashboard from your desk. The dashboard is free for consultants; clients subscribe from $69 a month per site.
Get the free Consultant Dashboard
Build your next client’s plan in EthicalHub and invite them with one link.
HACCP plan development: common questions
How long does it take a consultant to build a HACCP plan?
What are the steps in developing a HACCP plan?
Should the consultant or the client write the HACCP plan?
Can the consultant who wrote the plan also audit it?
Write it once. Keep it working.
The Consultant Dashboard is free. Build the plan and review the records in one place.