You Sent the Pre-Read 10 Minutes Before the Meeting. Nobody Read It.

The calendar alert fires. You drop the link to your meticulously crafted six-pager into Slack, tagging the five people in your next meeting. “Quick pre-read for our sync in 10!” you type, hitting send with a feeling of accomplishment.

You join the video call. “So,” you begin, “any initial thoughts on the proposal in the doc?”

Silence. One person is still reading the title. Another has the link open in a new tab but is clearly still finishing an email. Your engineering lead, bless their heart, says, “Sorry, just seeing this now. Can you walk us through the highlights?”

And just like that, your 30-minute decision meeting has become a 30-minute presentation. The pre-read failed. Again.

We all want the pre-read dream: a meeting where everyone arrives with full context, ready to debate trade-offs and make a crisp decision. We get the pre-read reality: a frantic skim followed by a live narration of the document you sent. The meeting becomes a monologue, and any real discussion is pushed to the last five minutes or, worse, to a follow-up meeting.

The problem isn't that your team is lazy. The problem is you’ve made the pre-read an impossible task. Sending a dense document minutes before a call isn’t preparation; it’s a pop quiz.

To make pre-reads work, you have to treat them not as homework, but as the first five minutes of the meeting, done asynchronously. This requires a contract with your team, built on a few non-negotiable rules.

The 24-Hour Rule

Send your pre-read at least 24 hours in advance. Not 12 hours. Not the evening before. A full business day.

This isn’t about giving people more time to procrastinate. It’s about respecting their schedule. Your last-minute document is an interruption that demands they drop their focused work to get up to speed on your priority. A 24-hour lead time allows them to fit your doc into their own workflow, whether it's first thing in the morning or during an afternoon focus block. It transforms your request from an urgent demand into a scheduled task.

The TL;DR is the Only Requirement

Your six-page analysis is for you. The first paragraph is for them.

Structure your pre-read like a pyramid. The absolute top must contain everything needed for a baseline decision.

• Line 1: The Goal. "We need to decide on the Q3 launch strategy for Project Heron."
• Line 2: The Context. "User growth has flattened, but engagement within our power-user cohort is up 15%."
• Line 3: The Options & Your Recommendation. "We have three options: A (big marketing push), B (focus on core feature adoption), or C (new experimental feature). I recommend B."

That’s it. That’s the pre-read. The rest of the document is an appendix for the curious. Anyone who reads those three lines can now participate in the meeting. If someone wants to challenge your recommendation, they know exactly where to dig deeper into the document to find the supporting data.

State the Expectation in the Message

Never just drop a link. Your Slack or email message is the instruction manual. Be explicit about what you need.

Don’t write: “Here’s the doc for tomorrow.”

Do write: “Pre-read for Heron Strategy @ 10am tomorrow: The decision we need to make is in the first paragraph. Please come prepared with your biggest risk or objection to Option B. The full analysis is below for context.”

This framing does two things. It defines the scope of the required reading (one paragraph), lowering the barrier to entry. And it primes them for the specific type of feedback you need, shifting their mindset from passive consumption to active critique.

Be Willing to Cancel the Meeting

This is the hardest and most important step. In the first minute of the meeting, ask: “Did everyone get a chance to review the one-paragraph summary?”

If the answer is no, you don’t plow ahead and present the doc. You end the meeting.

“No problem. Sounds like we’re not ready for a productive discussion. I’ll cancel this one so you can all have the time back. Let’s find 15 minutes tomorrow once everyone has had a chance to read the summary.”

This will feel painful the first time you do it. It might even feel passive-aggressive. But it’s not. It’s a powerful act of cultural reinforcement. You are protecting everyone's time from a low-value meeting. You are demonstrating that preparation is not optional. After you do this once or twice, people will show up prepared. The social contract will be set.

Your goal isn’t to get people to read your documents. Your goal is to have shorter, higher-quality meetings that result in clear decisions. Stop using pre-reads as a box to check and start using them as a tool to fundamentally change how your team collaborates.