Good instructions give one action per step. Each step starts with a verb, and each says what the reader should see when it worked. A warning goes before the step it applies to, never after.
That is the whole method. The sections below apply it to a task such as resetting a shared office printer or setting up a projector. They also show how to test the result on someone who has never done the task.
One action in each step
The most common mistake is a step that hides two or three actions. The reader does the first, loses their place and skips the rest.
Before: Turn the printer off, wait for the screen to go dark and open the back cover before checking the paper tray.
After: Turn the printer off with the power button on the front.
The "before" line holds four actions. Give each its own step, and the reader can stop, look up and come back without losing the thread.
Start each step with a verb: press, open, select, wait, check. A verb first makes the step a direct request. "The power button should be pressed" makes the reader work out who presses it.
The GOV.UK style guide asks for steps to be complete sentences that end in a period. A step such as "Power button" fails that test, because it names a thing and gives no action.
Number the steps and keep them in order
Digital.gov says lists are useful for showing the order in which things happen. For steps in a process, it suggests numbering the items. The GOV.UK style guide says the same: use numbered steps, not bullets, to guide someone through a process.
Keep the steps parallel. Each should be an action, not a mix of actions, facts and warnings. Digital.gov shows a list that fails this test, because one item is an action and the others are things to gather.
Put the condition before the action. "If the screen stays dark, check the plug" lets the reader skip a step that does not apply. "Check the plug if the screen stays dark" makes them read the action first and then find out whether it was meant for them.
Warnings, results and names
A few small additions make steps much easier to follow.
| Element | Where it goes | Example |
|---|---|---|
| Goal line | Above step 1 | This resets the shared office printer. |
| What you need | Above step 1 | You need to reach the front panel. |
| Warning | Just before the step it applies to | Do not pull the plug. Use the power button. |
| Action | The step itself, verb first | Press the power button once. |
| Expected result | Right after the action | The screen turns dark. |
| If it fails | At the end | If the screen stays dark, tell the office manager. |
A warning placed after the step arrives too late. The expected result lets readers check their own work. If the screen did not turn dark, they know before they move on.
Name each control the way it appears on the device. If the button says "Start", write "Start", not "the green button". The GOV.UK style guide uses bold only for the names of controls in instructions, as in "Select Start."
A full example
The wording below is an example. Labels and screens differ by model, so use the words printed on your own device.
- Check that nobody is printing. The screen says "Ready" when the printer is idle.
- Do not pull the plug. Press the power button on the front once. The screen turns dark.
- Wait 30 seconds.
- Press the power button once more. The screen lights up.
- Wait for the word "Ready". This can take a minute.
- Print one test page. The page comes out with no error message.
- If "Ready" does not appear, tell the office manager.
Every step is a short sentence. Each action has a result the reader can see. The warning comes before the step it protects.
Test it with someone new
You know the task too well to judge your own instructions. Digital.gov's usability testing page suggests finding three to five people who match your intended readers. It asks you to give each a short scenario, then watch and listen while they try. It also suggests asking them to think aloud.
Do not use your own team. People who helped write the task will fill in the gaps without noticing.
Stay quiet while they work. Each time the person hesitates, a step needs work. Fix it, then test again with someone else.
Before you share the instructions, check these points.
- Every step holds one action.
- Every step starts with a verb.
- Warnings come before the step they apply to.
- Each action has a result the reader can see.
- Buttons and labels use the exact words on the device.
- A person who has never done the task has tried the steps.
Paste a draft into the Easy-Read Editor to find sentences that run long. Long steps often hide a second action.
Common mistakes
- Two actions in one step. Split them, as in the example above.
- Vague verbs. "Check the printer" does not say what to look at. Write "Check that the screen says Ready."
- A warning at the bottom. Move it above the step. A note at the end is read after the mistake is made.
- Different names for one control. If it is the "power button" in step 2, it is not the "on switch" in step 4.
- No result. Without a result, the reader cannot tell a failed step from a slow one.
- One long list for a long task. Split it into stages with short headings, each with its own result. See the advice on when to use a list for more on lists.
FAQ
How many steps are too many?
There is no fixed number. When the steps no longer fit on one screen or page, split the task into stages. Give each stage a short heading and a visible result.
Should I use bullets or numbers?
Use numbers when order matters, as Digital.gov and the GOV.UK style guide both advise. Use bullets for items that have no order. Short labels that go with a task are covered in labels and signs.
Do pictures help?
They can. The W3C guidance lists images, illustrations and symbols among the ways to clarify meaning. The text must still work on its own, so write each step as if there were no picture. Keeping each step to one idea also helps, as in writing shorter sentences.
Sources
Each page below was opened and read on the date shown. Where a fact comes from one of them, the guide says so.
- Lists - Digital.gov Plain Language Guide Checked November 19, 2026
- A to Z style guide - GOV.UK content and publishing guidance Checked November 19, 2026
- Usability testing - Digital.gov Plain Language Guide Checked November 19, 2026
- Writing for Web Accessibility: Tips for Getting Started - W3C WAI Checked November 19, 2026
This guide gives general information about readability. See the Disclaimer. To report a mistake, use the Corrections page.