Preparing for a CFIA Inspection: A Facility Monitoring Checklist
If you run a licensed food business in Canada, a Canadian Food Inspection Agency inspection is something to prepare for, not to panic about. The operations that have a hard time are usually the ones that try to organize their records in the week before the inspector arrives. The operations that have an easy time are the ones whose monitoring system was already producing complete, retrievable records every day.
This article is a focused checklist for the monitoring and records portion of a CFIA inspection. It covers what to have ready before the inspector arrives, what to expect on the day itself, and the records-specific items that typically come up in conversation.
It is not a full Preventive Control Plan audit prep guide. The PCP, hazard analysis, sanitation program, allergen controls, supplier program, and recall procedures all sit alongside the monitoring side and deserve their own preparation. Treat this as one slice of the work, not the whole thing.
Note: This article is a practical overview, not legal advice. Inspection scope, frequency, and focus vary by licence type, commodity, and the inspector's discretion. Consult the CFIA or a qualified food safety professional for guidance specific to your operation.
Why the monitoring and records portion matters
For most food businesses, monitoring records are the largest body of evidence the inspector will look at. Temperature logs, humidity logs, sanitation checks, and the corrective action records tied to them are what an inspector uses to confirm that the controls in your PCP are actually operating day to day, not just written down in a binder.
A plan that reads well on paper but is supported by patchy records is a harder conversation than a plain plan supported by complete ones. Records show up first, so it makes sense to have that part of the operation in good shape before anything else.
Pre-arrival checklist
In the days leading up to a scheduled inspection, or as a general state of readiness for an unannounced one, walk through the following.
The monitoring-related parts of the PCP are current and reflect today's operation. The plan on the shelf should describe the equipment, products, suppliers, and procedures that are actually in use. If the line moved, if a cooler was replaced, if a product was added, the plan should reflect it. A current signature and review date on the cover help confirm the plan has been looked at recently.
Monitoring records for the last twenty-four months are retrievable. The SFCR generally requires PCP-related records to be kept for at least two years from the date the record was made, with three years for shelf-stable low-acid foods in hermetically sealed containers. Retrievable means more than "stored somewhere." It means a specific date and control point can be produced within a reasonable time without a treasure hunt.
Corrective action records are matched to their deviations. Every alert, excursion, or out-of-spec reading should have a corresponding record that describes what was observed, what was done with affected product, the root cause investigation, and the steps taken to prevent recurrence. Deviations without matching corrective actions are an issue inspectors look at closely.
Calibration records for thermometers and sensors are on file. Whether you calibrate in house against a reference instrument or use a calibration service, the schedule and the records should be available. Out-of-date calibration records weaken every monitoring reading that depends on the instrument.
Internal verification records are present. Verification is the periodic check that monitoring is being carried out and that the controls are still effective. That typically means record reviews, internal audits, or product testing where applicable. A monitoring program without a verification trail is incomplete under SFCR expectations.
Equipment maintenance logs are organized. Cooler maintenance, refrigeration service reports, wash line cleaning logs, and any other maintenance records tied to food safety controls should be filed alongside the monitoring records, not scattered across binders and email inboxes.
Staff responsible for monitoring can describe their procedures. If the inspector asks the cooler operator how they check temperatures and what they do when a reading is out of range, the answer should match the PCP. Mismatches between what the plan says and what staff actually do are a reliable source of findings.
Day-of checklist
When the inspector arrives, the goal is to be cooperative, accurate, and organized. A few practical items help.
Decide in advance who greets the inspector. Usually this is the licence holder, the operations manager, or a designated food safety lead. The greeter does not need to answer every question themselves, but they should know who to bring in for which topic.
Have a workspace ready. A clean table, reliable power, a chair, and reasonable proximity to the people and records the inspector will need are sufficient. The inspector will direct the visit, but a workable space speeds things up.
Provide the requested records clearly and stay within what's been asked. When the inspector asks for cooler temperature records for a specific date range, provide that range. Pulling additional months or unrelated records that were not asked for can complicate the inspection and is generally not helpful. Answer the question that was asked.
Answer questions about gaps honestly. If a record is missing, say so. If a procedure was not followed for a period, say so and explain what was done about it. Inspectors are typically far more concerned with operations that hide problems than with operations that found their own and corrected them. Documented gaps that were investigated and addressed are part of a functioning system.
Do not speculate. If a question is outside your area, say you will get the person who knows. Guessing at numbers, dates, or procedures usually creates more issues than it resolves.
Keep a log of what was requested and produced. A simple list of records the inspector asked for, what was provided, and any questions left open helps with follow up after the inspection ends.
Records-specific checklist
The following items come up often enough during inspections that they are worth confirming before the visit.
Monitoring data is timestamped and attributable. Each reading should identify what was measured, when, by whom or by what system, and the result. Logs where every entry looks identical, or where readings are recorded at impossibly tidy intervals, generally invite closer examination.
Alert history is reviewable. If you use an automated monitoring system, the alert history should be exportable or otherwise viewable for the retention period, with the corrective action records tied to each alert that mattered.
Records produced from electronic systems are accurate and retrievable. Electronic records are acceptable under the SFCR provided they are accurate, legible, and retrievable when requested. If your monitoring data lives with a third-party vendor, confirm in advance that you can produce a readable copy on request without depending on a live subscription or a specific staff member.
Backups exist for critical electronic records. A single hard drive or a single vendor account is a thin layer between you and a problem. Backups to a second location, or quarterly exports to your own storage, protect against typical failure modes.
Paper records are legible and complete. If logs are still on paper, the pages should be readable, the months should be filed in order, and the binders should be stored somewhere reasonably dry and accessible.
Practical posture during the inspection
A CFIA inspection is not a courtroom and it is not a sales meeting. It is a structured review by someone trained to look at specific things. The posture that tends to go best is cooperative, accurate, and unhurried. Provide what is asked for, answer what is asked, and let the records speak for themselves. If something is wrong, it is better to find it together than to have it found while you are trying to talk around it.
The strongest position to be in is one where your monitoring records have been complete and reviewed every month for the past two years, so the inspection becomes a process of confirming what you already know rather than discovering it for the first time. Getting to that state is not about working harder during inspection week. It is about having a monitoring system that produces complete records every day, including weekends, overnight, and on the days you are off site.
Storage Sentry is a wireless monitoring platform purpose-built for Canadian agricultural operations. It generates continuous, timestamped temperature and humidity records and sends prompt alerts when readings move outside your limits, helping support the monitoring and records portions of a CFIA inspection. Learn how Storage Sentry can help.
References
-
Canadian Food Inspection Agency. "Preventive control plan for food businesses: Record keeping." inspection.canada.ca
-
Canadian Food Inspection Agency. "Regulatory requirements: Preventive control plan for food businesses." inspection.canada.ca
-
Canadian Food Inspection Agency. "Understanding the Safe Food for Canadians Regulations: A handbook for food businesses." inspection.canada.ca
-
Canadian Food Inspection Agency. "Inspection process for food businesses." inspection.canada.ca