What should a weekly operations meeting agenda look like?
Five blocks in one hour: numbers (5 minutes), exceptions (20), decisions waiting on the owner (15), one thing to fix (15), owners and dates (5). Send the numbers the day before, so nobody reads them out in the room. Spend the hour on exceptions. End with every action on one named owner and a date.
Last updated:
The five-part agenda
| Block | Minutes | Who | Output |
|---|---|---|---|
| 1. Numbers | 5 | Ops lead | Questions on anything that moved. The numbers went out the day before. |
| 2. Exceptions | 20 | The owner of each number | What went over a limit or off track, and why |
| 3. Decisions waiting on the owner | 15 | Business owner | Each one decided, or handed off with a limit |
| 4. One thing to fix | 15 | Everyone in the room | One process change, with an owner |
| 5. Owners and dates | 5 | Ops lead | Every action with one name and one date |
The ops lead runs the meeting. The business owner speaks last.
What to put in the numbers
Pick five to seven numbers and keep them the same every week. Each one has one owner, and that person explains it when it moves. For example: cash on hand, overdue receivables, booked work, jobs finished on time, customer complaints, and the owner's own hours spent on approvals.
Your numbers will be different. Which ones to pick: weekly KPIs for an owner.
Exceptions, not updates
An exception is anything outside what was agreed:
- A number outside its range.
- A decision someone made over their limit, or held because they had no limit.
- A deadline that slipped.
- Anything that waited on the owner for more than a day.
Everything else stays out of the room. Work that is on track doesn't need airtime.
The owner stops answering requests inside a limit and sends them back to the person named. Those limits live in a decision authority matrix. If the same exception comes up three weeks in a row, the limit is wrong. Change the number and keep the decision where it is.
Common mistakes
- The status round-robin. Each person reports what they did, and nobody decides anything.
- Actions with no owner. "We'll look into it" means nobody will.
- The owner talking first. Once the owner gives an answer, the team stops offering theirs.
- New numbers every week. If the numbers change, nobody can see a trend.
Where this sits in SCOPE™ by Efficiency Sprint
SCOPE™ by Efficiency Sprint has five states: Stabilize, Codify, Ownership, Pulse, Engine. The weekly meeting is where Pulse starts. At Pulse, problems arrive as exceptions in a weekly report instead of as surprises. AI watches and reports, and the owner sees what's off without asking.
It only works after Ownership, when every number and every decision has a name on it. AI scales whatever's already there.
For the version you run with your ops lead, use the Weekly 101: 45 minutes, 5 sections, 22 prompts, every week.
Find out where your company stands
Efficiency Sprint makes companies operationally ready for AI. The operational AI readiness check takes about two minutes and shows where your company stands.
Questions
How long should a weekly ops meeting be?
One hour for the leadership team. Forty-five minutes for the owner and the ops lead alone. If it runs longer, the numbers weren't sent ahead, or the room is getting status updates.
Who should attend?
The ops lead, the person who owns each number, and the business owner. If someone owns nothing on the list, they don't need to be there. Send them the actions instead.
What numbers should we review?
Five to seven, the same ones every week, each with one owner. Start with cash, overdue receivables, booked work, on-time delivery and complaints. Add the owner's hours spent on approvals, so you can watch that number fall.
Should the owner run it?
No. The ops lead runs it, and the owner speaks last. The meeting is practice for the team deciding without the owner. If the owner runs it, every answer still comes from one person.
Can AI prepare the meeting?
Yes, once the numbers live in one place and every limit is written down. An agent can pull the numbers, flag what went over a limit, and send the list the day before. Every agent runs until it hits a gate a person still owns. The decisions in the room stay with people. You always need to know who is responsible. And it can't be AI.