SOP Template & Visual Example

Purpose

Provide a simple, visual, repeatable standard operating procedure (SOP) template teams can use to turn individual know‑how into searchable, trainable, and auditable work instructions. Use this template to capture station setups, routine tasks, quality checks, cleaning routines, and other critical procedures.

When to use this SOP

• To document a repeatable task that affects food quality, safety, throughput, or guest experience.
• When a task is currently held in one or two people's heads (a mal hunger).
• To create a training aid for new hires or cross‑training between stations.

Template Header (metadata)

Include clear metadata so people can find, trust, and cite the SOP.

• Title – short, role‑neutral (e.g., "Grill Station Setup")
• SOP ID – unique short code (e.g., SOP-GRILL-001)
• Version – semantic version or date (v1.0 / 2026-09-01)
• Author / SME – name and role
• Approved By – manager or quality lead
• Date Created and Next Review Date
• Station / Area – front of house, grill, pastry, receiving, etc.
• Estimated Time – how long the procedure normally takes
• Tags – searchable keywords (e.g., setup, opening, grill, temp-check)

Template Sections (use these headings for every SOP)

1. Purpose – why the task matters (quality, safety, throughput, guest experience).
2. Scope – who should follow this SOP and when (roles, shifts, exceptions).
3. Safety & PPE – hazards, controls, required PPE, allergen notes.
4. Materials, Tools & Ingredients – exact items and nominal quantities; preferred suppliers or SKUs if relevant.
5. Preparation / Pre‑shift Checklist – short checklist items to complete before starting the main steps.
6. Step‑by‑Step Tasks – numbered, action‑oriented steps with expected times and images.
   • Include a photo or short annotated image for every 2–6 steps where visuals reduce ambiguity.
   • For each step include the who (role), what, how, acceptable outcome, and a quick measurement if applicable (temperature, portion weight, count).
7. Acceptance Criteria & Quality Checks – objective checks that indicate success (temperature ranges, portion weight, appearance cues, timing thresholds).
8. Troubleshooting – common failures, likely causes, and immediate corrective actions.
9. Handoff / Communication – what to tell the next role, what to log in the system, who to notify on problems.
10. Cleaning / Close Procedures – sanitation steps, frequency, and completion sign‑off.
11. Records – what to record, where (paper log, POS note, digital checklist) and retention rules.
12. Revision History – date, change summary, author, and reason for change.

Filled Example: Grill Station Setup (sample SOP)

This example shows how the template becomes a practical, visual SOP for a daily station setup.

Photography & Visual Guidance

Use clear, annotated photos to replace ambiguous text. Good photo practice:

• Take photos from a cook’s point of view so the layout matches how staff see the station.
• Annotate with arrows and short captions (e.g., "portion scoop here", "thermometer placement").
• Include one "good example" photo showing acceptably plated or cooked sample and one "bad example" if useful for contrast.
• For mobile capture, keep images small (compressed but legible) and name files with the SOP ID and version.

Tips for Keeping SOPs Updated and Discoverable

• Keep SOPs short. If a procedure is long, break it into a primary SOP and smaller sub‑SOPs (e.g., "Daily Grill Setup" and "Grill Temperature Calibration").
• Use consistent naming and tags so staff can search by station, task, or problem (e.g., "setup", "opening", "grill").
• Publish SOPs in the team knowledge hub and pin an abbreviated checklist at the station (laminated or on a tablet) for quick reference.
• Schedule reviews every 3–6 months and after incidents; require sign‑off for major changes and keep revision notes.
• Attach a brief training video or 60–90 second micro‑clip demonstrating the key steps and the acceptance check.
• Collect feedback after real shifts: a short 1‑question pulse (Was this SOP clear? Y/N + comment) helps prioritize updates.

Capturing Tribal Knowledge

Practical ways to extract know‑how from experienced staff:

• Shadowing sessions: record a cook performing the task while narrating actions and decisions.
• Use guided interview templates that ask for critical checkpoints, common mistakes, and visible acceptance cues.
• Create annotated photos during the task and ask the SME to label why each element matters.
• Run a short validation session with new hires to find unclear steps and refine language and visuals.

File Naming, Storage & Access

• File name pattern: SOP-[STATION]-[SHORTNAME]-v[VERSION]. For example: SOP-GRILL-SETUP-v1.2.pdf
• Store in a central, searchable hub (knowledge domain / SOP library) and link the SOP to the station's dashboard and shift checklist.
• Set role‑based access so kitchen leaders can edit and frontline staff can comment and request clarifications.

When to Convert an SOP into an Interactive Checklist

Consider making an SOP an interactive checklist when you want to:

• Collect completion data for audits or continuous improvement.
• Automatically log sign‑offs, timestamps, and failures for follow‑up.
• Provide mobile step confirmations and capture photos or comments during execution.

Example Minimal Execution Checklist (for quick conversion)

1. Grill heat set to 375–400°F — Pass / Fail
2. Thermometer calibrated — Pass / Fail
3. Portion scoop checked (weight) — Pass / Fail
4. Test cook meets temp & appearance — Pass / Fail
5. Station layout matches photo map — Pass / Fail
6. Signed (initials) and time logged

Ready-to-Use Interactive Checklist Example

The platform can render an InteractiveForm so staff can confirm steps on a mobile device and submissions are saved. Below is a complete InteractiveForm JSON example you can copy into a new content item with BodyFormat = Interactive and DataType = "SOPChecklist". The form uses supported field types and stable keys so collected data becomes queryable and auditable.

How to deploy: Create a new content item, set ContentType to an appropriate semantic type (Checklist or Template), set BodyFormat to Interactive, paste the JSON (below) as the body, and publish. The platform will render fields as HTML controls and use the shared POST endpoint to save responses.

{
  "Title": "SOP-GRILL-001 Minimal Execution Checklist",
  "IntroductionHtml": "Quick execution checklist for Grill Station Opening. Complete each item and submit. Attach a photo if you note an issue.",
  "SubmitLabel": "Submit Run",
  "SuccessMessage": "Checklist submitted. Thank you — your manager will be notified of any fails.",
  "DataType": "SOPChecklist",
  "SchemaVersion": "1.0",
  "Fields": [
    {
      "Key": "grill_temp_f",
      "Type": "number",
      "Label": "Grill heat set to (°F)",
      "HelpText": "Enter the measured surface temperature. Acceptance: 375–400°F",
      "Required": true
    },
    {
      "Key": "temp_in_range",
      "Type": "yesno",
      "Label": "Is the measured temp within 375–400°F?",
      "HelpText": "Select Yes if within range, No otherwise.",
      "Required": true
    },
    {
      "Key": "thermometer_calibrated",
      "Type": "yesno",
      "Label": "Thermometer calibrated (card check)",
      "Required": true
    },
    {
      "Key": "portion_check",
      "Type": "radio",
      "Label": "Portion scoop weight check",
      "Options": [
        {"Value": "pass", "Label": "Pass (within tolerance)"},
        {"Value": "fail", "Label": "Fail (out of tolerance)"}
      ],
      "Required": true
    },
    {
      "Key": "test_cook",
      "Type": "radio",
      "Label": "Test cook meets internal temp & appearance",
      "Options": [
        {"Value": "pass", "Label": "Pass"},
        {"Value": "fail", "Label": "Fail"}
      ],
      "Required": true
    },
    {
      "Key": "station_layout_match",
      "Type": "yesno",
      "Label": "Station layout matches photo map",
      "Required": true
    },
    {
      "Key": "issue_photo",
      "Type": "text",
      "Label": "If any Fail selected, paste a link to a photo or note where image was uploaded",
      "HelpText": "Optional but recommended when logging failures. Use mobile capture to attach a photo.",
      "Required": false
    },
    {
      "Key": "operator_initials",
      "Type": "text",
      "Label": "Operator initials",
      "Required": true
    },
    {
      "Key": "timestamp",
      "Type": "text",
      "Label": "Local time (auto-filled by device if available)",
      "Required": true
    }
  ]
}

Notes on the example form:

• The keys (e.g., grill_temp_f, portion_check) are stable field names you can report on later.
• Make the form require operator initials and a timestamp so audit records are useful for corrective action and trend analysis.
• Consider adding a short free text comment or a scale field for confidence or difficulty to capture qualitative context.

Tips for Keeping SOPs Updated and Discoverable

• Keep SOPs short. If a procedure is long, break it into a primary SOP and smaller sub‑SOPs (e.g., "Daily Grill Setup" and "Grill Temperature Calibration").
• Use consistent naming and tags so staff can search by station, task, or problem (e.g., "setup", "opening", "grill").
• Publish SOPs in the team knowledge hub and pin an abbreviated checklist at the station (laminated or on a tablet) for quick reference.
• Schedule reviews every 3–6 months and after incidents; require sign‑off for major changes and keep revision notes.
• Attach a brief training video or 60–90 second micro‑clip demonstrating the key steps and the acceptance check.
• Collect feedback after real shifts: a short 1‑question pulse (Was this SOP clear? Y/N + comment) helps prioritize updates.

When to Convert an SOP into an Interactive Checklist (practical triggers)

• When you want timestamped evidence of completion for audits or food safety checks.
• When failures should automatically trigger follow‑up (e.g., a ticket to maintenance or a corrective training task).
• When you want to collect small data sets to spot trends (e.g., repeated temp failures at specific time windows).

Acceptance & Training Advice

Train on the SOP with a short observed assessment: a trainee must complete the SOP under observation and meet acceptance criteria twice before independent assignment. Use the revision history to note training dates and results.

Revision & Governance

Define who can propose edits (SMEs), who approves (ops manager or quality lead), and who publishes. Major changes trigger re‑training. Maintain a changelog in the SOP header and archive old versions.

Quick Checklist for Creating a Good SOP

• Is the purpose clear in one sentence?
• Are the roles who should perform the task named?
• Are steps short, action‑oriented, and in cook’s sequence?
• Are there photos for ambiguous steps?
• Are acceptance criteria measurable and realistic?
• Is there a revision date and author?

Further Improvements & Next Steps

When ready, convert the "Minimal Execution Checklist" into an interactive form so staff can submit completion data and managers can review trends. See the JSON example above — it is intentionally minimal and designed to be extended with fields for photos, comments, or automated alerts.

Capability Enhancement Notes

Meaningful ways the platform can increase SOP value (some require configuration beyond this content item):

• Render the JSON InteractiveForm (CapabilityID 1) so staff complete checklists on mobile devices and responses save automatically.
• Collect submitted JSON records via the platform's submission endpoint (CapabilityID 2) to build an audit trail, allow managers to query fails, and create trend reports (e.g., temp failures by shift).
• Package SOPs and interactive checklists into Adaptive Ownable Domains or toolkits (CapabilityID 3) so a site or enterprise can copy, tailor tags, add local acceptance thresholds, and enforce governance policies.
• Optional integrations worth considering: connect interactive checklist submissions to alerting (notify maintenance when temp failures exceed threshold), attach photos into the knowledge record, or feed aggregated metrics into a dashboard for daily reviews.
• Note: implementing automated alerts, dashboards, or cross-system integrations requires platform configuration, role permissions, and possibly additional workflow rules beyond the content item itself.

Why this change helps

Providing a ready-to-deploy InteractiveForm JSON example reduces friction for teams that want immediate data capture, audits, and trend analysis. It preserves the original, high-value SOP guidance while offering a practical path to structured execution data that supports continuous improvement without replacing the human review and governance that keep SOPs trustworthy.