A colleague returning from leave may be catching up on a full inbox, changed priorities, or both. Your message can make that return easier without asking them to reconstruct events from scattered threads. Focus on what has changed that affects their work, what needs attention now, and where they can find the rest if they want it. Avoid treating absence as consent to disclose personal details or assuming they already know decisions made while they were away. A brief, well-organized email gives them useful context and a clear way to respond.
The useful bits
- Lead with the reason you are writing and the current priority.
- Summarize only updates that affect the colleague’s work.
- State deadlines and next steps without implying they missed something they should know.
Start with a warm, low-pressure opening
Acknowledge that they are back, then move to why you are writing. Keep the greeting friendly but neutral: you do not need to ask why they were away, comment on their leave, or suggest they should be fully caught up. If they have shared personal details with you, follow their lead rather than repeating those details in a work email.
Make it easy to understand whether the message needs action. If it is simply an update, say so. If a decision or reply is needed, name that early and explain the timing. This helps the colleague sort the message without having to read a long history first.
Choose updates by relevance, not chronology
A complete play-by-play of everything that happened during an absence can bury the useful information. Include changes that affect the colleague’s responsibilities, a shared deliverable, a decision they need to make, or a commitment they may now need to handle. Leave out background that has no bearing on their work.
When a change matters, explain the current state and what led to it in a sentence or two. Distinguish decisions from proposals: “The team approved the revised outline” is different from “We are considering a revised outline.” If a detail is uncertain, say what still needs confirmation instead of presenting a guess as settled.
Make the present priority unmistakable
Separate urgent work from useful background. Name the task, the requested action, and any real deadline, including the relevant date or time zone when that could be unclear. If there is no immediate deadline, say that the colleague can review it when they are ready. Do not create urgency simply because the work continued while they were away.
If ownership changed temporarily, explain who is handling the work now and whether that arrangement continues. Avoid wording such as “You missed the discussion” or “As you know” when the colleague could not have been part of it. A neutral account of what happened gives them a fair starting point.
Point to the right source of detail
For a complex project, link the colleague to the current document or identify the relevant email thread by subject and date. Give a short summary in your message anyway; a reference is not a substitute for explaining why the material matters. If there are several threads, say which one contains the latest decision so they do not have to guess.
Share only materials they are authorized to access and that they need for this work. Avoid forwarding a large conversation containing unrelated or sensitive information just to provide context. If access is missing, state that plainly and ask the appropriate owner to help rather than assuming the colleague can see it.
Offer a manageable next step
When several items need attention, separate them into a small set of actions and identify which one comes first. Make clear what you will handle yourself; do not quietly transfer every open task back to the returning colleague. If priorities may have changed, invite them to flag a conflict before work proceeds.
Offer a conversation when the subject is complicated, but do not make a meeting the only route to basic information. A short written summary lets them prepare, check details, or respond asynchronously. If they need to correct your understanding, give them room to do so without framing questions as a failure to catch up.
Example: a concise project handoff
This example gives the colleague the current status, a specific request, and a way to ask for context. Replace the bracketed fields with accurate details; remove anything that does not apply.
To: [colleague] <[name]@example.com> Subject: [Project] — current status and next step Hi [Name], Welcome back. A quick update on [project]: while you were away, [brief relevant change or decision]. The current version is [document or thread reference]. The item needing attention now is [specific task]. Could you [requested action] by [date and time, if applicable]? [Name or role] is handling [other work] for now. If that timing conflicts with your current priorities, let me know and we can confirm what should come first. The background is in [specific thread or document]. I can summarize the decision or talk it through if useful; no need to review unrelated threads. Best, [Your name]
Check that the message is clear and fair
Before sending, read the email as if you had not seen any discussion during the absence. Can you tell what changed, what is already decided, what needs action, and when? Check that the request belongs with this colleague, the deadline is real, and any linked material is relevant and accessible.
After sending, confirm the message went to the intended recipient and that its references point to the material you meant to share. You can confirm the handoff is understood by asking for a simple acknowledgment or clarifying question when one is needed—not by assuming silence means agreement. If priorities remain unclear, resolve them with the relevant people before treating the work as accepted.
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction