Template

Meeting Pre‑Read & Action Follow‑Up Template

A ready-to-use pre-read and action follow-up template that helps meetings surface decisions, assign owners, record success criteria, and capture quick learning notes. Includes copy‑ready email text, timelines and RSVP rules, a decision record, an action tracker, retro prompts, and a short meeting effectiveness checklist.

Purpose

This template helps teams run read-before meetings that reliably produce decisions, clear owners, measurable success criteria, and short learning notes that feed organizational memory. Use the pre-read to prepare attendees; use the follow-up to convert meeting outcomes into tracked work and learning artifacts.

How to use this template

Share the pre-read at least 48 hours before the meeting (longer for complex topics). Bring a printed or shared digital copy to the meeting for reference. After the meeting, publish the decision summary and add action items to the team’s action tracker within 24 hours.

Pre‑Read (Share before the meeting)

Use this section as the top of a short document or email. Keep the pre-read focused — people are busy, so give them only what’s necessary to decide or contribute.

  • Objective: One short sentence describing the meeting outcome you need (e.g., "Decide vendor for Q4 inventory system rollout").
  • Required context / data: Key facts, metrics, or links (e.g., cost range, timeline constraints, vendor scorecard, customer impact summary). Use bullets and links — don’t paste long reports.
  • Options to consider: Short list of the realistic alternatives being evaluated (2–4 options). For each option, 1–2 lines of pros/cons.
  • Decision sought: Precise decision prompt you expect the meeting to answer (e.g., "Approve Vendor A and schedule pilot in Plant B").
  • Attendees & roles: List who must attend and their role (decision owner, subject expert, implementer, approver, observer). Mark who has final authority if appropriate.
  • Prep required: Clear, small tasks for attendees (e.g., "Review vendor scorecard and bring questions; submit cost concerns via comments before X date").
  • Timebox: Meeting duration and time allocation for key items (e.g., "45 minutes: 10m context, 20m discussion, 10m decision/assignment, 5m wrap").
  • Attachments / links: Link short supporting documents (max 3) and call out the exact pages or sections to read.

Suggested Timelines & RSVP Rules

  • Send pre-read: 72 hours before for complex decisions, 48 hours for routine decisions, 24 hours for operational check-ins.
  • RSVP deadline: at least 24 hours before the meeting. If a critical attendee cannot make it, require a named delegate with decision authority.
  • Read‑before expectation: attendees should mark "Read" and note 1–2 questions or objections in comments before the meeting.

Meeting Agenda (timeboxed)

  1. Opening & objective reminder (2 minutes) — facilitator restates the decision sought and success criteria.
  2. Context highlight (5–10 minutes) — short presentation limited to key data called out in the pre-read.
  3. Clarifying questions (5 minutes) — address factual clarifications only.
  4. Options discussion (time as required) — focus on tradeoffs relevant to success criteria.
  5. Decision or next step (5–10 minutes) — record the decision, owner, success criteria, and checkpoints.
  6. Wrap & immediate next steps (2–5 minutes) — confirm owners and deadlines.

Decision Record (Publish within 24 hours)

Capture every meeting decision in a concise, consistent format so teams can find how and why a decision was made later.

Decision Summary

Title: (short, searchable title)

Decision: (one clear sentence stating what was decided)

Owner: (person accountable for executing the decision)

Rationale / key considerations: (2–4 bullet points summarizing why)

Success criteria: (how we will know the decision worked — measurable where possible)

Next checkpoints: (dates and what will be reviewed at each checkpoint)

Linked artifacts: (links to pre-read, vendor docs, project plan, scorecards)

Action Follow‑Up Template (Action Tracker row)

Use a simple table in your team tracker or project board. Example columns:

  • Action ID
  • Action — short description
  • Owner — who will do it
  • Due date
  • Success criteria / Definition of Done
  • Checkpoint dates — interim reviews
  • Status — Not started / In progress / Blocked / Done
  • Linked decision — reference to Decision ID

Retrospective Learning Note (1–3 lines)

Capture one short learning: what went well about the meeting or decision process, and one small improvement for next time. Example prompts:

  • What assumption proved wrong and how will we test it?
  • What part of the pre-read was most helpful? What was unnecessary?
  • Did the meeting keep to its timebox? If not, why?

Quick copy‑paste templates

Pre‑read email subject / body

Subject: Pre‑read: [Meeting title] — Decision needed: [short decision]

Body: Objective: [one sentence]. Please read the linked pre-read and mark Read by [RSVP deadline]. Key links: [link1], [link2]. Bring questions to the meeting. Timebox: [duration].

Follow‑up / Decision email

Subject: Decision: [Decision title] — Owner: [name]

Body: Decision: [one sentence]. Owner: [name]. Success criteria: [measure]. Next checkpoint: [date]. Actions added to tracker: [link]. Learning note: [one line].

Lightweight Meeting Effectiveness Checklist (use after meeting)

  • Was the decision outcome clear? (yes/no)
  • Is there a named owner with a measurable success criterion? (yes/no)
  • Were the pre-read materials concise and sufficient? (yes/no)
  • Were action items entered into the tracker within 24 hours? (yes/no)
  • Is there at least one short learning note captured? (yes/no)

Common pitfalls & short remedies

  • Pitfall: Meeting produces only minutes, not ownership. Remedy: Never record a decision without a named owner and success criteria.
  • Pitfall: Too many attachments. Remedy: Link a single "concise context" file and reserve deep docs for optional reading.
  • Pitfall: Missing authority. Remedy: Clarify decision authority in the pre-read and name a delegate when needed.

Implementation tips for teams

  • Standardize the Decision ID format (e.g., DEC-2026-042) so records are searchable.
  • Integrate action items with your team board (Trello, Jira, Asana) and include the Decision ID in each card.
  • Keep pre-reads to one page of core content plus 1–2 short attachments.
Discuss Ask the Librarian

Discussion

Comments and conversation will live here.