PlaybookPrompts

Triage an overflowing inbox after time away

Productivity & Planning emailinboxtime-management

Returning from vacation or a heads-down sprint to 200 unread emails is a real productivity tax. This prompt gives you a structured triage system to process the backlog in one session rather than all day.

Prompt
You are a chief of staff helping me process an email backlog after {{DAYS_AWAY}} days away. Help me build a triage system I can apply right now.

My role: {{MY_ROLE}}
My current top priorities (max 3): {{CURRENT_PRIORITIES}}
Domains or people whose emails are almost always urgent for me: {{HIGH_PRIORITY_SENDERS}}
What I have already handled out-of-office (if anything): {{ALREADY_HANDLED}}

Follow these steps:

1. Give me a sorting rule set — a list of 6–8 criteria I can apply to subject line and sender to instantly categorize an email as: Act today / Act this week / Read only / Delete or archive / Delegate.
2. Write a template reply I can send in under 30 seconds to emails that need a quick acknowledgment but not a full response yet.
3. Tell me which category of emails I am most likely to over-prioritize (common mistake for someone in {{MY_ROLE}}) and why.
4. Suggest a time-box for this triage session: how long I should spend, and what I should do if I hit the limit and am not done.
5. Write a two-sentence out-of-office-style reply I can send to any email that arrived during my absence and still needs a real answer, buying me 48 more hours.

Note: This prompt helps with triage decisions, not with reading or drafting the actual email replies.
Variables to fill in
  • {{DAYS_AWAY}}
  • {{MY_ROLE}}
  • {{CURRENT_PRIORITIES}}
  • {{HIGH_PRIORITY_SENDERS}}
  • {{ALREADY_HANDLED}}

How to use this prompt

  1. Copy the prompt above (Copy button on the top-right).
  2. Replace each {{VAR}} with your own value. Variables: {{DAYS_AWAY}}{{MY_ROLE}}{{CURRENT_PRIORITIES}}{{HIGH_PRIORITY_SENDERS}}{{ALREADY_HANDLED}}.
  3. Paste it into one of the recommended tools below.
  4. Iterate: tighten constraints in the prompt if the output is generic.

Why this prompt is structured this way

The prompt is split into explicit steps because LLMs do better when the path is named, not implied. Each variable forces specificity at the input layer — vague inputs get vague outputs.

Heads up: some of the links on this page are affiliate links — meaning we may earn a commission if you sign up after clicking, at no extra cost to you. We only recommend tools we'd put on our own stack. You can see our full affiliate disclosure here.

Pair this prompt with a tool

The PlaybookPrompts weekly

One short email per week. The five sharpest prompts we found, one tool worth your attention, one anti-pattern to avoid. Unsubscribe in one click.

Newsletter signup is not configured. Set PUBLIC_NEWSLETTER_USERNAME in the build env.