← All training

⚙ Factory SOP

Shared blocks, recipe-specific steps, HACCP icons, photos — how the SOP page assembles itself.

10 sections · ~7 min read

A Factory SOP has three layers

Every approved recipe gets a Factory SOP page split into Pre-Production blocks, Recipe-Specific Production Steps, and Post-Production blocks. The first and third are shared across all recipes — toggle on what applies. The middle is unique to that recipe.

Open the Factory SOPs page

Lists every recipe with its SOP status. Filter by category, brand, factory line — and the dedicated SOP source filter (All · Legacy SOP · No SOP) plus the recipe Status filter to triage what still needs work.

📍 In RecipeHub: Factory SOP page

Legacy SOPs — auto-approved imports

Recipes that came in with their original DFC-MP PDF show a green Legacy SOP badge. These are auto-marked Approved at SOP level — they're validated documents from the old system. The PDF stays attached to the recipe (📎 download) while the live SOP page is rebuilt above it. Once the live version is ready, the Legacy badge can be archived.

📍 In RecipeHub: Factory SOP page

Role-specific notes
NPD: Use Legacy SOPs as your reference while authoring the live version — keep the PDF open in a second window.
FACTORY: Operators can keep using the Legacy SOP until the live version is signed off — both are valid until R&D archives the legacy one.
QA: Legacy SOPs already passed QA in the old system; you don't need to re-approve them at SOP level.

Pre-Production: Standard Blocks (collapsed by default)

These are the 22 shared blocks we seeded once: Receiving, Unpacking, Sifting, Sieving, Weighing, Line Clearance, Sanitization, etc. Each recipe just toggles ON the blocks that apply. No re-typing. On screen they're collapsed by default (header shows "X of 11 enabled") so the recipe-specific steps are visible without scrolling — click the header to expand. Printed SOPs always show every block in full.

📍 In RecipeHub: Factory SOP page

Recipe-Specific Production Steps

The middle section is what makes this recipe different — mix, cook, cool, portion, etc. Each step can carry HACCP icons (temperature, timer, weight, hygiene, danger, QC check, photo, tip), parameters (e.g. "Mixer speed: 2"), a CCP badge, and a warning banner. Reorder with the ▲▼ arrows. Use ⬆ Import to paste a list of steps (one per line, "Title: Description" or just description) and add them all at once.

📍 In RecipeHub: Factory SOP page

Role-specific notes
NPD: You write these steps when drafting the recipe. They flow into the SOP automatically.
FACTORY: You can edit step text, photos, and parameters here when capturing what really happens on the line.
QA: Full edit access — same as R&D. You can add / edit / reorder production steps and use ⬆ Import.

Post-Production: more shared blocks (also collapsed)

3.10 Cooling, 3.11 Blast Freezing, 3.13 Metal Detection (CCP-2), 3.14 FG Chiller (CCP-4), 3.15 FG Freezer (CCP-3), QA Sampling, Dispatch, Cold Chain. Same toggle pattern, same collapse-by-default rule. The Annexure at the bottom (auto-compiled list of DFC-QA-F* documents from the enabled blocks) is also collapsible — click any of the three section headers to expand.

📍 In RecipeHub: Factory SOP page

Hazards strip — pick which icons apply

The top of every SOP shows a PPE strip (hairnet, gloves, mask, safety shoes, goggles) and a Hazards strip. The Hazards strip has a ✎ Edit button — click it to toggle Biological / Chemical / Physical / Allergen plus any custom icons for this specific recipe. The catalog of available icons (including labels, inline SVGs, and emoji fallbacks) lives under Resources → 🪧 Safety Icons — edits there apply to every recipe.

📍 In RecipeHub: Factory SOP page

Role-specific notes
ADMIN: You can edit both the per-recipe picker AND the catalog page.
NPD: You can edit both the per-recipe picker AND the catalog page.
QA: You can edit both the per-recipe picker AND the catalog page.
FACTORY: Hazards are set by R&D / QA — you see them but don't edit.
VIEWER: Read-only view of the strip.

Live flowchart — the source of truth

Every SOP page has a 🔀 Flowchart button. It opens a process diagram of the recipe — auto-built from your shared blocks + recipe-specific steps. Edit titles, attach OPRP/CCP tags, reorder. This is the version operators run from, and it stays in sync with the SOP page automatically.

📍 In RecipeHub: Factory SOP page

Role-specific notes
NPD: You shape the Live flowchart by editing steps. The diagram updates as you edit.
FACTORY: You read it on the line. If it doesn't match what you actually do, flag R&D — don't treat it as wrong on your own.
QA: You sign off the CCPs and OPRPs that show on the diagram. They mirror the spec.

Captured flowchart — the legacy reference

65 of the imported recipes also show a 📑 As captured (N) button next to the Flowchart button. That's the original diagram from the old DFC-MP SOP doc, archived as image pages. Read-only — reference only. When both buttons are present, the Live flowchart wins. New recipes (anything authored from R&D draft onward) don't get a captured archive — they're Live from day one.

📍 In RecipeHub: Factory SOP page

Role-specific notes
FACTORY: Useful when you want to compare the Live flowchart against the version you trained on years ago.
NPD: Keep this open in a second window while you rebuild the Live version of an imported recipe — it shows you what the original diagram intended.
QA: When the Live flowchart drifts from the captured one and that drift wasn't intentional, that's a finding worth raising.

Edit Library to manage shared blocks

Need to add a 23rd block, or fix wording on an existing one? Admin / R&D / QA can all edit. Open via the ✎ Edit Library button on either the Pre or Post block section header. Library edits propagate to every recipe that has that block toggled on — that's the whole point.

📍 In RecipeHub: Factory SOP page

Role-specific notes
ADMIN: Be deliberate — Library edits hit every recipe instantly across the whole platform.
NPD: You can add / edit blocks. Same applies — changes are platform-wide.
QA: You can add / edit blocks. Same applies — changes are platform-wide.