A Standard Work Audit is a structured check of whether the documented work method matches what is actually happening at the Gemba.
The purpose is not to catch people doing something wrong.
The purpose is to verify that the current standard is understood, practical, followed, and still capable of producing the expected result.
Start with the actual standard
The audit needs a clear reference.
Depending on the process, that may include:
- work sequence;
- cycle time;
- standard WIP;
- quality checks;
- safety steps;
- process settings;
- material locations.
Standard Work should describe the best-known current method.
If the document is vague or obsolete, auditing compliance to it creates little value.
Observe the work directly
Do not conduct the audit only from a desk or checklist.
Go to the workplace and observe several cycles where practical.
Compare:
- actual sequence versus documented sequence;
- actual timing versus expected timing;
- actual WIP versus standard WIP;
- actual conditions versus required conditions.
The goal is to understand the real operating pattern.
Separate deviation from cause
If the employee is not following the standard, do not stop the analysis at “operator failed to comply.”
Ask why.
Possible causes include:
- missing material;
- poor tool location;
- equipment condition;
- unrealistic timing;
- unclear instruction;
- product variation;
- staffing shortage.
Genchi Genbutsu reinforces the need to understand facts at the actual place.
Verify whether the standard is still good
Sometimes the operator has discovered a better or safer method.
Sometimes the documented method became impossible after a process change.
The audit should distinguish:
- failure to follow a good standard;
- failure of the system to support the standard;
- a standard that should be improved.
That distinction prevents the audit from freezing obsolete work.
Connect to process confirmation
Process Confirmation may verify critical process conditions, controls, and reaction plans.
A Standard Work Audit is narrower.
It focuses specifically on the defined work method and whether the real sequence, timing, WIP, and supporting conditions align with that method.
Both can be part of daily management.
Use findings to improve the system
Useful audit findings may lead to:
- restored workplace conditions;
- retraining;
- equipment repair;
- material presentation changes;
- updated standard work;
- deeper problem solving.
Repeated findings should not simply create repeated audit actions.
They should trigger investigation into why the same condition keeps returning.
Choose frequency based on risk
High-risk or newly changed work may require more frequent verification.
Stable low-risk work may need less.
The audit frequency should consider:
- safety;
- quality risk;
- recent changes;
- training level;
- historical instability.
Layered Process Audits may provide another verification layer for selected critical controls across multiple management levels.
Keep the interaction respectful
The employee performing the work often understands barriers that are invisible in the document.
Useful questions include:
- What makes this step difficult?
- Where does the standard not match reality?
- What abnormal condition do you see most often?
- What would make the method easier to follow?
The audit should strengthen process knowledge.
Common mistakes
Auditing obsolete standards, using one observation to judge the entire process, treating every deviation as employee error, ignoring system conditions, creating audit scores without correcting recurring barriers, and failing to revise the standard after a verified better method are common mistakes.
Practical sequence
- confirm the current standard.
- observe the work directly.
- compare sequence, timing, WIP, and conditions.
- identify meaningful deviations.
- understand why the deviation occurred.
- determine whether the standard remains practical.
- restore missing conditions.
- update the standard when justified.
- verify the correction.
- use recurring gaps for deeper improvement.
The practical lesson
A Standard Work Audit should protect the process, not punish the operator.
The strongest audit asks whether the method and the operating system are both working as intended.