Use AI to Draft Work Instructions People Can Follow

If colleagues repeatedly ask how to do a task, a clear set of instructions may help. AI can organize your notes into a first draft. The important work is making sure those instructions describe the real process, including the exceptions an experienced person knows to check.

A standard operating procedure, often called an SOP, sets out an agreed way to perform a task. Putting it through an AI tool does not make it automatically correct, current or suitable for training. It still needs an owner and a practical check.

Begin with a low-risk, repeatable task

Choose something such as preparing a weekly internal meeting pack or requesting ordinary office supplies. Avoid making your first experiment a medical procedure, machinery operation, financial approval or safety-critical task.

Agree who owns the process and who can approve changes. If the organization already has a current procedure, use that as the starting point. Do not quietly replace it with a chatbot’s preferred method.

Capture what actually happens

Walk through the task yourself or ask its experienced owner to demonstrate it. Make notes about the beginning, the result and each decision along the way. Use approved tools and fictional examples; remove customer information, passwords and confidential details.

• What must be available before starting?
• Which action happens first, and who is allowed to perform it?
• How can someone tell that a step worked?
• What changes when information is missing or inconsistent?
• When should the person stop and ask for help?
• Who receives or approves the finished result?

If recording a demonstration would help, follow your organization’s recording and consent requirements. Check what is visible on screen before capturing it. A written walkthrough may be enough.

Draft and check the ordinary route and the exception

Everything needed for this rehearsal is in the copyable block. You can also write the steps yourself and compare them with the worked answer. In this fictional process, sending for review never means permission to purchase.

Turn the following fictional approved notes into draft instructions for an office-supply request. This is a writing exercise only. Do not send a request, order anything, or contact anyone.

N1: Riley owns the process. A request must contain an item, quantity, and team.

N2: If any required field is missing, return the request to its requester for clarification. Do not guess the missing value.

N3: When all required fields are present, send the request to Riley for review. This ends the documented procedure; review is not purchase approval.

N4: No submission system, contact address, deadline, purchasing permission, or later approval process is supplied.

Test A: Item = notepads; quantity = 3; team = events.

Test B: Item = notepads; quantity = missing; team = events.

Produce a purpose, owner, prerequisites, numbered steps, and a separate list of questions for Riley. Cite N1-N4 beside the steps they support. Show the route for Test A and Test B. Keep the instructions as a draft and do not invent a button, address, deadline, or authority to buy.

Review the draft alongside your notes. Watch for plausible additions, such as a button that does not exist or a suggestion to skip an approval. An instruction can sound reasonable and still be wrong for your workplace.

The W3C’s accessible-writing tips support descriptive headings, clear instructions and language readers can understand. Apply that approach to your procedure: explain unfamiliar terms and tell the reader what they should do at each step.

Check your result

The draft says, “If quantity is missing, order one to avoid delay.” Is that a reasonable completion of the instructions?

Original fictional practice added October 10, 2026; expanded with complete source notes and two worked routes on October 14.

Replace vague instructions with observable actions

“Handle the request appropriately” is difficult to learn from. In an illustrative office-supplies procedure, a clearer draft might say: “Check that the request includes the item, quantity and team. If a detail is missing, return it to the requester before continuing.” The actual fields and approvals must come from your organization.

Separate actions from decisions. If two outcomes are possible, explain both. Identify the point where the task is complete, and describe what evidence the organization expects to retain. Do not include secrets or personal records as examples.

Test it with someone who has not done the task

Use a test environment or fictional records. Ask a colleague to follow the draft while the owner observes. Make clear that confusing instructions are the problem you are investigating; the exercise is not an assessment of the colleague.

Note every question, unexpected result and place where the observer has to intervene. Fix those parts, then repeat the affected step. A successful ordinary case does not settle an exception, so include at least one missing-information scenario.

For tasks that require supervision or formal qualification, written instructions do not replace those requirements. Keep the responsible person involved.

Publish a controlled version

Once the owner approves it, give the procedure a title, version, review date and contact for corrections. Store the approved copy where the team can find it and identify older copies as superseded. Decide which changes require another practical test.

If you later make the instructions searchable through AI, follow our article on finding approved work instructions. Search and answer generation are separate from approving the underlying process.

Measure whether the instructions help: fewer clarification requests, fewer missed steps, or a more confident handover. Include the time needed to maintain them. Promise only what your own trial demonstrates, not “perfect consistency” or a guaranteed reduction in training time.

Illustrative photo by Bethany Fidanzo on Unsplash.