Executive meeting pre-read checklist for faster decisions

Meeting preparation

Key takeaways

• Capture decision owner, requested outcome, unresolved questions, source documents, and distribution deadline.
• Apply this control: verify versions, permissions, figures, dates, reading order, and claim ownership.
• Escalate if a required source is missing or accountable owners provide conflicting figures.

Operating data

Playbook

A pre-read should reduce uncertainty around a named decision, not demonstrate how much material the team collected. Begin with the decision owner, requested outcome, unresolved questions, source documents, and distribution deadline. Put the short decision memo first, followed by evidence in reading order. Background that does not affect the choice belongs in an appendix or linked repository.

Before release, reconcile versions, permissions, figures, dates, and claim ownership. Test every restricted link as a participant with equivalent access. Atlassian's meeting-notes template separates agenda, discussion, and actions; a decision pre-read should go further by tying each material assertion to its source and identifying who can explain it in the room.

Stop distribution when a required source is missing or accountable owners provide conflicting figures. The assistant should display both values, their origins, and the owner needed to resolve them, not choose the number that looks current. If resolution will miss the deadline, the chair decides whether to narrow the agenda, mark the uncertainty, or postpone the affected decision.

After the meeting, note which questions were answered, which material went unused, and whether access or correction failures consumed discussion time. This evidence improves the next packet without forcing one checklist onto every meeting. Research and briefing support can formalize the source review, and the board meeting guide covers controlled distribution for governance settings.