A preventive control plan contains a HACCP plan and adds to it. The CFIA puts it this way: both include a hazard analysis and the control measures that keep food safe, but a preventive control plan also describes how you meet the consumer protection requirements, such as labelling, packaging and grades, and, for slaughter, the humane treatment of food animals. If you already have a HACCP plan, you have most of the food safety part. What you add is the rest of section 89 of the SFCR.
The short version
- A HACCP plan follows the seven Codex principles. A preventive control plan is what section 89 of the SFCR asks for.
- The CFIA calls section 89(1)(c) "the HACCP plan" inside the preventive control plan.
- The preventive control plan adds labelling, net quantity, packaging, grades and standards of identity.
- It also asks for evidence that your controls work, and keeps its records two years.
- Neither covers traceability. That's section 90, on its own.
- TaroStack keeps the batch records both plans rely on. More at the end.
This is general information, not legal advice. Your CFIA inspector has the last word on what applies to you.
Side by side
| HACCP plan | Preventive control plan | |
|---|---|---|
| Where it comes from | The seven HACCP principles of the Codex Alimentarius | Sections 86 to 89 of the SFCR |
| Hazard analysis | Yes | Yes, section 89(1)(c)(i) |
| Critical control points, limits, monitoring, corrective action | Yes | Yes, section 89(1)(c)(ii) to (v) |
| Verification and records | Yes | Yes, section 89(1)(c)(vi) and (vii), records kept two years |
| Evidence the controls work | Validation | "Evidence that the control measures are effective", for every control |
| Premises, sanitation, pests, staff | The hygiene practices under the plan | Described in the plan wherever they control a hazard |
| Labelling, net quantity, packaging, grades, standards of identity | No | Yes, section 89(1)(a) and (b) |
| Humane treatment of food animals | No | Yes, for slaughter |
| Traceability | No | No, section 90 is separate |
The CFIA's own wording on the last row: "Traceability requirements are not part of the PCP requirements." The recall procedure (section 84) and the complaints procedure (section 83) are separate sections too.
The HACCP part, as the CFIA writes it
The CFIA's guide to the Food Safety Enhancement Program, its older HACCP-based approach, still describes a HACCP plan for section 89(1)(c) in 12 steps. The first five are preparation: the team, the product and its use, the ingredients and materials that touch the food, a process flow diagram and a plan of the building. Steps 6 to 12 are the seven Codex principles:
- Identify and analyze the hazards.
- Determine the critical control points.
- Set the critical limits.
- Set monitoring procedures.
- Set corrective action procedures.
- Set verification procedures.
- Keep records.
The CFIA says written monitoring and corrective action procedures are needed only for critical control points. A plan written this way before the SFCR can still serve as the preventive control plan, but the CFIA asks businesses to review it against the SFCR's requirements.
What a PCP adds
Consumer protection
Section 89(1)(a) and (b) ask for the measures you use to get the label, the net quantity and the packaging right, and to meet any grade or standard of identity for your food. A HACCP plan is about safety, so a label check belongs in it only where it controls a hazard, such as an undeclared allergen. In a preventive control plan, the label check is in the plan whatever it protects against: an allergen, a wrong weight, a missing lot code.
Evidence that the controls work
Section 89(1)(c)(i) and (ii) ask for "the evidence that the control measures are effective". For a critical limit, that's the reason the limit is safe: a published standard, a challenge study, a supplier's validation. For a prerequisite program, it's whatever shows the program does its job, such as swab results after cleaning.
Two years of records
Section 89(2) asks you to keep each document that shows the plan is being carried out for two years from the day it was made. What to keep, and how long.
A hot sauce maker with a HACCP plan
A six-person hot sauce maker in British Columbia wrote a HACCP plan when a grocer asked for one. It has one critical control point: the finished sauce's pH, with a critical limit of 4.0 or below, tested on every batch. Now it's shipping to Alberta and needs an SFC licence and a preventive control plan. It adds:
- The label check. Each new label is checked against the recipe, and each run's labels against the approved version.
- The fill check. Five bottles a batch are checked against the 150 mL on the label.
- The evidence for its pH limit: the reference it set the limit from, kept with the plan.
- The premises. It walks the CFIA's establishment checklist (sections 50 to 81) and writes down what it does for each, where something there controls a hazard.
- Two years of records, kept from now on.
Its HACCP plan stays as it was. The preventive control plan is the HACCP plan with those five added. A full preventive control plan example goes through every step for a bakery.
Where this stops working
Both plans are written once and filled in every day. A pH log on paper, filled in at the end of the shift, can't say which batches were bottled before someone noticed a reading above the limit. When the corrective action says "hold everything since the last good reading", it needs a list of lots that paper doesn't give you.
How TaroStack does it
TaroStack isn't HACCP software, and it doesn't write your plan. It keeps the batch records your plan relies on.
Batch-record forms carry your own checklist fields, such as the pH, the cook temperature or the label check, with initials, on the batch they belong to. Each batch has its lot code, records which ingredient lots went into it and prints lot labels. When a reading is out of limit, everything since the last good reading is a list of lots, and holding them is one step. Any lot opens a trace to its ingredients and its customers.
The trace report carries the names and addresses the SFCR asks for and downloads as one CSV file.
Lots, holds, recalls and batch records are on every TaroStack plan, from $9.99 a month; a business where three people record batches would be on Growth, at $39. It's free for 14 days. If you'd like a hand setting up, ask, and we'll do it with you.
