All Things Workplace

How-to: Send a Pre-Read Pack People Actually Open

Oct 21, 2026 | How-tos, Meetings & 1:1s

Pre-reads fail for predictable reasons: too long, no ask, sent too late, or dumped as a folder of links with no map. A pre-read pack people open is short, decision-framed, and respectful of attention. It turns the meeting into judgment time instead of first-time reading time.

Time box: 25–40 minutes to build the pack once your content exists, plus send 24–48 hours ahead (longer for board-level or cross-timezone reviews). If you cannot send ahead, shrink the meeting goal or accept that the room will skim live.

Use this from the Individual Contributor hub when you own a working session, and from New Manager / Director / VP when you run staff or leadership forums.

When to use / when not

Use when:
– The meeting needs a decision, design critique, or informed risk discussion
– Attendees can usefully prepare alone
– Artifacts already exist (memo, deck, prototype, data cut)

Do not use when:
– The meeting is purely generative brainstorming with no prior material
– Content is confidential beyond the invite list (use proper secure channels)
– You are hiding the recommendation in an appendix to avoid accountability

A pre-read is not a substitute for live conversation on sensitive people topics; use appropriate processes via how HR works.

Prep

Decide before you assemble files:

  • Meeting purpose in one sentence (decide / align / advise)
  • The ask for readers (comment by X, come with preference A vs B, read sections 1–3 only)
  • Minimum viable artifact (one memo or one slim deck, not both unless necessary)
  • Audience and what they already know
  • Owner of each open question

For cross-functional rooms, frame impact in shared language; how departments work together and, when money is involved, finance for non-finance managers.

Steps

  1. Write the cover note first (5–10 min). If the note is unclear, the pack is unclear.
  2. Pick one primary doc. Link supporting appendix material; do not require it.
  3. Add a decision box at the top of the primary doc: options, recommendation, deadline impact.
  4. Cut ruthlessly. Target a primary read measured in minutes, not hours. Put charts in appendix.
  5. Number the questions you want answered in the meeting.
  6. Send in the invite and chat with the same cover note.
  7. Set a comment-by time before the meeting when possible.
  8. Open the meeting by confirming who read and starting at disagreements, not page one.

Script (what to say / send)

Cover note (email / Slack / invite description):

Pre-read for [meeting] on [date]. Purpose: decide [decision]. Primary doc (8–10 min read): [link]. Please comment on questions 1–3 by [time]. Appendix optional. Recommendation is on page 1: [one line].

Decision box inside the doc:

Decision needed: [X]
Options: A / B / C
Recommendation: [B] because [reasons]
Ask of attendees: approve, amend, or reject with an alternative
Non-goals this meeting: [list]

Reminder (morning of, if needed):

Gentle nudge: pre-read is [link]. We’ll start on disagreements with the recommendation, not a full live read.

Meeting open:

“Assume the pre-read. Raise hands if you need a two-minute skim. Then we’ll go question by question. Goal: leave with a decision owner and next step.”

If half the room did not read:

“We have two choices: twenty-minute silent read now and a shorter decision window, or reschedule. I recommend silent read for ten, then decide.”

Output artifact

Pre-read pack:

  1. Cover note (fixed text block you reuse)
  2. Primary memo or slim deck with decision box on top
  3. Appendix (data, detailed design, legal notes) clearly marked optional
  4. Comment checklist: questions 1–n
  5. Decision log updated after the meeting

Store the pack where attendees already work (same drive/wiki as the team). Do not invent a new tool for each meeting.

When the decision affects go-to-market, include one short section on customer or pipeline impact using language consistent with how sales works, without stuffing CRM screenshots into the mandatory read.

Watch-outs

  • Novel-length decks. If everything is important, nothing is.
  • Sending Friday 6pm for Monday 9am across timezones without warning.
  • No recommendation. “What do you all think?” with thirty pages wastes seniors.
  • Punishing people who comment early. If critique gets you politically hurt, people stop preparing.
  • Reading the pack aloud anyway. Reward readers by starting at the controversy.
  • Link rot and permission errors. Check access as a different user if you can.
  • Pack as gotcha. Do not hide the hard tradeoff on slide 47.

Related hubs