Give clear instructions in an email by explaining the task, putting the actions in a workable order, and saying what the finished result should be. Include anything the reader needs before starting. If a missing file or unanswered question changes the process, explain what to do at that point.
A colleague can understand every sentence and still struggle to follow an email. The problem may be the sequence: the message asks them to fill in a sheet before explaining where the figures are, or tells them to overwrite a file before mentioning that the original must stay unchanged.
This guide helps you organize a short process for a colleague. The practice scenario is fictional, and its procedures are invented for the writing exercise.
Start with the task and the necessary preparation
Tell the reader what you want them to produce and why. For an agreed task, an opening could be:
Thanks for agreeing to prepare the North team’s reporting draft. We’ll use it to review November’s requests.
Then provide the information needed to begin: the source materials, their location, and any access or preparation requirements relevant to this task. Do not wait until the end of the email to reveal something needed in the first step.
The Google style guide’s advice on procedures recommends presenting prerequisite information before the steps that need it. Although that guidance is written for documentation, the same ordering principle is useful when explaining a process in an email.
Keep the preparation specific. “Everything is in the folder” may be unclear if the folder contains several versions. Name the required files or explain how the reader can identify them.
Put dependent actions in order
Use a numbered list when one action needs to happen before another. “First,” “then” and “finally” can help in a short sentence, but they cannot fix an incorrect sequence.
Compare these versions:
Fill in the reporting template and send me the link. Save it in Drafts. Make a copy first so the template stays blank.
- Make a working copy of the reporting template.
- Enter the figures in your copy.
- Save the completed draft in the Drafts folder.
- Reply with the link to your saved draft.
The second version places the copy instruction before the editing instruction. It also makes clear which file the recipient should send. This is a sequencing example; a complete task email would also identify the correct template and source figures.
Start each step with a clear action and object: “Open the approved template,” “Enter the total requests,” or “Reply with the link.” Keep closely related actions together when that makes the process easier to follow. Split a step if the reader could complete its first part and miss a separate requirement buried later in the sentence.
Make the request considerate and the steps direct
The British Council’s lesson on giving instructions by email recommends lists for readability and wording that suits the importance of the request. It also suggests giving a reason when useful and offering a way to ask questions.
For a colleague who has agreed to help, a courteous opening can introduce a direct list:
Thanks for helping with the draft. Please follow these steps so we keep the shared template unchanged.
You do not need to write “Could you please…” at the beginning of every step. Within that context, “Make a copy” clearly identifies an action. It does not, by itself, make the whole email rude.
If you are asking someone to take on a new task, establish that request rather than assuming they have accepted it. The guide to “could you please” and “would you mind” explains two ways to phrase a request.
Explain exceptions and the completion point
“Let me know if there are any problems” offers help, but a predictable problem deserves a specific instruction.
If the final figures are missing, reply to me before entering any figures. Wait for me to send them, then continue with the entry step.
This tells the reader what should pause, whom to contact and how to resume. It also avoids inviting them to fill the gap with an estimate.
When a task involves a possible future need, make clear whether the reader should prepare ahead or wait for it to arise. Practice that distinction with in case versus if in work emails.
End with an observable result. “Finish the report” might mean prepare a draft, obtain approval, or publish it. If you need a saved draft and a link, say so. A notification should follow the work it reports as complete.
Practice: explain a reporting task
You are Ari. Your colleague Morgan has agreed to prepare a reporting draft for the North team. Morgan already has access to the shared Monthly reporting folder.
These fictional facts are deliberately out of order:
- Morgan should reply to you with a link after saving the completed draft.
- The folder contains Approved reporting template and November final figures.
- The finished file belongs in the folder’s Drafts subfolder. It is a draft for your review, not an approved report.
- Morgan must make a copy of the template before editing. The original template must stay blank.
- The copy should be named North — November draft.
- Morgan needs to fill in three fields: Team with “North,” Month with “November,” and Total requests with the North team’s total from November final figures.
- If the final figures are missing, Morgan should reply to you and wait for you to supply them before entering figures or sending a draft for review.
Write the email before reading the example. Explain the purpose, identify the source materials, put the actions in order, and include the missing-figures instruction.
Here is one possible answer:
Subject: Preparing the North team’s November reporting draft
Hi Morgan,
Thanks for agreeing to prepare our reporting draft. I’ll use it to review the North team’s November requests.
In the shared Monthly reporting folder, you’ll find Approved reporting template and November final figures.
- Make a copy of Approved reporting template and name it North — November draft. Leave the original template blank.
- In your copy, enter North in Team and November in Month. For Total requests, use the North team’s total in November final figures. If that file is missing, stop before entering figures and reply to me. Wait for me to supply the figures, then continue this step.
- Save the completed draft in the Drafts subfolder of Monthly reporting.
- Reply to this email with a link to the saved draft so I can review it.
Please send me any questions as you work through the task.
Thanks, Ari
The model introduces the shared materials before the steps. It puts copying before editing and saving before sending the link. The exception appears where Morgan needs the figures, and the final step defines completion as sending a draft for review.
Check your own version against the facts. Would Morgan know which file to change, where the numbers come from, when to pause, and what to send you?
Revise the instructions when a prerequisite changes
Now change one fact: November final figures is not in the shared folder. You will send it to Morgan after they confirm that their working copy is ready. The recipient must still use the final figures rather than estimates.
Revise the sequence and update the materials paragraph so it no longer says both files are in the folder. For example:
The shared Monthly reporting folder contains Approved reporting template. I’ll send you November final figures once your working copy is ready.
A suitable replacement for the original second step is:
Reply to confirm that your working copy is ready. I’ll send you November final figures. Wait for that file, then enter North in Team, November in Month, and the North team’s total in Total requests.
The early reply now requests a necessary input. The later reply still sends the completed draft for review. Explaining those two purposes prevents “reply when ready” from referring to two different stages without clarification.
Before sending a real instructions email, read it in action order. Check that each required item is available before the reader needs it and that the final step describes the result you expect. Use the professional email format guide for the surrounding structure and the writing exercises for more practice.
To develop your own wording, start practicing for free. EmailBetter sends workplace scenarios tailored to your profile to your inbox. Write your reply in your usual email app, then review AI feedback in your dashboard.
Frequently asked questions
How do I write clear instructions in an email? +
State the task, provide the necessary materials or access information, and list the actions in the order the recipient needs to perform them. Explain any exception and the expected result, such as a saved draft and a reply with its link.
Is it rude to start an instruction with a verb? +
A direct step such as 'Open the template' can be appropriate within an agreed task. Explain the context and use a considerate opening. The relationship and situation matter; each numbered step does not need a separate politeness formula.
What should I say if the reader might be missing information? +
Identify the missing item, say which action should wait, and name the person to contact. Explain how to continue once the information is available, rather than leaving the reader to guess.
Practice this kind of email in your own inbox
EmailBetter sends you a workplace scenario. Reply from your usual email app and get AI feedback on your wording, with a suggested rewrite you can learn from. Start practicing for free.
Start practicing free →Keep reading
- September 11, 2026
Could You Please vs Would You Mind? Email Examples
Learn when to use could you please and would you mind in work emails. Compare verb patterns, permission requests, clear replies, and a short writing exercise.
- June 24, 2026
8 Professional Email Writing Exercises with Sample Answers
Practice professional email writing with eight workplace exercises. Compare your draft with sample answers for requests, reminders, apologies, and difficult replies.
- June 12, 2026
Professional Email Format: A Guide with Examples
Learn how to format a professional email, from the subject line and greeting to the request and sign-off. Includes a complete example and common editing fixes.