Food safety management system for a restaurant: what it is and what goes in it
A food safety management system, or FSMS, is the set of written steps, checks and records a kitchen uses to keep food safe every day. For a US restaurant it is not a product you buy or a certificate you must hold. It is your HACCP-style plan, your daily logs, your cleaning and pest routines and your staff training, kept together and kept up to date.
This page is for owners and managers who keep seeing "FSMS" or "food safety management system" and want to know what it means for one restaurant. It lists the parts, what to write for each, and when the formal ISO version matters. If you want the plan and logs built from your own menu, see your plan. No card.
What "food safety management system" means
The phrase comes from international standards. ISO 22000 is the best known: it sets out what a food business needs in place to control hazards, across a whole supply chain, and a certifier can audit a company against it [1]. In the UK, the term is also used for the written system a small caterer keeps to meet the law.
The US Food Code does not use "FSMS" as a rule. It asks the person in charge to show "active managerial control": a manager who actively works to prevent the main causes of foodborne illness, using training, procedures and monitoring [2]. In practice that is the same idea. A restaurant with a plan, logs, a trained team and a manager who checks them has an FSMS, whatever it is called.
So when a customer, a landlord or a form asks whether you have a food safety management system, the honest answer for most restaurants is: yes, here is our plan and our records. A plan and logs are what they want to see. See HACCP vs a food safety plan for how the words overlap.
The parts of a restaurant food safety management system
| Part | What it is | What you write or keep |
|---|---|---|
| 1. Who is in charge | A named person per shift who knows the plan | A line on the plan; a certified food protection manager where your local rule asks for one |
| 2. The menu review | Which foods and steps carry risk | A list of menu items by process: no cook, cook same day, cook-cool-reheat |
| 3. The HACCP-style plan | Critical steps, limits, checks, fixes | One page of control points plus the hazard review. See the plan format |
| 4. Prerequisite programs | Basic routines under the plan: handwashing, cleaning, pest control, supplier approval, allergen control | Short written procedures and the logs that go with them |
| 5. Monitoring logs | Daily proof the limits were met | Temperature, cooling, receiving, sanitizer, dish machine logs. See examples of HACCP logs |
| 6. Corrective actions | What staff do when a limit is missed | A line per control point, and a note each time it is used |
| 7. Training | Each person knows their checks | A sign-in sheet and dates. See HACCP training for staff |
| 8. Verification and review | The manager checks the checks, and the plan is updated | A weekly record review, monthly thermometer check, a dated yearly review |
Eight parts sound like a lot, but in a small restaurant parts 3, 4 and 5 are most of the paper, and a good template or a written plan covers parts 2 and 6 in the same file.
How the Food Code's "active managerial control" fits
The Food Code's annex on managing food safety practices names five main risk factors that cause foodborne illness in retail food: food from unsafe sources, improper cooking, improper holding temperatures, contaminated equipment, and poor personal hygiene [2]. Your management system is the way you show control of those five. Here is a simple map:
- Unsafe source: receiving log and approved suppliers.
- Improper cooking: cook temperature checks and the cooling and reheating logs.
- Holding temperature: hot and cold holding logs. See hot holding and cold holding.
- Contaminated equipment: cleaning log, sanitizer concentration log and dish machine log.
- Personal hygiene: handwashing procedure, illness policy, training record.
If you can point to a document and a log for each of the five, an inspector can see the system in minutes.
A template you can start from
This is the outline we would use for a one-location restaurant. Fill each heading with your own details. Do not copy another restaurant's text, because the limits and the menu are yours.
- Business and people. Name, address, person in charge, who has a food manager certificate.
- Menu and processes. Each dish grouped by how it is made, with the risky steps marked.
- Control points table. Step, limit, how checked, how often, who, what to do if missed, which log.
- Procedures. Half a page each for handwashing, cleaning and sanitizing, pest control, receiving, allergens, illness.
- Logs index. A list of each log, where it is kept and who fills it.
- Training record. Name, date, topic.
- Review record. The date of each review and what changed.
A blank version of items 3 and 5 is in the restaurant food safety plan template guide, and a filled example is in the HACCP plan example for a restaurant.
Paper, spreadsheet or app?
The system is the same in all three; only where you keep it changes.
- Paper binder. Cheap, works in a power cut, easy for an inspector to flip through. Risk: lost pages and blank days. See food safety log books.
- Spreadsheet. Good for review and for a plan you edit. Weak on daily checks at the line.
- App or software. Reminders and a history you can search. A monthly fee. See temperature log apps and HACCP software.
Choose the one your busiest cook will actually use on a Friday night. A system that is on the wall and filled in beats a better one that is not.
ISO 22000 and other certificates: when you need them
Most restaurants do not need ISO 22000. It is built for companies that make, pack or ship food and need an outside audit to sell to a large buyer. Reasons you might look at it anyway: a wholesale contract asks for it, a large catering client requires a certified supplier, or you run a commissary kitchen that supplies other businesses. Certification costs audit fees and staff time each year, and you can follow the same ideas without paying for a certificate. If a buyer asks for one, ask them exactly which standard they mean first. See HACCP certification for a restaurant for what a certificate is and is not.
How often to review it
- Every day: logs filled in, corrective actions written.
- Every week: the manager reads the logs and signs. Gaps get a conversation, not blame.
- Every month: thermometers checked in ice water. See the calibration log.
- At least once a year, and whenever the menu or equipment changes: reread the plan against the menu and date it. A new sous vide machine or a new dish served raw is a reason to review at once.
- After any incident: a complaint, a failed inspection item, a recall.
The review is what turns a plan into a system, because it keeps the paper matching the kitchen.
Common mistakes
- Buying a template with a different restaurant's menu in it.
- Having a plan but no daily logs, or logs with no plan behind them.
- One person who knows the system and nobody else.
- No review date, so the paper is years old.
- Writing "OK" in the temperature box instead of the number.
- Treating the system as something for the inspector, not the cooks.
Questions
What is a food safety management system?
The written steps, daily checks, records and training a food business uses to keep food safe. In a restaurant that means a plan, logs, procedures, training and a manager who reviews them.
Is a food safety management system the same as HACCP?
HACCP is the core method inside one: it finds the risky steps and sets limits. The management system also includes cleaning, pest control, training, records and review.
Does a US restaurant need an FSMS?
The Food Code does not use that name, but it expects active managerial control, which needs the same pieces. Some places also require a written HACCP plan for special processes. Ask your health department.
Is ISO 22000 required for a restaurant?
No. It is voluntary and aimed at food producers and suppliers. A restaurant may only need it if a buyer asks.
How long does it take to build one?
For a small restaurant with a simple menu, a few days of part-time work with a template, plus a couple of weeks of use to see what needs changing.
Can software build it for me?
Software can hold the logs and remind staff. Someone who knows your kitchen still has to check that the limits and steps match what you cook. See HACCP plan generators.
If you would rather have the plan written from your own menu, see your plan.
A smaller version for one kitchen is in the restaurant food safety program guide.
Sources
- ISO 22000:2018, Food safety management systems. https://www.iso.org/standard/65464.html
- FDA Food Code 2022, Annex 4: Management of Food Safety Practices, active managerial control. https://www.fda.gov/food/retail-food-protection/fda-food-code
- FDA, Hazard Analysis and Critical Control Point (HACCP). https://www.fda.gov/food/guidance-regulation-food-and-dietary-supplements/hazard-analysis-critical-control-point-haccp