Emails & Async Communication
A quick-reference phrasebook — 30 ready-to-use phrases you can look up and copy for professional IT emails, Slack messages, and status updates, from opening lines to pushback and closings. Want interactive practice instead? Try the Email & Professional Writing exercises.
- Lead with context: the reader doesn't have your mental state — set the scene in the first sentence
- One ask per message: multiple requests buried in one email get partial answers
- Set a deadline: "when you have time" means never — "by Thursday" gets a response
- Separate FYI from requests: state clearly whether a reply is expected
Opening Lines
- Following up on our conversation from [yesterday / the sprint planningˆ]…Most natural async opener — references shared context
- As discussed in our last meeting, I wanted to confirm…Connects to a prior sync — creates a paper trail
- I wanted to reach out regarding [the deployment timeline / the open ticket].Formal but not stiff — use for cross-team emails
- Quick update on [the migration / our investigation]:…"Quick update" sets correct expectations for a short message
- Looping in [name] who will be taking this forward.Handoff opener — adds recipient and clarifies ownership
- Just to keep everyone in the loop:…Informal broadcast opener for status updates to a team
Making Requests
- Could you please review the attached PR / doc by [Friday]?Polite request + clear deadline
- I'd appreciate it if you could share your feedback before the meeting.Soft request — good for optional or low-urgency asks
- Would it be possible to get this deployed to staging by end of day?Hedged request that still communicates urgency
- When you have a moment, could you take a look at [issue #123]?Lowest pressure phrasing — for non-blocking requests
- I need your sign-off on this before we can proceed.Clear blocker — don't hedge when approval is genuinely required
- Can you confirm whether [the API keys have been rotated]?Yes/no request — ask directly to get a direct answer
Declining & Pushing Back
- Unfortunately, this falls outside the current sprint scope — can we add it to the backlog?Declines and offers an alternative in one sentence
- We'd need to adjust the timeline or reduce scope to accommodate this.Classic scope/schedule/quality trade-off framing
- I'd suggest deprioritizing this for now — here's my reasoning:…Disagrees professionally and backs it up
- I have concerns about [the approach / the timeline] — could we discuss before we commit?Raises a flag without blocking — proposes a sync
- That's not something our team owns — you'd want to reach out to [team / person].Clear redirect — avoids absorbing work that isn't yours
- I want to make sure we're aligned on the priority — is this more urgent than [X]?Forces an explicit prioritization conversation
Closing Lines
- Let me know if you have any questions or need more context.Standard professional close — always safe
- Happy to jump on a call if it's easier to discuss this live.Offers sync when async is getting complex
- Looking forward to your feedback.Warm close for review / approval requests
- Please let me know if you need anything else from my side.Signals you're done and hands the ball over
- I'll follow up by [day / time] if I haven't heard back.Sets a follow-up expectation — reduces ambiguity
- Thanks for your time on this — much appreciated.Warm, genuine close for longer requests or difficult asks
Status Updates & Async Reports
- Status: 🟢 On track / 🟡 At risk / 🔴 BlockedTraffic light format — instantly scannable for managers
- Progress this week: [what was done]. Next steps: [what's next]. Blockers: [none / …].Three-part async status template — complete and concise
- ETA remains [Friday] — no change to the timeline.Proactive no-news update — confirms nothing changed
- We're behind by [X] — here's the revised plan:…Lead with the bad news, follow with the recovery plan
- No action needed — this is for visibility only.Sets expectation that no reply is required
- Action required by [name] by [date]:…Explicit call-to-action — use when someone must do something
Frequently Asked Questions
What's the difference between 'Acknowledged Received' and simply 'Received'? When should I use each?
'Acknowledged Received' indicates you've processed the email and understand its content, often requiring a response or action. 'Received' is purely confirmation that the email reached the recipient's inbox. Use 'Acknowledged Received' when the email needs further attention; otherwise, 'Received' is sufficient for basic notification.
I need to request clarification on a vague Jira ticket description - what's the best phrasing?
A good approach is: 'Regarding Jira Ticket #1234, I require further clarity. Specifically, could you elaborate on [mention the ambiguous part] and its impact on [relevant system/task]? Providing this detail will ensure accurate implementation.'
My team uses Slack heavily – how does asynchronous communication translate into a productive Slack message?
While Slack is real-time, framing your request as 'Please investigate' or 'Can you look into' provides context and sets expectations for an eventual response, mirroring the async nature of email. Clearly state the desired outcome and any relevant timelines to avoid immediate requests for updates.
How do I politely ask for a status update on a task that's been assigned to someone else?
A suitable phrase is: 'Hi [Name], Following up on the status of Task X. Could you provide an estimated completion timeframe? This will help us with our planning and ensure we're aligned on expectations.'
What's a good way to express urgency without sounding demanding in an email?
'Given the upcoming deadline for [Project/Task], I wanted to flag this issue requiring immediate attention. Please let me know if you foresee any potential delays or require additional resources to meet the target.'
I'm getting emails asking about 'MTTR' - what does that mean and how do I respond?
'MTTR' (Mean Time To Resolution) refers to the average time taken to fix an issue. You can politely reply: 'Could you clarify which specific incident you're referring to when mentioning MTTR? Providing context will help me understand your request.'
How do I gracefully decline a request for assistance that falls outside my scope?
'Thank you for reaching out. While I'm happy to assist with [related area], this particular request falls outside my current responsibilities and expertise. I can recommend [colleague/resource] who may be better suited to address your needs.'
I need to inform someone that a task is blocked – what's the most professional way to phrase it?
'Hi [Name], I wanted to let you know that progress on [Task] is currently blocked due to [reason]. I'm actively working to resolve this and will update you as soon as there's an estimated resolution time. Please let me know if you have any further questions.'
What's the best way to acknowledge receipt of a complex technical document?
'Thank you for sharing this comprehensive document regarding [Document Name]. I'll review it thoroughly and will reach out with any clarifying questions or feedback. Your insights are greatly appreciated.'
I received an email requesting a 'walkthrough' – what does that actually mean in a professional setting?
'Regarding the requested walkthrough, could you please clarify which specific aspects of [System/Process] you'd like me to demonstrate? Providing details about your goals will allow me to tailor the walkthrough effectively and ensure it meets your needs.'