Step-by-Step Instructions Examples for Any Workflow
Step-by-step instructions examples are a quick way to see what good work instructions look like: numbered actions, one per line, each starting with a verb, ending with a clear finish line. I hired and managed virtual assistant teams for years, including a team of ten in the Philippines, and the instructions that worked all followed the same four rules.
Good step-by-step instructions follow four rules: one action per step, start every step with a verb, show the screen or name the exact button, and say what done looks like. Write them from a recording of the task, not from memory, and test them by having someone new follow them cold.
Below are the rules, before and after rewrites, six filled-in examples and the prompt I use to have Claude write them.
Where step-by-step instructions sit
Instructions are the layer under a standard operating procedure. The SOP says why a process exists, who owns it and when it runs. The instructions are the clicks and keystrokes inside one task. If you need the full procedure format, start with my SOP template, and for whole procedures filled in, see these sample standard operating procedures.
| Document | Answers | Example |
|---|---|---|
| Process map | What happens, in what order, across people | Lead comes in, gets called, gets a proposal |
| SOP | Who, what, when, where, why, plus the steps | P001 New lead follow-up |
| Work instructions | Exactly how to do one task | How to add a lead to the CRM |
| Checklist | Did I do every step | Ten boxes ticked before a post goes live |
- 1
Record
do the task once on screen, talking as you go
- 2
Transcribe
the recording becomes text
- 3
Draft
Claude turns the transcript into numbered steps
- 4
Test
someone new follows them without help
- 5
Fix
every place they stalled becomes a clearer step
The four-rule checklist for work instructions
Every instruction should pass these four checks. If a step fails one, rewrite it before anyone uses it.
- One action per step. "Open the CRM and add the lead and tag them" is three steps. Split it. When something goes wrong, the person can tell you exactly which step broke.
- Start with a verb. Open, click, paste, select, type, save, send. The verb tells the reader what their hands do. "The settings page" is not a step. "Open the settings page" is.
- Show the screen or name the exact thing. Use the button's real label in bold, the field name as it appears, the folder path in full. Add a screenshot or a timestamp in the recording for any step where people get lost.
- Define done. The last line says how the person knows it worked: the confirmation message, the status that changes, the file that appears.
Two smaller rules save a lot of back and forth:
- Put exceptions in one place. A short "If this happens" section at the end beats ten "unless" clauses inside the steps.
- Say the trigger at the top. "Do this every time a new lead form comes in" stops the task from being forgotten.
Before and after: five rewrites
These are the kinds of instructions that get handed over in a rush, and the versions that actually work.
| Before | Problem | After |
|---|---|---|
| Update the client in the system | Which system? What update? | Open the CRM, search the client's email, change Stage to Onboarding, click Save |
| Send them the usual stuff | Nobody knows what "usual" is | Send the email template Welcome 1 from the shared inbox. Attach the onboarding PDF from Drive > Clients > Templates |
| Make sure the post looks good | No finish line | Preview on mobile. Check the title has no typos and the link opens. Done when the post shows Scheduled |
| Handle refunds as needed | No trigger, no limit | When a refund request comes in, check the order date. Under 14 days, issue it. Over 14 days, send it to the owner |
| Do the weekly report | Twelve hidden steps | Split into steps: export the sales sheet, paste into the report tab, write three lines on what changed, send to the owner by Monday 10 a.m. |
The refund window above is a sample policy. Use your own.
Six step-by-step instructions examples
Each example below is a sample in my format, written for a small service business. Swap in your own tools and names.
Example 1: Add a new lead to the CRM
Trigger: a new lead form arrives in the shared inbox
1. Open the lead form email.
2. Copy the lead's name, email, phone and company.
3. Open the CRM and click "Add contact".
4. Paste each field into the matching box.
5. Set Source to the form name in the email subject.
6. Add the tag "new-lead".
7. Click Save.
Done when: the contact appears in the "New leads" view with the tag.
If the email already exists: open that contact and add a note instead.Example 2: Send a monthly invoice
Trigger: the 1st of each month
1. Open the billing tool and go to Invoices.
2. Click "Duplicate" on last month's invoice for the client.
3. Change the date and the invoice period.
4. Check the amount against the client's contract in Drive.
5. Click Send.
Done when: the invoice status shows "Sent" and the client's email is listed.
If the amount does not match the contract: do not send. Message the owner.Example 3: Schedule a social post
Trigger: a post is marked "Approved" in the content board
1. Open the approved post card and copy the caption.
2. Download the image or video from the card.
3. Open the scheduler and click "New post".
4. Upload the file and paste the caption.
5. Select the accounts listed on the card.
6. Set the date and time from the card.
7. Click Schedule.
8. Move the card to "Scheduled".
Done when: the post shows in the scheduler calendar on the right day.Example 4: Book a discovery call
Trigger: a lead replies asking to talk
1. Open the reply in the shared inbox.
2. Copy the booking link from the "Booking link" snippet.
3. Reply with the snippet "Book a call" and the link.
4. Change the lead's Stage in the CRM to "Call offered".
Done when: the lead books and the call appears on the calendar.
If they have not booked in 2 days: send the snippet "Booking follow-up".Example 5: Add a new team member to the tools (technical directions)
Trigger: a new hire's start date is confirmed
1. Open the admin page of the email provider and create their account.
2. Add them to the shared drive with "Editor" access on their team folder only.
3. Invite them to the project tool and the team chat.
4. Add them to the password manager's team vault for their role.
5. Send them the "Welcome to the team" email with their login steps.
Done when: they confirm they can open each tool on day one.
Never: share a password in chat or email.Example 6: Publish a blog post
Trigger: a draft is marked "Ready" by the editor
1. Open the draft and copy the title, body and meta description.
2. Open the website editor and click "New post".
3. Paste the title and body. Set the meta description.
4. Upload the hero image and write its alt text.
5. Click Preview and check it on desktop and mobile.
6. Click Publish.
7. Paste the live link in the content board card.
Done when: the live link opens and the card shows "Published".For each of these, the full SOP around it adds the owner, the purpose and the why. You can see those versions in the ten sample SOPs, and the flow between them in these process flowchart examples.
How to write step-by-step instructions with Claude
This is how I write instructions now. For years, I recorded a video of the task and an assistant typed the steps by hand. Now Claude writes them from the transcript, and the person who does the task checks them.
- Record the task once. Talk out loud: what you are clicking and why. Say the trigger at the start.
- Get the transcript from your screen recorder.
- Paste it into Claude with this prompt:
> Here is a transcript of me doing a task. Write step-by-step instructions from it. Rules: one action per step, every step starts with a verb, use the exact button and field names I said, add a "Trigger" line at the top and a "Done when" line at the end. Put exceptions in an "If this happens" section. Do not add any step I did not do. List anything unclear under "Questions for me".
- Answer the questions Claude lists. They are the gaps a new hire would hit.
- Test it cold. Give the instructions to someone who has never done the task. Every place they stop is a step to rewrite.
If you write instructions every week, save the prompt and your format as a Claude skill so every transcript becomes instructions with one short request. I explain how in Claude skills for business. VAs can run the same setup per client, which I cover in Claude Code for virtual assistants.
- 1
Record
one take of the real task
- 2
Draft
Claude writes numbered steps
- 3
Use
the team follows them
- 4
Flag
anyone stuck notes the step number
Every question from the team becomes a clearer step
Common mistakes in step-by-step instructions
- Writing from memory. You skip the steps you do on autopilot, which are the ones a new person needs most.
- Paragraphs instead of steps. If it reads like an email, nobody can find step 4 again.
- Vague verbs. "Handle", "manage" and "deal with" hide the real actions.
- No done line. Without it, every task ends with "is this right?" in your inbox.
- One giant document. Keep one task per set of instructions, and link them from the SOP.
From instructions to automation
Once a task is written as clear steps, you can see which steps a person needs to do and which steps software can run. Fixed steps like "add the tag" go to a workflow tool. Steps that need reading or writing can go to an AI agent working from the same instructions. I walk through that split in AI business process automation and in n8n vs Claude Code. Before you hire for a task, it is worth reading hire a virtual assistant vs AI.
Step-by-step instructions examples: FAQ
How do you write step-by-step instructions?
Write one action per step, start each step with a verb, use the exact names of buttons and fields, and end with a line that says what done looks like. Write from a recording of the real task, then test the steps on someone new.
What is an example of work instructions?
A work instruction is the exact steps for one task, such as adding a lead to a CRM: open the form email, copy the details, click Add contact, paste each field, add the tag, save. It ends when the contact shows in the right view.
What is the difference between an SOP and work instructions?
An SOP covers a whole procedure: purpose, owner, timing, tools and steps. Work instructions cover the exact clicks for one task inside it. Most SOPs link to several sets of work instructions.
What are technical directions examples?
Technical directions are step-by-step instructions for a technical task, such as giving a new hire access to the email, shared drive and password manager. They follow the same rules, with extra care on exact settings, permissions and what never to do.
Can AI write step-by-step instructions?
Yes. Claude writes clear numbered instructions from a transcript of you doing the task. Give it your rules and format, ask it to list anything unclear, and have the person who does the task test the result.
Get the jobs, not just the format
The AI Operator Kit gives you five ready systems for content, leads, outreach, sales and building, a daily operator plan and 107 prompts sorted by job, so the tasks your team runs every week already have clear instructions written for Claude.