What must the next teammate know?
You have fixed an export preview and need another teammate to finish the release. A message says only “preview fixed, please ship”.
The question
RelayDesk and both work schedules are fictional. For this case, Berlin is fixed at UTC+1 and Chicago at UTC−6; do not apply other calendar rules. It is 14:30 UTC. You work in Berlin, and the receiving engineer works in Chicago.
| Local start | Local end | UTC start | UTC end | |
|---|---|---|---|---|
| Berlin | 08:00 | 17:00 | 07:00 | 16:00 |
| Chicago | 09:00 | 17:00 | 15:00 | 23:00 |
The normal overlap is 15:00–16:00 UTC. The receiving engineer must approve the release.
The preview is correct for the supplied example. The receiving engineer still needs the customer’s goal, the change made and the checks required before release.
“Choose your next action and explain the trade-off.”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: What is missing from the message?
What would you do here? Open the move you’d make.
Write the decision context
The strong move. The next teammate needs a reasoned decision, not just a status label.
Send more screenshots without explaining the goal.
Tempting, but it misses something. Screenshots alone do not explain why this change is right.
See how a strong candidate says it
“Explain the customer’s job, the original failure, the change and what remains unverified.”
Why it works: The next teammate needs a reasoned decision, not just a status label.
Step 2: What overlap can you use?
What would you do here? Open the move you’d make.
Prepare first, then use overlap
The strong move. A readable handoff makes scarce live time useful.
Wait until 16:00 UTC to begin the handoff.
Tempting, but it misses something. Your workday ends when the normal overlap ends.
See how a strong candidate says it
“The normal overlap is one hour, from 15:00 to 16:00 UTC. Prepare the written handoff now, then use overlap for unresolved questions.”
Why it works: A readable handoff makes scarce live time useful.
Step 3: What changes if the start moves?
The Chicago engineer’s start moves to 10:00 local, or 16:00 UTC. Both end times stay unchanged.
What would you do here? Open the move you’d make.
Make the handoff asynchronous
The strong move. An asynchronous handoff can preserve ownership without assuming after-hours availability.
Assume you must stay late without discussing it.
Tempting, but it misses something. The case gives no agreement to extend either person’s workday.
See how a strong candidate says it
“There is now no working-time overlap. Send the evidence and open decision before your day ends, with an explicit acknowledgement request.”
Why it works: An asynchronous handoff can preserve ownership without assuming after-hours availability.
Step 4: Who makes the final call?
What would you do here? Open the move you’d make.
Confirm ownership and the next update
The strong move. Sending a message does not prove that someone has accepted the open decision.
Mark the release approved when you send the handoff.
Tempting, but it misses something. Only the receiving engineer can approve it; message delivery is not acceptance.
See how a strong candidate says it
“Ask the engineer to acknowledge ownership, run the remaining checks and state the release decision. Tell the customer when the next confirmed update will arrive.”
Why it works: Sending a message does not prove that someone has accepted the open decision.
The answer, in short
- Decision
- Leave a clear asynchronous handoff and confirm the release owner.
- Because
- The late start removes overlap, and release approval is still open.
- What would change it
- A changed schedule or a verified approval could change the next step.
Common traps
- Local clock times can hide a missing overlap.
- Sent context is not accepted ownership.
Check your answer
- I used the supplied UTC offsets.
- I wrote the customer goal and open checks.
- I handled the lost overlap.
- I kept release authority explicit.
Last reviewed Nov 10, 2026