Standard Work Documentation

Standard work is the documented best-known method for a process. Not the method someone thinks is best. Not the method one supervisor prefers. The method that, given current equipment, current layout, and current technology, produces the most consistent quality and efficiency — and is documented, trained, and verifiable.

Standard work documents are living. When the process changes, the document changes the same day. Outdated standard work is operationally worse than no standard work — it creates compliance confusion and tells the floor team that the documents don’t matter.

Three Core Documents

1. Job Breakdown Sheet (JBS)

One process, one page. Written at the operator level — simple language, no jargon, no passive voice.

Three columns:

Column	What it captures
Steps	The sequence of actions to perform the task
Key Points	What matters about each step — what a new associate might skip or do incorrectly
Reasons	Why the key point matters — safety, quality, efficiency

The Reasons column is the most important and most frequently left blank. An associate who understands why a step matters complies with it. One following a list without knowing why does not.

Example — RF case picking:

Step	Key Point	Reason
Log into RF scanner at zone start	Verify badge ID matches assigned scanner ID	Ensures picks are attributed to your performance record accurately; mismatches create labor reporting errors
Scan pick location label before touching product	Scanner must confirm before you touch the case	Prevents picks from wrong location; this is the first quality gate

2. Work Instructions

More detailed than a JBS — for complex processes with decision points, system transactions, or exception handling:

• Receiving QC
• Hazmat processing
• Pick verification on high-value items
• Returns processing

Format: photos, system screenshots, explicit decision trees (“if the scan doesn’t match, do X; if the weight is outside tolerance, do Y”).

Critical rule: Work instructions live at the workstation, not in a binder on the supervisor’s desk. If the document isn’t accessible at the point of use, it doesn’t exist as an operational tool.

3. Skills Matrix

A visual grid showing which associates are:

1. Trained in a process
2. Certified as competent
3. Able to train others

What it surfaces:

• Cross-training gaps — only one person knows how to process hazmat returns = single point of failure
• Training progress — where the onboarding cohort is on their ramp to full certification

Escalation rule: A critical single-point-of-failure (the one person who knows Process X is a turnover or absence risk) escalates to Tier 3. See Tier Huddle System.

The Skills Matrix is updated by supervisors, reviewed in Tier 2.

Document Lifecycle

Standard work is a living system:

• Process change → document updated same day
• WMS release adds a new putaway step → JBS for putaway updated before associates return to the process
• Kaizen event changes pick sequence → JBS updated before training begins; old version destroyed
• Outdated documents → remove from workstation immediately. Outdated standard work is worse than no standard work.

Connection to Other CI Tools

• 5S: Standard work documents are part of the visual management system — they live at the workstation as part of the standardized zone
• Kaizen events: Day 4 is specifically for documenting the new standard and training every affected associate before the event closes — see Kaizen Event Management
• CAPA: Corrective actions that change a method require standard work update as part of the action closure — see Structured Problem Solving
• Tier huddles: Skills Matrix is reviewed at Tier 2; cross-training gaps escalate to Tier 3