A Weekly Executive Inbox Triage That Protects Decision Time

A practical weekly inbox triage for executive assistants that separates decisions from noise and keeps the calendar honest.

Executive assistant triaging an inbox into decisions and updates
Table of Contents

An executive opens their inbox on Monday and finds 240 unread messages. Twelve of them need a decision this week. The rest are updates, receipts, introductions, and threads that ended on Friday without anyone closing them.

A weekly inbox triage is the assistant’s tool for finding those twelve messages before the executive wastes an hour scrolling. It is not a second inbox and it does not involve answering on the executive’s behalf. It is a short, repeatable pass that turns a pile into a short list with context.

Agree on the decision categories first

Before touching the inbox, agree on what counts as a decision. Typical categories include approve spend, choose a vendor, confirm a hire, respond to a client, and set a priority. The list should be short enough to remember and specific enough to apply.

Anything outside the list stays in the inbox or moves to a queue. A triage that escalates everything produces a longer list and the same problem. The value comes from the filter, not from the volume.

Scan for decisions, not for unread

Sort by sender or by thread rather than by arrival time. A decision often arrives in a thread that started last week, so an unread-first pass will miss it. Search the inbox for the agreed categories and for the names of open projects.

Open the thread long enough to identify the ask, the deadline, and the person waiting. Do not attempt to resolve the issue during the scan. The triage is for routing, and resolution belongs in the review block.

Write a one-line ask for each item

For every decision, write one line that names the choice and the deadline: “Approve the vendor contract by Thursday” or “Choose between the two office options before the lease call.” Put the line at the top of the note, not at the bottom of a summary.

Add a link to the thread and the name of the person waiting. The executive should be able to act without reopening five messages. If the ask is unclear, mark it as needing clarification instead of guessing.

Protect a review block

Put the decision list into a calendar block that is long enough to work through it and short enough to survive. Forty-five minutes twice a week is usually better than a two-hour block that gets moved.

Keep the block adjacent to the executive’s existing planning time. A triage list reviewed during a meeting or between calls gets skimmed. A dedicated block gets decisions made.

Close the loop on the same day

After the review, record the decision in the place the team uses: the project note, the tracker, or the thread itself. Tell the person who was waiting. A decision that is made but not communicated creates the same follow-up work as no decision at all.

Return the remaining items to the inbox or move them to a later list with a date. Do not leave a half-finished triage open for a week, because the context will be stale by the next pass.

Measure the triage, not the inbox

Count the decisions surfaced, the time to first response, and the items that were escalated but did not need a decision. These numbers show whether the filter is working.

Do not measure success by inbox zero. An empty inbox is a side effect, not a goal, and chasing it encourages archiving messages that still need attention. The useful outcome is a short, accurate decision list that reaches the executive before the deadline.

Handle the message that is not a decision

Most of the inbox is not a decision. Receipts, confirmations, newsletters, and FYI threads should be archived or routed without reaching the executive. The triage pass should move them out of the way quickly.

Be careful with messages that look routine but hide a commitment. A calendar invitation, a contract attachment, or a request copied to the executive may need a decision even when the subject line sounds administrative. Read enough of the thread to tell the difference.

Keep the list short enough to finish

A decision list with thirty items will not be reviewed. Aim for the handful that carry a deadline in the next two weeks, and put the rest on a later list with a date.

If the list keeps growing, the filter is too broad or the executive is deferring too much. Both are worth raising. A triage that produces an unmanageable list is not protecting decision time; it is moving the pile from one screen to another.

A note on urgent items

Urgent messages need a different route. Agree in advance what qualifies, who to contact, and what the assistant may do without waiting. Do not let the urgent route become the normal route.

When an urgent item is handled outside the triage, record it in the next list so the executive knows what happened. A gap in the record is worse than a short interruption.

What to hand back

When the executive asks for the triage to be automated, resist the temptation to route by keyword alone. A rule can move receipts and newsletters, but it cannot judge whether a client thread contains a real decision.

Keep a human pass for the accounts and projects that matter most, and automate the rest. The weekly triage is small enough to sustain and specific enough to trust, which is why it protects decision time better than a more ambitious system.

#executive assistant#inbox#triage#decision support

Need Help With Delegation?

Discuss your role scope, systems, and recurring delegation priorities.

Get My Free Consultation