Timezone & Async Phrases: Working Across Time Zones
5 exercises on async handoffs, timezone-aware scheduling, and OOO messages. Choose the most natural and professional option.
0 / 11 completed
1 / 11
You've finished a task but your colleague in Singapore is offline. You want to let them know the work is ready without expecting an immediate reply. What do you write?
"I'll leave this in your queue for when you're online": This phrase explicitly frames the handoff as async — it goes into a queue (a natural metaphor in engineering), and it signals that no synchronous response is needed. Real examples: "PR is ready — I'll leave this in your queue for when you're online"; "No rush, I'll leave it in your queue for when you come back online." Option B is too apologetic and a bit passive — "I'll wait" puts you in a holding pattern. Option C ("no rush") is conversational but vague about what "it" is; "your queue" is cleaner. Option D asks for acknowledgement — "let me know" — which still creates a small expectation of reply. Option A is the most intentional, async-native phrase.
2 / 11
You're proposing a meeting time to a colleague in New York (you're in Berlin, UTC+2). You want to be helpful about time conversion. What do you say?
"In your timezone that would be...": Doing the conversion for the other person is a mark of thoughtfulness and async maturity. It removes friction and shows you've already thought about the inconvenience. Real examples: "I'm thinking 4 PM CET — in your timezone that would be 10 AM EST, does that work?"; "In your timezone that would be around 2 PM — let me know if that's feasible." Option A is helpful but the phrasing "your time or ours" can feel slightly transactional. Option C is passive-aggressive and shifts labour unnecessarily. Option D (UTC) is technically correct but impractical — most people don't have UTC mapped in their heads. Option B is the warmest and most professional form.
3 / 11
Two engineering teams in different continents have very few overlapping hours. You want to find a suitable meeting slot. What do you propose?
"Let's find an overlap that works for both teams": "Overlap" is the standard term in distributed-team vocabulary — it refers to the window when two timezone-separated groups are both online. The phrase is collaborative, action-oriented, and neutral. Real examples: "Let's find an overlap that works for both teams — I see a 2-hour window around 3 PM UTC"; "We're trying to find an overlap that works for both teams without anyone staying up late." Option A is vague and just restates the problem. Option C is blunt and can feel unfair — it singles out one team to sacrifice. Option D is valid practice but doesn't directly address finding the slot. Option B names the goal precisely and moves things forward.
4 / 11
A question comes up in a team thread that doesn't need an immediate answer. You want to handle it asynchronously without scheduling a call. What do you write?
"I'll async this — no need to wait on me": Using "async" as a verb is now idiomatic in distributed engineering teams — it signals a deliberate choice to handle something outside real-time. The phrase also releases the other party from waiting, which is a key async courtesy. Real examples: "Good question — I'll async this in Notion, no need to wait"; "I'll async this — expect a write-up in the doc by EOD." Option A is too casual and doesn't assign any ownership. Option C sounds dismissive of meetings without offering a clear alternative process. Option D is reasonable but wordy and slightly passive ("get to it later"). Option B is crisp, uses the right async-native vocabulary, and sets a clear expectation.
5 / 11
You're writing an out-of-office (OOO) auto-reply for a week-long leave. Which message is the most professional and informative?
Clear OOO messages: A good OOO message includes three elements: exact dates, an escalation path for urgencies, and a commitment to follow up. This sets clear expectations, respects the recipient's time, and prevents messages from falling through cracks. Real examples: "I'm OOO 21–28 June. Urgent: contact mark@company.com. Non-urgent: I'll respond 29 June."; "Out of office until 28 June — for time-sensitive requests contact the team lead at [email]." Option A is friendly but vague — "this week" is ambiguous, and there's no escalation path. Option C is formal but unhelpful — it offers no contact alternative or return date. Option D is too casual ("Ping me on Slack") for external or cross-company communication. Option B is complete, professional, and actionable.
6 / 11
John from the London team is reviewing your pull request. He mentions a potential issue with the database connection pooling that might require further investigation. You want to acknowledge his feedback and indicate you'll address it when you have time without pressuring him for an immediate response. What's the most appropriate comment to leave on the code review platform?
The key here is to acknowledge the feedback and offer support without creating urgency. Option 2 politely confirms receipt and offers assistance, addressing a common concern when dealing with asynchronous communication. Options 1 & 3 are too demanding; they imply immediate action which isn't appropriate given the time zone difference. Option 4 asks for elaboration but doesn't express appreciation.
7 / 11
Sarah (San Francisco) is working on a critical bug fix. David (London) needs to understand the changes before deploying. David's timezone is GMT+1. Which Slack message best communicates that Sarah has finished her work and is happy to answer questions when David's online?
This question tests phrasing for asynchronous communication. Option A is too demanding and assumes immediate availability. Option B implies deployment without confirmation. Option D suggests a specific time, which isn't ideal when working across continents. Option C politely informs David of progress while offering support later.
8 / 11
You're writing the PR description for a new feature that impacts users in both Europe and Asia. You need to highlight this potential timezone consideration. Which of the following sentences is most appropriate?
This assesses awareness of potential impact. Option A is too vague. Option B doesn't acknowledge the specific timezone differences. Option D is misleading and overpromises. Option C accurately describes a realistic possibility and provides context, demonstrating an understanding of asynchronous delays.
9 / 11
Mark (Sydney) needs to schedule a brief sync with the team in New York. He wants to be considerate of everyone's time and avoid scheduling during peak working hours in either location. Which proposal is the most professional?
This tests proactive scheduling practices. Option A is overly assertive and doesn't consider other timezones. Option B is ambiguous and relies on assumptions about Mark's timezone. Option D lacks detail and professionalism. Option C demonstrates consideration by suggesting a specific time (with the correct timezone abbreviation) and asking for confirmation, crucial when dealing with asynchronous communication.
10 / 11
Emily (Berlin) has left a comment on a code review that requires clarification but doesn't necessitate an immediate discussion. What is the best way to respond asynchronously?
This focuses on appropriate responses in asynchronous situations. Option A is dismissive and doesn't acknowledge the need for clarification. Option B demonstrates a willingness to investigate without pressure. Options C and D are overly reactive and disrupt the flow of asynchronous communication – it's better to defer until needed.
11 / 11
You're setting up an out-of-office (OOO) auto-reply for a two-week period. Which of the following messages best balances professionalism and information regarding asynchronous communication?
This assesses the appropriate tone and level of detail for an OOO message. Option A is completely unhelpful. Option B provides essential contact information for urgent matters, acknowledging asynchronous support while clearly stating availability. Options C and D are too informal and lack crucial details.
What will I practise in "Timezone & Async Phrases: Working Across Time Zones"?
This module focuses on Phrasebook — real workplace phrasing you'll use on the job. It contains 11 scenario-based multiple-choice questions with instant feedback.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account or sign-up required.
How many questions does this exercise have?
This module includes 11 questions. Each one gives an immediate right/wrong result plus a full explanation of the correct phrasing.
What happens if I answer a question incorrectly?
You'll see the correct answer highlighted straight away, along with a plain-English explanation of why it's right and why the other options don't fit — mistakes are part of the learning here.
Can I retry the exercise if I want a better score?
Yes — use the 'Try again' button on the results screen to reset your score and go through the questions again. There's no limit on attempts.
Who is this Phrasebook exercise for?
It's aimed at IT professionals with working English who want to sound more natural and precise around phrasebook — useful whether you're preparing for real conversations at work or just building confidence with the vocabulary.
Do I need an account to track my progress?
No account is needed. Your progress through the exercise is tracked locally in your browser for the current session, and you can replay the module at any time.
How is this different from reading a blog article?
This exercise is an interactive drill that tests and reinforces specific phrasing through multiple-choice questions with instant feedback, while blog articles explain concepts and vocabulary in prose. The two work well together.
Where can I find more Phrasebook exercises?
See the Phrasebook hub for more modules like this one, or browse the full Exercises page for other IT-English topics.
Can I complete this exercise on my phone?
Yes — every exercise on CoderSlingo is fully responsive and works on phones and tablets, so you can practise anywhere.