Work instructions are the most granular form of documentation: they describe exactly what to do at a single step in a process, in enough detail that someone with zero context can execute it correctly on the first try. Every SOP contains an implicit set of work instructions; making them explicit is what separates documentation that works from documentation that sits unread.
Glossary
What is a Work Instruction?
A work instruction is the operator-level detail nested inside an SOP — the exact clicks, keystrokes, and decisions needed to complete one task step.
01
Work instruction vs SOP vs runbook
An SOP is the procedure — the what and why. A work instruction is the operator guide — the exact how. A runbook is an SOP for an operational incident. All three fit in Guidyy.
02
What a good work instruction includes
Action verb, specific system and field names, expected output, and a screenshot or screen recording. The screenshot is what turns a work instruction from a reading exercise into a confirmation step.
FAQ
Frequently asked questions
Who writes work instructions?+
The person who performs the task, immediately after performing it — not a technical writer months later.
How long should a work instruction be?+
One screen. If it's longer, split it into two work instructions.
Guidyy
Ship the documentation in 60 seconds.
Record once with Guidyy. Get a step-by-step guide, a clickable interactive demo, and a branded PDF — automatically.
Get Guidyy freeRelated reads