Skip to main content
Heads upFSMA 204 compliance is July 20, 2028 — extended via H.R. 5371 in November 2025. Get the implementation checklist →
HACCPLAN
Use case / CFIA preventive control plan

Use case / CFIA preventive control plan

How do I create a CFIA preventive control plan?

Build the PCP around real products, hazards, controls, monitoring records, traceability, and recall evidence instead of treating it like a one-time document.

Updated 2026Commercial use caseCFIA / SFCR

Andrew Langevin· 2026-06-05· 8 min read

01Direct answer

Start with the food, not the binder.

To create a CFIA preventive control plan, list the foods you make or import, map how they move through the business, identify hazards, define controls, show how those controls are monitored, and keep records that prove the system works. The plan should also connect to sanitation, allergens, supplier approval, traceability, recall, training, and complaints.

A small food business can write a basic PCP in a document. The problem starts when the document is separate from daily records. If the product changes, a supplier changes, or the process changes, the PCP must still match the floor.

What CFIA is checking

The plan has to match current practice. The inspector can compare the written PCP, the room, the records, labels, supplier files, and staff answers.

02Core workflow

The PCP pieces to build first.

  1. 01

    Product and process

    Food name, ingredients, packaging, shelf life, storage, intended use, and process flow.

  2. 02

    Hazards and controls

    Biological, chemical, physical, and allergen hazards, with controls that make sense for the process.

  3. 03

    Monitoring records

    What gets checked, how often, what limit applies, and who records the result.

  4. 04

    Corrective actions

    What staff do when a limit is missed, a lot is held, or a record is incomplete.

  5. 05

    Verification

    How the business reviews records, checks the system, and confirms fixes worked.

Use the interactive version

Create a live PCP workspace in HACCPlan

Build product records, hazards, controls, monitoring logs, corrective actions, supplier files, traceability, and recall evidence in one workspace.

Free signup. No card. Saved records and larger workflows are available in the app.

03Why it breaks

PCP documents get stale when records live elsewhere.

Many operators write the PCP once, then run the business from paper logs, spreadsheets, email, and memory. That creates drift. The supplier list is updated, but the ingredient hazard review is not. The sanitation schedule changes, but the procedure stays old. A new product uses an allergen, but the label review process is not updated.

That drift matters because inspections are evidence-based. A clean document is not enough if the records do not prove the controls were followed. HACCPlan keeps the PCP closer to the daily work.

04What HACCPlan does

Turn the PCP into an operating system.

HACCPlan treats the preventive control plan as a connected set of records. The product record feeds the hazard analysis. The hazard analysis feeds monitoring. Monitoring feeds corrective action. Supplier records support ingredient control. Traceability and recall records prove the business can respond when something goes wrong.

  1. 01

    Plan builder

    Draft the product, process, hazards, controls, monitoring, corrective actions, verification, and records.

  2. 02

    Supplier link

    Connect ingredient specs, CoAs, certificates, and allergen letters to the plan.

  3. 03

    Inspection view

    Export or stage the records an inspector is likely to request first.

  4. 04

    Change review

    When a product, process, or supplier changes, know which PCP sections need review.

05Next step

Build the first product before the full manual.

Pick one active product and build the evidence path from receiving to shipping. If that product is clean, repeat the pattern. If it is messy, the gaps will show you what the PCP needs.

Start with one product

Build your first CFIA PCP record set

Use HACCPlan to connect the product, ingredients, controls, monitoring records, traceability, and recall evidence before the next inspection.

Use the workspace for saved PCP work, not just a static document.

06Proof

The plan should prove daily control.

The strongest PCP is not the longest one. It is the one that makes evidence easy to follow. If a control is written into the plan, the business should be able to show the record, the review, the exception, and the fix. If the product changes, the plan should show when it was reviewed.

That is the page-one test for a Canadian operator: does the PCP explain the real process, and do the records prove the process is controlled?

07Related

Read the Canadian page, then build the workflow.

Start with Canada SFCR solutions, then use HACCP software, traceability, and audit readiness to build the live record set.

Andrew Langevin·CFIA-licensed facility, Brantford ON· Published 2026-06-05· 8 min read· Wikidata Q139112497