CFIA Inspections: What to Expect and How to Prepare

How to be ready before they arrive, what CFIA looks at when they do, and what to do when CFIA is already engaging.

CFIA inspections are a fact of life for licensed Canadian food businesses. Most close without issue. The question is not whether an inspection will happen. It is whether, when it does, the business is ready and the response holds up if the contact escalates.

This page is organized around three timelines: getting ready before an inspector arrives, what CFIA looks at when they do, and what to do when CFIA is already engaging. The first section is for businesses that have not had recent inspector contact and want to be ready. The third section is for businesses that are already in correspondence with the Agency. The middle section walks through how an inspection actually unfolds.

Get Ready Before They Arrive

For licensed food businesses that have never been inspected, that have not been inspected in years, or that have just been notified that an inspection is coming, this is where to start.

The conventional wisdom is that an inspection is the moment of truth. The more accurate way to think about it is that the inspection is the audit; the truth is built before. Inspectors tend to appreciate candour, but they do not give credit for explaining what the documents were supposed to say. They read what is in front of them and what they see on the floor, and they form a view about whether the two match.

For licensed manufacturers in particular, an inspection is more likely before 2028 than it has been in years. CFIA's 2026-27 Departmental Plan sets a target that, by March 31, 2027, at least 85% of food establishments with identified compliance issues will have addressed them on follow-up or been brought into compliance. The Agency is also moving forward with a plant-based manufactured foods action plan that strengthens inspection oversight, licensing controls, risk modelling, and enforcement.

The plan was developed in response to the Inspector General's review of safety gaps in manufactured food facilities, which itself followed the Joriki Listeria outbreak (we wrote about that here). The outbreak resulted in three deaths and 20 reported illnesses, and the Inspector General's review found that 26 of the 54 plant-based food manufacturing establishments, close to half, had never been visited by CFIA.

For licensed food businesses without recent inspector contact, two things have shifted in the past 12 months. Inspections are more frequent, and inspectors look more closely on arrival. Both changes are most pronounced in the manufactured-food sector. A facility that has not been inspected in years should not assume the next inspection will be light because the prior pattern was light.

What "ready" means in practice

Readiness is a memorialized set of operational facts that hold up when an inspector reads the documents and then walks the floor. For many food businesses, sometimes readiness looks more like a dusty binder.

The “dusty binder” gap between what is on paper and what is actually running typically shows up in six places. And these gaps can turn compliance-focused inspections into enforcement files. The question for each is not whether the information a food business provides to an inspector it is current; it is whether that information would be accepted if a finding landed there.

The Preventive Control Plan ("PCP") is where the written word most often diverges from practice. A PCP that describes a process the facility no longer runs, or that omits a process the facility now runs, fails its first test. The PCP needs to reflect the lines, ingredients, and packaging configurations as they exist on the day of the inspection. For many facilities, the PCP has not moved since a consultant captured the operation 18 months ago. Reformulations, equipment changes, supplier substitutions, and added SKUs all create dissonance the next inspection will find. The PCP is also the document the Agency reads first when something escalates: how it was drafted, by whom, and against what hazards all become part of the matter that follows. A PCP that has not been refreshed on a line that has changed three times in the same period is a finding waiting to be written.

The supplier verification file is one of the first places an inspector looks because it is one of the easiest places to spot a control gap. Letters of guarantee, certificates of analysis, audit reports, and approved-supplier lists need to be current and tied to specific lots or shipments. A file that shows the supplier programme stalled two years ago, with the facility running on assumption since, is itself a finding. The same file does double duty when a supplier-side issue triggers a recall or enforcement: what is in it determines where liability falls and whether the company can show it acted reasonably.

Recall procedures are not a desk exercise. They need to name specific people, list specific actions, and have been timed against the timelines the regulation requires. A facility that has the procedure on paper but has never run a mock recall, or has never updated it since the head of operations changed, will struggle when it is called on. The procedure is also where traceability gets tested: it is one thing to say the supply chain has one-up and one-down traceability; it is another thing to demonstrate it under time pressure. When a recall does land, the difference between voluntary action and a Minister-ordered recall is set early; what the procedure says and how it is executed shape which one the facility is dealing with.

Traceability across reformulations and ingredient changes is harder than steady-state traceability. The traceability records need to track the change, not just the steady state. Reformulations and ingredient substitutions complicate the picture because the input may have changed mid-production run, mid-quarter, or across SKU variants that look identical to the consumer. The records that follow the change are the ones that hold up when an inspector audits backward from a finished product, and the ones that hold up if an enforcement matter requires reconstructing the chain in front of an adjudicator.

Training records need to reflect what staff actually know and do. A training matrix that shows everyone trained on every SOP is suspicious; a matrix that shows new hires trained, refresher cycles completed, and competency verified through observation is credible. Inspectors talk to staff. If the operator on the line cannot describe the deviation procedure that the binder says they were trained on six months ago, the inspector knows. If a finding turns into something larger, the same records frame what the company can later argue: who knew what, and when.

Operational records are the daily evidence that the PCP is working. Cleaning logs, monitoring records, deviation logs, and corrective action records need to be current, complete, and aligned with the frequencies and limits the PCP specifies. The most common failure pattern: the PCP requires a check every two hours, the log shows checks every shift, and the inspector counts the gap. These are also the records that get pulled when a recall or enforcement matter requires showing that the controls were running on a particular shift. What is on file today is what holds up months from now.

The gap most firms have

The pattern across all of these is the same: the documents say one thing, the operations do another. That gap is what inspectors are trained to spot. They are not looking for a perfect facility; they are looking for whether the facility's representation of itself matches what they observe. Where it does, the inspection is operational. Where it does not, the inspection becomes the start of an enforcement file.

A newer version of this pattern is the AI-generated or template-generated PCP. The problem is not the tool used to draft it. The problem is that the document often reads as fluent and complete while failing to describe how the facility actually runs, what hazards it faces, and which controls are in place. We are seeing matters move from compliance promotion into a more combative enforcement posture where the quality, specificity, and apparent origin of the materials provided appear to have damaged the facility's credibility with the Agency. The fix is not more generic documentation; it is documentation that survives contact with the floor.

What CFIA Looks At When They Arrive

An inspection that goes well is an operational event. An inspection that goes badly can trigger enforcement action, generate findings that take months to resolve, and leave a mark on the compliance record that affects the company for years. The difference between those outcomes is usually preparation, not luck.

The ERA Model

CFIA allocates inspection resources using the Establishment-based Risk Assessment (ERA) model. The ERA assigns a risk score to each licensed establishment based on product type, volume, compliance history, and the adequacy of the preventive control plan. Higher scores mean more frequent inspections.

Compliance history is the input companies most often underestimate. A confirmed violation, an AMP, or a poorly managed recall adds to the score. The effect compounds: a higher score brings more inspections, more inspections bring more opportunities for findings, and findings push the score higher. But not every entry on the record is fixed at the time it lands. Which entries are contestable, which AMPs warrant a CART review, and which corrective actions will land credibly are decisions that shape the score over time. Managing the ERA score is a long-term compliance strategy, not an afterthought. For how AMPs and other enforcement actions affect the compliance record, see AMP Challenges.

Inspector Powers

SFCA ss. 24-27 give CFIA inspectors broad authority. An inspector may enter any place where food is manufactured, prepared, stored, packaged, or sold; examine food, packaging, labelling, and records; take samples; seize and detain food or other things; and require the production of documents and information. These powers are exercised without a warrant when the inspector has reasonable grounds to believe a regulated activity is being conducted or a regulated item is present, apart from a dwelling-house.

The practical consequence: when an inspector arrives, the company is expected to cooperate. Obstruction is a prohibition under SFCA s. 16 and an offence under s. 39. That said, cooperation does not mean unconditional agreement with every finding or characterization the inspector makes. What must be produced, what is volunteered, and what is deferred for review are decisions that shape the file as it forms.

During the Inspection

One dynamic that companies do not always appreciate: the inspector's observations and characterizations carry significant weight within CFIA. Findings documented by an inspector are often received by the Agency as the factual record. If the company disagrees with how a finding is described, the time to raise that disagreement is during the inspection or in the immediate written response, not months later in an enforcement proceeding.

Practical steps that protect the company:

  • Designate a point person to accompany the inspector throughout.

  • Take contemporaneous notes of the inspector's observations and any oral statements.

  • If the inspector identifies a finding, ask clarifying questions about what specifically is being cited and under which provision.

  • Answer accurately and directly.

  • Avoid speculation.

  • Do not adopt the inspector's characterization unless it is accurate.

Something we think about a lot is how cooperation is required, but unreviewed admissions are not. Regulated parties that build inspection reception into their standard operating procedures handle inspections more consistently than companies that improvise. An inspection reception SOP covers who is the designated point person, who else should be notified internally, what records should be readily accessible, what areas the inspector is likely to want to see, and how findings are documented and escalated. GSJ&Co. builds these SOPs as part of compliance programme work.

Responding to Findings

The written response to inspection findings is often the most consequential document in the file. It establishes the company's position, frames the narrative, and becomes part of the permanent compliance record. CFIA uses the written response to assess whether the company understands the issue and has a credible corrective action plan.

A response that is defensive, evasive, or generic will not satisfy the Agency. A response that demonstrates genuine understanding of the finding, explains the root cause, and presents specific corrective measures with a realistic timeline is in a materially stronger position. The written response should be reviewed by counsel before submission. When findings escalate toward AMPs, licence suspension, recalls, or prosecution, the analysis shifts to enforcement actions; those are addressed in CFIA Enforcement Actions: A Practical Guide.

When CFIA Is Already Engaging

Most contacts close without enforcement. The inspector reviews documents, moves through the operation, asks questions, and leaves. When the contact is heading the other way, the considerations are different. The work is no longer about whether the facility will be visible to the Agency. It is about what the Agency takes away from this contact, and what shape the file is in when they next come back.

Three patterns are common. The most frequent is time pressure: CFIA has demanded specific documents within a defined window, often shorter than the company would like. The work in this scenario is producing the documents accurately within the time the Agency has set, and being deliberate about what should and should not be submitted. A submission padded with documents the Agency did not ask for usually creates more findings than it resolves. A submission that is late, or that misses a specific item the Agency requested, usually damages the inspector's read of the company more than the underlying issue warrants.

A second pattern is the AI-generated file. A facility has used AI tools or generic templates to draft PCPs, SOPs, or procedural documents, and CFIA has flagged the result for generic language, missing specifics, or mismatches with the operation. The work is rebuilding the submission so that it describes the operation as it actually runs, then preparing for the follow-up visit that usually comes with it. The fix is not better generated text; it is text written by someone who has walked the floor and read the regulation.

A third is the documents-versus-operations gap. A facility has submitted documents in good faith and CFIA has identified that what is on paper does not match what they are seeing on the floor. The exposure here is twofold: the underlying compliance gap, and the credibility gap that the mismatch creates with the inspector. The work is closing the gap on the floor, correcting the documents, and getting the next contact to land on a consistent picture.

Each pattern has a different remediation path but they share one thing: the file shape when CFIA next makes contact will reflect the work done now, not the documents that were on the shelf before the file opened.

Where Counsel Fits

Counsel is most useful at four points along the inspection timeline. Before the inspection, on the readiness side:    walking the PCP against actual operations, reviewing the supplier verification file and recall procedure against the timelines the regulation requires, and building inspection-reception SOPs that name the point person and the escalation path. During a disputed finding: managing the written response so the company's position is protected before the compliance record is set. After findings are issued: coordinating the response strategy when escalation is in view. In ongoing compliance record management: assessing which compliance record entries are contestable, which corrective action plans will be credible to CFIA, and how to position the facility for a lower risk score over time.

For operators looking to get ahead of an inspection, whether it would be a first inspection, a first in years, or one already known to be coming, we work with licensed Canadian food businesses to build the readiness picture and the document-operation alignment that determines what an inspection finds.

For operators where CFIA is already engaging and the response needs to land fast, we work to that timeline, including submissions under tight windows, rebuilding documents that have triggered Agency concern, and closing documents-versus-operations gaps before the next contact.

GSJ&Co. advises on inspection preparation, response to findings, corrective action plans, and ERA score management. Contact info@gsjameson.com or +1 (647) 638-3994.

Primary Authorities

Last updated: May 2026. This page is maintained by GSJ&Co. and updated when there are material changes to CFIA inspection practice or the governing legislation.