Why the first half hour sets the day
The first thirty minutes often determine whether an executive spends the day reacting or directing. If the first input is a crowded inbox, the agenda is set by whoever wrote last. A short brief gives the principal a controlled starting point with the decisions that need attention and the changes that happened overnight. It does not replace the inbox, but it frames how the inbox is read.
The brief also protects the assistant from becoming a human notification feed. Without a routine, urgent items arrive as interruptions throughout the morning, and the same issue is explained three times. A single prepared document creates one moment of orientation and leaves the rest of the morning for work. The discipline is in the timing and the selection, not in the length.
Build one page, not a folder
A brief that requires scrolling through five documents is not a brief. Keep the core to one page with four blocks: decisions needed today, changes since yesterday, calendar risks, and items the principal should read. Anything else belongs in an appendix or a link. The one-page constraint forces the assistant to prioritize rather than summarize everything.
Use plain headings and short lines so the page can be read in a few minutes. Put the most consequential item first, even if it arrived last. The principal should be able to stop reading after the first block and still know what requires a decision. A brief that buries the important item under status updates defeats its purpose.
Separate decisions from awareness
Not every item needs an action. Label each entry as decide, review, or know so the principal can allocate attention correctly. A decide item needs a recommendation and a deadline, a review item needs a document and a question, and a know item needs one sentence of context. This labeling prevents the brief from becoming a list of everything the assistant noticed.
For each decide item, include the options and the assistant's recommendation. The recommendation should be short and explicit, such as proceed with the vendor or wait for legal review. The principal can accept, reject, or ask for more information, and the assistant records the choice. A decision item without a recommendation pushes the analysis back to the principal at the worst time.
Include the calendar's hidden traps
The calendar block should do more than repeat the day's meetings. Flag the events with missing preparation, tight travel connections, conflicting attendees, or unresolved reschedules. Note the one meeting most likely to run long and the one with the least clear purpose. The principal can then decide whether to intervene before the day starts.
Include the time and place for the first external commitment and the name of the person meeting the principal. A short line about parking, access, or a changed entrance saves a scramble later. The assistant should also note any commitment that requires a document the principal has not yet seen. These details are small, but they are exactly the ones that derail a morning.
Write the overnight change log
Overnight changes are easy to miss because they arrive after the principal has stopped reading. Summarize the changes that affect today: a moved flight, a cancelled attendee, a revised figure, or a new request from a board member. State what changed and what the assistant has already done about it. The principal should not have to ask whether the change was handled.
Keep the change log factual and short. Avoid speculation about why someone changed a plan unless the reason affects the decision. If a change creates a conflict, say so directly and offer the options. A change log that reads like a news feed is less useful than three lines that name the consequence.
Set a delivery time and a fallback
Choose a delivery time that fits the principal's actual routine, not an aspirational one. If the principal reads at seven, the brief should arrive by six forty-five with enough time to act. If the principal travels early, send the brief the night before and update it only when something material changes. Consistency matters more than the exact hour.
Define a fallback for mornings when the assistant is unavailable or the information is incomplete. A short message that says the brief is delayed and names the one urgent item is better than silence. The principal should know who to contact if the brief does not arrive. A routine without a fallback becomes a single point of failure.
Review the brief with the principal weekly
Ask the principal once a week which parts of the brief were useful and which were noise. A five-minute conversation is enough to adjust the balance between decisions, awareness, and calendar detail. The assistant should track which items were acted on and which were consistently skipped. The brief should evolve from observed use rather than from the assistant's assumptions.
Do not add a section just because it seems professional. Every block costs attention, and a brief that grows without limit will be skimmed or ignored. For related guidance, see our article on mapping executive inbox decisions and our executive support services. The O*NET occupational profile describes the coordination and information duties that make a brief useful.
Key takeaways
- Keep the core brief to one page with decisions, changes, calendar risks, and required reading.
- Label each item decide, review, or know so the principal can allocate attention.
- Give every decision a recommendation and a deadline, not just a description of the issue.
- Flag calendar traps such as missing preparation, tight travel, and unresolved reschedules.
- Set a reliable delivery time, a fallback, and a weekly review of what the principal actually used.