Management
●
May 26, 2025
●
8 min reading
Meeting Pre-Read : a guide with template
.avif)
You join a meeting and realize half the people have no idea why they’re there.
But it doesn’t have to be that way.
In this article, you’ll learn: what a pre-read actually is (and isn’t) and how to structure it so people actually read it
What Is a Pre-Read?
A pre-read is a short document you share before a meeting. It gives your team the key information they need—before anyone speaks a word.
Pre-reads work for almost any kind of meeting. You're hiring someone? Share the candidate’s profile and evaluation criteria beforehand. Running a strategy session? Add in market data and your proposed direction. Kicking off a project? Drop in the goals, timelines, and scope.
With a pre-read, your team shows up aligned. No one’s caught off guard. No one’s left wondering, “Wait, what’s this meeting about again?”
What does it concretely look like ? A brief summary, a few slides, a doc with bullet points.
Recommended Elements & Structure of a Pre-Read

A bad pre-read is worse than no pre-read.
Let’s start with the golden rule—brevity. Your pre-read should take no more than 5 minutes to read. That’s your limit. If it’s longer, your team won’t finish it. They might not even open it.
Aim for one page. Two, max.
Now let’s talk structure. Here’s the format we recommend:
1. Title and Meeting Info
Start with the basics. What’s this about? When’s the meeting? Who’s coming?
- Meeting Title: Be specific. “Hiring Debrief: Product Manager Final Round” is better than “Hiring Meeting.”
- Date & Time
- Participants
Simple. Clear. On to the next.
2. Executive Summary
This is the heart of your pre-read. One short paragraph explaining what the meeting is for, what decisions need to be made, and what context people need to show up ready.
- Why are we meeting?
- What are we trying to decide or solve?
- What should participants know beforehand?
If your team reads only this section, they should still get the big picture.
3. Agenda
List the topics you’ll cover—in order—with time blocks. Yes, time blocks. If you have 30 minutes, every minute should have a purpose.
Example:
- 5 min – Recap of candidate interviews
- 10 min – Panel feedback
- 10 min – Hiring decision
- 5 min – Next steps
This helps everyone focus. It also keeps your meeting from running off the rails.
4. Background & Context
Add any supporting data, links, or documents people need to review.
But here’s the key—don’t overload.
Summarize the essentials. Link to the full report, slide deck, or resume, but don’t paste it all into the pre-read. Curate the info. Respect your readers’ time.
5. Questions to Prepare For
End with 2 or 3 questions you expect participants to think about.
This is where the magic happens. These prompts push your team to show up with ideas—not just observations.
Example:
- What concerns (if any) do you have about the candidate’s fit for the role?
- Is the current timeline for launch still realistic?
- Which priorities should we revisit before finalizing the roadmap?
These questions set the tone. They focus the discussion. They turn passive attendees into active participants.
Pre-Read Outline Template

Here’s a plug-and-play format you can copy, paste, and personalize:
[Meeting Title]
- Date & Time: [Insert date & time]
- Participants: [List of attendees]
- Owner: [Who’s running the meeting?]
- Type of Meeting: [Decision / Brainstorm / Update / Hiring Debrief, etc.]
Executive Summary
A quick overview of what this meeting is about and why it matters.
Example:
We’re meeting to debrief on the final round interviews for the Product Manager role. We’ll review feedback from each panelist, align on hiring concerns, and decide whether to move forward with an offer. We also need to confirm the start date if we proceed.
Agenda
A breakdown of what we’ll cover and how much time we’ll spend on each item.
- 5 min – Recap of interviews & candidate background
- 10 min – Panel feedback roundtable
- 10 min – Discussion & decision
- 5 min – Next steps + offer timeline
Background & Context
Key information, links, or data your team should review before joining.
- [Link to candidate’s resume]
- [Link to interview notes or scorecards]
- [Summary of role requirements]
- [Any concerns raised during the interview process]
Use this section to surface only the most relevant information. Don’t drown your team in documents. Give them just enough to be ready.
Discussion Questions
These are the key points we’ll want input on during the meeting.
- What stood out to you—positively or negatively—about the candidate?
- Are there any red flags that need to be addressed before moving forward?
- Do we have alignment on the candidate’s fit with the team and company?
- If we decide to hire, when should we aim for a start date?
Optional Notes
Add anything else that could help guide the conversation.
This is the place for edge cases, concerns, or extra context that doesn’t fit elsewhere. Use it sparingly.
Automate Agendas & Minutes with Noota

Writing agendas and tracking minutes is a pain.
It’s repetitive. It’s time-consuming. And it pulls your focus away from what actually matters—running a productive meeting.
That’s why you need a tool like Noota.
- Customizable Agenda Templates : Before your meeting, pick a template or build your own. Whether it’s a hiring debrief, strategy session, or project check-in, Noota lets you set the structure upfront. No more blank docs. No more last-minute scrambling. You build a format once, then reuse it every time.
- Automated Recording & Real-Time Transcription : The second your meeting starts, Noota starts working. It records, transcribes, and captures everything in real time. You’re not typing. You’re not distracted. You’re fully present.
- Automatic Action Item Extraction: This is the game-changer. Noota doesn’t just write what was said. It figures out what needs to happen next. Who owns what. What the deadlines are.
- Instant Sharing :As soon as the meeting ends, Noota wraps everything up—agenda, minutes, tasks, and decisions—into a clean summary. One click, and your whole team gets it. Even the people who missed the meeting stay in sync.
- Tool Integrations : Noota fits right into your workflow. It connects with Notion, Slack, HubSpot, your ATS—whatever tools you’re already using. So the insights from your meeting don’t stay stuck in a document. They move with you.
You want to streamline your meetings before & after ? Try Noota for free now.
FAQ
1. What is a meeting pre-read and why does it matter?
A pre-read is a short document shared before a meeting that gives attendees the key information they need before anyone speaks a word. It explains why the meeting is happening, what decisions need to be made, and what context people should have going in.
The practical result: people show up aligned instead of confused, discussions start at the right level instead of from scratch, and passive attendees become active participants because they've had time to think. Without a pre-read, the first ten minutes of most meetings are just catch-up — wasted time that a five-minute document could eliminate.
2. What should a meeting pre-read include?
Five elements cover everything a useful pre-read needs:
- Title and meeting info — specific meeting name, date, time, and participants so there's no ambiguity about what's happening
- Executive summary — one short paragraph answering why you're meeting, what you're trying to decide, and what people need to know; if your team reads only this section, they should still get the full picture
- Time-boxed agenda — topics in order with minutes allocated to each; if you have 30 minutes, every minute should have a purpose
- Background and context — summarize the essentials and link to full documents rather than pasting everything in; curate ruthlessly
- Questions to prepare for — two or three specific prompts that push people to arrive with ideas, not just observations
3. How long should a meeting pre-read be?
No more than five minutes to read — one page ideally, two at most. If it's longer, most people won't finish it, and some won't open it at all. A bad pre-read that overwhelms people is worse than no pre-read because it trains your team to ignore future ones.
The goal is to give people just enough to be ready, not to replace the meeting itself. Summarize the essentials in the document and link to the full report, slide deck, or candidate profile for anyone who wants to go deeper.
4. What are the best questions to include at the end of a pre-read?
The discussion questions section is where pre-reads deliver the most value — they're what turns the meeting from a presentation into a conversation. Good questions are specific to the decision being made and force real preparation.
Examples that work:
- For a hiring debrief: "What concerns do you have about the candidate's fit for the role?"
- For a strategy session: "Is the current launch timeline still realistic given what we know now?"
- For a project kickoff: "Which priorities should we revisit before finalizing the roadmap?"
Avoid vague questions like "What do you think?" — they produce vague answers. The more specific the question, the more useful the pre-meeting thinking it generates.
5. Is there a tool that automates meeting agendas and follow-up minutes?
Noota handles both sides. Before the meeting, you build a template once — hiring debrief, strategy session, project check-in — and reuse it every time so the structure is set without last-minute scrambling. During the call, it records and transcribes in real time in 50+ languages with speaker identification. When the meeting ends, it extracts action items with owners and deadlines automatically and generates a clean summary you can share in one click.
Trusted by 5,000+ clients including Carrefour, Deloitte, and EY. Integrates with Notion, Slack, HubSpot, your ATS, and 80+ other tools. GDPR-compliant, SOC2 Type II certified, EU data centers.
.webp)

.avif)
