BlogTemplates
Weekly team meeting agenda template
A weekly team meeting agenda template plans a discussion to review last week's commitments, coordinate work that depends on another team and request help with issues the team cannot resolve. Carry each commitment forward with its original owner and due date. Use it when open work needs discussion, then record agreed decisions in the minutes.
Short answer
- Use this agenda when open work needs a team discussion; put routine updates in the preparation notes.
- Carry an open commitment forward with the original owner and due date; show proposed changes separately.
- For a dependency, name the providing team, receiving team, needed input and date.
- A response can decline an escalation. Record what was said before treating any requested work as agreed.
How do I run a weekly team meeting that follows up last week's commitments?
- For
- A team lead running a recurring weekly team meeting
- What it does
- Plans a review of last week's commitments, cross-team dependencies and escalation requests, each with an owner.
- Works in
- Plain Markdown; paste into any notes or docs app
Disclosure. Candor is an app that will compete with some products named here. We describe every product, including Candor, from its own documentation, and we'll test them all with the same published method.
You can join the Candor waitlist at candor.inc. This is a website template, not demonstrated Candor app output. [2]
Use the Copy button on the blank block, or select it and copy. For plain text, keep the labels and replace each table row with one labelled line per column. There are no downloadable files.
If you have a Word file, Google's web instructions say to double-click it in Drive, then choose “Open with Google Docs.” [1] That documents the opening steps; it does not verify this template's layout.
Template
Weekly team meeting agenda
Fill this before the meeting. Write "unknown" for unchecked facts and "none reported" only when that is what the source says. Keep proposed changes separate from agreed commitments. Refresh the status before sharing.
## Meeting details
- Team:
- Meeting date and time (include time zone for remote meetings):
- Meeting link or location:
- Facilitator:
- Note-taker (optional):
- Prepared by and preparation date:
- Attendees expected:
- Apologies or unavailable people:
## Purpose and desired outcome
- What should be clearer or decided by the end:
- Preparation people should bring:
- Time available:
## Carry forward last-week commitments
Repeat a row for each commitment still needing attention, including older open work. Keep the original owner and due date. In the last column, distinguish a proposed change from an agreed revision and cite the agreement. Include completed work only when its closure needs confirmation.
| Commitment from | Commitment and source reference | Original owner | Original due date | Current status and evidence | Change or help requested |
|---|---|---|---|---|---|
| | | | | | |
## Cross-team dependencies
Repeat a row for each piece of work this team needs from, or must provide to, another team. A needed-by date is a request; record any agreed delivery date and its source in the status column.
| Workstream or deliverable | Providing team | Receiving team | What is needed and source reference | Needed by | Current status or open question | Effect if delayed |
|---|---|---|---|---|---|---|
| | | | | | | |
## Escalation requested
Repeat for each issue needing help beyond the team's scope. State who can respond. Record a response only when received; a reply does not necessarily accept the request.
- Issue and evidence or source reference:
- Decision, resource or intervention requested:
- Person or group asked to respond:
- Response needed by:
- Effect of waiting:
- Status (request to raise / raised / response received / still open):
- Response and source, if received:
- Next check, owner and date, if agreed:
## Topics for this meeting
Repeat a row per topic. Put the intended output in the last column; discussion alone is not a decision.
| Order | Topic and preparation reference | Person bringing it | Timebox | Intended output (update / question / decision request) |
|---|---|---|---|---|
| | | | | |
## Close
- Items that need a separate follow-up:
- Proposed owner and due date (confirm in the meeting):
- Topic to carry into next week's agenda:
- Link or location for the later meeting record:
Filled example
Fictional example: all people and work records below are invented, including the test result. This agenda is prepared on 25 October for a meeting on 26 October 2026. It records no outcome from that future meeting.
Weekly team meeting agenda
## Meeting details
- Team: Harborline release team
- Meeting date and time (include time zone for remote meetings): 26 October 2026, 10:00–10:40 India Standard Time (UTC+05:30)
- Meeting link or location: Harborline project room
- Facilitator: Isha Menon
- Note-taker (optional): Omar Das
- Prepared by and preparation date: Isha Menon, 25 October 2026
- Attendees expected: Isha Menon (release), Omar Das (support), Rhea Bose (design), Kabir Shah (data)
- Apologies or unavailable people: None reported
## Purpose and desired outcome
- What should be clearer or decided by the end: Decide how to handle the overdue guide review and confirm the request for an export-test reviewer before the planned 30 October release.
- Preparation people should bring: Guide v0.8 and export test record HL-EX-42; release checklist v3, including its 28 October export-check target.
- Time available: 40 minutes
## Carry forward last-week commitments
| Commitment from | Commitment and source reference | Original owner | Original due date | Current status and evidence | Change or help requested |
|---|---|---|---|---|---|
| 19 October 2026 | Finish the setup guide review; 19 October minutes, item 2 | Omar Das | 23 October 2026 | Overdue as of 25 October; guide v0.8 still has two old screenshots | Proposed: ask design for replacements by 28 October; no revised deadline agreed |
## Cross-team dependencies
| Workstream or deliverable | Providing team | Receiving team | What is needed and source reference | Needed by | Current status or open question | Effect if delayed |
|---|---|---|---|---|---|---|
| Export test result | Data Platform | Harborline release team | Confirm whether retry keeps the selected date range; test HL-EX-42 and checklist v3 | 28 October 2026, requested | First export passed in the fictional record; retry result unknown; delivery date not agreed | Export check stays open, putting the planned 30 October release at risk |
## Escalation requested
- Issue and evidence or source reference: Export retry result remains unconfirmed in test HL-EX-42.
- Decision, resource or intervention requested: Ask the platform lead to assign a reviewer for one retry test.
- Person or group asked to respond: Data Platform lead
- Response needed by: 27 October 2026, requested
- Effect of waiting: The release team cannot close the export check on the evidence it has.
- Status (request to raise / raised / response received / still open): Request to raise; no response or decision recorded yet.
- Response and source, if received: None received as of the 25 October preparation note.
- Next check, owner and date, if agreed: Not agreed; ask Kabir at the meeting whether he can check on 27 October.
## Topics for this meeting
| Order | Topic and preparation reference | Person bringing it | Timebox | Intended output (update / question / decision request) |
|---|---|---|---|---|
| 1 | Last week's open commitments, 19 October minutes | Isha Menon | 5 minutes | Question: which commitments still need attention? |
| 2 | Export retry gap, HL-EX-42 | Kabir Shah | 12 minutes | Decision request: who should raise the reviewer request? |
| 3 | Setup guide screenshots, guide v0.8 | Rhea Bose | 8 minutes | Question: can design accept the proposed 28 October target? |
| 4 | Release checklist v3 | Isha Menon | 10 minutes | Question: what remains before the planned 30 October release? |
| 5 | Close and follow-up checks, open items above | Isha Menon | 5 minutes | Decision request: confirm follow-up owners and dates |
## Close
- Items that need a separate follow-up: Export retry test, if Data Platform has not responded.
- Proposed owner and due date (confirm in the meeting): Kabir Shah to check for a response on 27 October 2026; proposed, not agreed.
- Topic to carry into next week's agenda: Whether the export check is closed.
- Link or location for the later meeting record: Harborline / Release / Weekly check-ins / 26 October 2026
The timeboxes total 40 minutes, including the close. The dependency names the missing result; the escalation asks for someone who can help get it. Neither request is accepted yet.
When to use this
Use this when open commitments need discussion across a team. For quick individual updates, a list may take less preparation. For a project review centred on milestone forecasts, use a project status agenda instead.
The layout is optional. An agenda is like a parcel label: it says what is going where but does not prove delivery. Keep the delivery evidence in the later record. (Writing someone into the agenda does not mean they accepted the work.)
What to customise
- Ask owners to update open commitments against the previous minutes or tracker. Keep the original due date and cite any agreed revision beside it.
- Check each dependency with both teams. Separate the date your team needs an input from a delivery date the other team accepted.
- Raise an urgent request before the meeting if its response is needed sooner. Add the request's current status to the agenda.
- Share the preparation references, then choose timeboxes that fit the whole meeting, including the close. Keep routine updates in the pre-read unless they change the plan.
Remove note-taker or apologies fields if they do not help. Drop escalation when the team can resolve its own issues. Choose your team's date format and status labels; changing labels does not change its rules.
Field-by-field guidance
| Field | What to enter | Where to get it | Common mistake |
|---|---|---|---|
| Team, date and time, location or link | Group, scheduled time, place and time zone | Calendar invitation | Leaving off the time zone for a remote meeting |
| Facilitator, optional note-taker, preparer and date | Meeting lead, optional recorder of notes, and agenda author/date | Team agreement or calendar | Treating the note-taker as owner of every follow-up |
| Expected attendees and apologies | Expected people and known conflicts | Invitation and replies | Guessing why someone is unavailable |
| Desired outcome, preparation and time available | Needed result, what to bring and meeting window | Work plan and invitation | Listing topics without saying what each should produce |
| Commitment and source | Prior agreement and its record reference | Prior minutes or tracker | Treating a proposed agenda item as an agreement |
| Commitment from | Date or meeting where the commitment was agreed | Prior minutes or tracker history | Treating a proposed agenda item as proof of agreement |
| Original owner and due date | Person and deadline recorded when the commitment was first agreed; cite later agreements separately | Prior minutes or tracker history | Replacing the original deadline with a requested revision |
| Current status, evidence and change or help requested | What has happened, its supporting record, and a specific ask | Work record and owner | Calling a forecast complete or treating a request as accepted |
| Workstream, providing team and receiving team | Deliverable and both teams' roles | Project plan or issue | Naming only one side of the dependency |
| Needed input, source and needed-by date | The input or decision, its reference and required date | Project plan and work item | Giving a date without saying where it came from |
| Dependency status, open question and effect of delay | What is known and what work waits | Updates from both teams | Presenting a guess as a confirmed status |
| Escalation issue, evidence and requested intervention | Specific issue, proof and help sought | Open issue or decision log | Writing “escalate this” without a clear ask |
| Person asked, response date and effect of waiting | Role that can respond, requested date and consequence of waiting | Ownership map and delivery plan | Treating the requested response date as an accepted deadline |
| Escalation status | Request to raise, raised, response received or still open | Person who raised the request | Recording an answer that has not arrived |
| Response and next check | What the recipient actually said, with its source; next checker and date only if agreed | Reply and follow-up agreement | Treating a reply as acceptance, or assigning a check without agreement |
| Topic, preparation reference, presenter, timebox and intended output | Subject, source, speaker, time and whether the topic needs an update, answer or decision | Proposed agenda and linked material | Giving every topic the same time by default |
| Follow-up, proposed owner and due date | Work to propose for agreement at the meeting | Preparation notes and open issues | Treating a proposal as an accepted action |
| Next week's topic and later record location | Carry-forward subject and where the record will live | Open items and filing convention | Treating the agenda as the final meeting record |
Voice and AI workflow
Before the meeting, dictate or write preparation notes against the blank fields, with a source reference for each fact. Afterward, confirm new commitments with the people involved before recording them as agreed.
Use only notes you are authorised to share. Remove confidential or identifying details before using an AI tool (removing names alone does not make the remaining notes safe to share). Keep unchecked facts marked “unknown”.
Copy this prompt with the blank agenda and approved, de-identified preparation notes:
Fill the supplied Weekly team meeting agenda template from the preparation notes below. Return an agenda using the same headings and field names.
Carry forward each open commitment with its source reference, agreement date, original owner, original due date, current status and evidence, and any requested change or help. Cite an agreed revision separately; do not overwrite the original commitment. For each cross-team dependency, name the workstream, providing team, receiving team, needed input or decision, source, needed-by date, current status or open question, and effect of delay. Separate requested dates from agreed delivery dates. For each escalation, state the issue and evidence, requested intervention, person or group asked, requested response date, effect of waiting, request status, any actual response and its source, and next checker/date only if agreed. A reply may decline the request; do not treat it as acceptance.
Include the meeting details, purpose, preparation and time available. List topics with their preparation references, presenters, timeboxes and intended outputs. Flag timeboxes that exceed the meeting window; do not invent allocations. End with proposed follow-ups and the later record location, leaving unagreed owners and dates unresolved.
Write “unknown” when the notes do not answer a field. Keep source references beside the facts they support. Do not infer a name, status, agreement, decision, owner or due date. Flag conflicting notes for a person to resolve. Do not turn a preparation note into a record of what the meeting decided.
Before using this tool, remove confidential or identifying data and check permission to share the remaining notes. Afterward, a person must confirm every name, source reference, status, escalation, decision and due date with the relevant people and records. This prompt has not been tested.
Blank template and approved preparation notes follow:
What this page can't tell you
This optional layout cannot establish which commitments your team accepted, whether another team agreed to provide something, or who can resolve an escalation. Check project records and organisational rules before treating it as official.
Questions
How can I make the most of a weekly team meeting?
Use the agenda for open commitments, cross-team dependencies and issues that need escalation. Put routine updates in preparation notes and reserve meeting time for discussion.
What makes a good team meeting?
Give each topic an intended output, such as an update, question or decision request. Carry open work forward with its original owner and due date.
How do you prioritize and follow up on action items from meetings?
Carry open commitments into the next agenda with their original owner and due date. Record a changed owner or deadline separately as proposed until the team agrees to it.
About this page
Candor is being built as personal voice intelligence for everyone. You can join the Candor waitlist at candor.inc. Candor's own documentation is at candor.inc/docs.
Candor's docs on this page's topic: What the summary includes.
Last checked: 4 November 2026. Candor details come from Candor's documentation and homepage. [2] To report an error, write to support@candor.inc. [3]
Sources
- Switch from Microsoft Word to Google Docs, Google Docs Editors Help — https://support.google.com/docs/answer/9310150?hl=en — checked 2026-11-04
- Candor homepage — https://candor.inc/ — checked 2026-11-04
- Candor privacy policy (last updated October 30, 2026) — https://candor.inc/privacy — checked 2026-10-31