Key takeaways
- Nine ready-to-adapt SOPs for a hypothetical Singapore restaurant: greeting and seating, order taking, allergen questions, kitchen tickets, food holding, temperature checks, kitchen safety, refunds and voids, and closing cash-up.
- Each SOP names an owner, a trigger, numbered steps and what to do when something goes wrong.
- Food safety steps follow SFA’s published temperatures: keep ready-to-eat food out of 5°C to 60°C, chill at 4°C or lower, freeze at -18°C or lower, and cook or reheat to at least 75°C for 2 minutes.
- Put the approval steps for voids, refunds and discounts into your POS permissions, so the SOP is enforced rather than remembered.
Most restaurant SOPs fail for one of two reasons: they are too vague to follow (“serve guests warmly”) or too long to read in a busy shift. The examples below sit in between. Each one is a short, numbered procedure that a new service crew member or cook can follow on day one, written for a hypothetical 60-seat casual restaurant in Singapore. Change the names, times and thresholds to fit your outlet.
If you want the method behind them (how to choose which SOPs to write, the anatomy of a good SOP and version control), start with our restaurant SOP template guide. This page is the worked examples, role by role.
How to use these SOP examples
Every example uses the same five-part layout, which you can copy straight into a document or your staff app:
- Code and title, such as SOP-FOH-01 Greeting and seating. Codes make it easy to refer to a procedure in training records.
- Owner: the role responsible, not a person’s name, so the SOP survives staff turnover.
- Trigger: when the procedure starts.
- Steps: numbered, one action per line, in the order they happen.
- If something goes wrong: the exceptions staff actually meet, and who decides.
Timings such as “within two minutes” are examples of standards an outlet might set, not industry benchmarks. Pick numbers you can staff for and measure.
Front of house SOP examples: greeting, seating and order taking
SOP-FOH-01 Greeting and seating
Owner: host or shift lead. Trigger: guests reach the entrance.
- Acknowledge the guests straight away with eye contact and a greeting, even if you are busy with another table.
- Ask for the booking name or the number in the party.
- Check the table plan on the POS and choose a table that fits the party and any needs you can see (pram, wheelchair, elderly guest who prefers not to sit on a high stool).
- Walk the guests to the table, hand over menus or point out the QR code and explain how ordering works if it is their first visit.
- Mark the table as seated on the POS and tell the section server which table has been seated.
If something goes wrong: if no table is free, give an honest wait estimate, take a name and mobile number, and add the party to the queue list. Never promise a time you cannot keep. If a booked table is still occupied, offer the waiting area and tell the shift lead.
SOP-FOH-02 Order taking
Owner: section server. Trigger: table seated.
- Approach within the outlet’s standard (for example, two minutes of seating) with water and specials.
- Before taking the order, ask: “Does anyone at the table have a food allergy or dietary requirement?” If yes, follow SOP-FOH-03.
- Key each item to a seat number, with modifiers (doneness, less spicy, no ice) chosen from the POS list rather than typed as free text.
- Repeat the order back, including modifiers.
- Send the order. Hold later courses and fire them when the table is ready.
- Check that the ticket has reached the kitchen printer or display.
If something goes wrong: if an item is sold out (86’d), apologise, suggest an alternative and tell the shift lead so it is switched off on the POS and QR menu. Our steps of service guide covers the full sequence from greeting to farewell.
Allergen question SOP
SOP-FOH-03 Handling an allergen question
Owner: server, with the chef in charge. Trigger: a guest mentions an allergy, intolerance or dietary restriction.
- Never guess. Say: “Let me check with the kitchen before you order.”
- Ask exactly what the guest must avoid. SFA lists the eight most common food allergens as milk, egg, fish, crustaceans, soya beans, peanuts, tree nuts and wheat (SFA, food allergy and intolerance). Guests may have others.
- Tell the chef in charge in person and record the allergy on the order as a modifier or note, so it prints on the kitchen ticket.
- The chef checks the recipe or spec sheet for every component, including sauces, marinades, garnishes and frying oil.
- If the kitchen cannot be confident the dish is free of the allergen, tell the guest plainly and suggest another dish.
- Prepare the dish with clean utensils and boards, away from the allergen, and plate it separately.
- The chef or server hands the dish to the guest by name and confirms the allergy was noted.
If something goes wrong: if a guest shows signs of a reaction, call 995 immediately, alert the manager and keep the dish and ticket for review. For the policy side (allergen matrix, supplier changes, menu wording), see our allergen management guide.
Kitchen SOP examples: ticket handling and food holding
SOP-BOH-01 Kitchen ticket handling
Owner: station cooks, with the expeditor or head chef at the pass. Trigger: a new ticket arrives.
- Read the whole ticket, including modifiers and any allergy note, before starting.
- Acknowledge the ticket (call it out, or start it on the kitchen display).
- Cook by course. Starters first; hold mains until they are fired.
- Allergy tickets: stop, clean the board and tools, then cook the dish separately.
- At the pass, check each plate against the ticket for modifiers, garnish and temperature.
- Mark the ticket complete once the runner has picked up the plate.
If something goes wrong: if an ingredient runs out, tell the shift lead at once so the item is switched off on the POS. If a ticket is unclear, ask the server; do not guess.
SOP-BOH-02 Cooking, hot holding, cooling and reheating
Owner: cook on each station. Trigger: any cooked food that is not served immediately.
- Probe meat and poultry to an internal temperature of at least 75°C for 2 minutes, as in SFA’s advisory on food safety practices.
- Preheat bain-maries and hot cabinets before use and hold hot food above 60°C (SFA, proper temperature for hot foods).
- Do not keep ready-to-eat food in the 5°C to 60°C danger zone for more than 4 hours.
- To cool, divide large batches into smaller portions or shallow pans and refrigerate straight away. Food kept for reuse must be chilled below 5°C within 4 hours of cooking.
- Reheat to an internal temperature of at least 75°C for at least 2 minutes, and reheat only once.
- Thaw frozen food in a chiller at 0°C to 4°C, in a microwave, or sealed in leak-proof packaging under ice water that is changed often.
- Store cooked and ready-to-eat food above raw food, and use colour-coded boards and utensils for raw and ready-to-eat items.
If something goes wrong: if hot-held food is found below 60°C and you cannot tell how long it has been there, discard it and record why.
Temperature checks: chillers, freezers and hot holding
SOP-BOH-03 Temperature checks
Owner: opening and closing cooks; shift lead verifies. Trigger: opening, mid-shift and closing (or the times your food safety plan sets).
- Read each chiller and freezer display, and check with a probe thermometer at least once a day.
- Targets from SFA’s food safety tips: fridges and chillers at 4°C or below; freezers at -18°C or below. SFA’s page on temperature control in cooked food sets out the 5°C to 60°C danger zone.
- Record the unit, time, reading and your initials on the log.
- Check hot-holding units against the 60°C target at the same times.
- The shift lead signs the log at the end of each shift.
If something goes wrong: if a chiller reads above 4°C, check the door seal and whether it is overloaded, recheck after a short interval, move high-risk food to another unit if it stays high, and call the technician. Record the corrective action. Our restaurant temperature log guide has a log layout and calibration steps.
Kitchen safety and fire SOP
SOP-BOH-04 Kitchen safety, gas and fire
Owner: head chef; every kitchen staff member follows it. Trigger: every shift.
- Wear anti-slip shoes, fitted clothing with sleeves rolled up, and hair secured.
- Clean spills immediately. When mopping, do it in sections so there is always a dry path, and put up a warning sign.
- Keep walkways and fire exits clear of boxes and bins.
- Check gas hoses for damage at opening; report any damaged hose and do not light that burner.
- Never use water on a grease fire. Use a fire blanket or the correct extinguisher, and only if it is safe to do so.
- At closing, turn off gas at the burners and at the main valve.
These steps follow the Workplace Safety and Health Council’s page on preventing common kitchen hazards, which names slips, trips and falls as one of the top workplace injuries in F&B and also recommends gas detectors, locking gas cylinders in fireproof cabinets away from heat, and regular fire and evacuation drills. MOM’s workplace safety and health pages cover employer obligations and accident reporting.
Kitchen exhaust belongs in your manager’s SOP list too. SFA’s guidelines for licensed food retail premises say that SCDF’s Fire Code requires kitchen exhaust systems to be properly maintained, with the entire duct and hood degreased and cleaned at least once every 12 months by a specialist. Operators must keep the maintenance records, and SFA officers ask for them during inspections.
Cashier SOP examples: refunds, voids and discounts
SOP-CSH-01 Voids, refunds and discounts
Owner: cashier or server; approved by the shift lead. Trigger: a guest asks for a change after an item has been sent to the kitchen or paid for.
- Before sending: the server can remove an item without approval.
- After sending (void): the server asks the shift lead, who approves on the POS with their own login and chooses or writes the reason (guest changed mind, wrong item keyed, kitchen error).
- After payment (refund): check the original bill, refund to the same payment method where possible, and have the shift lead approve. For cash refunds, the guest signs the refund slip.
- Discounts: apply only listed promotions. Anything else needs manager approval.
- Never void or refund your own orders without a second person.
- The manager reviews the void, refund and discount report every day.
If something goes wrong: if a guest disputes a card charge, do not refund in cash; record the details and pass them to the manager.
Closing cash-up SOP
SOP-CSH-02 End-of-day cash-up
Owner: closing shift lead plus one witness. Trigger: last bill paid.
- Check that no tables are left open on the POS. Close or transfer any open tabs.
- Count the cash drawer by denomination with a witness. Take out the float (for example, a fixed $200) and bag it for tomorrow.
- Compare counted cash with the POS expected cash and record any over or under.
- Settle the card terminal batch and compare card, PayNow and e-wallet totals with the POS tender report.
- Compare delivery platform orders with what the POS recorded.
- Seal the takings in a bag, record the amount and both signatures, and store it in the safe or bank it the next day.
- Escalate any variance above the outlet’s limit (for example, $5) to the manager with a note.
Our guide to daily sales reconciliation goes deeper into matching tenders, settlements and bank credits.
Rolling out the SOPs, and where the POS helps
Examples only help if staff use them. A simple rollout:
- Train one SOP at a time. Read it together, demonstrate it, then watch the staff member do it.
- Record sign-off. Keep a sheet with each staff member, SOP code, date trained and trainer.
- Keep food safety training current. SFA requires food handlers to pass the WSQ Food Safety Course Level 1 and be registered, including part-time and outsourced staff (SFA advisory).
- Review after incidents. A complaint, near miss or inspection finding is a reason to change the SOP, not only to remind staff.
SOP-DEL-01 Packing takeaway and delivery orders
Delivery mistakes are made at the packing counter, out of the guest’s sight. This example uses the same layout as the SOPs above.
Owner: packer on the delivery station; shift lead checks. Trigger: a takeaway or delivery ticket reaches the pass.
- Read the whole ticket, including modifiers, allergy notes and cutlery requests.
- Check each item against the ticket as it arrives at the pass. Keep hot and cold items in separate bags.
- Pack sauces and soups in sealed containers, upright, so they cannot leak.
- Label any allergy order clearly on the container and the bag.
- Add cutlery and napkins only if requested.
- Seal the bag with a sticker or tape so it cannot be opened unnoticed, and attach the order label.
- Hand the bag to the rider or customer only after matching the order number, and mark it collected on the POS or tablet.
If something goes wrong: if an item is sold out, tell the shift lead before the order is packed so the customer or platform can be informed, and switch the item off on every channel. If a rider is late, keep hot food in the holding area for no more than your set time and tell the shift lead. Keep food out of the 5°C to 60°C danger zone for no more than 4 hours. Our SOP template guide explains how to write and review procedures like this one.
Build as many controls as you can into the systems staff already use. In ChaChaCha, staff permissions decide who can do what at the till, table management and split bills keep service steps consistent, and the kitchen display system routes tickets by station with order prioritisation and prep timers. English and Chinese kitchen tickets help mixed-language kitchens read the same order. POS reports and automated payment reconciliation support the cash-up SOP. Every void and comp is logged in an audit trail, and end-of-night reports break down sales by staff member. For specific void or refund reason settings, ask us to confirm, or contact us for a walkthrough.