How to write step-by-step instructions with examples

Define what done looks like

Before writing step one, write a sentence describing the finished result. ‘Update the report’ is hard to verify. ‘The shared report contains this week’s totals and shows the week ending date’ gives the reader something concrete to check.

Next, identify the starting point. Is the reader signed in? Does the file already exist? Do they need someone else’s input? Put that information before the sequence instead of hiding it in a later step.

Use an action verb and a specific object

Start with words such as Open, Select, Enter, Connect, or Check. Follow the verb with the exact object. Prefer ‘Open the Weekly report tab’ to ‘Go to the relevant section.’ Use the names people will see.

Keep terminology consistent. If you call something a request in the first step, do not switch to ticket, item, and case unless those are different things. Repeated labels are useful in instructions because they help the reader recognize the same object.

• Vague: ‘Set everything up.’ Clearer: ‘Open Meeting settings and select the room microphone.’
• Vague: ‘Save it properly.’ Clearer: ‘Save the file in the shared Reports folder with the week ending date in its name.’
• Vague: ‘Check the result.’ Clearer: ‘Confirm that the new teammate appears in Pending invitations.’

Split a step when the reader must make a new decision

One step does not have to mean one click. A short sequence such as ‘Enter the email address and select Send’ may be easy to follow. Split it when the reader needs to compare options, change location, or verify an intermediate result.

For example, choosing someone’s access role deserves its own explanation. Burying that decision between typing an address and sending an invitation can cause someone to accept a default without understanding it. Give the choice the space its consequence deserves.

Add checks and explain the important branches

Place a checkpoint where a wrong result would affect later work. Tell the reader what they should see, hear, or have completed. Avoid adding ‘check’ after every harmless action; focus on moments where confirmation helps them continue confidently.

Write branches as a condition followed by an action: ‘If the invitation is still pending, confirm the email address before resending it.’ Avoid listing every rare exception in the main sequence. Link a separate troubleshooting note when the explanation would interrupt the task.

Let a new reader reveal the missing steps

Ask someone to follow the instructions from the stated starting point. Watch without supplying extra directions. A question such as ‘Which folder?’ is a specific editing task: name the folder. A pause at an unfamiliar term means you may need to define it or use a more familiar word.

Finish by checking the actual outcome together. Then remove any explanation that did not help the reader act or verify the result. The aim is enough detail to complete the task, not the shortest possible word count.

Use the instruction manual template for a repeatable structure. In 1explain, you can write the steps directly or review a draft generated from video or audio, then let readers follow one step at a time through a shared trainee link.