6 Free Meeting Agenda Templates (Editable Word + Text)
Download six editable meeting agendas with exact timings: standup, one-on-one, client, kickoff, retrospective and leadership. Includes a worked example.
A meeting agenda is a plan for a conversation: the outcome you need, the topics to cover, who leads each item and the time available. A useful agenda makes it possible to prepare and to decide what can wait. It does not need to be long.
These six free templates cover a team standup, one-on-one, client meeting, project kickoff, retrospective and board or leadership meeting. Each has a schedule whose minutes add up, preparation prompts and space for follow-ups. Change the topics and timings to fit your meeting.
Download all six as an editable Word document (.docx) or plain text (.txt). No sign-up is required. The same agendas appear below, so you can copy only the one you need. The Word file is a document to edit; the text version can be pasted into your own notes or document tool.
Choose the right agenda
| Meeting | Suggested length | Leave with |
|---|---|---|
| Team standup | 15 minutes | Priorities and blocker follow-ups |
| One-on-one | 30 minutes | Support needs, feedback and commitments |
| Client meeting | 50 minutes | Clear decisions and next deliverables |
| Project kickoff | 80 minutes | Scope, responsibilities and first milestones |
| Retrospective | 60 minutes | Improvement experiments with review dates |
| Board or leadership | 90 minutes | Recorded decisions and follow-ups |
The durations are editable starting points, not rules about how long every meeting should take. If an item needs a decision from someone who cannot attend, resolve that dependency before treating the meeting as a decision session.
Fill in five things before sending
- Outcome: write a result, such as “Choose the pilot’s first customer group,” instead of a broad label such as “Discuss launch.”
- People: include those who supply essential information, do the work or have the authority to decide. Tell others how they will receive the outcome.
- Preparation: link the exact document or options to review and state what participants should look for. Send it with enough time for the actual preparation required.
- Schedule: include a start time and time zone, a lead for each topic and a closing recap. The tables below show minutes elapsed from the start, not clock times.
- Record: leave space to distinguish decisions, assigned actions and unresolved questions. A question is not an action until someone agrees to own the follow-up.
If you add an item, assign it time and shorten, defer or remove another item. A “parking lot” should name the deferred topic and who needs to resolve it; it should not become an invisible extension to the meeting.
1. Team standup agenda — 15 minutes
Purpose: Agree the next work priorities and identify blockers that need a separate follow-up.
Prepare: Update the task board. Bring one priority and any help needed; keep detailed status updates in writing.
Date: [date] Start/time zone: [time, zone]
Team: [names] Facilitator: [name]
| Elapsed time | Minutes | Topic | Lead | Output |
|---|---|---|---|---|
| 00–02 | 2 | Confirm today’s shared priority | Facilitator | One clear focus |
| 02–12 | 10 | Round: progress, next work, blockers | Team members | Dependencies and help needed |
| 12–15 | 3 | Assign blocker follow-ups | Facilitator + owners | Owner and next contact time |
For five speakers, the ten-minute round allows two minutes each. For more people, divide the ten minutes between them, use written updates, or split by workstream. Move troubleshooting to a follow-up with the people involved.
Keep at the bottom of this agenda:
- Blocker: [issue] Follow-up owner: [name] Next contact: [date/time]
- Parking lot: [topic and people needed]
This is a general team standup template. If you use Scrum, the official Scrum Guide defines the Daily Scrum as a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt their plan. The team can choose its structure; the familiar three-question round is not mandatory.
2. One-on-one agenda — 30 minutes
Purpose: Discuss the employee’s priorities, support needs and feedback; agree practical follow-ups.
Prepare: Both people add topics beforehand. Review the last agreed actions. Decide which sensitive matters should stay outside a shared record.
Date: [date] Start/time zone: [time, zone]
Employee: [name] Manager: [name] Cadence: [weekly/fortnightly/other]
| Elapsed time | Minutes | Topic | Lead | Output |
|---|---|---|---|---|
| 00–15 | 15 | Employee topics and support needs | Employee | Priorities, challenges, help requested |
| 15–25 | 10 | Feedback, context and development | Both | Specific feedback and next steps |
| 25–30 | 5 | Recap commitments | Both | Actions, owners and dates |
Start with the employee’s topics, then rebalance the time together if something urgent arises. Keep this conversation distinct from a task-by-task status report. Agree what is recorded and who can access it.
Keep at the bottom of this agenda:
- What is going well? [notes]
- What is difficult, and what support would help? [notes]
- Action: [task] Owner: [name] Due: [date]
3. Client meeting agenda — 50 minutes
Purpose: Resolve the named client questions and agree the next deliverables without implying unapproved commitments.
Prepare: Share the proposal, progress report or decision options. Name who can approve scope, cost and dates.
Date: [date] Start/time zone: [time, zone]
Client attendees: [names] Internal attendees: [names]
Decision needed: [specific question]
| Elapsed time | Minutes | Topic | Lead | Output |
|---|---|---|---|---|
| 00–05 | 5 | Welcome and confirm the objective | Meeting lead | Agreed purpose |
| 05–10 | 5 | Review previous actions | Action owners | Complete, blocked or revised |
| 10–25 | 15 | Main topic or decision 1 | [topic owner] | Decision or unresolved point |
| 25–35 | 10 | Main topic or decision 2 | [topic owner] | Decision or unresolved point |
| 35–45 | 10 | Client questions | Client + team | Answers and follow-ups |
| 45–50 | 5 | Confirm next steps | Meeting lead | Owners, dates and review point |
This version totals 50 minutes. If your calendar slot is 45 minutes, remove five minutes from a named discussion and update the schedule. Do not silently cut the client’s questions or the closing recap.
Keep at the bottom of this agenda:
- Decision: [agreed outcome or “not decided”]
- Deliverable: [item] Owner: [name] Due: [date]
- Open question: [question] Next review: [date, if agreed]
4. Project kickoff agenda — 80 minutes
Purpose: Align the team on the goal, scope, responsibilities, dependencies and first milestones.
Prepare: Circulate the project brief. Bring scope boundaries, draft milestones and known dependencies; mark estimates as estimates.
Project: [name] Date: [date] Start/time zone: [time, zone]
Sponsor: [name] Project lead: [name] Participants: [names]
| Elapsed time | Minutes | Topic | Lead | Output |
|---|---|---|---|---|
| 00–10 | 10 | Why the project exists | Sponsor | Goal and success measures |
| 10–25 | 15 | Scope and exclusions | Project lead | What is in and out |
| 25–35 | 10 | Roles and decision authority | Project lead | Who owns and approves what |
| 35–50 | 15 | Timeline and dependencies | Workstream leads | Milestones and constraints |
| 50–60 | 10 | Working agreements | Team | Communication and escalation routes |
| 60–75 | 15 | Questions and risks | Team | Unresolved assumptions |
| 75–80 | 5 | Confirm first actions | Project lead | Owners and due dates |
This version totals 80 minutes. For a 60-minute slot, move the ten-minute working-agreements discussion to a pre-read, reduce scope to ten minutes and questions to ten minutes. Recalculate the elapsed times before sending.
Keep at the bottom of this agenda:
- Success measure: [observable outcome]
- In scope: [items] Out of scope: [items]
- First action: [task] Owner: [name] Due: [date]
5. Retrospective agenda — 60 minutes
Purpose: Choose improvements based on the period just completed and decide how to check whether they help.
Prepare: Review evidence from the period and the last improvement experiment. Invite observations without requiring people to disclose sensitive personal details.
Period/project: [name] Date: [date] Start/time zone: [time, zone]
Facilitator: [name] Participants: [names]
| Elapsed time | Minutes | Topic | Lead | Output |
|---|---|---|---|---|
| 00–05 | 5 | Set the context and working agreements | Facilitator | Shared scope for the discussion |
| 05–20 | 15 | What helped? | Team | Practices worth keeping |
| 20–35 | 15 | What got in the way? | Team | Specific problems and contributing factors |
| 35–50 | 15 | Choose improvement experiments | Team | Changes the team can actually try |
| 50–60 | 10 | Assign and schedule review | Owners + facilitator | Owner, measure and review date |
Discuss events and systems rather than assigning blame. Separate a hypothesis about a problem from evidence. Choose only as many experiments as the team can carry out and review; do not turn every observation into a task.
Keep at the bottom of this agenda:
- Experiment: [change to try] Owner: [name]
- What we will observe: [measure or evidence] Review date: [date]
- Previous experiment: [keep/change/stop, with reason]
6. Board or leadership meeting agenda — 90 minutes
Purpose: Review performance, make the listed decisions and record unresolved risks and follow-ups.
Prepare: Circulate the relevant reports and decision papers. For a formal board, have the secretary or responsible adviser adapt the agenda to the organisation’s governing requirements.
Organisation: [name] Date: [date] Start/time zone: [time, zone]
Chair: [name] Record keeper: [name] Participants: [names]
| Elapsed time | Minutes | Topic | Lead | Output |
|---|---|---|---|---|
| 00–05 | 5 | Review previous minutes and actions | Chair | Corrections and outstanding actions |
| 05–25 | 20 | Strategy and performance | Executive lead | Progress and decisions needed |
| 25–40 | 15 | Financial review | Finance lead | Questions and agreed follow-ups |
| 40–70 | 30 | Decision papers | Named decision owners | Each decision recorded separately |
| 70–80 | 10 | Risks and oversight | Risk owners | Escalations and unresolved issues |
| 80–85 | 5 | Other agreed business | Chair | New items acknowledged |
| 85–90 | 5 | Actions and next meeting | Chair + record keeper | Owners, dates and next meeting |
This is a discussion template, not a complete formal board procedure. Add required opening matters, declarations, approvals or voting steps where applicable, and extend or rebalance the timings explicitly.
Keep at the bottom of this agenda:
- Decision: [exact wording] Result/approval: [record as required]
- Action: [task] Owner: [name] Due: [date]
- Next meeting: [date/time]
Worked example: turn a topic into a decision
The following example is fictional. Cedar Studio is preparing a customer-onboarding pilot. Its first draft says only “Onboarding update — 20 minutes.” That does not tell attendees what to prepare or whether they can decide anything.
A more usable agenda item is:
| Field | Filled example |
|---|---|
| Decision needed | Choose email or an in-app checklist for the first pilot |
| Preparation | Read the two sample flows and the support team's three recurring questions |
| Lead | Priya, product lead |
| Decision owner | Morgan, pilot sponsor |
| Time | 20 minutes: 5 for evidence, 10 for discussion, 5 for the decision |
| Output | Chosen pilot format, any conditions and the first assigned action |
After the meeting, the notes might say: “Use the email flow for the pilot. Priya will send the draft to Morgan by 20 October. Whether to add the in-app checklist later remains open.” Those are the outcomes of this fictional discussion. They should not be written into the agenda beforehand as though they were already agreed.
Use the agenda during the meeting, then make a separate record
Keep the agenda visible. At the end of an item, say whether the group made a decision, needs more information or deferred it. If a discussion overruns, ask which remaining item to shorten or reschedule. At the close, read back each agreed action with its owner and date; leave the date unassigned if nobody agreed one.
An agenda describes the intended meeting. Meeting notes or minutes describe what happened. You can keep the agenda headings as a scaffold, but label topics that were skipped and decisions that were not reached. For formal minutes, follow your organisation's required review and approval process.
Meetings Brief live transcription can capture the conversation and create an AI brief from the transcript text. Review names, decisions and commitments before using it. The brief does not automatically follow your agenda headings, and the agenda alone cannot establish what was decided. If you already have written notes, the meeting summary generator is a separate starting point.
For the next step, see how to share meeting notes with your team, including audience selection, access settings and corrections.
FAQ
How far ahead should I send an agenda?
Send it early enough for the preparation you request. A short check-in may need only a shared list of topics; a financial review may need several days for reading and questions. State when the pre-read is ready and when participants should add agenda items. There is no single lead time that suits every meeting.
Should a one-on-one use the same agenda every week?
A recurring structure can help, but review unfinished commitments and let both people change the topics. Do not copy old sensitive notes into every new meeting record. Agree where the running record lives and who has access.
What if we run out of time?
Record which item was deferred, whether a decision is still needed and who will arrange the next discussion if that was agreed. Do not record a proposal as approved simply because the meeting ended. Update the agenda for the follow-up rather than restarting the entire conversation.
Can I edit or reuse these templates?
Yes. Copy a section from this page or use the free Word pack and text pack. Replace the bracketed fields, recalculate the schedule when you change durations and remove prompts that do not apply. These templates are practical starting points, not a substitute for an organisation's formal meeting requirements.