Food safety software built for restaurants.

I do not run a restaurant. I run a CFIA-licensed (Canadian Food Inspection Agency) mushroom production facility in Brantford, Ontario, and a private-label division that ships product under multiple client brand names from one kitchen. The compliance pain is structurally identical to a 5-unit restaurant chain: different brand on every label, one set of records, one inspector who shows up unannounced. I built HACCPlan because I needed it for my own operation. The restaurant build exists because restaurant operators kept asking me to adapt the same data model to their floor. Here is what I learned.

01The mismatch

Why your restaurant needs different software than a manufacturer or a paper binder.

Most restaurant food-safety tools were built by one of two kinds of people: software engineers who have never worked a Friday-night line, or food-safety consultants who left the kitchen 15 years ago. The result is software that looks beautiful on a corporate laptop and is miserable to use at 7:42 PM with greasy gloves and eight minutes between ticket dumps.

The paper alternative is worse. A clipboard hung on the walk-in door is fine for a 1-unit operation where the owner is on the line. It falls apart the moment you add a second store, a second shift, or a sous chef who back-fills the temp log at 10:30 PM. Inspectors know. You know. Everyone pretends.

The job of restaurant food-safety software is not to invent new compliance work. The Food Code already tells you what to monitor. The job is to turn the digital signals that already exist (walk-in probes, dishwasher rinse, point-of-sale) into the format the inspector wants to see, without making the line cook do the work twice.

02The hazards

The five hazard buckets that drive every restaurant inspection.

What gets the average restaurant in trouble? Not exotic pathogens, not rare equipment failures. The CDC tracks contributing factors for every foodborne outbreak, and the same five buckets show up over and over. Memorize these, build a record against each one, and you have answered 90% of what an inspector will ask.

1. 01

   Temperature abuse

   Cooler down overnight. Hot-line below 135 degrees Fahrenheit. Cold-line creeping past 41. Chili cooled in a 6-inch deep pan and still at 90 degrees four hours later. Reheating a brisket to "warm" instead of 165 in under two hours. Temperature provisions (FDA Food Code section 3-501-series) are consistently the top family of critical violations in NYC and LA County open inspection data.

2. 02

   Cross-contamination

   Raw chicken sitting on the shelf above bagged spinach. The same cutting board used for raw beef and tomato slicing in the same shift. Gloves changed once an hour instead of between tasks. Food-contact surfaces wiped with the bar towel that has been around since 11 AM.

3. 03

   Ill food workers

   A line cook with vomiting symptoms still working the cold station because he needs the shift. No written health policy on file. No record that the manager asked. Norovirus spreads through ill workers and is consistently the number one contributing factor in CDC restaurant outbreak data. The Food Code is not subtle about this (section 2-201.11).

4. 04

   Allergen mismanagement

   Shared fryer oil between battered shrimp and french fries. Pesto with pine nuts subbed into the staff meal version of a dish. A new menu item that contains sesame oil and was never added to the allergen matrix. Cross-contact lawsuits are the fastest-growing restaurant liability vector by some margin.

5. 05

   Handwashing and personal hygiene

   Handwash sink blocked by a stack of bus tubs. No soap. No warm water. Gloves used as a substitute for handwashing instead of an addition to it. Handwash-sink violations (section 5-205.11) are the single most-cited individual violation across most major-city databases.

Every one of these is something the Food Code already controls for. Every one is something a digital log plus a real-time dashboard can catch. The intervention point is recordkeeping discipline. Not new regulation.

03The Food Code

The FDA Food Code sections every operator should know by heart.

Quick context on what governs you. Restaurants are regulated as retail food establishments, and the framework is the FDA Food Code as adopted by your state, not FSMA (the Food Safety Modernization Act). FSMA's preventive-controls rule for human food (21 CFR Part 117) explicitly exempts retail establishments under section 117.5(g). What applies is the Food Code edition your state has adopted — most are on the 2017 edition, a smaller number on 2022 (the current edition), some still on older ones. Your local health department is the enforcer.

Look up your state's adoption status before you commit to a checklist. The FDA publishes a State Adoption Tracker that tells you which edition and which amendments. Below are the sections an inspector will reach for first.

A few more that drive inspections: section 5-205.11 (dedicated handwash sink, accessible at all times, used for nothing else), section 3-501.17 (date marking — refrigerated ready-to-eat TCS food held more than 24 hours marked, max 7 days at or below 41), and section 3-501.19 (Time as a Public Health Control — written procedures permitting up to 4 hours at any temperature, useful for buffets and sushi service).

Note: TCS stands for Time/temperature Control for Safety — the foods (meat, poultry, fish, dairy, cooked starches, cut leafy greens, cut tomatoes, cut melons, sprouts, garlic-in-oil) where time and temperature are the primary controls. PIC is the Person In Charge — the manager on duty responsible for active managerial control.

04ADDE Act

What changes on July 1, 2026 in California — and why every chain operator should be watching.

California signed the ADDE Act (SB 68) on October 13, 2025, and it takes effect July 1, 2026. The law applies only to restaurants with 20 or more locations nationally — large chains, not independents — and requires that every menu item disclose the presence of any of the Big 9 allergens. Disclosure can be on the printed menu or digital (QR code, app), but if you offer digital, you also have to offer a print option on request. Enforcement runs through CDPH (the California Department of Public Health) and local health agencies, with existing health-code monetary fines as the penalty mechanism.

If you operate 20 or more locations and any of them are in California, this is a real software-and-process project. If you operate fewer than 20 locations, the law does not apply to you yet — but section 3-602.12(C) of the Food Code already says you must provide accurate written allergen information when asked. A live allergen matrix is the cleanest way to do that without depending on a line cook to remember.

05Multi-location

The multi-location problem nobody solves at SME prices.

Here is the structural reality. A 5-unit chain has roughly five times the failure surface but rarely five times the food-safety staff. The director of operations at a 20-store fast-casual cannot personally verify that Store 7's walk-in was logged at 8 AM Tuesday. She infers it from inspection scores (lagging 30 to 90 days), from field consultant visit reports (one store at a time, monthly), and from internal QA audits (also lagging). The problem is not policy. The problem is visibility.

A real-time dashboard turns compliance from inference into observation. The features that matter, in operator terms:

1. 01

   Per-location compliance score, updated daily

   Logs completed against logs required. Open critical violations. Training overdue. CFPM cert expiring in the next 30 days. One number per store, drill down on tap.

2. 02

   Exception alerts that page the right person

   Walk-in temp missed twice in 48 hours sends an SMS to the store manager and a CC to the DO. Cooling log not completed on a 6-quart batch of chili pages the chef on duty. The point is to catch the problem at hour 3, not at the next inspection.

3. 03

   Brand-standard SOP push

   Corporate publishes one HACCP plan, one allergen matrix, one opening checklist, one closing checklist. Every location inherits it. Local variations (a unique appliance, a regional menu item) require approval and route through corporate so the master record stays clean.

4. 04

   Audit-trail integrity

   Logs entered at the time of the check, by the person who did it, on the device that was present. Back-dating blocked or flagged. Auto-timestamp from the device clock, not a typed time the cook can fudge.

5. 05

   CFPM and food-handler card tracker per location

   A 20-store chain has roughly 40 to 60 CFPMs (one or two per location per shift) and 500 to 800 food-handler cards (every employee handling food). Renewal alerts at 60, 30, and 7 days. Failure mode without tracking: someone's card lapses, the inspector finds it, the store gets cited.

“

I have 12 locations. My field consultants spend six hours a week driving between stores to check that the temp logs are actually being filled out. Half the time they are filled out at 4 PM for the whole day. We need to see this in real time, not as a Monday-morning report card.

”

Composite — director of operations, regional fast-casual

The reason this rarely gets solved at SME pricing is structural: the platforms that do multi-location dashboards well (SafetyChain, Crisp) are priced for chains with 500 stores and a corporate food-safety team. The platforms that are priced for 3-to-20-unit operators (Jolt, FreshCheq, FoodDocs) treat multi-location as an add-on rather than a first-class design constraint. HACCPlan's multi-tenancy logic came directly from my private-label division, where Nature Lion produces under several client brand names from one kitchen — same data model, different label. That model adapts cleanly to multi-concept and multi-location restaurant operations without per-location pricing at the lower tiers.

06The build

What is inside the restaurant build of HACCPlan.

None of this is generic software with a "restaurant" label glued on. Each piece exists because a real operator needed it and asked.

1. 01

   Tablet-first floor UI

   Every log entry is a single-task screen with large tap targets (sized for gloved hands — closer to 64 points than the standard 44). Auto-timestamp from the device clock. Voice entry for hands-busy moments ("walk-in three eight, freezer five"). Photo capture for probe readings, glue traps, and allergen sub-recipes. Offline mode that holds the entry locally when the kitchen wifi drops at peak service and syncs when it comes back.

2. 02

   Bluetooth probe integration

   The pocket thermometer reads the food, the reading goes straight into the cooking or cooling log on the tablet — no transcription, no back-fill. Supported probes (verify the current list before you commit) include the Thermapen Bluetooth and several Cooper-Atkins and Comark models. The cooking log knows the section 3-401.11 target for the dish you selected and flags an under-temp before the dish leaves the line.

3. 03

   IoT temperature sensor support, exception-based monitoring

   The walk-in, the freezer, the hot well, and the fryer oil bath increasingly come wifi-instrumented. A wireless probe ($30 to $80) reports every five minutes to a hub, which uploads to the dashboard. Manual logs become exception-based: the manager verifies the automatic reading once per shift instead of recording four readings per fridge per day. What IoT does not replace: cooking temperatures (point-in-time, probe in the food), employee illness logs (pure human input), handwash and sanitizer cadence (observational), cooling logs (require time-stamped 135-to-70-to-41 checks on the specific food). The healthy stack is IoT for ambient equipment plus tablet-first manual logs for everything else.

4. 04

   Big 6 illness log with FDA Form 1-A on file

   Form 1-A signed by every food employee at onboarding, stored against the employee record, retrievable in two taps for the inspector. Daily verbal check digitized — the PIC checks a box on shift open, the log timestamps. Exclusion and restriction decisions logged with the reason and the return-to-work date.

5. 05

   Per-item allergen matrix, ADDE-ready

   Add a menu item with its recipe. The system maps each ingredient to the Big 9 plus mustard and sulphites for Canadian operations. Cross-contact flags (shared fryer, shared utensils, shared boards) raised against the recipe. Exportable for printed menu, digital menu, QR-code disclosure, and table tent in the formats the ADDE Act requires.

6. 06

   CFPM and food-handler card tracker

   One record per employee with role, location, certification type, issue date, expiry, and renewal status. Bulk procurement workflow (some operators run their food handler enrollment in batches through one accredited provider). Manager-on-duty proof at any point in the last 12 months on demand for the inspector.

7. 07

   Inspection-day binder, one tap

   HACCP plan. Last 30 days of temperature logs. Employee illness log. CFPM certificate. Food-handler card register. Allergen menu disclosure. Cleaning schedule. Pest log. Water test. Training log. The full packet the inspector will ask for, generated in the order they typically work through it, exportable as a single PDF or visible directly on the tablet you hand them.

8. 08

   Multi-location dashboard

   Per-store compliance score, daily. Exception alerts to SMS or email. Brand-standard SOP push. Audit-trail integrity controls. CFPM and food-handler tracker rolled up to the corporate level. Designed so the DO sees Store 7's missed walk-in log on Tuesday morning, not in next month's inspection report.

07Starter kit + templates

Where to start — the free templates that cover the most-failed logs.

If you are not ready to commit to software, start with the logs that get cited most often. Each of these is a fillable PDF you can use on a tablet or print to a clipboard. No account needed, no email gate.

Most operators run on the free templates for a few weeks before deciding whether the software fits. That is the right order. Get the logs filled out reliably on paper first; the software is just the version that keeps the records integrated, time-stamped, and inspector-ready.

08Getting started

What the first 30 days on HACCPlan actually look like.

A realistic onboarding for a single-location restaurant runs roughly like this. Multi-location chains add a corporate-setup week up front.

1. 01

   Days 1 to 3 — set up the basics

   Create the location, add the manager and CFPM details, upload the existing HACCP plan (or generate a starter from the built-in template), import the current menu. Sign the FDA Form 1-A for the manager-on-duty.

2. 02

   Days 4 to 10 — load the team

   Add every food employee, assign roles, attach food-handler cards with expiry dates, sign Form 1-A. Set up exception-alert routing (which manager gets paged for what).

3. 03

   Days 11 to 20 — go live on the logs

   Switch the temperature, cooking, cooling, hot/cold hold, dishwasher, and cleaning logs from paper to the tablet. Pair Bluetooth probes if you use them. Spend one shift per station shoulder-to-shoulder with the line cook making the entries until the rhythm clicks. Keep the paper backups for the transition month — belt and suspenders.

4. 04

   Days 21 to 30 — build the allergen matrix

   Map every menu item to the Big 9. Flag cross-contact (shared fryer oil, shared boards). If you have a California location and 20+ stores nationally, this is where ADDE prep starts. Generate the printed and digital disclosure formats in parallel so the next menu print run is clean.

By day 30 you should be running the inspection-day binder export against a real practice run. Hand it to the GM and have her pretend to be the inspector. If she can find the cooling log for last Tuesday's chili in under 30 seconds, the system is working. If not, that is what month two cleans up.

Footnotes

1.FDA Food Code 2022 — full PDF — fda.gov

2.FDA Food Code — State Adoption Tracker — fda.gov

3.FDA Food Code 2022 — Summary of Changes (sesame, written allergen disclosure §3-602.12(C)) — fda.gov

4.21 CFR §117.5(g) — FSMA preventive controls retail exemption — ecfr.gov

5.CDC MMWR — Contributing Factors of Foodborne Illness Outbreaks (NORS 2014–2022) — cdc.gov

6.FDA Form 1-A — Conditional Employee / Food Employee Reporting Agreement — fda.gov

7.California SB 68 (ADDE Act) — effective July 1, 2026 — leginfo.legislature.ca.gov

8.National Restaurant Association — 2026 State of the Industry — restaurant.org

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