An executive brief needs enough context to support a decision and enough restraint to make that decision visible. A page full of metrics can still leave the meeting unsure what action to take.
Set the reporting boundary
Name the portfolio, reporting period and projects included. Distinguish current reported information from accepted or verified information. Explain gaps that materially affect the summary, such as a missing update or an unresolved review.
Comparisons are most useful when the reader understands what is being compared. Keep the reporting boundary stable, or explain the change.
Separate different kinds of exception
A late submission, a movement in the schedule and an unresolved review question are different signals. They need different people and different next actions. Combining them into one unexplained score can hide the work the team needs to do.
For each significant exception, give the project, the observation and the source record. Keep background detail accessible without reproducing the entire review in the brief.
Write the decision before the commentary
Identify what the meeting is being asked to resolve: a response owner, an escalation, a request for further information or a proposed next step. Name who is responsible for carrying the decision forward and the agreed follow-up date.
Where narrative assistance is used, review every consequential statement against its source. Generated wording does not establish that a milestone, explanation or conclusion has been accepted.
Carry the result into the next cycle
Record the outcome beside the issue. At the next meeting, show whether the action is complete, still open or superseded by a new decision. The brief becomes more useful when it closes the loop between observation and action.
The illustrative portfolio decision brief in our examples library shows three fictional projects with distinct follow-up needs.