How to Write and Control Hospitality SOPs

A useful hospitality standard operating procedure tells a trained person what task to complete, who owns it, what must be checked, what acceptable completion looks like, what record to make and when to stop or escalate. It is tested in the real venue, approved by an authorised person, linked to training and removed when it is replaced.

An SOP is not useful because it is long or formal. It is useful when it reduces uncertainty during an actual shift. Nor does an SOP prove that a venue is compliant: the task, legal requirements, equipment instructions, training and supervision still need to be correct.

Decide whether the task needs an SOP

Not every action deserves a multi-page procedure. Choose a format that fits the work.

A cleaning schedule may say what is cleaned, when and by whom. The SOP explains how a particular item is safely cleaned and sanitised. A completed record shows what happened. Combining all three into one crowded sheet can make each purpose harder to understand.

Prioritise an SOP when the task:

• has a food-safety, WHS, legal, financial or customer risk;
• is completed by several people or shifts;
• often produces inconsistent results;
• involves a decision or escalation point;
• is performed infrequently and easy to forget;
• depends on equipment or a supplier instruction; or
• has caused incidents, waste, complaints or rework.

Confirm the authority behind the task

Before writing steps, identify what governs the work:

• current Australian law, code or regulator guidance;
• state, territory or council requirements;
• licence or food-safety program;
• equipment manufacturer instructions;
• chemical label and safety information;
• contract, insurance or landlord conditions;
• approved recipe, product specification or brand standard; and
• the venue’s actual layout and staffing model.

Record the source and review date in the SOP or its control register. Do not paste regulator wording into a procedure without translating it into the venue’s safe, practical method. For regulated or technical tasks, have a qualified person review the method before approval.

business.gov.au recommends identifying important processes, developing SOPs, making them accessible, teaching staff and reviewing them regularly. That is a sound operating cycle, but each venue still needs to confirm the requirements that apply to the subject.

Assign an owner, approver and users

Every SOP needs three perspectives.

Owner: keeps the procedure accurate and starts reviews. This may be a head chef, venue manager, bar lead or owner.

Approver: has authority and competence to confirm the method and resources. For higher-risk procedures, approval may require a food-safety, WHS, HR, licensed-trade or legal reviewer.

Users: the people who perform or supervise the task. Include them while drafting because they know where the work becomes unrealistic.

One person may hold several roles in a small venue, but the record should still show which responsibility they were fulfilling. “Management” is too vague when a procedure is overdue or an exception occurs.

Observe the task before writing

Watch a competent person complete the task at a representative time. Ask them to explain:

• the trigger to start;
• required tools, protective equipment and records;
• the safe setup;
• the normal sequence;
• the checks that matter;
• variations by product, shift or equipment;
• what can go wrong;
• when they stop and call a manager; and
• what proves completion.

Compare the observed method with the authoritative sources. Do not preserve a shortcut merely because “that is how we have always done it”. Equally, do not write an idealised process that the venue’s space, equipment or roster cannot support. Fix the underlying condition or set an honest limitation.

Use a clear SOP structure

A small-venue SOP can usually fit these fields:

1. Title and identifier—plain task name and unique code if the venue uses codes.
2. Purpose—the outcome and risk controlled.
3. Scope—locations, products, shifts and people covered.
4. Responsibility—who performs, verifies and escalates.
5. Before you start—training, tools, PPE, food controls and isolation.
6. Steps—numbered actions in the order they occur.
7. Decision points—if/then choices and authority limits.
8. Completion standard—the observable result.
9. Records—what to record, where and how long under the venue’s rule.
10. Escalation—when to stop, isolate, notify or obtain specialist help.
11. Sources and linked documents—current references.
12. Document control—version, owner, approver, approval date and next review.

Use descriptive headings and short sentences. Start steps with verbs such as check, isolate, record, confirm and escalate. Define technical terms once. Put warnings immediately before the hazardous step, not in a paragraph several pages earlier.

Write actions that can be observed

Weak instructions hide the standard:

• “Clean thoroughly.”
• “Check the fridge.”
• “Use good judgement.”
• “Report if necessary.”

Stronger instructions identify the action and outcome:

• Remove loose soil using the approved cleaning method before applying sanitiser.
• Record the representative food temperature using the approved probe method.
• If the reading is outside the normal limit, label the food on hold and notify the shift manager.
• The shift manager records the disposition decision and verifies the equipment before restart.

Do not write a step more precisely than the evidence allows. If safe chemical concentration depends on the product label, refer to the current approved label rather than hard-coding a number that may change when the product changes.

Include decisions, limits and escalation

Hospitality work changes quickly. A procedure that covers only the normal path invites improvisation when the supplier substitutes a product, the power fails or a customer reports an allergy.

For each likely exception, define:

• what the user notices;
• what they must stop or protect;
• what they may decide;
• what they must not do;
• who has the next authority;
• what information to provide; and
• what record closes the exception.

Example:

If the cool-room display is above the venue’s normal range, do not adjust the control repeatedly or move food without a plan. Keep the door closed where safe, notify the manager, measure representative food under the temperature procedure, record times and readings, and follow the manager’s disposition and maintenance decision.

This is more useful than “report faulty fridge”, because it connects the equipment issue with food and decision ownership.

Make the document usable during a shift

Design for the user and location.

• Put short task steps at the work point where appropriate.
• Keep background explanation in training material if it distracts from execution.
• Use images only when they show a real position, part or standard clearly.
• Provide translations, demonstration or other accessible formats where needed.
• Ensure mobile or digital versions load where the task is completed.
• Protect printed copies from damage without making them impossible to replace.
• Avoid tiny tables and dense landscape pages beside a wet bench.

An employee who cannot understand the procedure needs training and an accessible instruction method. A signature does not correct unclear language.

Test the draft in the real venue

Choose a trained person who did not write the SOP. Ask them to complete the task while the owner observes without coaching unless safety requires intervention.

Check:

• Can they find the current procedure?
• Do they understand the start trigger and responsibility?
• Are tools and records available?
• Does the sequence match the physical workspace?
• Are decision points clear?
• Can they identify when to stop?
• Does the completion standard produce a consistent result?
• How long does the task reasonably take?
• What did the user have to ask or assume?

Revise the document and correct missing resources. A failed test may reveal a training, layout, equipment or roster issue rather than a wording problem.

Approve, issue and train

Approval should record:

• final version;
• sources checked and date;
• operational test completed;
• required specialist review completed or pending;
• owner and approver;
• effective date; and
• which earlier version is replaced.

Train the people who use or supervise the SOP. Explain why the control exists, demonstrate the task, have the employee perform it and verify competence. Record the topic, version, date, trainer, employee and result.

Do not assume an email attachment is training. For a safety-critical or complex task, provide supervision until the person can complete it correctly.

Control versions and remove old copies

Document control prevents two different “correct” methods from circulating.

Maintain a register with:

• SOP title and identifier;
• current version and effective date;
• owner and approver;
• authorised storage location;
• review date or trigger;
• printed-copy locations; and
• archived or withdrawn version.

When a new version is issued:

1. mark it approved and current;
2. update the master location;
3. replace work-point and printed copies;
4. archive the old master under restricted access if retention is required;
5. mark superseded copies clearly so they cannot return to use;
6. notify and retrain affected users; and
7. verify that digital bookmarks or QR links still point to the current version.

Never rely only on a filename such as FINAL-SOP-v2-new. Use a controlled version and approval record.

Review on time and after change

Set a routine review interval suited to the risk and source volatility, plus event triggers:

• incident, near miss, complaint or failed check;
• regulator, award, licence or guidance change;
• new equipment, chemical or supplier;
• menu, layout or operating-model change;
• repeated staff workaround;
• audit finding;
• contractor recommendation; or
• user feedback that a step cannot be completed.

Review the method, not just the date in the footer. Observe the task again, confirm sources, inspect records and check that staff are using the current version.

Worked example: closing the commercial dishwasher

The first draft says: “Clean dishwasher, switch off and report faults.” During testing, the closer cannot tell which filters are removed, whether the machine must cool, which chemical controls apply or what counts as a fault.

The owner checks the manufacturer’s instructions and chemical information, then writes the start condition, safe shutdown, removable components, cleaning sequence, completion check and fault escalation. The procedure says not to remove fixed guards or perform electrical work. A separate closing checklist confirms completion; a fault form captures the asset, symptom and out-of-service status.

A trained employee tests the revised procedure. The SOP owner adjusts the image and tool list, approves version 1.0, trains closers and removes the handwritten sheet previously taped to the wall.

Common SOP mistakes

• Writing from memory without observing the task.
• Copying a template from another country or venue.
• Mixing policy, instructions and records into one crowded page.
• Using vague verbs and no completion standard.
• Omitting stop-work and escalation limits.
• Hard-coding values that belong in a current label or award source.
• Treating a signature as proof of competence.
• Issuing a new version without removing old copies.
• Keeping no source or approval record.
• Reviewing the footer date while ignoring actual workarounds.

Hospitality SOP implementation checklist

• ☐ Prioritise tasks by risk, inconsistency and operational impact.
• ☐ Select the correct format: policy, SOP, checklist, instruction or record.
• ☐ Confirm current authority, instructions and venue constraints.
• ☐ Assign owner, approver and users.
• ☐ Observe a competent person completing the task.
• ☐ Write clear action steps, decisions and completion standards.
• ☐ Include records, stop-work rules and escalation.
• ☐ Test the draft with a user who did not write it.
• ☐ Obtain specialist review where the task requires it.
• ☐ Approve, issue, train and verify competence.
• ☐ Register the version and remove superseded copies.
• ☐ Review after change, failure or the scheduled date.

Take the next useful action

Choose one repeated task that produces errors or questions. Observe it once, write the trigger, five to ten key actions, completion standard and escalation point, then test that draft with another trained employee before building a large SOP library.

The Free Hospitality Checklists can help identify repeated checks that need clearer ownership. The Hospitality Operations Master Collection provides editable venue systems. For the wider controlled-document set, read What Documents Should a New Venue Have Ready?.

General-information limitation: General operational information only. Confirm current food-safety, WHS, employment, privacy, licence, equipment, chemical and jurisdictional requirements with the relevant authorities and qualified advisers. An SOP or signed training record does not by itself make work safe, lawful or compliant.

References and source review

• Policies, procedures and processes, business.gov.au. Accessed 24 August 2026.
• Safe Food Australia, Food Standards Australia New Zealand. Accessed 24 August 2026. Used as an example of authoritative task-specific source material for food procedures.

Source review date: 24 August 2026