How to Write a Pre-Read People Open Before the Meeting

You attach a nine-page document to the invite, write “please review beforehand,” and walk into the meeting. Four people have read the first page. Two have read nothing. You spend the first fifteen minutes re-presenting what you already wrote, which is the exact outcome the pre-read was supposed to prevent.

The document is rarely the real problem. The problem is that nobody can tell, from the outside, what reading it will cost them or what you need from them afterward. A pre-read is a message first and a document second, and most of them fail at the message.

Put The Ask Above The Attachment

People decide whether to read in about five seconds, from the note that carries the document. That note should say what the meeting must decide, what you need from the reader, and how long the reading takes.

Before:

Hi all, attaching the Q4 vendor consolidation doc for Thursday. Please review beforehand so we can have a productive discussion. Let me know if you have questions.

After:

Thursday’s meeting needs to decide one thing: whether we move the three analytics vendors to a single contract by January 15. The doc is 4 pages and takes about 10 minutes. Please read sections 1 and 3 and bring one objection or one question. If you cannot make the meeting, reply with your vote by Wednesday at noon.

The second version names the decision, the deadline, the reading time, and the part that matters. “Productive discussion” tells nobody anything.

Lead The Document With The Recommendation

Most pre-reads are written in the order the author thought about the problem: background, options, analysis, then a recommendation on page seven. Readers who stop early leave with the history and no conclusion.

Reverse it. Open with a short summary: the decision, your recommendation, and the one or two facts it rests on. Everything after that is evidence for readers who want to check your work. If you want a fuller treatment of this ordering, the same logic runs through the BLUF email guide.

The practice of making people read a written narrative before discussing it is not new. Amazon’s six-page memo habit is the best known example, and CNBC’s account of what Jeff Bezos said about it makes the useful point that writing a good memo is harder than building slides, because prose forces you to decide what matters most. Whether your company reads silently in the room or beforehand, the discipline is the same: you cannot hide a missing conclusion in a paragraph.

Cut Everything The Room Already Knows

Background is the easiest section to over-write, because it feels safe. Ask who in the meeting needs it. If the answer is “everyone but one person,” give that person a link and delete it from the main text.

A good test: for each section, finish the sentence “if the reader skips this, they will be unable to ___.” If you cannot finish it, the section is an appendix. Move it below a line that says “Reference only.”

Aim for pages a reader can finish in ten minutes. A pre-read that takes forty minutes is not a pre-read, it is homework, and people triage homework.

Tell People Which Parts To Skip

Readers are more generous when you respect their time out loud. A single line works: “Sections 1 and 3 are required. Section 2 is background; skip it unless you worked on the 2025 rollout.”

Then close the document with the questions you want answered, written as questions. “Do we accept a 12-month minimum term?” gets a prepared answer. “Thoughts?” gets silence.

If the pre-read is meant to feed a call, pair it with a tight meeting agenda and a calendar invite description people read, so the three pieces say the same thing and do not contradict each other on the date or the decision.

Draft The Cover Note With A Reusable Instruction

The cover note is short, but it is the part people skim under pressure, which is when drafts come out vague. A Wrivio Context for pre-read notes could say:

Rewrite this as a short note introducing a meeting pre-read. State the decision to be made, the deadline, the reading time, and the sections that are required. End with one specific ask. Keep every name, date, figure, and commitment exactly as written. Do not add pleasantries about being productive or collaborative.

Press Ctrl+Shift+Space, paste the rough note, and check the diff to confirm the date and the vote deadline did not change. If you use Cloud, the text goes to Wrivio’s backend; Local keeps it on your machine, which matters when the pre-read covers vendor pricing or personnel.

After the meeting, send a recap email that records the decision, so the next pre-read can start from what was settled.

Common Questions

How long should a meeting pre-read be?

Short enough to read in about ten minutes, which is roughly two to four pages for most business writing. If it runs longer, put the recommendation and key evidence up front and mark the rest as reference.

When should I send a pre-read?

At least one full working day before the meeting, and earlier for decisions that need real thought. A pre-read sent that morning is read by almost nobody, so treat the deadline as a commitment on your side too.

What if people still do not read it?

Make the cost of not reading visible and the cost of reading small. Name the required sections, ask for a reply or a vote beforehand, and consider opening the meeting with five minutes of silent reading, as some teams do, rather than re-presenting.

Should a pre-read be a document or an email?

For a decision that fits in a few paragraphs, put it in the email body so nothing needs opening. Use an attachment or linked doc only when the evidence is too long for a message, and keep the summary in the note either way.

Download Wrivio for Windows to turn a rough pre-read note into a clear ask with the dates and decision left exactly as you wrote them.