Brief for the decision, not the topic
A weak brief collects everything known about a subject. A useful one tells the executive why the meeting exists, what result is needed, who is involved, and where judgment is required. Put the desired outcome in the first line.
Use a one-page structure
Place the objective and requested decision first. Follow with the recommended position, supporting facts, consequences of delay, and participant interests. Finish with questions, risks, and likely actions. Link source documents rather than pasting them into the brief.
Set a workflow with clear owners
Request inputs three business days before the meeting, assemble the draft two days before, and deliver the final with a preparation block one day before. Use consistent naming and storage. Our guide to executive support SOPs shows how to document recurring workflows.
Run a five-minute quality check
Verify names, titles, dates, amounts, and links. Remove old comments and conflicting recommendations. Distinguish facts from assumptions and check the audience for sensitive material. The US General Services Administration advises setting a purpose, sharing materials in advance, and clarifying roles in its accessible meeting guidance.
Close the loop
After the meeting, record the decision, action owners, dates, and unresolved questions. For board-facing work, use our board meeting preparation checklist to coordinate materials and approvals.