The Inbox Triage Protocol.

The senior professional's real inbox problem is not volume. It is shape. The emails that take the most time are not the longest. They are the ones with three asks, two assumptions, one piece of new information, and a slightly defensive tone.

Those emails get re-read. Three times, four times, before a reply gets written. That re-reading is the cost.

The protocol replaces the re-read

You paste the email. The model returns four things, in this exact order:

• What they actually need. One sentence. Cut through the wind-up.
• The action plan. A numbered list of what gets done, by whom, by when. Three to five items.
• The reply. A draft response, in your tone, that confirms the action plan and asks any unresolved questions.
• The calendar item. A title, a date, a length, a short agenda. Optional. Only if a meeting is needed.

You read the four outputs. You read them once. You edit the reply. You send.

The full prompt

Below is one client email. I am a senior [profession]. Read it carefully. Then produce four sections, in this order, with no other prose:
1. What they actually need. One sentence.
2. Action plan. Numbered list. Each item: action, owner, due date.
3. Draft reply. In a calm, senior, professional tone. Confirm the plan. Ask anything unresolved. No more than 150 words.
4. Calendar item. Only if a meeting is needed. Title, date, length, three-line agenda.
Use placeholders for names you do not know. Do not invent details.

Email:
[paste]

Why this order

The first sentence is the most important output. It forces a translation from how the client wrote, to what the client actually wants. Most emails have the real ask buried in the middle. Pulling it forward is the single highest-leverage move.

The action plan is next because it is the part you would think through anyway, just out loud, instead of in your head while reading the email for the fourth time.

The reply is third because it is the easiest to fix. You read the first two, you have an opinion, and the draft becomes raw material instead of an answer.

What it catches that you would miss

Senior professionals are very good at the work. They are less good at the unstructured asks that arrive in client emails between real work. The two failure modes are:

• The reply that answers what was asked, but not what was meant
• The reply that is fine, but six hours later than it should have been

The protocol fixes both. The first by translating intent into action. The second by making the reply cheap enough that it goes out today.

The rule about sending

You always edit before sending. The model does not know your client, your history with them, or what was said on a call last Tuesday. You do. The draft is scaffolding. The send is yours.

Filed under Workflow · The Leverage Years · Vol. I, Issue 08.