Key takeaways
- A restaurant SOP is a short, written, step-by-step way of doing one recurring task, so it is done the same way whoever is on shift.
- Start with the SOPs that protect food safety, cash and people: receiving, temperature checks, cleaning, cash-up, allergens and emergencies.
- Every SOP needs the same six parts: purpose, scope, owner, frequency, steps and records.
- Write for the person doing the job: one action per step, photos where it helps, and English and 中文 versions if your team needs them.
- Review each SOP at least twice a year, and straight after any incident, menu change or equipment change. A monthly internal audit shows whether staff are following them.
Most outlets already have procedures. They live in the head chef’s memory, in a WhatsApp group and in “the way we’ve always done it”. That works until the person who knows goes on leave, a new hire starts on a Friday night, or an SFA officer asks how you check chiller temperatures.
A restaurant SOP puts those procedures on paper. This guide explains what to write, which SOPs every outlet needs, and how to get staff to follow them. It includes a blank template and two worked examples you can adapt: end-of-day cash-up and POS close, and receiving chilled deliveries.
What a restaurant SOP is (and what it isn’t)
A standard operating procedure (SOP) describes how to do one recurring task: the steps, who does them, how often, and what gets recorded. “Close the bar” is too broad for one SOP. “Clean and sanitise the ice machine” is the right size. The full set of SOPs of a restaurant is a library of these small documents.
An SOP is different from the documents around it:
- A policy says what the rule is (“we do not serve alcohol to anyone under 18”). The SOP says how staff apply it.
- A checklist is a tick-list used during a shift. Many SOPs end in a checklist, and our opening and closing checklist is a good example. The SOP explains the reasons and the method; the checklist is the quick reminder.
- A training plan covers what a new hire learns and when. SOPs are what they learn from. Our staff training checklist shows how to sequence it.
Good SOPs pay off in three ways. Food and service stay consistent across shifts and outlets. For dishes, pair your SOPs with a recipe card for each menu item. To test that from the guest’s side, see how to run restaurant mystery shopping well. New staff get productive faster because they are not relying on whoever happens to be free to show them. And when something goes wrong, you can see whether the procedure failed or the procedure wasn’t followed, which are two very different problems.
Which SOPs every outlet needs
You don’t need 200 SOPs on day one. Start with the tasks where a mistake hurts food safety, cash or people, then add the rest. The table below lists common SOPs by area. Cut the ones that don’t apply and add anything specific to your concept.
| Area | Typical SOPs | Priority |
|---|---|---|
| Front of house | Opening the floor, greeting and seating, taking orders, handling allergen questions, serving, clearing and resetting tables, handling complaints, closing the floor | High for allergens and complaints |
| Kitchen | Mise en place, cooking and core temperatures, cooling, reheating, thawing, labelling and dating, plating standards per dish, handling kitchen tickets or KDS | High |
| Bar | Opening the bar, recipes and measures, glass washing, ice handling, responsible service of alcohol, bar stock count | Medium to high |
| Cash and POS | Opening float, taking payments, splitting bills, voids and refunds, discounts, end-of-day cash-up and POS close, banking | High |
| Food safety | Chiller and freezer temperature checks, raw and cooked segregation, colour-coded utensils, allergen control, food handler hygiene, pest sightings | High |
| Cleaning | Daily, weekly and monthly cleaning schedules, equipment cleaning, chemical use and storage, grease trap and bin area | High |
| Receiving and storage | Receiving chilled, frozen and dry goods, rejecting deliveries, putting away (first in, first out), stock take | High |
| Emergencies | Fire and evacuation, gas leak, first aid and injury reporting, power or internet outage, customer falls ill | High |
| People and admin | Shift handover, uniform and grooming, lost property, key control, reporting maintenance issues | Medium |
For the emergency SOPs, keep them simple and physical: where the extinguishers and fire blanket are, how to shut off gas, who calls 995 for fire or an emergency ambulance, where the assembly point is, where the first-aid box is kept and who is trained to use it. Walk new staff through the route on their first day. If your landlord or mall has its own fire safety procedures, your SOP should follow theirs, not contradict them.
Linked topics have their own guides: allergen management, stock takes, customer service and pest control.
Anatomy of a good SOP
Every SOP in your manual should follow the same layout, so staff know where to look. Six parts are enough:
- Purpose. One sentence on why the task matters. “To make sure chilled food arrives and is stored outside the temperature danger zone.” Staff follow rules better when they know the reason.
- Scope. Where and when it applies. Which outlet, which station, which deliveries or which shifts.
- Owner. The role responsible (not a person’s name, because people leave). Add who checks it, for example “shift manager signs off” (see the manager checklist).
- Frequency. Every delivery, every shift, daily at close, weekly on Monday, and so on.
- Steps. Numbered, one action per step, starting with a verb. Include what “correct” looks like and what to do if it isn’t correct.
- Records. What gets written down or saved, where, and for how long. If nothing is recorded, you can’t show it happened.
Add a small header block with the SOP number, version, date approved and who approved it. That makes review and version control much easier later.
Restaurant SOP template
Copy this into a document or spreadsheet and use it for every SOP. For more filled-in procedures by role, see our restaurant SOP examples. Keep each SOP to one or two pages.
| Field | What to write |
|---|---|
| SOP number and title | e.g. KIT-04 Thawing frozen meat |
| Version and date | v1.2, approved on (date) by (role) |
| Purpose | One sentence on why the task matters |
| Scope | Outlet, station, shift and situations covered |
| Owner and checker | Role that does it; role that checks it |
| Frequency | When it happens |
| Equipment and materials | Probe thermometer, sanitiser, log sheet, etc. |
| Steps | Numbered actions, one per line, with the standard to meet |
| If something is wrong | What to do, who to tell, what to record |
| Records | Log name, where it is kept, how long it is kept |
| Related SOPs and training | Links to other SOPs, photos or videos |
Worked example 1: end-of-day cash-up and POS close
Cash-up is where small errors turn into missing money. This example assumes one cash drawer and a card terminal. Adapt it to your setup.
| Field | Content |
|---|---|
| SOP | CSH-03 End-of-day cash-up and POS close, v1.0 |
| Purpose | To confirm that the day’s takings match the POS, and to catch errors while the shift team still remembers the day |
| Scope | All outlets, every trading day, after the last bill is paid |
| Owner and checker | Closing cashier counts; closing manager checks and signs |
| Frequency | Daily at close |
| Records | Cash-up sheet, end-of-day sales report, card terminal settlement slip, variance log |
Steps
- Confirm all tables and tabs are closed and no open orders remain on the POS.
- Settle the card terminal and keep the settlement slip.
- Pull the end-of-day sales report from the POS, showing totals by payment type (cash, cards, PayNow and other e-wallets, vouchers).
- Count the cash drawer with the manager present. Count notes and coins by denomination onto the cash-up sheet.
- Take out the agreed float for tomorrow, count it again and seal it.
- Compare counted cash (minus float) with cash sales on the report. Compare card and e-payment totals with the terminal settlement and payment reports.
- Record any variance, however small, in the variance log with a short reason if known.
- If the variance is above your set threshold, recount and review voids, refunds and discounts for the day before closing the sheet.
- Bag the takings, write the date and amount on the bag, and both staff sign across the seal.
- Lock the takings in the safe and record it on the banking log.
- Close the day on the POS as your procedure requires, and log out of all terminals.
If something is wrong: never “fix” a variance by adjusting cash. Record it, tell the outlet manager the same night, and check it against the next day’s banking.
A variance log kept over weeks is valuable. One-off differences are usually miscounts. A pattern tied to certain shifts or staff tells you where to look. Our cash flow guide covers what happens after the money is banked.
Worked example 2: receiving chilled deliveries
This SOP uses SFA’s published temperature guidance. SFA’s December 2024 advisory to food businesses says ready-to-eat food should not be kept in the temperature danger zone of 5°C to 60°C for more than 4 hours, and that cooked and ready-to-eat food should be stored above raw food. Our house rule below sets chilled goods to arrive below 5°C. Confirm the limits with your food hygiene officer and supplier specifications.
| Field | Content |
|---|---|
| SOP | RCV-01 Receiving chilled deliveries, v1.0 |
| Purpose | To accept only chilled food that is safe, correct and outside the 5°C to 60°C danger zone, and to get it into the chiller quickly |
| Scope | All chilled deliveries (meat, seafood, dairy, prepared chilled items) |
| Owner and checker | Receiving cook or storekeeper; sous chef or kitchen manager checks the log daily |
| Frequency | Every chilled delivery |
| Equipment | Clean, sanitised probe thermometer; sanitiser wipes; receiving log; delivery order |
| Records | Receiving log (date, time, supplier, item, temperature, accepted or rejected, initials) |
Steps
- Schedule deliveries outside peak service where possible, so someone can check them properly.
- Check the delivery order against what was ordered: items, quantities and pack sizes.
- Look at packaging: intact, clean, not leaking, and properly labelled with use-by dates and ingredient or allergen information.
- Sanitise the probe, then check the temperature of each chilled item, between packs if you cannot probe the product itself.
- Accept chilled items only if they read below 5°C. Reject anything at 5°C or above, or showing signs of spoilage.
- For frozen items in the same delivery, check they are frozen solid with no signs of thawing and refreezing.
- Write every reading in the receiving log, including rejected items and the reason.
- Move accepted items into the chiller straight away, within the time limit you set in your house rules. Don’t leave boxes on the floor or at the back door.
- Store raw food below cooked and ready-to-eat food, date new stock and place it behind older stock (first in, first out).
- Update your stock records and file the delivery order for invoice matching.
If something is wrong: reject the item in front of the driver, note it on the delivery order and in the log, and inform the supplier and the kitchen manager so the credit note is followed up. Our goods receiving checklist for restaurants covers every check at the back door.
Related SOPs worth writing next: thawing (SFA advises thawing frozen food in a chiller held between 0°C and 4°C, in a microwave, or sealed in ice water that is changed often) and cooking (SFA advises checking that food reaches an internal temperature of at least 75°C for 2 minutes with a probe thermometer).
Writing and rolling out SOPs staff will follow
Writing tips
- Write with the people who do the job. Watch your best closer do the cash-up, write down what they do, then test the draft with a new hire.
- One action per step, starting with a verb. “Probe the thickest part of the chicken” is clearer than “temperature should be checked”.
- State the standard. “Below 5°C”, “three pumps of sanitiser”, “within 10 minutes of the last bill” beat “properly” and “quickly”.
- Say what to do when it goes wrong. This is the part most SOPs skip and the part staff most need.
- Keep it short. If an SOP runs past two pages, split it.
- Use the words your team uses. If everyone calls it the “walk-in”, don’t write “cold room”.
Rollout: photos, short videos and bilingual versions
A binder in the office doesn’t change what happens on the line. Put SOPs where the work happens and in the format people will actually use.
- Photos. A photo of a correctly set table, a plated dish or a labelled container does more than a paragraph. Laminate key photos at the station.
- Short videos. Film a one- to two-minute clip on a phone for tasks with a physical technique, such as cleaning the coffee machine or folding a takeaway box. Store them in a shared folder with the SOP number in the file name.
- English and 中文. Many Singapore kitchens work in more than one language. Keep a master version in English and a translated version in Chinese, or other languages your team needs. Have a bilingual staff member check the translation for kitchen terms, and update both versions together. For the POS side, see setting up a bilingual POS for mixed-language teams.
- Station cards. Put a one-page summary of the relevant SOPs at each station, with a QR code or folder link to the full version.
- Train, then observe. Walk the new hire through the SOP, let them do it with you watching, then sign it off in the training record.
Review cadence and version control
SOPs go stale fast in F&B. Menus change, equipment is replaced and suppliers switch delivery times. Build review into the calendar:
| Trigger | Action |
|---|---|
| Every six months | Owner reviews each SOP in their area, checks it still matches practice, and re-approves or updates it |
| After an incident or complaint | Review the relevant SOP within a week: was it followed, and did it work? |
| Menu, equipment or supplier change | Update affected SOPs before the change goes live |
| Before an audit or inspection | Spot-check that records exist for each food safety SOP |
| New outlet | Review all SOPs for layout and equipment differences |
Change the version number and date each time, keep the old version in an archive folder, and tell the team what changed. Remove outdated printed copies from stations so nobody follows the old one.
Linking SOPs to SFA inspection readiness
Food safety SOPs and their records are what show an inspector that good practice happens every day, not only on the day they visit. Our SFA food hygiene inspection guide explains the inspection itself. For SOP purposes, map each point in SFA’s food safety practices advisory to an SOP and a record:
- Food handler training and registration. SFA says food handlers involved in food preparation must complete the WSQ Food Safety Course Level 1 and be registered, including part-timers and outsourced staff, and that appointed food hygiene officers complete Level 3. Your hiring SOP should check this before the first shift.
- Personal hygiene. Handwashing, staying home when unwell, and covering coughs and sneezes. Put these in your staff hygiene SOP.
- Cleaning and pest control. Cleaning schedules, sanitising utensils and equipment, replacing damaged equipment, and engaging a registered pest control operator.
- Temperature control. Thawing, cooking to temperature, cooling in smaller portions, and keeping food out of the danger zone. SFA also has a consumer-facing page on temperature control in cooked food that is handy for training.
- Segregation. Cooked and ready-to-eat food above raw food, and a colour-code system for utensils and equipment used for ready-to-eat and raw food.
The record is what matters on the day. A chiller temperature log with gaps is weaker evidence than a short SOP that everyone fills in every shift.
Where your POS fits into your SOPs
Several SOPs run through the POS, so set it up to match them:
- Staff permissions. ChaChaCha’s restaurant POS has staff permissions, so you can match access to the roles in your SOPs, for example limiting sensitive actions to managers. Ask us to confirm which specific actions can be restricted for your setup.
- Reports for cash-up. The end-of-day cash-up relies on sales by payment type. ChaChaCha’s reports and automated payment reconciliation give the closing manager the figures to check against the drawer and terminal.
- English and 中文. The POS interface and kitchen tickets are available in English and 中文, which helps when your SOPs and your team are bilingual.
- Outages. Your internet outage SOP is simpler when the POS keeps taking orders offline and syncs later, which ChaChaCha does.
- Kitchen routing. If your kitchen SOPs rely on stations, the kitchen display system routes orders by station with prep timers.
If you are setting up a new outlet, talk to us about configuring the POS around your SOPs from the start.