The weekly meeting in most service businesses is an hour of people remembering out loud. Who quoted what, which jobs are waiting on parts, who owes us money. The information exists; it is just in three tools and five heads, so the meeting becomes the place it gets reassembled, badly, every Monday.
The version below takes fifteen minutes because it does not reconstruct anything. It reads five numbers off one screen, asks four questions, and assigns whatever falls out. It assumes a single pipeline where every customer sits at one stage; if you do not have that yet, that is the first action item.
Minute 0–5: five numbers, read, not discussed
| Number | Where it comes from | What a bad number means |
|---|---|---|
| Open quotes over 7 days old | Pipeline, quoted column, sorted by age | Follow-up has stopped; the sequence is off or nobody is working the list |
| Completed, not invoiced | Pipeline, completed column | Cash is sitting in finished work; invoice at close is not happening |
| Unpaid over 14 days | Invoices, overdue | Reminders are not running or a customer needs a call |
| Median first response, last 7 days | Lead queue | A channel has lost its owner; find which one |
| Bookings next 2 weeks vs capacity | Schedule | Either a gap to fill or a crunch to plan for |
Read them aloud, in that order, with last week's beside them. No discussion yet. The discipline of reading before talking is what keeps the meeting short, because most of the talking people want to do is explaining a number nobody has seen yet.
Minute 5–12: four questions
- 01Which quotes are we going to lose this week, and who is calling them?
Go down the aging quotes list. For each over seven days: is the sequence still running, has the customer replied, is this worth a call? Assign the calls. Close the ones that are genuinely dead so the number is honest next week.
- 02What is blocked, and on whom?
Jobs waiting on parts, approvals, access, or a decision. Each one gets a name and a date. A blocked job with no owner is a job that will be discovered on the morning it was supposed to start.
- 03Where did last week's leads come from, and which channel was slow?
Count by source, and look at response time by channel. One channel is almost always worse than the rest, and it is usually the newest one. Give it an owner.
- 04Who is due to hear from us?
Renewals, rebook reminders, promised callbacks, win-backs. Most of these should be sending automatically; the question is which ones need a person, and who.
Minute 12–15: assign and stop
Every action from the four questions becomes a task on the relevant customer record with a name and a date, created during the meeting, not after. Then stop. A meeting that ends early builds the habit of attending; one that runs over teaches everyone to dread Mondays.
What changes after six weeks
- The numbers stop being surprises. Once everyone knows the five will be read aloud, the aging quotes get worked on Thursday, not confessed on Monday.
- The meeting gets shorter. As the automatic follow-up, reminders, and invoicing take over, question four mostly answers itself and question one shrinks.
- The owner stops being the database. When the pipeline is the source of truth, "ask Dan" becomes "look at the board," and Dan can miss a Monday.
If the meeting needs anyone to remember anything, the system is missing something. Fix the system, not the meeting.
Common questions
What should a weekly meeting for a service business cover?
Five numbers read from one screen (aging quotes, completed-not-invoiced, unpaid over 14 days, median first response, bookings versus capacity), then four questions: which quotes are at risk, what is blocked and on whom, which lead channel was slow, and who is due to hear from us. Assign tasks on the records and stop at fifteen minutes.
How long should a weekly ops meeting be?
Fifteen minutes, if it runs from a pipeline rather than from memory. Meetings run long when they are reconstructing last week from three tools and five people; they run short when the numbers are already on a screen and the only work is deciding who does what.
Who should attend?
Whoever quotes, whoever schedules, whoever invoices, and the owner. In a 3–20 person business that is usually three to five people. Technicians who do not quote or schedule do not need to be there; their items reach them as tasks.
What if we do not have a pipeline to run it from?
Then the first meeting has one action item: get every open quote, scheduled job, completed job, and unpaid invoice onto one board, each at one stage. Until that exists, the meeting will be a reconstruction every week, and it will take an hour.