Vacation Backlog Re-Entry Planner

Triage email, messages, tasks, and project updates after time away without letting the backlog eat your whole week.

Prompt Template

You are a productivity coach helping me return from time away without panic-scrolling through every message. Build a re-entry plan.

**Time away:** [dates and number of workdays missed]
**Role:** [manager / founder / IC / freelancer / student / other]
**First day back work hours:** [available hours]
**Known urgent items:** [anything already flagged]
**Inbox/message volume:** [email count, Slack/Teams count, tickets, DMs]
**Meetings already scheduled:** [list]
**Active projects before leaving:** [project list and status]
**Delegates or coverage owners:** [who covered what]
**Energy level:** [rested / jet-lagged / stressed / sick / unknown]
**Hard deadlines this week:** [deadlines]

Create:
1. **First 30 minutes plan** — what to check first and what not to touch yet.
2. **Backlog triage rules** — delete/archive, skim, respond, schedule, delegate, escalate.
3. **Priority map** — urgent, important, waiting-for-me, informational, and stale/no action.
4. **Time-blocked first day** — realistic schedule with recovery buffers and no-meeting recommendations.
5. **Inbox processing script** — search filters, labels, and reply templates for common situations.
6. **Project re-entry checklist** — how to get status from owners without asking everyone for essays.
7. **Stakeholder update** — short message announcing what I am prioritizing and when people can expect replies.
8. **Week-one recovery plan** — how to prevent the backlog from swallowing deep work.

Be strict: the goal is not to catch up on everything; it is to regain control.

Example Output

Re-Entry Plan: First Day Back

First 30 Minutes

1. Check calendar for today/tomorrow only.

2. Search email for: `from:(manager OR key client) newer_than:10d`.

3. Check Slack mentions from coverage owner and project leads.

4. Write a “triage in progress” status so people know you are back.

**Do not:** open newsletters, browse every channel, or reply chronologically.

Triage Rules

| Bucket | Rule | Action |

|---|---|---|

| Urgent + blocking | Someone cannot proceed without you | Reply or schedule same-day |

| Important, not urgent | Project decisions, strategy docs | Time-block this week |

| FYI | Updates with no ask | Archive after skim |

| Stale | Deadline passed or resolved by others | Archive; thank coverage owner if needed |

First-Day Schedule

9:00-9:30 — Calendar + urgent scan

9:30-10:15 — Coverage owner debrief

10:15-11:30 — Email triage pass 1

11:30-12:00 — Stakeholder update

1:00-2:30 — Top project catch-up

2:30-3:00 — Break/walk

3:00-4:00 — Reply batch

4:00-4:30 — Plan tomorrow

Tips for Best Results

  • 💡Never process backlog oldest-first; start with people and projects where your delay is blocking progress.
  • 💡Use a temporary status like “Back today, triaging urgent items by 2pm” to reduce duplicate nudges.
  • 💡Book a short debrief with your coverage owner before digging through every thread.
  • 💡Leave 30-40% of the first day unscheduled — re-entry always has surprise debris, like a productivity version of Die Hard air vents.