← All patterns Pattern . triage and briefing

Cross-platform mailbox intelligence.

A pattern for turning email and meeting-transcript backlogs into a prioritised morning briefing. Described as a reusable capability.

Input email + transcript backlog Output prioritised briefing Cadence daily Sorts by priority and workstream
The pattern

Read the backlog overnight, hand back a short briefing in the morning.

The skill triages an email and meeting-transcript backlog into a prioritised morning briefing. It surfaces unanswered messages, open follow-ups and half-finished commitments, and organises them by priority and by workstream so the first ten minutes of a day are spent deciding rather than scrolling.

What it surfaces

  • Unanswered messages that are still waiting on you.
  • Follow-ups that you said you would come back to.
  • Half-finished commitments that risk slipping.

How it sorts

  • By priority, so the urgent items lead.
  • By workstream, so context does not get fragmented.
Why a briefing, not an inbox

The inbox is a queue; a briefing is a decision surface.

An inbox shows everything in arrival order, which is the wrong order for deciding what to do first. Reshaping the backlog into a ranked briefing turns a reading task into a deciding task. Microsoft 365 provides the mail and calendar surface; the triage logic sits on top and does not act on anything by itself.

A capability pattern. No mailbox contents, no names, no employer process.