Glossary

Work Instruction

A work instruction is a detailed, step-by-step document that describes exactly how to perform a single, specific task. It is the most granular level of process documentation, sitting below a standard operating procedure and specifying the precise actions needed to complete one task correctly.

What is a work instruction?

A work instruction answers one question in full: how do I do this specific task, exactly? It's the ground floor of process documentation — more detailed and narrower than an SOP. Where an SOP describes a whole procedure at a workflow level, a work instruction drops into a single task within it and spells out every action, in order, with no assumed knowledge.

The distinction is one of altitude. A company might have a policy that sets the rule, an SOP that describes the end-to-end process, and then a set of work instructions that each cover one task inside that process — "how to enter a new supplier in the accounting system," "how to run the weekly backup." The work instruction is where the abstract process becomes concrete, clickable actions.

Because they're so specific, work instructions lean heavily on precision: exact button names, field values, screenshots, expected results, and what to do if something looks wrong. They're written for the person actually performing the task, often someone doing it for the first time, so clarity and unambiguous steps matter more than brevity.

Key characteristics

Task-level granularity

A work instruction covers exactly one task — not a whole process. If it branches into several distinct activities, those are separate work instructions.

Highly detailed and specific

It names the exact actions: which button, which field, which value. There's no room for interpretation — the point is that two people follow it identically.

Written for the doer

The audience is the person performing the task, often for the first time. It assumes no prior familiarity and explains each step in plain, concrete terms.

Visual where it counts

Annotated screenshots and expected-result callouts remove ambiguity that words alone can't carry — especially for software tasks with lots of small UI details.

Sits inside a larger process

Work instructions usually belong to an SOP. The SOP says what happens and in what order; the work instructions say exactly how to do each part.

SOP vs work instruction

SOPs and work instructions are often used interchangeably, but they describe different levels of detail. The clean way to think about it: an SOP is the procedure, a work instruction is one task within it.

	SOP	Work instruction
Scope	A whole process or procedure, end to end	One specific task within that process
Level of detail	Procedural — the sequence of activities and who does what	Granular — the exact clicks, fields, and values for one task
Answers	What needs to happen, in what order, and when	Exactly how to perform this single task
Audience	Anyone who owns or oversees the process	The person actually performing the task
Relationship	May reference several work instructions for its steps	Usually belongs to a parent SOP

What to include in a work instruction

1A clear title naming the single task the instruction covers.
2The purpose — what completing this task accomplishes and why it matters.
3Prerequisites: access, tools, permissions, or prior steps that must be in place first.
4Numbered, specific steps in exact sequence, each describing one concrete action.
5Screenshots or visuals for steps where the UI is easy to misread.
6Expected results, so the doer can confirm each step worked before moving on.
7What to do if something goes wrong — the common error and how to recover.

How Glyde fits

Work instructions are the most tedious documentation to write by hand precisely because they're the most detailed — every click, every field, a screenshot for each step. That granularity is exactly what Glyde captures automatically. You perform the task once while recording, and Glyde produces the numbered, annotated steps with screenshots, so the work-instruction-level detail is captured rather than reconstructed from memory.

Because Glyde reads the actual on-screen actions and page context — DOM state and structured step data, not just pixels — the steps name the real buttons and fields you interacted with, which is the level of specificity a work instruction lives or dies on. When PII shows up in a screenshot, SmartBlur redacts it on-device before it leaves your machine. The result is a task-level how-to accurate enough to hand to someone doing the work for the first time.

Try Glyde Free See example SOPs

FAQ

Work Instruction, answered

What is a work instruction in simple terms?

It's a detailed, step-by-step guide for doing one specific task exactly right. It's the most granular kind of documentation — it tells the person performing the task precisely which actions to take, in order, with no assumed knowledge.

What's the difference between an SOP and a work instruction?

An SOP describes a whole process at a procedural level — what happens and in what order. A work instruction zooms into one task within that process and spells out exactly how to perform it. An SOP may reference several work instructions for its individual steps.

What should a work instruction template include?

A title naming the task, its purpose, prerequisites, numbered and specific steps, screenshots where the UI is easy to misread, expected results so each step can be verified, and guidance for common errors. The goal is that two people follow it identically.

How detailed should a work instruction be?

Detailed enough that someone doing the task for the first time can complete it without asking questions. Name exact buttons, fields, and values, and show what a correct result looks like. If it's vague enough to be interpreted two ways, it isn't specific enough.

Turn your next recording into a real SOP

Record once, get documentation your team can follow on day one. Free plan, no credit card required.

Try Glyde Free