A meeting pre-read needs a question, not just a file

A meeting pre-read needs a question, not just a file. Tell people which decision or discussion the material prepares, where to look, what response to bring and when to read it.

“Please review before tomorrow” leaves every important choice to the recipient. They have to guess which pages matter, how carefully to read, whether silence means approval and what the meeting is supposed to produce. Attaching the right document to a vague request still creates poor preparation.

Start with the work the meeting must do

The pre-read exists to change the quality of the conversation. Define that change before choosing the document.

A weak request says:

Please review the launch brief before Thursday.

A useful request says:

On Thursday we will decide whether to launch to the pilot group or all customers. Read pages 2–4 of the launch brief. Come ready to identify one risk that would block your preferred option. Add factual corrections by Wednesday at 3 p.m.

The second version tells a reader why the material matters and what mental work to do. It also separates two kinds of response: factual corrections can happen before the meeting; the trade-off belongs in the discussion.

Give each reader a lens

Different people should not necessarily read the same material in the same way.

In a launch decision:

• support may test whether the rollout creates work the team cannot absorb;
• engineering may challenge the estimate and failure modes;
• sales may identify customer commitments the options affect;
• the decision owner may compare the whole trade-off.

Give each participant a lens in one sentence. This is not about scripting their opinion. It prevents a room full of people from highlighting the same obvious paragraph while the important constraint goes unexamined.

The lens should match why that person is invited. If you cannot explain what perspective someone should bring, reconsider whether they need to attend. A reader can comment before the meeting without becoming part of the meeting audience.

Point to the minimum useful material

“Read the deck” makes the recipient perform document archaeology. A strong pre-read identifies the smallest source that supports the meeting question:

• pages 2–4, not the entire launch brief;
• the comparison table, not every research note behind it;
• the two changed clauses, not the full agreement;
• the decision record and one new estimate, not the whole project folder.

If the long source is necessary, add a reading guide. State which sections are essential, which are reference only and which have changed since the last review.

Do not copy the same information into a shorter attachment merely to make it feel approachable. That creates another version to reconcile. Keep the authoritative material where it belongs and write a short path through it.

This complements the rule that a file needs its meeting context. The source meeting explains why a document matters after the fact; the pre-read question explains how to use it before the discussion.

Ask for a visible response

“No comments” can mean agreement, lack of time, a missed message or uncertainty about where to respond. Choose a response that makes preparation visible without manufacturing busywork.

Useful requests include:

• correct factual errors in the shared material;
• choose a preferred option and give one reason;
• identify a blocking risk;
• add one question the meeting must answer;
• acknowledge that the material was reviewed and no objection remains.

Match the response to the purpose. Do not ask everyone to leave a comment if the only useful outcome is reading for context. Do require an explicit answer when the meeting owner would otherwise mistake silence for approval.

Keep responses with the meeting or source material, not scattered across private chat and email. Follow-up questions are easier to resolve when they stay with the meeting that created them.

Set a deadline that leaves room to react

A pre-read deadline of “before the meeting” gives the organiser no time to use the responses. If a factual correction arrives two minutes before the call, the options may already be wrong.

Set the deadline based on what happens next:

• corrections must arrive early enough to update the material;
• blocking risks must arrive early enough to investigate or reschedule;
• preferences may be due closer to the meeting if they need no synthesis;
• a long or technical source needs enough working time to read properly.

Explain the deadline briefly. “Comments by Wednesday at 3 p.m. so Mira can revise the options before Thursday” is easier to respect than an unexplained date.

If the material changes after the deadline, tell readers what changed and whether they need to review again. Do not silently replace the file and assume prior acknowledgements still apply.

Do not replay the whole pre-read in the meeting

Opening with a full presentation teaches people that reading was optional. It also uses prepared participants’ time to subsidise unprepared ones.

Begin with a short readiness check:

We are choosing pilot or general release. The brief was updated with support’s correction. Is anyone missing context that prevents the decision?

If the room is not ready, choose deliberately:

1. pause for a short silent review if the material is genuinely brief;
2. narrow the decision to what the available context supports;
3. reschedule the decision and protect the rest of the agenda;
4. proceed with the authorised, prepared people if absent context is not required.

Do not shame someone for missing a pre-read whose request arrived late or had no clear question. Treat preparation failure as a system signal: the scope, timing, audience or delivery needs repair.

Use a five-line pre-read request

Before sending, fill in these lines:

Meeting outcome: Decide pilot or general release.

Read: Launch brief, pages 2–4.

Your lens: Identify operational risks support cannot absorb.

Respond: Add corrections and one blocking risk.

Deadline: Wednesday at 3 p.m., so the options can be revised before Thursday.

Attach or link the source material to the relevant meeting record and agenda item. Scripta can keep the objective, agenda, files, notes and resulting decisions together. It does not decide who needs to read what; that is the organiser’s editorial judgment.

The pre-read should leave the meeting with less explaining to do and a clearer question to answer. A file alone cannot create that outcome. A focused request can.