How to Prepare for a Meeting: Checklists and Decision Brief
Use separate organiser and attendee checklists, a copyable decision brief and readiness checks for meetings with missing information or decision-makers.
On this page
Prepare for a meeting by defining the result needed, reading the relevant material, deciding what input you must bring and checking that the right people can participate. Organisers should make the purpose and required preparation clear. Attendees should arrive with questions, evidence and any decision authority their role needs.
Use the two checklists below to check readiness, then copy the decision brief if your meeting must choose a course of action. You do not need a new app or an elaborate document to use either.
Organiser's pre-meeting checklist
Before sending or updating the invitation, check these items:
- Outcome: Write the decision, problem or feedback you need in one sentence.
- Need to meet: Decide whether a written update or comments on a document would do the job.
- People: Invite the people who supply essential information, decide, implement or need to participate. Identify who can make the decision.
- Preparation: Link the exact document or version to read and state the question readers should consider.
- Access: Confirm attendees can open the materials with their actual accounts; check external guest access where relevant.
- Agenda: Give each item an owner, purpose and realistic space. Put the most consequential item early enough to reach it.
- Participation: Include joining details, time zone and any access or accommodation arrangements people need.
- Record: Agree who will capture decisions, unresolved questions and actions, and where the reviewed result will be kept.
For a ready-made running order, use the meeting agenda templates. An agenda answers what happens during the meeting; this checklist asks whether the people and information are ready for it.
Attendee's pre-meeting checklist
- Read the purpose and identify what you are expected to contribute.
- Open the pre-read and review the parts relevant to the stated question.
- Bring the figures, examples, approvals or dependency updates you own. Separate confirmed information from estimates.
- Write the one or two questions or risks that could change the outcome.
- Check actions from the previous meeting that you were responsible for.
- If you cannot decide on behalf of your team, say who must be consulted and what can be agreed today.
- Confirm the time, joining link and how to participate. Raise access or preparation problems before the call when possible.
“I have read the document” is less useful than being able to explain your recommendation and what would change it. Equally, do not invent a view just to appear prepared: identify what you still need to know.
Choose a preparation level that fits the stakes
There is no universal rule that every meeting needs 20 minutes of preparation or that every document must be sent 24 hours ahead. Work backward from what people actually need to do and any formal notice requirements that apply.
| Meeting | Prepare before it | Readiness test |
|---|---|---|
| Routine team check-in | Changes, blockers and updates that affect others | Can people identify where help or coordination is needed? |
| Decision meeting | Options, recommendation, constraints and unresolved evidence | Can the authorised people make a responsible choice? |
| Client review | Latest deliverable, feedback questions and the scope of approval | Is everyone looking at the same version and clear on what sign-off means? |
| One-on-one | Shared topics, previous commitments and support needed | Does each person have space to raise what matters? |
| Formal board or committee | Agenda, papers, notice, quorum and procedural requirements | Has the responsible governance lead checked the applicable rules? |
For formal governance meetings, a general productivity checklist is not enough. Use the board minutes guide alongside the rules applicable to your organisation.
Copy this one-page decision brief
Use this when the meeting needs a decision. Keep it proportionate: a routine choice may need only a few lines, while a consequential decision needs more evidence.
Decision meeting — [topic]
Outcome needed: By the end, decide [specific choice or next step].
Decision owner: [person or group authorised to decide]
Participants and contributions: [who brings which information or implementation perspective]
Background: [what changed, what is already agreed and why this needs attention]
Constraints: [budget, date, capacity, policy or other real limits]
| Option | Benefit | Trade-off / risk | Evidence or assumption |
|---|---|---|---|
| [A] | [Benefit] | [Trade-off] | [Source or explicitly labelled assumption] |
| [B] | [Benefit] | [Trade-off] | [Source or explicitly labelled assumption] |
| [Wait / do nothing, if realistic] | [Benefit] | [Trade-off] | [What we still need to know] |
Recommendation: [preferred option and reasoning]
What could change the recommendation: [missing fact, dependency or risk]
Read beforehand: [specific document, version and relevant section]
Questions for attendees: [the input actually needed]
Record after discussion: [decision, rationale, conditions, actions with owners and agreed dates, unresolved items]
This brief is an original practical format. The broader approach has a useful primary-source example in Atlassian's page-led meeting play, which uses a written purpose, context and outcomes, with reading time built into the meeting. You can also share material beforehand; choose the approach that fits your participants rather than assuming everybody had time to read.
Worked example: prepare a decision, not a vague “catch-up”
This example is fictional.
Vague invitation: “Website update — discuss next steps.” Attendees cannot tell whether they need performance figures, a design review or authority to approve spending.
Prepared invitation: “Choose which of two onboarding changes to test next. Maya will bring the support-ticket themes, Arjun the implementation estimate, and Leah the proposed success measure. Read the two-screen comparison before the call; we will also allow five minutes to review it together. We can approve a test today, but any additional spending needs separate approval.”
Decision brief extract:
| Question | Prepared answer |
|---|---|
| What is being decided? | Which onboarding change to test first |
| What is already fixed? | Existing privacy requirements and the current release window |
| What evidence is available? | Support themes and an implementation estimate; neither is proof of the eventual outcome |
| What remains uncertain? | Whether either change improves completion |
| What can be agreed today? | The test choice, owner and success measure; no unapproved spending |
The invitation makes the limits of the decision visible. A prepared meeting can still end with “we need more evidence”; it should not invent certainty to justify having met.
What to do when preparation is incomplete
The key document is missing or inaccessible. Ask the owner to fix access and state which part is needed. If the meeting depends on reading it, choose explicitly between reading together, narrowing the purpose or rescheduling. Do not quietly expect an absent pre-read to have happened.
An essential decision-maker cannot attend. Confirm whether someone has delegated authority. Otherwise use the time to develop a recommendation and label it as such; do not record it as approval.
The evidence is stale or disputed. Date the source, show the conflicting information and decide what needs checking. A later correction is easier when the original uncertainty was visible.
You are an attendee who has not prepared. Say what you have and have not reviewed. Ask for focused reading time or contribute only within what you know. Do not make up figures or endorse a document you have not seen.
The agenda is too large. Prioritise the decision or issue that makes the meeting necessary. Defer items deliberately and identify how they will return instead of simply extending the meeting.
Prepare the remote and hybrid details
Check the joining link, audio and screen-sharing route before a high-stakes call. Share accessible documents rather than relying only on a screen image. Make space for written contributions and remote attendees who cannot easily interrupt. Ask about required accommodations instead of assuming one meeting format suits everyone.
If you plan to record or transcribe, explain the purpose, tool and intended access in advance and follow applicable law and organisational policy. Confirm the actual sound source the tool will capture; a browser tab, a room microphone and a phone call are different routes. The recording and transcription guide helps choose one.
Manual notes remain an option. Do not turn a short preparation checklist into an unnecessary software setup exercise.
Close the loop after the meeting
Use the meeting's final minutes to read back the decisions and actions while people can correct them. Mark an owner or date as unassigned if none was agreed. Keep proposals, approvals and conditions separate.
Send or save the reviewed record where the intended people can access it. State any unresolved question and how it will be revisited, if agreed. Use the meeting recap template for the after-meeting document rather than copying the invitation and calling it a summary.
If you already have authorised notes and need help organising them, the Meetings Brief summary generator can draft a summary from text. Text is sent to Anthropic's AI and daily limits apply; review the result before sharing. Read the privacy policy, and keep sensitive material out of an external service unless your organisation permits it. AI is optional: the checklist and decision brief above work on their own.
Frequently asked questions
How long should I prepare?
Enough to understand the purpose and contribute the evidence or decision your role requires. A quick check-in and a major governance decision need different preparation. If the material cannot be read within the available time, change the plan rather than claiming an arbitrary number of minutes is sufficient.
What if the invitation has no agenda?
Ask: “What outcome do we need, and what should I bring or read?” If an answer is unavailable, use the meeting title and recent context to prepare questions, and be clear about the limits of what can be decided.
Should preparation always happen before the meeting?
No. For a document-led discussion, planned shared reading can make preparation accessible to everyone. Include that time in the agenda; do not treat unplanned reading as evidence that the meeting was ready.
Should the organiser take the notes?
Agree responsibility before starting. Where practical, give facilitation and detailed notes to different people. In a small meeting one person may do both, but pause to confirm decisions rather than assuming the record will look after itself.
When should we cancel or postpone?
Consider it when the meeting cannot achieve a useful outcome because essential people, authority or information are missing. Explain what must change and who will arrange it. If the remaining discussion still has value, narrow its purpose explicitly.
Sources and scope
Practice source checked 24 October 2026. The checklists, decision brief and example are original working aids; suggested timings are not research-backed universal standards.