Standard Operating Procedure(SOP)

What is a Standard Operating Procedure?

A Standard Operating Procedure (SOP) is a documented, step-by-step set of instructions for performing a recurring task in a food manufacturing operation. SOPs cover both routine operational activities (cleaning, equipment maintenance) and food safety-critical activities (CCP monitoring, corrective actions, allergen segregation).

Under FSANZ Standard 3.2.1, food safety programs must include SOPs that document how each food safety control (CCP, GMP requirement, allergen procedure) is implemented. Standard 3.2.2 requires all food businesses to maintain systematic procedures for food handling and safety. SOPs are the operational expression of these requirements.

What Makes an Effective SOP

An effective SOP includes:

• Clear purpose: What is this procedure for?
• Scope: Which products or situations does this apply to?
• Responsibilities: Who performs each step?
• Step-by-step instructions: What exactly is done, in what order, by whom?
• Acceptance criteria: How do you know the procedure was done correctly? (e.g. "Internal pot temperature must be ≥75°C")
• Records: What records are kept to document completion?
• Frequency: How often is this procedure performed?
• Review date: When will this procedure be reviewed and updated?

SOPs in Practice for Australian Food Manufacturers

Common SOPs in food manufacturing:

• Cleaning and sanitising: Detailed cleaning procedures for each piece of equipment, including agent, concentration, contact time, and verification method
• CCP monitoring: For each CCP, how it is monitored, how often, the recording method, and what happens if a limit is breached
• Allergen management: How allergen-containing products are segregated, how equipment is cleaned between allergen runs, how allergen incidents are reported
• Personnel hygiene: Hand washing procedures, when to wash, what soap/sanitiser to use
• Recall procedure: Steps for identifying affected product, notifying customers and authorities, managing product retrieval

Common mistakes:

SOPs written but not followed. An SOP that is not enforced is useless. Regular audits should verify that staff are following documented procedures, not shortcuts.

SOPs that are too complex or unclear. If an SOP is 10 pages long or uses unclear language, staff will not follow it. Effective SOPs are concise and unambiguous — use simple language, numbered steps, and visual aids where helpful.

SOPs not updated when processes change. If you install new equipment, change a supplier, or change a recipe, the related SOPs must be updated. Outdated SOPs are worse than no SOPs — they create confusion about which procedure is current.

Worked example: A meat pie manufacturer's SOP for CCP monitoring (cooking temperature) specifies: (1) insert thermometer probe into the geometric centre of the pie filling; (2) wait 15 seconds for stabilisation; (3) record temperature on the CCP log; (4) if temperature <75°C, continue cooking and re-check; (5) if temperature ≥75°C, approve product for cooling. This SOP is specific, unambiguous, and verifiable.

How Batchbase Supports SOP Documentation and Compliance

Batchbase's food safety program module allows you to document SOPs and assign them to specific production tasks or CCPs. When an operator performs a task, they confirm they followed the SOP, and the system records this confirmation. This creates an audit trail demonstrating that procedures are being followed consistently.

Related Standards and References

• FSANZ Standard 3.2.1 — Food safety programs (SOP documentation requirement)
• FSANZ Standard 3.2.2 — Food safety practices (systematic procedures requirement)
• FSANZ food standards code