Building a Daily Executive Brief That Survives a Busy Morning

Decide what the brief is for

A daily brief should help an executive make one or two decisions before the day begins, not reproduce every message that arrived overnight. Start by naming the decisions the brief is meant to support, such as which meetings need preparation or which approvals are waiting. Then remove any section that does not change a decision. A shorter brief that gets read is more useful than a complete one that sits unopened.

Ask the executive how they use the first thirty minutes of the day. Some leaders want a single screen on a phone, while others want a printable page beside their calendar. The format should match that habit rather than the assistant's preference. Observe the actual morning routine before designing the template. A brief that requires a laptop when the executive reads on a phone will fail quietly.

Set a delivery time that leaves room for a response before the first meeting. If the brief arrives at the same moment the executive walks into a call, it becomes a record rather than a tool. Test the timing for a week and ask whether the brief was read before the first decision. Adjust the schedule before changing the content, because late delivery is often mistaken for weak content.

Pull from a small set of trusted sources

Use one calendar, one task or approval queue, and one source for external news that matters to the business. Pulling from five systems creates a brief that is long, late, and hard to defend when a number is wrong. Write down the source for each section so a reader can check it. A brief without traceable sources becomes a set of assertions that no one can verify under pressure.

Separate what changed from what is merely scheduled. A meeting that has been on the calendar for a month is context, while a new attendee or a moved deadline is news. Lead with the changes that affect a decision or a commitment. The executive should be able to see the delta in under a minute, even on a phone between two calls.

Include one line on what the assistant is handling so the executive does not duplicate the work. That line should name the action and the expected completion, not a general status. Keep it short enough that it does not become a second task list. The brief is a coordination tool, not a diary of everything the office touched yesterday. Mark it done when the action is complete so the next brief does not repeat the same note.

Write the items so they can be acted on

Each item should say what happened, why it matters, and what the executive needs to do. Avoid labels such as urgent or important without a reason. If an item needs a decision, state the options and the recommendation. If it needs no action, say so and remove it from the next brief so the page stays useful. A reader should never have to open three tabs to understand the ask.

Use plain language and avoid internal shorthand that only one team understands. A new chief of staff should be able to read the brief without asking for a translation. Spell out names on first use and link to the source document rather than pasting a long excerpt. Clarity is more valuable than a polished tone when the reader has five minutes.

Put the most consequential item first, even if it arrived last. Order by the cost of delay rather than by the time the message arrived. If two items compete for the same meeting, combine them into one decision. The brief should reduce the number of separate conversations the executive needs to have before lunch. The order itself is a signal about what the office believes matters most.

Protect the brief from drift

Review the brief after two weeks and mark the sections that were never read. Remove them or replace them with something that changes a decision. A template tends to grow as each team adds a request, so someone must own the subtraction. The owner should be the person who writes the brief, not a committee that meets monthly. Ask the executive which section they would miss if it disappeared.

Keep a short list of standing questions the executive asks every morning. If the same question appears three days in a row, add the answer to the template. If a section produces no question and no action for a month, cut it. The brief should evolve from observed use rather than from a planning workshop that never sees a real morning.

When the executive is traveling or in a different time zone, adjust the delivery time and the sources rather than skipping the brief. A shorter travel version can cover only the meetings, approvals, and travel changes for that day. Note the time zone at the top so the reader does not misread a deadline. The format can change without losing the habit that makes the brief useful.

Measure whether the brief changed the day

At the end of the week, ask which decisions were made because of the brief and which were made without it. A brief that never precedes a decision is entertainment, not support. Record one example and one gap. The example shows what to keep, and the gap shows what to fix next week. Keep the note short enough to review at the next planning session.

Track the time between delivery and the first action the executive takes on an item. A long gap may mean the brief arrives too late or the item is not clear enough to act on. Do not use the metric to pressure the executive; use it to improve the timing and the wording. The goal is a brief that fits the morning rhythm rather than one that adds another obligation.

Choose one change for the next week, such as a new delivery time or a shorter approval section. Keep the rest of the template stable so the comparison is meaningful. Review the change after five working days and keep it only if the brief was read earlier or acted on faster. A daily brief improves through small, tested adjustments rather than a full redesign.

Related resources

• Measuring brief freshness in executive daily summaries
• Turning Executive Inbox Approvals into a Tracked Queue
• Preparing a Chief of Staff Weekly Agenda from Open Decisions

Frequently asked questions