How to Write Clear Task Instructions (That Anyone Can Follow).

You've asked someone to handle a task. You explained what you needed. Then the result comes back completely wrong.

Here's the thing: most of us are terrible at giving instructions because we're experts in our own businesses. We forget that what's obvious to us isn't obvious to everyone else.

Good instructions mean tasks get done right the first time. No back-and-forth, no redoing work, no frustration. Let me show you the simple framework that works.

The Five Essential Elements

Every good task instruction needs these five parts:

1. The Context (Why This Matters)

Start by explaining why the task exists. Not in exhaustive detail, but enough that someone understands the purpose.

Bad: "Update the customer database."

Better: "Update the customer database so we have current contact information for our end-of-month newsletter."

When people understand the why, they make better decisions about the how. They know what matters most and where they have flexibility.

2. The Outcome (What Success Looks Like)

Describe exactly what you want as the end result. Not how to do it – that comes next – but what the finished task should look like.

Bad: "Fix the spreadsheet."

Better: "The spreadsheet should show all sales from January to March, sorted by date, with totals at the bottom of each month. Any orders over $500 should be highlighted in yellow."

Be specific. Use examples if it helps. If you can, show them a finished example of what you want.

3. The Process (Step-by-Step)

Now break down how to actually do it. Number your steps. Keep them simple.

Bad: "Process the invoices."

Better:

1. Open the invoices folder in Google Drive

2. For each invoice, check that the amount matches the purchase order

3. If it matches, move it to the "Approved" folder

4. If it doesn't match, move it to "Query" and note the discrepancy in the spreadsheet

5. At the end, email me the total amount of approved invoices

Notice each step is one action. Don't combine multiple actions into one step.

4. The Tools and Access (What They Need)

List everything they need to complete the task. Don't assume they know where things are.

Include:

• Software or platforms needed

• Where to find files or information

• Login details (if required)

• Templates or examples they should use

"You'll need access to Xero (login details in the shared password manager), the March invoices folder (linked below), and the invoice tracking spreadsheet."

5. The Boundaries (Decision Points and Limits)

This is what most people forget. Tell them what they can decide themselves and what needs your approval.

Example: "If an invoice is under $100 different from the PO, approve it and make a note. If it's over $100 different, flag it for my review before processing. If you're unsure about anything, ask rather than guess."

Clear boundaries prevent bottlenecks (everything waiting for your approval) and mistakes (wrong decisions made independently).

Making Instructions Scannable

People don't read instructions carefully. They scan them. Format your instructions so they can be easily scanned and referenced.

Use:

• Bold text for key points or warnings

• Numbered lists for sequential steps

• Bullet points for non-sequential information

• Headings to break up sections

• Short paragraphs (3-4 lines maximum)

Avoid:

• Long blocks of text

• Paragraphs that combine multiple ideas

• Important details buried in the middle of sentences

The Template Approach

For tasks you delegate regularly, create templates. It saves time and ensures consistency.

Basic Task Template:

TASK: [Clear, specific title]

CONTEXT: [Why this task matters]

OUTCOME: [What the finished result should be]

PROCESS:

1. [First step]

2. [Second step]

3. [Third step]

TOOLS NEEDED:

- [Tool or resource]

- [Tool or resource]

DECISIONS YOU CAN MAKE:

- [What they have authority to decide]

MUST CHECK WITH ME:

- [What needs your approval]

DEADLINE: [When it's due]

QUESTIONS? [How to reach you if stuck]

Save this template and fill it in whenever you delegate a task. It takes 5 minutes upfront but saves hours of confusion later.

Common Mistakes to Avoid

Assuming knowledge. You've been doing this for years. Define acronyms. Spell out processes. Write as if explaining to someone on their first day.

Skipping obvious steps. "Update the file" assumes they know which file and where it is. Include every step: "Open Google Drive > Marketing folder > Content Calendar spreadsheet."

Using vague language. "Format it properly" means nothing. Instead: "Use Arial 12pt font, 1.5 line spacing, left-align all paragraphs."

No examples. Show, don't just tell. Include a screenshot or link to a finished example.

Test Your Instructions

Want to know if your instructions are actually clear? Test them.

The best test: Give them to someone unfamiliar with the task and watch them try to follow them without additional help from you. You'll quickly see where confusion happens.

Can't do that? Read your instructions out loud to yourself. If you have to add verbal explanations as you read, those explanations need to be in the written instructions.

Building Your Library

Save your instructions. Document tasks you do regularly, tasks you plan to delegate, and tasks that have caused confusion. Store them somewhere accessible and update them when processes change.

Start Small

You don't need to document everything tomorrow. Start with one task. Write clear instructions using the five-part framework. Use it. Refine it.

The time you invest in writing clear instructions pays back multiplied. Every time that task needs doing, the instructions do the teaching for you.

Need help creating systems that make delegation easier? Let's talk about what's working in your business and what could work better.