Team Meeting Agenda: A Template for Weekly Meetings

A good weekly team meeting agenda has five parts in a fixed order: a quick check-in, a review of last week’s action items, the one or two numbers the team watches, the discussion topics people submitted in advance, and a read-back of decisions and new tasks. For a team of up to about eight people that fits in 45 minutes. The order matters more than the timings: commitments are checked before anything new is discussed, and the meeting cannot end until every new task has one owner. The template is below, then a filled example, how to run it, and how the notes become tasks.

This page is about the recurring weekly meeting. The daily version is covered in standup meeting questions, the first meeting of a project in the project kickoff meeting agenda, and a manager’s private meeting with one person in the one-on-one meeting template.

The weekly team meeting agenda template

Weekly team meeting: [Team name]
[Day, Month day, year], [time], [room or link]
Facilitator: [name]   Notes: [name]   Timekeeper: [name]
Topics due by: [day before, noon]

 0:00   5 min  Check-in: one sentence each, no status updates
 0:05  10 min  Last week's action items: done, in progress, or blocked
 0:15   5 min  Numbers we watch: [metric 1], [metric 2]
 0:20  20 min  Discussion topics, in ranked order
               1. [Topic], raised by [name]. Needs: decide / input / inform
               2. [Topic], raised by [name]. Needs: ...
               3. [Topic], raised by [name]. Needs: ...
 0:40   5 min  Read-back: decisions made, new action items and owners
 0:45          End. Anything not reached moves to next week or to chat.

Three roles keep it honest. The facilitator moves the agenda and stops side conversations. The note-taker writes down decisions and action items, not a transcript. The timekeeper calls time on each block. On a small team one person can be both facilitator and timekeeper, but the note-taker should be someone else, because you cannot steer a discussion and record it well at once. Rotate the roles each week.

A filled example

Weekly team meeting: Customer support
Monday, October 6, 2026, 10:00 AM, Room 3B and video link
Facilitator: Priya   Notes: Luis   Timekeeper: Priya

 0:00   5 min  Check-in
 0:05  10 min  Last week's action items
               - Update the refund macro for the new policy (Sam): done
               - Draft holiday coverage schedule (Maria): in progress
               - Get Spanish-language queue numbers (Luis): blocked,
                 waiting on the phone vendor's export
 0:15   5 min  First-response time, open tickets over 3 days old
 0:20  20 min  Topics
               1. Weekend coverage in November. Raised by Maria.
                  Needs: decide
               2. Moving FAQ answers into the help center. Raised by Sam.
                  Needs: input
 0:40   5 min  Read-back
 0:45          End

Note what is missing: nobody reads out what they did all week. Status that the group does not need to discuss belongs in a written update before the meeting, and the agenda only lists topics that need the people in the room.

Before the meeting

1. Collect topics by a set time, such as noon the day before. Each topic names who raised it and what it needs: a decision, input, or only to inform.
2. Rank them. Decisions first, then input. Pure information goes in the written update instead, unless it changes someone’s work this week.
3. Send the agenda and any material before the meeting. The Section 508 guidance on accessible meetings↗ (opens in a new tab) advises giving attendees presentations, handouts and other materials in advance in an accessible format, which also helps anyone who reads faster than they listen.
4. Pull last week’s action items into the agenda, so the review starts from a list rather than from memory.

How to run it so it ends on time

• Start on time, even if someone is late. Waiting teaches everyone that the start time is a suggestion.
• In the action-item review, each owner gets one line: done, in progress, or blocked and why. A blocked item gets a new action to unblock it, with its own owner.
• Give each topic a time limit when you set the order, and when it runs out, the facilitator asks: decide now, give someone the action to bring a proposal, or take it offline.
• When a topic needs a decision, name who decides before the discussion starts. The federal government’s Digital Services Playbook↗ (opens in a new tab) puts it as a play, “Assign one leader and hold that person accountable,” and a weekly meeting works the same way on a smaller scale.
• On a hybrid call, read chat questions out loud and describe anything shared on screen, so people joining by audio are not left out.
• Never skip the read-back. Five minutes in which the note-taker reads every decision and every new action item with its owner turns a conversation into an agreement.

Team meeting ideas to keep it from going stale

A weekly meeting with the same shape every week is a feature, but the discussion block can still vary. Some ideas that work in the 20-minute slot:

• Lean coffee once a month. Digital.gov’s guide to team engagement methods↗ (opens in a new tab) describes it: attendees spend two minutes writing topics on sticky notes, one idea per note, dot-vote, set a time for each, and start with the most votes. It hands the agenda to the team.
• A five-minute demo. One person shows something finished that week, live, not on slides.
• One customer story. Someone brings a support ticket, a call or a piece of feedback, and the team asks what it would change.
• A backlog check. Look at the top of the team’s list and ask whether the order still makes sense.
• A short retro every fourth week: what to keep, what to change, one thing to try. Each change becomes an action item with an owner.
• A cancel test. If the agenda has no decide or input topics by the deadline, cancel the meeting and send the written update instead.

Turning the notes into tasks

The meeting is only as good as what happens after it. File every action item as a task on the board the team works from, the same day, and make the note-taker responsible for filing rather than each owner. Write each one verb first, with one owner and a done-when line. The full method, with a template and how to follow up, is in the meeting action items template; how to record decisions alongside them is in the meeting minutes template.

On a fenbs board, Add many turns the read-back into tasks in one paste: each line becomes a task, an indented line becomes its note, and a line starting with bug:, feature: or enhancement: sets its kind. Everything is previewed before anything is created. fenbs has no assignee field and no due dates, so the owner and check-in go on the first line of the note. Put the meeting name in the category, such as “Support weekly”, and next week’s review starts by filtering the board to it. Decisions the meeting made go on the Decisions and rules page, so nobody has to dig through notes to find them.

- Decide November weekend coverage and post the schedule
    Owner: Maria. Check-in: October 13 meeting.
- Draft three FAQ answers for the help center as a pilot
    Owner: Sam. Done when: drafts shared in the team channel.
- bug: Refund macro still links the old policy page
    Owner: Luis. Check-in: October 8.

If an AI assistant such as Claude or ChatGPT is connected to the board over MCP, it can draft the list from your notes. Ask it to show you the items before it files anything, and to leave any item without an owner as a question for you.