M360 Compass · Management insights
Work instruction for a task your team repeats

A work instruction gives a colleague a clear starting point, actions in order and a result they can check. To see whether it works, ask someone who knows the workstation to try the draft on a practice job and watch where they need help.
Picture a small print shop with two PDFs that have almost identical names. The employee who set up the job knows which one to open. The person covering their shift needs a way to find the right file without searching someone else’s inbox. A useful instruction points to the selected file, explains what to check before printing a proof and says where to record the result.
Which task needs a work instruction?
Choose something that several people do or cover for each other. Look for a difference in how people work that has a visible consequence. An order gets sent back for a correction. A colleague waits for the only person who knows which file to open. Someone forgets a check and discovers the error at the next step. Give the instruction a name that describes what the employee needs to do, such as “Prepare a proof for internal review.”
Go to the workstation and ask someone who does the job to show you a recent example. Watch which records they open, what clues they use and what they leave for the next person. Ask them to show you the last case where they stopped. A real exception helps you decide where the instruction needs a decision. The EPA’s guide to preparing procedures recommends having people who know the activity write the procedure.
Set the boundaries next. The task starts when the employee can see something specific, such as a link to the production file in the job ticket. It ends when they can point to a result the next person can use. The Government Digital Service guide to identifying user needs describes defining the task from the user’s point of view and recording what would satisfy the need. You can apply the same questions to a job aid.
What should the instruction include?
Start with who uses the instruction and what they need at hand. Write the actions in the order the employee will do them. “Open the PDF from the link on the job ticket” tells the employee where to look. “Open the correct file” leaves the choice to them. The Canada.ca Content Style Guide recommends numbered lists for steps that follow a sequence.
Fictional example. At the print shop, job A-108 needs one paper proof for internal review. The job ticket lists the size, expected page count and version v3. The inbox still contains v2. This is an excerpt from the instruction.
| When | Action and check |
|---|---|
| Start | Open the PDF linked in the job ticket and compare its version with the ticket. |
| Before printing | Compare the size and page count with the values on the job ticket. |
| If something differs | Put the job on hold and ask the job lead to confirm which file to use. |
| Finish | Put one proof in the review tray and record its version on the job. |
Put the exception beside the check that reveals it. In this example, the employee compares versions before producing the proof. If the linked file and the ticket disagree, the instruction tells them when to stop and who can resolve it. The lead then corrects the job ticket so the next attempt begins with the right reference.
How do you test the draft on the job?
Pick a practice job and a colleague who knows the workstation but did not write the draft. Give them the starting information listed on the sheet and let them work through it. When they ask which file to open or where to find a field, record the question and the step where it came up. The EPA guide recommends having someone other than the author try a draft procedure before finalizing it.
Try two versions of the fictional job. First give the colleague a ticket that correctly links to v3. Check that one proof reaches the tray and that the version is recorded on the job. Then give them a ticket that links to v2. Watch whether they stop before printing and contact the right person. If you have to point out where the file version appears, add that detail to the sheet and run the same case again.
Ask what they understood from the instruction and what they had to guess. Our guide to workplace communication styles gives examples of questions that help uncover the information someone needs to proceed.
Who keeps the instruction current?
Store the sheet where both regular and backup staff can find it from the workstation. Name the person who keeps it current and show the date of the version in use. When an action changes, replace the copies at the workstation and ask another person to try that part of the job. Keep a record of prior versions if the team needs to see when and why a step changed.
Agree on what will prompt a review. It might be a renamed field, a change of tools or the same question coming up on two shifts. If you recently took charge of the team, the guide for first-time managers offers questions for working out who decides and who follows through.
How can you follow up in M360 Compass?
When two colleagues get stuck at the same step, record what happened and decide who will check the instruction with the team. With M360 Compass Momentum, you can record the issue and decision, assign an owner and due date, and track the action between meetings. Keep the current instruction available at the workstation. Close the action once someone has tried the corrected step. To see how an action can be tracked, request a M360 Compass demo.
Frequently asked questions about work instructions
How long should a work instruction be?
Start with a sheet that someone can scan at the workstation. If you are documenting two tasks with separate starting points and results, write two instructions and link them. Keep the steps that affect the work or the final check.
How is it different from a procedure?
In this guide, a procedure covers the sequence of work and who is responsible. A work instruction explains the actions for a single task. A print production procedure could link to a work instruction for preparing a proof.
Should I include screenshots?
Use a screenshot when it helps someone find a control or field they might miss. Crop it to the part they need and explain the action in text as well. Check the image when the interface changes.
When is the sheet ready to share?
Have someone who knows the workstation try a routine case and an exception. They should be able to produce the expected result or flag the problem at the right point. Fix the places where they needed an explanation before sharing the sheet.
