Weekly Team Meeting Agenda: One Hour That Fixes Something Every Week

A weekly team meeting agenda that works fits in one hour and gives the first half of it to your biggest problem. Hold it on a quiet midweek afternoon rather than Monday morning, when your phone rings most, and end it by reading back every promise with an owner and a date.

Why the time slot matters

A meeting takes your whole team away from the phone at the same moment. Monday drew 28% of the calls in our data, and Monday morning alone drew 15%, so a 9 o'clock Monday meeting puts everyone in a room just as the calls pile up.

Tuesday to Thursday from 2 to 5 drew just 10% of the calls, spread over nine hours, which makes it the quiet time to sit down together. Your own pattern may differ, so pull a month of your calls by day and hour before you pick a slot. Then have someone outside the room cover the phone, even in the slow hours.

A caller who reaches voicemail can just as easily call the next business on the list. Our speed to lead guide shows why that first callback matters so much, and it lays out a routine for the calls you do miss.

Copy this weekly team meeting agenda

Paste this into your notes, and fill in the problem and the numbers the day before. The times assume a one-hour meeting that starts on the hour.

Keep two running lists in the same document as the agenda: the problem list and the promise list. Those two lists tie each week's meeting to the one before it, so nothing gets solved twice or dropped.

Time	Part	What happens	Who leads
0:00 to 0:02	Opening prompt	One question, a thank-you or a prayer	The meeting runner
0:02 to 0:32	Top problem	Name what's wrong, pick one fix, set an owner and a date	The meeting runner
0:32 to 0:47	Calls and numbers	Last week's calls by day and hour, then each person's numbers	Each number's owner
0:47 to 0:52	Last week's promises	Done, or a new date	Each promise's owner
0:52 to 0:57	Anything else	News, and who's out next week	Anyone
0:57 to 1:00	Read back	Each new promise with its owner and date	The note taker

Set it up before the first meeting

Three habits make the hour work, and each one takes a few minutes a week.

• Pick a quiet slot and keep it. Book the slow afternoon your calls point to as a repeating hour, so the meeting doesn't slide back to Monday morning when the week gets busy.
• Keep one running list of problems. Anyone can add to it during the week, and the day before the meeting, the person who runs it moves the biggest problem to the top, so the hour starts on the right one.
• Pick one person to run it. That person watches the clock and keeps the conversation on track, and it doesn't have to be the boss, as long as the team lets them cut a tangent short.

What numbers each person should bring

Each person brings three or four numbers they control, written next to last week's figures, so the team sees a trend instead of a single week.

Choose numbers a person can move with their own work, because a number nobody controls only starts arguments. When a figure slips three weeks running, it moves to the problem list, where it gets the half hour it deserves rather than a rushed debate in the middle of the meeting.

• Whoever answers the phone brings calls answered, calls missed and how many missed callers got a callback the same day.
• Whoever sells or quotes brings estimates sent, estimates booked and the oldest estimate still waiting on an answer.
• Whoever runs the jobs brings jobs finished, jobs that needed a return trip and anything that ran past its scheduled day.
• Whoever keeps the books brings money collected, invoices past due and any bill that changed more than anyone expected.
• A church or nonprofit team can swap in the numbers it already tracks, such as first-time guests, volunteer shifts filled or gifts received.

Keep it to one hour

Meetings have grown over the years. A 2017 article in Harvard Business Review reported that executives spend nearly 23 hours a week in meetings on average, up from less than 10 hours in the 1960s. A weekly team meeting shouldn't add to that pile, so keep yours to one well-run hour.

If an hour isn't enough, fix how you use it rather than making it longer. Ask people to post routine updates in a shared note before the meeting, push long debates onto the problem list, and protect the top problem's half hour.

Mistakes that sink a weekly meeting

Watch for these three, because each one undoes a part of the agenda.

• Saving the big problem for the end, where it gets five minutes and comes back next week.
• Letting the numbers turn into a debate, when the why belongs on the problem list for its own half hour.
• Adding time when the hour runs over, which gives every debate more room to drift.

How we help you see your calls

The calls part of this meeting is easier when you can see every call your ads bring in. We track each call and form, and your portal lists every one with the time it came in and what it cost, so your own busy and quiet hours are easy to spot.

Our home services page shows how we run Google Ads for local businesses. If you'd like to talk through how calls reach your team today, book a call with Miguel. He'll ask how your phones are covered during the week, and he'll show you what call tracking would add.

Questions people ask

What should be on a weekly team meeting agenda?

Fit six parts into one hour: a two-minute opening prompt, half an hour on your top problem, fifteen minutes on calls and numbers, five on last week's promises, five on anything else and three to read back new promises. The top problem goes near the start, while heads are fresh.

How long should a weekly team meeting be?

Keep it to one hour, with half of it on one problem. If an hour isn't enough, change how you use it instead of making the meeting longer, because a longer meeting leaves more room to drift.

What is the best day for a weekly team meeting?

Pick the quietest slot in your own call history. Monday drew 28% of the Google Ads calls to 29 of our client accounts, while Tuesday to Thursday from 2 to 5 drew 10% spread over nine hours, so a midweek afternoon makes a good starting point.

Who should run the weekly team meeting?

One person runs it, watches the clock and keeps the talk on track. It doesn't have to be the boss, as long as the team lets that person move a long debate to the problem list.

What numbers should a team review each week?

Each person brings three or four numbers they control, such as calls missed, estimates booked or invoices past due, next to last week's figures. A number that slips three weeks in a row goes on the problem list for its own half hour.

See how we track every call our ads bring in

Read next

• Call Log Template: What to Write Down From Every CallA ready-to-copy call log, the one question to ask every caller, and how to sort wrong numbers.
• ChatGPT Custom Instructions Examples: Make Each Fix Only OnceEight custom instructions examples to copy, and a four-line card that carries your fixes into every chat.
• ChatGPT Prompt Templates: Write the Weekly Ask Once and Save ItCopy-ready ChatGPT prompt templates for the jobs you run every week, and how to save each one.