KoltrixCovering a teammate's inbox during vacation without chaos
A before, during and after checklist for vacation cover: out-of-office text that routes people, in-flight threads, decision limits and the return-day catch-up.
On this page(7 sections)
- Before: the person going away
- Out-of-office message
- Handoff list
- Access and decision limits
- During: the person covering
- Daily routine
- Decisions
- What not to do
- After: the return
- The covering person, on the last day
- The returning person, on day one
- Adjusting for the length of the absence
- When the person covering is already busy
- A note on fairness
- Key takeaways
A teammate going on vacation shouldn't mean customers wait two weeks, or that the person covering spends those weeks guessing. Most of the chaos comes from things nobody wrote down the day before they left.
This checklist splits vacation cover into three parts: what the person leaving does, what the person covering does, and how the return goes. Use it as-is or adapt it for your team handbook.
Before: the person going away
Start this two or three days before the last working day, not the last afternoon.
Out-of-office message
- Set dates clearly, including the return date. "Back Monday, October 6" beats "back next week."
- Route people somewhere useful. Name the shared address or the colleague covering, not just "I'll reply when I'm back."
- Separate urgent from non-urgent. Tell people what to do if something can't wait.
- Keep it short. Three or four lines.
A template:
Thanks for your email. I'm out until Monday, October 6, with limited access
to email.
For support or account questions, please write to support@[yourdomain],
where the team will help. For anything about [project/account], contact
[colleague name] at [address].
I'll reply to anything that still needs me when I'm back.
Avoid promising "I'll read everything when I return." You probably won't, and you don't need to.
Handoff list
- List in-flight threads that need action while you're away: customer name, thread link, what's next, by when.
- List threads that can wait so the cover person doesn't feel obliged to touch them.
- Flag expected incoming mail: a renewal decision, a contract reply, a bug fix confirmation.
- Note context the cover person can't find in the thread: "They're sensitive about price; check with the founder before discussing discounts."
A simple format works best:
Thread: [link]
Customer: [name/company]
Status: [waiting on them / waiting on us / waiting on engineering]
Next step: [what and by when]
Notes: [anything not in the thread]
Access and decision limits
- Confirm the cover person has access to the mailboxes they'll need, through their own account. Never share your password.
- Write down what the cover person should not decide alone: refunds above a limit, contract changes, roadmap commitments, anything legal.
- Name an escalation contact for those decisions while you're away.
- Turn off personal forwarding rules that might send mail into a void.
During: the person covering
Daily routine
- Check the handoff list first each day. Deadlines on it beat new mail.
- Work the shared inbox as usual. Customers writing to support@ shouldn't notice any difference.
- Scan mail sent directly to the absent person, if you have access, for anything urgent. Out-of-office replies route most people, but not everyone reads them.
- Reply as yourself. Sign with your own name and, where useful, mention you're covering: "I'm helping while Priya is out this week."
Decisions
- Stay inside the agreed limits. If something needs a decision you weren't given, acknowledge the customer, give a time, and escalate.
- Avoid changing the direction of a relationship. Don't renegotiate, don't promise features, don't make exceptions that set precedent.
- Write down anything significant you decided or promised, in the thread or the handoff list.
A good holding reply when you can't decide:
Thanks for your patience. [Name] is out this week, and I want to make sure
you get the right answer on this. I've passed it to [escalation contact],
and you'll hear back from us by [day].
What not to do
- Don't let mail pile up "for when they're back." That just moves the backlog.
- Don't reply to every newsletter or tool notification in their personal inbox. Leave noise alone.
- Don't silently archive things you're unsure about. Label them for the return instead.
After: the return
The covering person, on the last day
- Update the handoff list: what was resolved, what's still open, what changed.
- Label threads that need the returning person specifically (for example
for-priya) so they're easy to find. - Write a five-line summary. What happened, anything surprising, decisions made, open escalations.
The returning person, on day one
- Read the summary and handoff list first, before opening the inbox.
- Turn off the out-of-office message.
- Work the labeled threads, then mail sent directly to you.
- Skim the rest newest-first. In long threads, the latest message often makes older ones irrelevant.
- Thank the person who covered, and tell them anything they should know for next time.
Block the first morning back for catch-up. Scheduling meetings on the return morning is a reliable way to spend the week behind.
Adjusting for the length of the absence
Not every absence needs the full checklist. Scale it:
| Absence | What's enough |
|---|---|
| One or two days | Out-of-office message, a quick note in team chat about anything due |
| One week | The full "before" list, a daily check by the cover person |
| Two weeks or more | Everything above, plus a mid-point check-in with the escalation contact and a written summary halfway through |
| Parental or extended leave | Treat it as a temporary handoff of ownership, not cover: reassign customers and threads explicitly, and update the out-of-office message as plans change |
For long absences, the biggest risk is relationships drifting. A key customer who hears nothing for a month may assume nobody is minding the account. A short "I'm looking after your account while Sam is on leave" email from the cover person prevents that.
When the person covering is already busy
Cover usually lands on someone with a full workload of their own. Be realistic about what they can absorb:
- Agree on a smaller scope. Maybe they handle the handoff list and urgent mail only, and everything else waits.
- Lower response targets temporarily, and update any auto-acknowledgment or support hours note if customers will notice.
- Split cover between two people by area (billing versus technical questions) instead of piling it all on one.
- Pause non-essential work for the cover person during that week. Cover added on top of an unchanged workload tends to get done badly.
If the team can't cover an absence properly, that is useful information about staffing, not a failure of the person covering.
A note on fairness
Covering is real work. If one teammate always covers for everyone, it becomes an invisible second job. Rotate cover, keep it on the calendar, and treat it as part of workload planning rather than a favor.
Key takeaways
- The out-of-office message should route people somewhere useful, not just announce absence.
- A short handoff list of in-flight threads prevents most problems.
- Agree in writing what the cover person may and may not decide.
- Cover from your own account, sign with your own name, and stay inside your limits.
- Return with a summary and labeled threads, not a raw inbox.
Start with Koltrix
Your domain, one inbox, and an API that sends.
A team inbox where AI sorts and drafts (nothing is sent without your click), plus the transactional API and SMTP relay your product sends with. 7 days free, no card.
