Standard Operating Procedure (SOP) templates.

01The signature-block moment

What an inspector actually reads first.

The first inspector who opened my Standard Operating Procedure (SOP) binder in Brantford didn't read the cooking procedure. She flipped to the back page and looked at the signature block. Two columns: who on the line had been trained, and what version of the SOP they had been trained on. One column had a name. The other was blank. The conversation got harder for about twenty minutes.

That moment changed how I write every SOP. The procedure itself matters — but the part inspectors check first is whether the document is a controlled record with a trained operator behind it. An SOP without a version number, an effective date, and a training-record row is, to a regulator, an unwritten habit on paper. It drifts with turnover. It can't be audited.

“

The procedure tells me what you intended. The signature block tells me whether anyone on the line knows it.

”

What every Quality Assurance (QA) lead learns by their second audit

Every SOP template on this page carries the same eight content elements and the same four document-control elements. The threshold is cited to the regulation behind it. The training-record row is built into the bottom. The corrective-action block exists even when most operators will skip it. The point is that the document is defensible the day you print it — not the day after the inspector points out what was missing.

02What an SOP is

What an SOP is, and what makes one inspector-defensible.

A Standard Operating Procedure (SOP) is a written, dated, controlled document describing how a routine activity is performed to protect food safety. The operative word is written. A procedure an experienced cook performs flawlessly in their head is, to the regulator, an unwritten habit. It can't survive the turnover of the person who knows it.

Every inspector-defensible SOP carries eight content elements. The three most-missed are monitoring, corrective action, and the document-control block — the same three that generic Word-template SOPs almost universally skip.

1. 01

   Title

   The activity covered. “Two-stage cooling of cooked Time/Temperature Control for Safety (TCS) foods” — not “Cooling.”

2. 02

   Purpose

   The hazard being controlled. “Control Clostridium perfringens growth during cooling of cooked TCS foods.” The hazard tells the inspector the SOP was written by someone who knew why the procedure exists.

3. 03

   Scope

   The products, processes, and employees the SOP applies to. “All cooked soups, stocks, sauces, braised meats. All line cooks and prep staff.”

4. 04

   Responsibility

   Who performs the activity, and who verifies. “Performed by: line cook on duty. Verified by: shift supervisor at end of shift.”

5. 05

   Procedure

   Step-by-step in plain operational language. Numbered steps the line can follow without a translator. Define every acronym the first time it appears.

6. 06

   Monitoring

   How compliance is verified at the time of the activity. Probe temperature, sanitizer parts-per-million (ppm), visual check, stopwatch. Without this, the SOP describes an intention, not a verified procedure.Most-missed element

7. 07

   Corrective action

   What to do when the monitoring step shows the procedure failed. Where to record it. “If product temperature is >70°F at the 2-hour mark, discard and document on the corrective-action log.”Most-missed element

8. 08

   Records

   Which log captures the activity as evidence. Pairs every SOP with a matching log so the procedure leaves a paper trail.

Plus four document-control elements that make the SOP a controlled record rather than a loose page:

1. 01

   SOP number and version

   An identifier like SOP-COOK-001 Rev. 03. The number tracks the SOP through versions; the revision number proves the document has been maintained.

2. 02

   Effective date and next review date

   When the current version became active, and when it's scheduled for review. Annual review at minimum, plus after any regulatory or equipment change, plus after any incident.

3. 03

   Approval signature

   Signed by the food safety lead or owner. The signature converts a draft into the current operating standard.

4. 04

   Training-record reference

   The link to the training log proving the line was trained on this version. Without it, the SOP has no audit defense.

When an inspector says “your SOP isn't sufficient,” they almost always mean one of these twelve elements is missing or stale. The starter pack at the bottom of this page ships every SOP with all twelve elements already in place.

03The 20 operational basics

The 20 SOPs every food operation needs.

The library indexed below covers the twenty operational basics that show up in every U.S. and Canadian rule. The catalog is the same whether you run a 30-seat restaurant in Ontario, a 12-person bakery in Ohio, or a small Hazard Analysis and Critical Control Points (HACCP)-plan meat plant in Quebec. What changes is which regulation cites it and how prescriptive the rule is.

1. 01

   Cooking SOP

   Poultry and stuffed foods 165°F for 15 seconds. Ground meat 155°F for 17 seconds. Whole-muscle beef, pork, seafood, and shell eggs 145°F for 15 seconds. One SOP, with a per-product temperature table.FDA Food Code §3-401.11

2. 02

   Cooling SOP

   Two-stage cooling: 135°F to 70°F within 2 hours, then 70°F to 41°F within an additional 4 hours. Total 6 hours. USDA Food Safety and Inspection Service (FSIS) Appendix B is stricter for meat plants — 130°F to 80°F in 1.5 hours, then 80°F to 40°F in 5 more hours.FDA Food Code §3-501.14

3. 03

   Reheating SOP

   Previously cooked TCS food reheated to ≥165°F within 2 hours before being placed in hot holding.FDA Food Code §3-403.11

4. 04

   Hot-holding SOP

   ≥135°F continuously. Probe every 2 hours minimum and log.FDA Food Code §3-501.16

5. 05

   Cold-holding SOP

   ≤41°F continuously. Probe every 2 hours during service; check at open and close.FDA Food Code §3-501.16

6. 06

   Thawing SOP

   Four approved methods: under refrigeration, under cold running water ≤70°F for ≤4 hours, as part of cooking, or in a microwave followed immediately by cooking. Counter-thawing is a violation in every U.S. and Canadian jurisdiction.FDA Food Code §3-501.13

7. 07

   Handwashing SOP

   ≥20 seconds with soap and friction, water ≥100°F, at a designated handwashing sink. Wash before starting work, after any contamination event, after using the restroom, between raw and ready-to-eat handling.FDA Food Code §2-301.12 / §2-301.14

8. 08

   Glove-use SOP

   No bare-hand contact with ready-to-eat (RTE) food. Change gloves between proteins, after any contamination, and at minimum every 4 hours of continuous use.FDA Food Code §3-301.11 / §3-304.15

9. 09

   Cleaning SOP

   Per-area cleaning with detergent and water. Frequency depends on the surface and the soil load. Pairs with the Master Sanitation Schedule (MSS).21 CFR §117.35 / FDA §4-602

10. 10

    Sanitizing SOP

    Chlorine 50–100 ppm, quaternary ammonium 200–400 ppm, or iodine 12.5–25 ppm. Verified with a test strip every batch, logged as a number.FDA Food Code §4-501.114

11. 11

    Dishwashing SOP (three-compartment sink)

    Wash ≥110°F, rinse, sanitize at the correct ppm OR high-temperature ≥180°F final rinse. Test strips or heat-sensitive labels every shift.FDA Food Code §4-301.12 / §4-501.114

12. 12

    Employee illness SOP (Big 6)

    Exclude or restrict any food handler reporting symptoms or diagnosis of Norovirus, Shigella, Shiga toxin-producing Escherichia coli (STEC), Salmonella Typhi, nontyphoidal Salmonella, or Hepatitis A.FDA Food Code §2-201.11

13. 13

    Allergen control SOP

    Segregation in storage, dedicated tools or full clean-down between allergen and non-allergen runs, label verification at packaging, supplier-allergen control on incoming ingredients. Big 9 allergens: milk, eggs, fish, crustacean shellfish, tree nuts, peanuts, wheat, soybeans, sesame.21 CFR §117.135(c)(2) / FALCPA / FASTER

14. 14

    Receiving SOP

    Probe TCS food at the truck. Refrigerated ≤41°F. Frozen ≤0°F with no signs of partial thaw. Reject damaged packaging. Verify Certificate of Analysis (COA) and seal where required. Capture Key Data Elements (KDEs) for FSMA 204 listed foods.21 CFR §117.80 / FSMA 204

15. 15

    Shipping SOP

    Vehicle pre-inspection, cold-chain temperature at loading, trip temperature monitoring, KDE capture on outbound traceability lots.FSMA Sanitary Transportation Rule

16. 16

    Mock recall SOP

    Annual minimum. Two-hour target to reconstruct the chain from raw-ingredient lot to finished-product shipment. Recall team contacts current within 30 days.21 CFR §117.139 / SFCR §84-85

17. 17

    Foreign object SOP

    On any foreign-object find: stop the line, quarantine back to the last clean point, root-cause the source, document.21 CFR §117.135(c)(1) / BRCGS §4.9

18. 18

    Glass break SOP

    Glass-and-brittle-plastic register maintained. On break: isolate the area, quarantine product within a defined radius, document close-out.BRCGS §4.9.6 / SQF §11.6.4

19. 19

    Pest sighting SOP

    Log the sighting on shift, notify the pest contractor, document the corrective action, track sighting trends month over month.21 CFR §117.35(c) / SFCR §60

20. 20

    Sanitation Standard Operating Procedure (SSOP)

    USDA-specific. Pre-operational and operational sanitation for federally inspected meat, poultry, and egg facilities. Signed daily by the responsible employee. Records under 9 CFR §416.16.9 CFR §416.12

21. 21

    Thermometer calibration SOP

    Ice-point calibration weekly and any time a probe is dropped. Reading must be 32°F ± 2°F (0°C ± 1°C). Pairs with the temperature-log program.FDA Food Code §4-302.12

The starter pack at the bottom of this page ships all twenty SOPs in one bundle.

04SOPs by regulation

Which regulation requires which SOP.

The SOP catalog above is the same across jurisdictions. The rule that requires it — and the inspector who reads it — changes. Match your operation to the regulatory anchor that applies, then download the SOPs that cite that anchor in the header.

1. 01

   Restaurant or retail food establishment

   Restaurants, cafes, food trucks, grocery delis. State or provincial health departments enforce the Food Code, often with local amendments. Cooking, cooling, reheating, holding, handwashing, glove use, dishwashing, illness exclusion, and sanitizing SOPs are the operational core.FDA Food Code 2022

2. 02

   Food and Drug Administration (FDA)-registered manufacturer

   Under the Food Safety Modernization Act (FSMA) Current Good Manufacturing Practices (cGMP) and preventive controls rule. §117.135 requires written process, allergen, and sanitation controls. Each control must be written, monitored, verified, and recorded. Records retained 2 years under §117.315.21 CFR §117.135

3. 03

   USDA-inspected meat, poultry, or egg plant

   Daily-signed Sanitation Standard Operating Procedures (SSOPs) required by §416.12. Pre-operational plus operational. The SSOP is the document FSIS inspectors open first. HACCP plan under Part 417 covers the process side. Records retained 1 to 2 years depending on product per §416.16.9 CFR Part 416 (SSOP) + 9 CFR Part 417 (HACCP)

4. 04

   Canadian licence holder

   Safe Food for Canadians Regulations. §86 requires a written Preventive Control Plan (PCP) covering biological, chemical, and physical hazards plus sanitation, hygiene, allergen, traceability, complaints, and recall — the Canadian SOP layer. §87 requires monitoring and verification records. CFIA enforces.SOR/2018-108 (SFCR) §86 + §87

5. 05

   Global Food Safety Initiative (GFSI)-certified operation

   Three schemes, slightly different paperwork expectations. SQF Edition 10 is effective January 2, 2027 and tightens change management. BRCGS Part 3 §3.1 documented procedures, §4.9 foreign body and glass, §4.11 housekeeping, §5.3 allergen, §7.2 training. FSSC 22000 V6 layers ISO 22000:2018 with ISO/TS 22002-1 Prerequisite Programs (PRPs) and adds food defense and food fraud as V6 additions.SQF Edition 9 / BRCGS Issue 9 / FSSC 22000 V6

The takeaway: the same twenty SOPs map to every major rule. The header citation changes depending on which inspector is reading it.

05SOP vs SSOP

SOP vs SSOP — the terminology distinction operators get wrong.

The two terms get used interchangeably online. They aren't the same.

Functionally an SSOP is an SOP — but if your facility is FSIS-regulated, the document and records must satisfy 9 CFR Part 416 specifically, not just 21 CFR §117. Many small processors maintain both: SSOPs for sanitation under the USDA rule, generic SOPs for everything else.

06Training-bound versioning

Training-bound versioning — what makes the SOP audit-ready.

The SOP is half the document. The other half is the training record that ties an employee by name to a specific version on a specific date. Without that tie, the SOP has no audit defense. This is what the inspector was looking for when she flipped to the back page of my binder.

The flow is straightforward but easy to break under turnover. Here is what a defensible version-control loop looks like in practice:

1. 01

   The SOP exists at Rev. 01, effective 2026-03-15

   A line cook named Maria L. is trained on Rev. 01 on 2026-03-18. She signs the training log. The training log identifies the SOP number, the revision, and the date she was trained.

2. 02

   The SOP updates to Rev. 02 on 2026-09-01

   For example, the Food Code was updated and the cooking temperature table now reflects the current text. The new version gets a new effective date, a new approval signature, and a new next-review date.

3. 03

   Everyone previously trained on Rev. 01 needs re-training within 30 days

   The supervisor pulls the training matrix, sees who was on Rev. 01, schedules them for re-training, and captures new signatures against Rev. 02.

4. 04

   The inspector opens the binder, sees Rev. 02 effective 2026-09-01, and asks “show me training records for the current version”

   The supervisor hands over the Rev. 02 training matrix. Every name on the line is on the current version. The signature block has a name and a date next to every operator.

This is the loop the paid HACCPlan product automates — auto-generated re-training tasks when a version increments, surface alerts when an employee is on an outdated revision, audit-trail report. The free templates on this page include the training-record row at the bottom of every SOP so paper-based or spreadsheet-based operators can implement training-bound versioning by hand. The product upgrade is automation. It isn't a feature hidden behind a paywall.

This loop is aligned to 21 CFR §117.4 (training of individuals), SQF Edition 9 §11.6.7, BRCGS Issue 9 §7.2, and FSSC 22000 V6 via ISO/TS 22002-1 §13.

07The twelve-element checklist

What every defensible SOP includes — the twelve-element checklist.

Before you print an SOP and post it on the wall, run it through this checklist. Most off-the-shelf Word templates miss at least three of these. Every template in the HACCPlan starter pack ships with all twelve.

1. 01

   Title

   Names the activity, not the document type. “Two-stage cooling of cooked TCS foods” — not “Cooling SOP.”

2. 02

   Purpose

   Names the hazard being controlled. The hazard is what the rule is protecting against, not the operational outcome.

3. 03

   Scope

   Products, processes, and employees the SOP applies to.

4. 04

   Responsibility

   Who performs the activity, who verifies, who approves changes.

5. 05

   Procedure

   Numbered steps in plain operational language. Every acronym defined first time it appears.

6. 06

   Monitoring

   How compliance is verified at the time of the activity. The threshold cited to the rule.

7. 07

   Corrective action

   What to do when monitoring shows the procedure failed, and where to record it.

8. 08

   Records

   Which log captures the activity. Every SOP pairs with at least one log.

9. 09

   SOP number and version

   Identifier plus revision number. SOP-COOL-001 Rev. 02.

10. 10

    Effective date and next review date

    When the version became active. Annual review at minimum.

11. 11

    Approval signature

    Signed by the food safety lead or owner.

12. 12

    Training-record reference

    Links to the training log that proves the line was trained on this version.

08Format and language

Three formats, three languages — the way real kitchens read.

A printable PDF on the wall covers the post-inspection rebuild operator. A Word file covers the operator who needs to brand or modify the template. A Google Doc covers the operator who runs their document control in Drive and needs cloud version history. The HACCPlan starter pack ships all three formats for every SOP — print one, customize one, version one.

The language piece is the part most template libraries miss. The reality of a U.S. or Canadian kitchen line is bilingual or trilingual. Two of my line cooks read Spanish first. The English SOP I taped to the wall in Year One was decoration. They could follow it because they had been trained — but if an inspector had asked them to read the cooking temperatures off the document, the answer would have been long.

The starter pack ships every SOP in English, French, and Spanish:

1. 01

   English

   Default. Available day one for every SOP in the catalog.

2. 02

   French

   Native-speaker reviewed. Released per SOP as translation review completes through 2026.CFIA Quebec, Ontario bilingual operations

3. 03

   Spanish

   Native-speaker reviewed. Same rolling release.U.S. restaurants, food trucks, agriculture, small manufacturers

09How to use these

How to use these templates (and when to upgrade).

Start with the SOPs that map to your highest-frequency operations. For most restaurants, that is cooking, cooling, handwashing, dishwashing, and the per-shift sanitation procedure. For most small manufacturers, it is receiving, allergen control, cleaning, sanitizing, and the production-process SOPs. Build the document control register in parallel — a single spreadsheet that tracks SOP number, revision, effective date, next review date, and the training-record reference for each one.

1. 01

   Paper-and-binder

   Print the PDF. Sign the approval block. Tape it to the wall next to the activity it covers. Capture training signatures on the back page. This is enough for a small restaurant or food truck operating under the FDA Food Code or provincial public-health authority.

2. 02

   Spreadsheet-managed

   Maintain the document control register in Excel or Google Sheets. Each SOP gets its own row. Set a monthly calendar reminder to review expiring SOPs and re-issue training tasks. This scales to about 20 employees and 30 SOPs before it starts breaking down.

3. 03

   Software-managed

   When you cross 20 employees, multiple shifts, or more than one location, the version-control and training-record loop starts to drift. This is the point at which automated SOP management — auto-generated re-training tasks, version-increment alerts, multi-language sync — earns its cost. The free templates remain the source document; the software is the workflow around them.

The free starter pack is complete. Every regulation citation, every monitoring step, every corrective-action block, every training-record row is in the PDF you download. The paid product adds automation and version-control plumbing. It does not add content removed from the free document.

10Why this library exists

Why I built this library.

Three things drove me to write a full SOP library instead of just buying one.

The first was the signature block in the back of my binder. The blank column changed how I thought about every procedure I wrote afterward. The procedure isn't the document. The training tie-in is the document.

The second was a 5-gallon batch of brisket I cooled the wrong way six months into running the facility. I pulled it out of the walk-in at 62°F the next morning. Tossed the whole batch. There was no cooling SOP on the wall because nobody had written one. By the end of that week, every cooling procedure was on paper, dated, posted, and trained — and that template is the one in the starter pack today.

The third was a consultant who quoted me $4,800 for eighteen generic Word files I'd already seen on Google. I built mine instead — regulation-cited, version-controlled, training-record row on every page. Those same SOPs are here, free, in three languages. What the paid product adds is the version-control and training-record automation — not the SOPs themselves.

11FAQ

Common questions.

1. 01

   Are these really free? What's the catch?

   There is no catch on the documents. The PDFs, Word files, and Google Docs templates are complete — every regulation citation, every monitoring step, every corrective-action block. The email address you provide goes onto a six-email nurture sequence and you can unsubscribe at any time.

2. 02

   Will inspectors actually accept these?

   An SOP becomes inspector-acceptable when it is approved by your food safety lead, dated, posted, trained on, and verified. The template is the starting frame. You fill in the facility-specific values (your unit numbers, your responsible employees, your matching log names), sign the approval block, and train the line on the current version. That document is then yours — not HACCPlan's — and it carries the same weight as any other written procedure under §117.135 or §416.12.

3. 03

   What's the difference between an SOP and an SSOP?

   An SOP is any written procedure. An SSOP is specifically a USDA-FSIS sanitation procedure under 9 CFR §416. If you operate a federally inspected meat, poultry, or egg plant, you need SSOPs that meet §416 — not just generic cleaning SOPs. See section 5 above.

4. 04

   Do I need every SOP in the library?

   No. Match the catalog to your operations. A bakery doesn't need a poultry-cooking SOP. A small juice processor doesn't need a glove-use SOP if they have no hand-pack step. Download the ones that match what you actually do. The starter pack is a superset — pick the operational subset and ignore the rest.

5. 05

   Are the templates editable?

   Yes. The PDF is fillable for the facility-specific fields (your name, your unit numbers, your dates, your signatures). The Word and Google Docs versions are fully editable. If you want to add facility branding, change the layout, or merge two SOPs into one — that is the Word or Docs version.

6. 06

   How often are the SOPs updated?

   Annually at minimum, plus on any regulatory change. When the FDA publishes the next Food Code update or CFIA issues a guidance revision, the affected SOPs are updated within 60 days. The version number on the cover page tells you which revision you have.

7. 07

   French and Spanish versions — when?

   English is available today for every SOP. French and Spanish are rolling out per SOP through 2026 as native-speaker review completes. The starter pack ZIP contains every translation available at the moment of download.

8. 08

   How long do I need to keep the records that pair with these SOPs?

   FSMA preventive controls records: 2 years (21 CFR §117.315). FSIS Sanitation SSOP records: on-site 6 months, total 12 months (9 CFR §416.16). Food Code retail: per state/province retention requirement, commonly 90 days to 1 year. SQF and BRCGS: 2 years typical. The starter pack includes a one-page retention summary by jurisdiction.

12Where to start

Pick your first three SOPs this week.

If you don't have any SOPs in place, do not try to build all twenty at once. Start with the three that fail most often on inspection and that the line will use every shift.

1. 01

   Handwashing SOP

   Twenty seconds, water ≥100°F, friction, designated handwashing sink. Post above every handwashing sink. Train every employee on the current version in the first week. Pairs with the per-shift hygiene observation log.

2. 02

   Cooling SOP

   Two-stage cooling with the 2-hour and 6-hour checkpoints. Most-failed log on every restaurant inspection. Pairs with the cooling temperature log.

3. 03

   Sanitizing SOP

   Sanitizer concentration in ppm verified with a test strip every batch. Post next to the three-compartment sink. Pairs with the per-shift cleaning and sanitizer log.

Once those three are running every shift for two weeks straight — with signatures and supervisor verification — add cooking, cold holding, and the employee illness SOP. Add the rest as your operation needs them. The full library is in the starter pack at the top of this page; the point is the daily habit, not the binder.

Pair every SOP with its matching log. The SOP describes the procedure. The log proves the procedure happened. Without the log, the SOP is a wall decoration.

Footnotes

1.21 CFR §117.135 (Preventive Controls) — ecfr.gov

2.21 CFR §117.4 (Training) — ecfr.gov

3.9 CFR Part 416 (USDA-FSIS Sanitation SSOP) — ecfr.gov

4.FDA Food Code 2022 — fda.gov

5.FDA Cooling Cooked TCS Food guidance — fda.gov

6.FDA Employee Health and Personal Hygiene Handbook — fda.gov

7.SOR/2018-108 Safe Food for Canadians Regulations — laws-lois.justice.gc.ca

8.CFIA Preventive Controls — inspection.canada.ca

9.USDA-FSIS Sanitation SOP Guide — fsis.usda.gov

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