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
Templates / Records

Templates / Records

Food safety records library.

Records are the operational evidence that your plans were followed. The library below is the actual forms an inspector opens first — each one cited to the regulation that requires it, in formats you can print today.

Updated 2026Template hubTier 2

Andrew Langevin· 2026-06-04· 14 min read

01The inspection moment

What an inspector opens first.

I run a Canadian Food Inspection Agency (CFIA) licensed mushroom facility in Brantford, Ontario. On my first inspection in 2023, the inspector walked past my 47-page Preventive Control Plan (PCP) without opening it. She didn't ask about my food safety policy. She asked to see my last thirty days of receiving logs. Then thirty days of cleaning logs. Then thirty days of Critical Control Point (CCP) monitoring. The audit was the records. The plan was background.

That order is not unique to me. Inspectors at the U.S. Food and Drug Administration (FDA), the U.S. Department of Agriculture Food Safety and Inspection Service (USDA-FSIS), and CFIA all work the same way. They open the records binder first because records are the operational evidence that the plan was followed. A beautiful plan signed by a Preventive Controls Qualified Individual (PCQI) means nothing if the records show the plan wasn't followed.

Don't read the plan. Read the records. The plan is the promise; the records are the proof.

What every inspector knows by their second site visit

The library below is the set of forms I have personally built, used, scrapped, and rebuilt over five years of Safe Food for Canadians Regulations (SFCR) operation and 50,000+ orders shipped. Each one cites the exact regulation that requires it — so when the next inspector asks “show me where this is required,” you can point at the column header.

02The definitional spine

Records vs plans vs manuals — the distinction that matters.

Operators routinely lump three different documents together. Inspectors do not. Before you download a single form, internalize this:

  1. 01

    Plans are forward-looking process documents

    The HACCP plan, the food safety plan, the recall plan, the food defense plan, the allergen control plan, the sanitation plan, the environmental monitoring program. These say “here is how we will do X.” Written once, revised when conditions change. They live under /templates/plans.

  2. 02

    Manuals are standing policy documents

    The food safety manual, the Good Manufacturing Practices (GMP) manual, the quality manual, the employee handbook. These codify the rules of the operation and get reviewed annually. They live under /templates/manuals.

  3. 03

    Records are operational data

    The filled-in temperature log, the signed receiving slip, the dated cleaning checklist, the swab result, the corrective-action form with the supervisor's initials. Records are the single most-checked artifact in any inspection or audit. They are what this page is about.

The FDA rule is explicit about the difference. 21 CFR §117.305 says records must “contain the actual values and observations obtained during monitoring,” “be created concurrently with performance of the activity documented,” and be “as detailed as necessary to provide history of work performed.”1 A plan says what should happen; a record proves it did.

What this means for you

When you search for records, you've already passed two earlier checkpoints. You've decided you're running a food business. You've written (or paid for) a plan. Now you're trying to build the daily evidence that operationalizes the plan. That puts you mid-build to mid-operation — exactly where the next inspector wants to find you.

03The regulatory foundation

The rules that require each record.

The defensible difference between a junk template and a real one is whether the form cites the regulation. Below are the five rule sets you might sit under. Most operators sit under one or two. Read your own; ignore the rest.

21 CFR §117.190 — the six FSMA record categories.

The Food Safety Modernization Act (FSMA) Preventive Controls for Human Food rule lists six explicit record categories every FDA-registered food manufacturer must keep:2

  1. 01

    Basis for not establishing a preventive control

    Documentation of why you chose not to establish a preventive control under §117.136(b), when applicable.

  2. 02

    Monitoring records

    Records that document the monitoring of preventive controls — temperature logs, pH logs, time logs, anything that proves the control is being executed.

  3. 03

    Corrective action records

    Records that document corrective actions — what went wrong, what you did about it, and how you prevented it from happening again.

  4. 04

    Verification records

    Records that document verification — validation studies, monitoring verification, corrective-action verification, instrument calibration, product testing, environmental monitoring, records review, and reanalysis.

  5. 05

    Supply-chain records

    Records that document the supply-chain program — supplier approval, Certificate of Analysis (COA) results, letters of guarantee.

  6. 06

    Training records

    Records that document applicable training — who was trained, on what, when, and by whom.

Every record on this page maps to one of those six categories. Memorize the six — they are the structure every FDA inspector uses to organize their request list.

21 CFR §117.305 and §117.315 — content and retention.

§117.305 is the FDA's general records rule. Records must be original, true copy, or electronic. They must contain actual values and observations from monitoring and verification. They must be accurate, indelible, and legible. They must be created concurrently with performance — not back-filled at the end of the week. They must be detailed enough to provide a history of work performed. They must identify the facility, date, time when appropriate, signature or initials, and product/lot code where appropriate.1

§117.315 sets retention. All records must be retained at the plant or facility for at least two years after the date they were prepared. Records relating to the general adequacy of equipment or processes — validation studies, for example — must be retained at least two years after their use is discontinued. Off-site storage is permitted if records can be retrieved within twenty-four hours of an official request — except the food safety plan itself, which must remain on-site. Electronic records accessible from an on-site location count as on-site.3

9 CFR §417.5 — the USDA-FSIS rule for meat and poultry.

If you process meat or poultry, you answer to FSIS, not FDA. The rule is different. §417.5 requires the written hazard analysis with supporting documentation, the written HACCP plan with decision-making documents, and records documenting monitoring of CCPs, corrective actions, verification activities, and calibration of process-monitoring instruments. Each entry must be made at the time the event occurs and signed or initialed by the employee making the entry.4

Retention under FSIS is split by product type:

Slaughter + refrigerated

1 year

Slaughter activities and refrigerated product records must be retained at least one year. Off-site storage allowed after six months.

Frozen, preserved, shelf-stable

2 years

Frozen, preserved, or shelf-stable products require two-year retention. The same six-month off-site rule applies.

SFCR §89–§92 — the rules for Canadian operators.

If you hold a CFIA licence under the Safe Food for Canadians Regulations, four sections matter:5

  1. 01

    §89 — Written PCP requirement

    Licence holders (and certain growers and importers) must prepare, keep, and maintain a written Preventive Control Plan covering their activities — including the documents, methods, and records that demonstrate compliance.

  2. 02

    §90 — Traceability records

    Persons other than retailers must keep documents identifying the food (common name, lot code or unique identifier, manufacturer), the immediate supplier (one-step-back), and the immediate customer (one-step-forward) — including dates received and provided.

  3. 03

    §91 — Production on request

    Traceability records must be produced to CFIA within 24 hours of a request (shorter if CFIA believes there is a risk). Electronic formats must be plain text, single file, and software-compatible.

  4. 04

    §92 — Labelling

    Labels must include common name, lot code or unique identifier, and manufacturer or processor name and location when food is provided to others.

Retention under SFCR is two years after the day the food was provided to (or by) the regulated party. The 24-hour production rule under §91 is the one that catches Canadian operators most often. CFIA does not wait for your filing system to be ready. If you can't pull one-step-back and one-step-forward records for a given lot code in 24 hours, you are non-compliant — even if the records exist somewhere.6

FSMA Section 204 — the 2028 traceability rule.

For foods on the FDA's Food Traceability List (leafy greens, sprouts, herbs, melons, cucumbers, peppers, tomatoes, tropical tree fruits, nut butters, certain ready-to-eat deli salads, soft cheeses, finfish, crustaceans, shell eggs), Section 204 of FSMA requires Key Data Elements (KDEs) at Critical Tracking Events (CTEs). The compliance date was extended in August 2025; the new effective date is July 20, 2028.7 Records retention is two years, in an electronic sortable spreadsheet producible within 24 hours.

If you sell any item on the Food Traceability List, start building the KDE-at-CTE record now. The 2028 date sounds far. It isn't — implementation takes 18 to 24 months for most operations.

04The library

The records you actually keep.

Below is the working set. Every form ships with the regulation in the column header. Print, clipboard, sign every shift. As your operation grows, the binder grows with it.

These are the monitoring records that prove each preventive control is being executed. Under §117.190(a)(2), these are non-negotiable for any FDA-registered facility with a temperature CCP — which is almost every facility. Under SFCR §86, they are the operational evidence that your PCP is implemented.

Sanitation records cover both the FSMA preventive-control category (sanitation as a preventive control where hazards warrant) and the Food Code requirement for food-contact surface cleaning. The sanitizer ppm column is the field most free templates skip — and the field most inspectors check first.

Download — the cheat-sheet

Free, ungated. Fillable on a tablet or computer in any PDF viewer. Print blank and fill on a clipboard. No account needed.

The cheat-sheet isn't a record itself — it's the reference you tape inside the walk-in door so every line cook knows the number before they fill out the log.

05The full inventory

The 24+ records every operator should have.

Below is the full inventory grouped by purpose. Forms I've already published as downloads are linked above. The rest are either sibling pages on this site or records you should build yourself using the citation guide below.

  1. 01

    Monitoring and CCP records

    Temperature logs (refrigeration, freezer, cooking, hot holding, cold holding, receiving), CCP monitoring log, pH and water activity (aw) lab monitoring, cooking and cooling logs against HACCP critical limits, Time as a Public Health Control (TPHC) log. See /templates/temperature-log.

    §117.190(a)(2) / §417.5(a)(3)

  2. 02

    Sanitation and environmental records

    Cleaning log, pre-operational inspection, Adenosine Triphosphate (ATP) swabbing log, environmental monitoring program (Listeria, Salmonella swab) log, pest control activity log, water testing log. See /templates/cleaning-log and /templates/records/swab-logs.

    §117.35 / §117.190(a)(4)

  3. 03

    Allergen and cross-contact records

    Allergen verification log, allergen cleaning validation log (Enzyme-Linked Immunosorbent Assay (ELISA) or Lateral Flow Device (LFD) verification). See /templates/records/allergen-verification.

    §117.135(c)(2)

  4. 04

    Receiving and supply chain records

    Receiving log (with temperature check and reject criteria), supplier approval form, Certificate of Analysis (COA) log, letter of guarantee, returns and customer-rejected product disposition log. See /templates/records/receiving and /templates/records/supplier-approval.

    §117.190(a)(5)

  5. 05

    Corrective action and deviation records

    Corrective Action Report (CAR), deviation log, non-conformance report, holds and release disposition form. See /templates/records/corrective-action and /templates/records/deviation-log.

    §117.190(a)(3)

  6. 06

    Verification and calibration records

    Verification log (records review, environmental review), calibration record (thermometer plus other process instruments). See /templates/records/equipment-calibration.

    §117.190(a)(4)(iv)

  7. 07

    Training and people records

    Training record, sick-employee exclusion log, employee hygiene and handwashing log. See /templates/records/employee-hygiene.

    §117.190(a)(6) / Food Code §2-201

  8. 08

    Customer-facing and complaint records

    Customer complaint log with severity classification, recall communication log. See /templates/records/customer-complaint.

    §117.190(a)(4)(iv)

  9. 09

    Specialty and scheme-required records

    Glass and brittle plastic register (BRCGS Issue 9), foreign object and metal-detection log, mock recall record (SQF requires twice yearly), visitor and contractor log, chemical inventory and Safety Data Sheet (SDS) records, waste and recycling logs. See /templates/records/glass-foreign-material and /templates/records/internal-audit-report.

    SQF / BRCGS / FSSC

Don't keep records you don't need

Not every record on this page applies to every operation. A coffee roaster doesn't need an allergen-verification log if no allergens cross the line. A restaurant doesn't need a mock recall record unless they hold inventory under a brand. Use the citation in each header to decide whether the record is required for your regime. Keeping records you don't need is its own form of risk — the inspector will read every one you write.

06How to use the library

Format, frequency, and where they live.

Three practical questions every operator asks when they print a new form.

  1. 01

    Which format do you actually use?

    Print the PDF for clipboard use on the floor. Most inspectors prefer paper for the in-the-moment record because handwriting is harder to back-fill. Keep a scanned or digital copy for long-term retention. For traceability records under SFCR §91 or FSMA 204, electronic format is required — and must be producible as a sortable spreadsheet within 24 hours.

  2. 02

    How often do you read it?

    A record is useless if no one reviews it. Build a weekly supervisor verification into every log — initials and date by a supervisor or QA lead, confirming they read the week's entries. This is the verification step under §117.165 and SFCR §86. Without it, the log can be argued to be self-checking, which makes it not a record at all.

  3. 03

    Where do they live?

    Two binders or two folders. The active 90 days lives near where the record is created — walk-in door, line workstation, receiving desk. After 90 days, move to a long-term retention binder or scanned archive. Under §117.315(c), off-site retention is fine as long as you can retrieve in 24 hours. The exception is the food safety plan itself, which must stay on-site.

07The retention timer

The 1-year, 2-year, and 24-hour rules.

Retention confusion is the single most common records question. The rules differ by regime:

FDA / FSMA / SFCR

2 years

21 CFR §117.315 — two years from creation date for all FSMA preventive-control records. SFCR §90 — two years from when the food was provided. FSMA 204 — two years (effective July 2028).

USDA-FSIS

1 or 2 years

9 CFR §417.5 — one year for slaughter and refrigerated product; two years for frozen, preserved, or shelf-stable. Different rules per product line in the same facility.

The retention clock starts on the date the record was created — not the date the product was made, sold, or consumed. If you packed product on January 1, 2026 and signed the receiving log for the ingredients on December 15, 2025, the receiving log clock starts December 15, 2025.

For multi-regime facilities (FDA-registered and SFCR-licensed, or FDA and USDA), apply the longer of the two retention periods. It's simpler than tracking which record sits under which rule.

08The Canadian section

CFIA-specific records most US operators miss.

If you're a Canadian operator, or a US operator shipping to Canada under a co-packing arrangement, three SFCR requirements are not on most US-built record templates.

  1. 01

    Traceability under §90 — one-step-back, one-step-forward

    The CFIA traceability rule is not just “keep your invoices.” The records must identify the food (common name, lot code or unique identifier, manufacturer), the immediate supplier, and the immediate customer (other than the consumer), along with dates received and dates provided. This applies even if you're a single-truck operation. The two-year retention starts on the date the food was provided.

  2. 02

    PCP-required documents under §89

    The Preventive Control Plan itself, plus the documents, methods, and records that demonstrate the plan is being implemented. Many small CFIA operators write the PCP and then never document the daily evidence that proves they're executing it. A CFIA inspector will ask for both.

  3. 03

    The 24-hour production rule under §91

    Traceability records must be produced to CFIA within 24 hours of a request (shorter if CFIA believes there's a risk). Electronic format must be plain text, single file, software-compatible. If your records are spread across three filing cabinets, a Dropbox folder, and an old laptop in the back office, you will not hit 24 hours. Build the production workflow before the inspector calls.

The Canadian Produce Marketing Association (CPMA) Traceability SFCR Guidance Document v2.1 is the most-detailed industry resource for SFCR §90 compliance.8 Read it once, then build the records workflow it describes. See /learn/cfia-sfcr for the deeper Canadian-regime guide.

09What auditors actually check

The five records inspectors open first.

From eight site visits across three regimes — two CFIA, a third-party SQF gap assessment, and shadowing inspections at peer facilities — the priority order is remarkably consistent. Inspectors don't read every record. They sample. They look at:

  1. 01

    The most recent 30 days of monitoring records

    Any gaps? A single missed temperature reading isn't fatal. A pattern of missed weekends or missed Mondays is.

  2. 02

    A random sample of deviations from the past year

    Pick ten. Was each closed with a documented corrective action? Did the corrective action prevent recurrence, or did the same deviation appear three weeks later?

  3. 03

    Training records for the line staff at the time of the last deviation

    Did the employee who caused or detected the deviation have current training in the relevant control? If not, training is a contributing root cause.

  4. 04

    Traceability response time

    The inspector hands you a lot code. Can you produce one-step-back and one-step-forward within 24 hours (SFCR §91 / FSMA 204)? Practice this. If you can't, the rest of your records don't matter.

  5. 05

    Calibration records for monitoring instruments

    Every probe thermometer, every pH meter, every metal detector. On schedule? Signed? The instrument is the foundation of every monitoring record, so a missed calibration cascades.

Show me the calibration log for the probe you used to take that reading. If the probe wasn't calibrated, the reading isn't valid, and neither is the log.

A CFIA inspector, two minutes into my second visit

For the full auditor-priority deep-dive, see /learn/audit-prep/what-auditors-actually-check.

10The defensible record

What every record row needs.

Eight fields, every row. Most free templates online have four or five. The three most-missed:

  1. 01

    Date and time

    The actual date and clock time. Not “morning” — “7:15 a.m.”

  2. 02

    Facility or unit identifier

    Which refrigerator, which line, which batch, which lot code.

  3. 03

    Threshold printed in the column header

    The required value plus the citation. “Refrigerator temp (≤41°F per §3-501.16)” — not just “Refrigerator temp.” An inspector who can't see the threshold assumes you don't know it.The most-missed

  4. 04

    Actual value or observation

    The number or note the recorder actually saw. Per §117.305, this is the legal definition of a record.

  5. 05

    Recorder initials

    Real initials of the person who took the reading. Not a stamp, not a typed name.

  6. 06

    Corrective action column

    Most rows will be blank. The column has to exist so when a reading goes out of range, the operator can document what they did.The second most-missed

  7. 07

    Supervisor verification

    A separate column where a supervisor initials and dates a periodic review — typically weekly. This is §117.165 verification. Without it, the log is self-checking.The third most-missed

  8. 08

    Concurrent creation

    The record must be created at the time the event occurs, not back-filled at the end of the week. §117.305(d) and §417.5 both require this. The single fastest way to lose an inspector's trust is to be caught back-filling.

Never back-fill

I've watched two operators lose audits over back-filled records. The inspector spotted the same handwriting across fourteen days of entries that were supposedly written by three different shifts. Back-filling is fraud. If you missed an entry, write “missed” with the date you discovered the gap and the corrective action you took. Honest gaps are recoverable; fake entries are not.

11Specialty operators

The records I add for specialty production.

If you're running a specialty operation — fermentation, sous-vide, reduced-oxygen packaging, mushroom cultivation, raw dairy — the baseline records aren't enough. For mushroom production, which is what I do, three additional records carry weight beyond the standard library:

  1. 01

    Water activity (aw) and oxygen monitoring

    For substrate sterilization, spawn runs, and packaged mushroom product. The aw reading is the single best predictor of mold or Clostridium growth in low-acid product. I log it at the end of every substrate batch and at packaging.

  2. 02

    Sterilization validation

    Time-temperature profile of every sterilization cycle, captured by a data logger inside the autoclave. The data logger printout gets stapled to the cycle log. Without this, you can't prove the sterilization actually achieved the kill step.

  3. 03

    Spawn batch genealogy

    One-step-back beyond the SFCR §90 requirement — tracing every fruiting batch back to its spawn source and substrate lot. This isn't mandatory under SFCR §90, but it's the only way to investigate a contamination event without recalling six months of inventory.

The Mushroomology chapter I contributed for Brill (Chapter 29, 2026) covers the underlying microbiology in more detail.9 The principle generalizes: every specialty production has a small set of records that are not on the FDA or CFIA template lists but that are non-negotiable for the product category. Find yours.

12Sibling templates

Where each record family lives on this site.

The records hub is the operational middle of the templates silo. The forward-looking plans live in one sibling; the standing policies live in another:

  1. 01

    The plans that drive the records

    See /templates/plans for the HACCP plan, food safety plan, recall plan, allergen control plan, and sanitation plan. These are the “what we will do” documents.

  2. 02

    The manuals that codify the policies

    See /templates/manuals for the food safety manual, GMP manual, and quality manual. These are the “here are the rules” documents.

  3. 03

    The Standard Operating Procedures (SOPs) the records prove

    See /templates/sops for the procedures that the daily records confirm are being executed.

  4. 04

    The worksheets that support verification

    See /templates/worksheets for CCP determination, hazard analysis, and validation worksheets.

  5. 05

    The audit checklist that ties everything together

    See /templates/audit-checklist for the inspector's-eye review of your full records-plus-plans-plus-manuals system.

  6. 06

    The temperature and cleaning record families

    See /templates/temperature-log and /templates/cleaning-log for the two most-used record families with their own dedicated hubs.

For the regulatory deep-dives behind each record requirement, see /learn/recordkeeping — and specifically the retention requirements guide for the cross-regime cheat-sheet.

13Where to start

Pick your first three records this week.

If you have nothing in place, build in this order. Skip ahead only if a regulation requires you to.

  1. 01

    The walk-in cooler log

    Twice daily. Threshold printed in the header. Tape it to the inside of the door so you can't walk past. This satisfies §117.190(a)(2) monitoring and SFCR §86 implementation.

  2. 02

    The receiving log

    Every incoming shipment. Temperature on arrival, supplier, lot code, reject criteria. This is the only record that satisfies SFCR §90 one-step-back traceability.

  3. 03

    The corrective action form

    Blank in the binder until something goes wrong. When it does, write what happened, what you did, and how you'll prevent it next time. This is §117.190(a)(3) and the record most likely to be sampled by an auditor reviewing your deviations.

Once those three are running for two weeks straight, add the cleaning log, the calibration log, and the cooking log. Build the rest as your operation needs them. The library is exhaustive on purpose — but starting with three records you actually maintain beats starting with twenty you don't.

The point of the record is the daily habit. The binder is the artifact.

Footnotes

1.21 CFR §117.305 (General requirements applying to records) — law.cornell.edu/cfr/text/21/117.305

2.21 CFR §117.190 (Implementation records required for this subpart) — law.cornell.edu/cfr/text/21/117.190

3.21 CFR §117.315 (Requirements for record retention) — law.cornell.edu/cfr/text/21/117.315

4.9 CFR §417.5 (HACCP Records, FSIS meat and poultry) — law.cornell.edu/cfr/text/9/417.5

5.SOR/2018-108 Safe Food for Canadians Regulations, sections 89–92 — laws-lois.justice.gc.ca

6.CFIA Traceability Regulatory Requirements — inspection.canada.ca

7.FSMA Section 204 / Food Traceability Rule compliance-date extension (Federal Register, August 2025) — federalregister.gov

8.CPMA Traceability SFCR Guidance Document v2.1 (June 2021) — cpma.ca

9.Mushroomology, Chapter 29 (Andrew Langevin, Brill 2026, ISBN 9789004751699) — degruyterbrill.com

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