Sending a long document before a meeting does not tell colleagues what kind of reading will help. A short guide can connect the document to the decisions you actually need from them.
Choose no more than three questions for this meeting. Give each a stable heading or page reference and say what is open to change. “Review the proposal” becomes more actionable as “At section 3, should the pilot include the second location?”
Separate preparation from the meeting outcome
Explain whether readers should send comments beforehand, bring a position, or simply become familiar with the background. Include a reasonable deadline and use the organisation’s approved sharing method.
An illustrative note might say: “Please read the one-page options summary. At the meeting we need to choose a pilot location; staffing numbers are background estimates, not an approval request.” This prevents a reader from spending their available time polishing details that are not being decided.
If the document changes after circulation, identify the changed section instead of silently replacing it and expecting everyone to rediscover the difference.
At the meeting, return to the same questions. If the discussion uncovers a missing assumption, record that rather than forcing a decision just because it was on the agenda. A useful pre-read makes the decision clearer, including when the responsible answer is to gather one more piece of information.
Editorial illustration from this site’s image library; not documentary evidence of the example or object discussed.