Key takeaways
Short answer: An SOP defines how to perform a task correctly, safely and compliantly — a stable reference that changes rarely. Standard work captures the current best way to run a repeating cycle: its sequence, takt time and standard work-in-process. SOPs serve compliance; standard work is the baseline for improvement and is expected to change every time the team finds a better way. See also oee for manufacturing.
A standard operating procedure exists to make sure a task is done the correct, safe, compliant way every time, by anyone. It is a reference document, change-controlled and stable by design.
Standard work documents the current best method for a repeating operation, including its timing and material flow. Crucially, it is meant to be the baseline that every improvement starts from, not a frozen rule.
An assembly cell has an SOP that says "torque the bracket to 24 Nm, verify with the calibrated wrench" — a compliance requirement that will not change unless engineering changes the spec. It also has standard work that says the operator builds the unit in nine steps at a 47-second cycle with two units of WIP. When a kaizen finds an eight-step sequence at 42 seconds, the standard work is re-written that afternoon; the SOP is untouched, because the torque spec did not change. Confusing the two would have either frozen the improvement or loosened the compliance.
Treat standard work like an SOP — heavyweight, change-controlled, rarely touched — and you freeze it, and continuous improvement stops. Treat an SOP like standard work — casually rewritten on the floor — and you erode compliance and safety. They look similar but serve opposite masters: one stability, one change.
The SOP guarantees the task is done correctly; standard work optimises how the cycle flows. They reference each other — standard work must stay inside the SOP envelope — but the SOP sets the non-negotiables while standard work captures the current best practice within them.
1. Treating standard work as a detailed SOP. It freezes, and improvement halts.
2. Letting operators rewrite the SOP informally. Compliance and safety erode.
3. No owner for standard work. It drifts from reality and nobody updates it.
4. Standard work that ignores takt. Without takt and WIP it is just a method sheet, not standard work.
Standard work stabilises cycle time, which directly supports the Performance term of OEE. Unstable, undocumented cycles show up as speed loss and micro-stops; a maintained standard work is part of how high-performing lines hold their Performance number.
Fabrico makes cycle-time variation visible, so you can see when reality drifts from standard work and act before it shows up as Performance loss. Book a demo to see cycle-time tracking against your standard.
No — it captures timing and WIP and is meant to change often, while an SOP is a stable compliance reference.
The team doing the work, with team-leader support; they update it whenever a better method is proven.
Every time a better method is validated — that is the point of it.
No — they serve compliance and improvement respectively, and a line needs both.
It specifies sequence, takt time and standard WIP, not just the correct way to do a task.
Programați o întâlnire individuală cu experții noștri sau înscrieți-vă direct în planul nostru gratuit.
Nu este nevoie de card de credit!
Login
Blog
