How to number screenshot steps in a procedure

The basic unit

Separate the action from its expected result.

Start with the conditions the reader needs: the right screen, permissions, input and starting state. Write a short action using the visible control label. Follow it with the result the reader should check before moving on.

A screenshot of the result alone does not tell someone where to click. Mark the target in a before-action image, then show an after-action image if the change is not obvious. Use a label or shape as well as colour so the marker remains understandable.

A repeatable sequence

Keep one numbering system.

1. 01

   Outline the actions

   Write the procedure in order before adding pictures. Split a step that contains several unrelated actions. Keep a small group together only when it is one simple operation.

2. 02

   Match text and image

   If the instruction is step 3, its callout should be 3. When two images explain the same action, label them 3a and 3b or Before and After instead of inventing extra action numbers.

3. 03

   Handle decisions explicitly

   For example: if the status is Approved, continue to step 5; if it is Pending, follow the pending branch. Give each branch a clear ending or rejoin point. Do not make readers infer a path from image placement.

4. 04

   Test from a clean start

   Ask a reviewer unfamiliar with the draft to follow it in an authorised test context. Record where they hesitate. Check numbering again after every change.

Maintenance

Document numbering cannot update pixels.

Use the editor’s automatic numbering for written steps so insertions renumber the text. A number drawn into a screenshot remains unchanged. Keep editable annotation sources or regenerate those images when steps move.

Use fictional examples in training materials. Record the screen context rather than a product build number in the instructions. If a control label changes, update the image and matching sentence together rather than leaving two competing names.

• The first action follows naturally from the stated starting conditions.
• Every callout identifies one unambiguous target.
• Branches say where to continue or stop.
• The final step explains what completion looks like.

Tool choice

Choose a method that fits the job.

A document editor’s numbered lists and a basic annotation tool often suffice. For repeated capture-and-export work, Bundlepix is an option for organising and annotating screenshots. The procedure’s wording and decision logic still require human review.

Further reading

Sources and reference material

• Microsoft: Insert pictures in Word