reph

Templates · Operations & projects

Weekly team meeting template

Running agenda for the weekly team meeting: wins, metrics, priorities, blockers, decisions and action items with owners

Start with this template →Sign in

Opens on reph with the template ready to start. No account needed; sign in to keep your document.

Use it when

Your team meets every week and wants one running agenda where wins, numbers, blockers, decisions and actions live in the same place

Who it's for

ManagerEngineering managerTech leadProduct managerOperations

Part of a kit

Team rituals, step 1 of 5. The recurring meetings a team runs on: weekly team meeting, 1:1s, retros, all-hands and offsites.

Filled example

The template filled in for a made-up company, so you can see what good looks like.

Platform team weekly

Facilitator: Priya Raman · Date: 2026-09-28 · Note taker: Tomas Vidal

Last week's action items

Wins

  • Northwind's SSO migration went live with zero support tickets (Jun and Amara)
  • Build times dropped from 14 to 9 minutes after the cache change (Tomas)
  • Lena from Support thanked the team for the faster incident status page updates

Metrics

Deploys per week
31
▲ +11%
Change failure rate
3.2%
▼ -1.1%
P1 incidents
0

Deploys rose because the faster build makes smaller changes cheap; failure rate fell with them, which is the pattern we want.

Priorities this week

  1. Finish the Postgres 16 upgrade on the two remaining replicas
  2. Close the Fernhill audit findings before their Oct 6 review
  3. Draft the Q4 reliability goals for Thursday's planning

Blockers

Blocker Impact Needs Owner
No vault admin access for credential rotation Rotation slips, audit finding stays open Security to grant temporary role Jun
Replica upgrade window conflicts with a sales demo Upgrade delayed a week Move the demo or the window Priya

Discussion

  • Pager load on weekends (10 min, raised by Amara): four weekend pages in September, three from the same flaky disk alert. Proposal: raise the threshold and add a runbook link.
  • Hiring loop (5 min, raised by Priya): two onsite slots needed next week.

Decisions log

Decision Why Decided by Date
Raise the disk alert threshold to 90% for 30 minutes Three false pages in a month, no real incident behind them Team, Priya to confirm 2026-09-28
Move the replica upgrade to Wednesday night Keeps the Lumen Labs demo stable on Tuesday Priya 2026-09-28

Action items

The template

Show the blank template

Weekly team meeting

Facilitator: [your name] · Date: [date] · Note taker: [name]

Add items before the meeting. The facilitator orders them by what needs the whole team in the room.

Last week's action items

Carry forward anything still open. Close or re-date it, never silently drop it.

Wins

Shipped work, customer moments, help someone gave. One line each, with who.

Metrics

The same few numbers every week, so the trend is the conversation.

[Primary metric]
0
▲ +0%
[Quality metric]
0
▲ 0%
[Delivery metric]
0

One sentence on what moved and why.

Priorities this week

Top three for the team, in order. If everything is a priority, nothing is.

Blockers

What is stuck, what would unstick it, and who can help.

Blocker Impact Needs Owner

Discussion

Topics that need the group. Timebox each one.

  • [Topic] (5 min, raised by [name]):

Decisions log

Record each decision so absentees do not reopen it.

Decision Why Decided by Date

Action items

Questions

How long should the meeting run?
Thirty to forty five minutes; anything needing longer gets its own follow-up
Who fills in the agenda?
Everyone adds items before the meeting; the facilitator trims and orders them
What if there are no decisions this week?
Leave the log row empty; a week of updates only is a sign the meeting could be async

Fill it with your agent

Connect Claude to reph over MCP, then paste this. The draft arrives as suggestions you accept or reject section by section. How to connect Claude.

Find my reph doc "Weekly team meeting" with search_docs, then read it with read_doc. Carry forward last week's open action items with status, take metrics from the dashboard numbers I paste, and wins and blockers from the team channel and sprint board. Leave Decisions empty for the meeting. File it with suggest_edit, one replace_section op per section (heading line kept) so each can be accepted alone. Ask each open question (blockers with no owner, unconfirmed metrics) with add_comment quoting that section's heading line, then call request_review with a one-line summary.

Related templates

1:1 notes

Recurring 1:1 agenda: wins, blockers, growth, action items

ManagerEngineering managerTech lead

Retrospective

What went well, what didn't, and what we'll change

ManagerOperationsEngineerProduct manager

All-hands agenda

Run of show for a company all-hands: timed segments with presenters, Q&A collection, and follow-ups owed afterwards

ExecutiveFounderOperationsCommunicationsManager

Offsite agenda

Team or leadership offsite plan: goals, pre-reads, day-by-day schedule, sessions with owners, decisions to make, logistics and outcomes

ExecutiveFounderManagerEngineering managerOperations

Project kickoff

Align a new project on goals, scope, roles and cadence

ManagerProduct managerOperations

RACI matrix

Who is Responsible, Accountable, Consulted and Informed

ManagerOperationsProduct manager

Start with this template →Sign in