A Standard Work Instruction (SWI) is a work instruction written in the lean manufacturing tradition. It sits at the workstation, like any work instruction, but it carries two extra ingredients: a takt time (the rate at which a unit must be produced to meet customer demand) and a fixed work sequence (the precise order of operator actions). [1] [2] These come from the Toyota Production System concept of standard work, which the Lean Enterprise Institute defines through three components: takt time, work sequence, and standard work-in-process. [1] An SWI is the document that carries that information to the operator. The defining property of an SWI is that it represents the **current best-known method**, not a fixed rule. [3] [4] It changes whenever a kaizen event finds a faster, safer, or cleaner way to do the work, which is why teams that adopt SWIs need a tool that makes updates fast.
Key characteristics
- Written at the workstation level, like any work instruction, but includes takt time and work sequence. [1]
- Treated as the current best-known method, not a permanent rule. [3]
- Updated through kaizen, often by the operators themselves.
- Visible at the workstation rather than buried in a document control system. [2]
- Linked back to the parent SOP, but changes locally without triggering an SOP review.
- Contains specific tools, settings, and accept/reject criteria for the task.
Example
Final assembly station SWI
A 12-station assembly cell building electrical sub-assemblies has an SWI posted at station 7. The header shows takt time (52 seconds), the work sequence (6 numbered actions in order), and the standard tools. A takt-time chart at the bottom shows how each action fits into the cycle. When a kaizen event finds a way to shave 4 seconds off the wire-routing step, the supervisor records the new method on a phone, the SWI is regenerated, and the new version is at the station within minutes. Over a year, dozens of small updates compound into measurable productivity gain.
Comparison
SWI vs SOP
| Aspect | SWI | SOP |
|---|---|---|
| Origin | Toyota Production System, lean | Quality, compliance, ISO 9001, FDA |
| Purpose | Capture current best method | Define how work must be done |
| Includes timing | Yes (takt time) | No |
| Includes sequence | Always | Sometimes |
| Change cadence | Whenever a better method is found | Annual or per process change |
| Who updates it | Supervisor or operators | QA or document control |
How SOPX handles this
SWIs fail when the tool used to maintain them is too slow. The whole point of an SWI is that it evolves as the team finds better methods. If updating it takes a week of approvals, the standard goes stale and operators start running the old method. SOPX is built for fast updates: a supervisor films the new method, the AI structures it into steps with descriptions, the previous version is preserved in history (Pro plan supports version restore), and the new SWI is live at the station within minutes. Working as SWI software for lean teams, SOP software for quality teams, and work instruction software for the floor, SOPX keeps every layer aligned.
Related use case: Process Standardization →Frequently asked questions
Is an SWI the same as a work instruction?
Is an SWI the same as standard work?
How often should SWIs be updated?
Who should write SWIs?
Can SWIs replace SOPs?
Sources
Statements above draw on the references below. Numbers in the text link to the matching entry.
- [1]Standardized WorkLean Enterprise Institute · Accessed 2026-05-06
- [2]Standard Work InstructionsLearn Lean Sigma · Accessed 2026-05-06
- [3]Standardized Work in Lean Manufacturing6sigma.us · Accessed 2026-05-06
- [4]Standard workWikipedia · Accessed 2026-05-06