Start here
Who this helps
Use this guide if your emails get results but not warmth - recipients answer, yet you notice colleagues' messages sound easier and get faster replies. It covers the writing side of work English: reminders, review requests, status notes, and scheduling threads.
If your problem is meetings and spoken updates, the companion work-vocabulary page covers that lane. This one stays inside the inbox, where tone lives entirely in word choice because your voice cannot soften anything.
Section 2
Real situations to practise
Task update by email. A written update needs to survive skimming, so front-load the verbs: “Quick status: the draft is wrapped up, the data section is held up by the export bug, and I will follow up with IT today.” Write it as three short lines a reader can scan in five seconds, then practise the one-line version for a busy thread: “Wrapped up on my side - over to you.”
Review and approval. The standard request line is “Could you look over the attached ___ by ___?” - attach the deadline or you will be writing a second email. When you need formal approval rather than comments, switch verbs: “Could you sign off on the final version?” Practise both, because asking a director to look over something you actually need signed produces a polite but useless reply.
Scheduling change. In writing, particles do the work your voice cannot: “Could we move the call up to 9:30?” means earlier; “Could we push it back to Thursday?” means later. Always offer the replacement slot in the same sentence. For cancellations, “I need to call off tomorrow's demo” is fine internally; for clients, soften to “I'm afraid we need to reschedule.”
Problem solving. A blocker email has three sentences: what came up, what you tried, what you need. “A permissions error came up during setup. I have tried resetting the tokens but cannot sort it out. Could you look into it, or point me to whoever can?” Ending with a question, not a complaint, is what gets blocker emails answered.
Section 3
Weak vs improved examples
Every weak line below is the kind that gets answered slowly or not at all. The improved lines are the standard email moves - notice each one adds a reference point, a date, an attachment, or an option that makes replying effortless.
Follow-up email - Weak: “I write again about the invoice.” Improved: “I am following up on the invoice we discussed on Monday.” “Following up on” plus the date turns a nag into a professional standard every inbox recognizes. Requesting review - Weak: “Please check this.” Improved: “Could you look over the attached summary before I send it out?” Naming the attachment and the next step tells the reader exactly what kind of attention you need.
Clarifying a blocker - Weak: “I cannot continue.” Improved: “I am held up by one missing approval and can move ahead once it comes through.” The improved line reports a system state, not a personal failure - managers unblock those faster. Scheduling - Weak: “We need another time.” Improved: “Could we move the meeting up to 10:00 or push it back to after lunch?” Two concrete options mean the reply can be one word.
Closing an action - Weak: “I finished everything.” Improved: “I wrapped up the notes and shared them with the team.” Named deliverables close threads; “everything” reopens them. Now rewrite one email from your own sent folder using these pairs as the pattern - real traffic is the best worksheet.
Section 4
Phrase bank
Email phrases work as complete lines, so learn them with their sentence frames, not as bare verbs.
Openers - “I am following up on ___,” “I am reaching out about ___,” “Just circling back on ___.” One opener plus one date reference and your first line is done.
Requests - “Could you look over the attached ___?”, “Could you send over the ___?”, “Could you look into why ___?” The could-you frame keeps every request polite without extra padding.
Handoffs and threads - “Looping in Dana, who owns this,” “Forwarding this on to the right team,” “Picking up where we left off last week.” These lines manage the people on the thread, which is half of email work.
Closers - “I will get back to you by Friday,” “We can move ahead once legal signs off,” “Wrapping up this thread - final notes attached.” A closer with a date prevents the follow-up you would otherwise write next week.
Practical focus
- I am following up on the invoice from Monday
- I am reaching out about the January order
- Could you look over the attached draft?
- Could you send over the updated figures?
- Looping in Dana, who owns this account
- Picking up where we left off last week
- I will get back to you by Friday
- We can move ahead once legal signs off
Section 5
Second-turn practice
In email, the second turn is your reply to their reply, and it usually needs one of three moves: confirm (“Received - I will get back to you by Thursday”), narrow (“Quick question before I look into it: which environment?”), or redirect (“Looping in Amir, who owns that system”).
Drill it on real material: pull five replies from your inbox and answer each in two lines with one phrasal verb. Speed matters more here than in speech - a short second turn within the hour beats a perfect paragraph tomorrow, and the three frames above are what make short possible.
Section 6
Mini scripts to adapt
These four cover most of a working week - change names, dates, and attachments and keep the bones.
Store them as drafts in your mail client, because the moment you need a reminder email is the worst moment to compose one.
Practical focus
- Reminder: “Hi Sam, I am following up on the invoice we discussed on Monday. Could you confirm the payment date? Happy to resend the details if useful.”
- Review request: “Hi Dana, could you look over the attached proposal by Wednesday? I would like to send it out Thursday morning, so even quick comments help.”
- Blocker: “Hi team, a sync error came up during testing. I have tried a full reset and cannot sort it out - could someone from platform look into it today?”
- Reschedule: “Hi Priya, something urgent came up on my side. Could we push our call back to Friday, same time? If earlier works better, I can also do Thursday at 9.”
Section 7
Review checklist
Run this scan before pressing send - it is faster than the follow-up email a vague message creates.
Practical focus
- Does my first line name the thread - following up on what, reaching out about what?
- Does every request verb come with an object and a deadline - look over what, by when?
- Did I use loop in or forward on to manage people, instead of leaving them to find the thread?
- Is every verb client-safe, or did an internal phrase like chase up slip into an external email?
- Does my closer contain a date - get back to you by when?
- Could the recipient answer this email in one line? If not, cut until they can.
Section 8
Personalization worksheet
Open your sent folder and find the three emails you write most often - for most people a reminder, a review request, and a status update. Rewrite each with the verbs from this page, then delete every sentence that does not name a thing, a person, or a date. Save the survivors as templates with blanks: “I am following up on ___ from ___. Could you ___ by ___?”
Next, keep a small decode list for incoming mail: the first time a colleague writes circle back, chase up, or roll out, add it with the sentence it arrived in. Your own company's email dialect is the most useful phrase bank you will ever build, and it is free.
Section 9
Practice tasks
Task 1: The two-line reminder - Write a follow-up on something real that is actually overdue, using following up on plus the original date, and send it. Task 2: Verb surgery on sent mail - Take three emails from your sent folder and replace one flat verb in each (check, send, ask) with the email-native version (look over, send over, follow up on).
Task 3: Register sort - Sort ten verbs from this page into client-safe and internal-only, then verify your sorting against real emails from your manager. Task 4: Reply sprint - Choose five unanswered low-stakes emails and reply to each in two lines with one phrasal verb, inside fifteen minutes.
Task 5: Decode drill - Find one incoming email full of phrasal verbs and rewrite it in plain verbs to prove you decoded it, then answer the original. Task 6: Template test - Use one saved template for a real message and time yourself; under a minute means the template works.
Section 10
Common mistakes to avoid
Email tone errors are invisible to the sender and loud to the receiver - these six are the ones that cost replies.
Practical focus
- Translating your first language's reminder style: “I write again” reads as irritation - the standard is “I am following up on…”.
- Using circle back with external clients who may hear it as evasive corporate filler - give a date instead.
- Confusing send out (distribute to many) with send over (deliver to one person) - the mailing list will notice.
- Hinting instead of asking: “I look forward to the report” hints; “Could you send the report over by Friday?” asks.
- Dropping the object: “I will follow up” with no on-what leaves the reader guessing which thread you mean.
- Stacking three phrasal verbs in one sentence until the email sounds chatty - one per sentence keeps it professional.
Section 11
A practical plan
This plan works inside your real inbox - no invented emails, because tone habits only change on messages with real recipients.
Finish the week with three saved templates. They are the deliverable, and they keep paying after the plan ends.
Practical focus
- Day 1: harvest - collect every phrasal verb from ten real incoming work emails and sort them by function.
- Day 2: write five opener lines and five closer lines using following up on, reaching out, and get back to you by.
- Day 3: rebuild your most recent reminder and review request with the new frames; save both as drafts.
- Day 4: script the blocker email and the reschedule email for a current real situation.
- Day 5: run the register sort - client-safe vs internal - against real emails from your manager.
- Day 6: send two real messages from your templates and time how long each took to write.
- Day 7: check the replies - which lines got fast, short answers - and promote those lines into the permanent templates.
Section 12
How to use feedback
Email gives you feedback nobody announces: reply speed and reply length. If your reminders get answered within a day, your follow-up lines work; if replies keep asking “which document?”, your requests are missing objects.
Once a month, show one real thread to a teacher or fluent colleague and ask two questions only: which line sounds abrupt, and which phrase would they never send to a client. Then fix the template, not just the single email, so the correction repeats itself automatically.
Section 14
Choose phrasal verbs by email function before adding them to professional messages
Phrasal verbs in work emails can be useful, but only when they match the message function and the tone. A good first step is to group them by email job. Follow up belongs to reminders and status checks. Set up belongs to meetings or systems. Look into belongs to investigation. Carry out belongs to procedures or tasks. Hand over belongs to responsibility transfer. If learners study these verbs as one mixed list, they may recognize them but still choose awkwardly in real messages.
Function-based grouping also protects professionalism. Some phrasal verbs sound neutral in business contexts, while others sound too casual or unclear for a formal email. Compare look into with check out, or follow up with chase up. The right choice depends on relationship, urgency, and whether the email needs to sound polite, firm, or concise. Work-email practice should therefore teach meaning and register together. The goal is not to use more phrasal verbs. It is to use the few that make workplace writing clearer and more natural.
Practical focus
- Group work-email phrasal verbs by function: follow-up, setup, investigation, transfer, and completion.
- Check register before using a phrasal verb in a formal or sensitive message.
- Compare similar verbs so casual options do not enter serious emails by accident.
- Prefer clarity over adding phrasal verbs just to sound more natural.
Section 15
Build sentence frames so phrasal verbs do not create grammar mistakes
Many learners know the meaning of a phrasal verb but make mistakes when it enters a sentence. Work emails need stable frames. I wanted to follow up on, Could we set up, I will look into, The team carried out, and I can hand this over to give the learner a safe starting point. These frames show the preposition, object position, tense, and tone all at once. That matters because a wrong preposition or missing object can make a professional message look less controlled than the writer's actual level.
Frame practice also helps with editing. After writing an email, scan the phrasal verbs and ask whether each one has the right object, preposition, and tone. If the sentence feels too casual, replace the phrasal verb with a single-word alternative such as investigate, arrange, complete, continue, or transfer. This choice is not about one style always being better. It is about choosing the version that helps the reader understand the work and relationship quickly.
Practical focus
- Store each work-email phrasal verb inside a complete sentence frame.
- Check object position, preposition, tense, and tone during revision.
- Use single-word alternatives when a phrasal verb sounds too casual or unclear.
- Practise with real email functions such as reminders, meetings, updates, and handovers.