How to Run an Agency Weekly Operations Review
Run an agency weekly operations review in 45 minutes: what to track, a fixed agenda, owners and due dates for every issue, and how to hand off the chair.
A weekly operations review is a fixed meeting where the agency looks at how delivery, clients and capacity are running. It is not about the creative work itself. It is where problems show up while there is still time to act on them.
This post covers how to run one: what to look at, who attends, the agenda, and how decisions turn into action. By the end you will have an agenda you can copy and a way to run the meeting without the owner holding every thread.
Here is the short version. Hold the review at the same time every week, for 45 minutes. Before the meeting, one person updates a single tracker with the facts: project status, deadlines at risk, client issues, team capacity and money owed.
In the meeting, go through the same five areas in the same order. Spend time only on items that are off track. Every issue leaves the room with one owner and one due date, and the next review starts by checking those actions.
The owner attends at first, then hands the chair to someone on the team once the format holds.
What a weekly operations review covers
The review is about how the agency runs. It is not a creative critique and it is not a readout of every task. Those belong in project meetings.
It covers five areas. Delivery: which projects are on track, which are at risk, and why. Clients: open complaints, approvals waiting, and accounts that have gone quiet. Team and freelancers: who is overloaded, who has spare time, and who is starting or leaving.
The last two are money and systems. Money means invoices overdue and projects running over the hours quoted. Systems means any process that broke this week and needs fixing.
If you already run a short project scan on Mondays, keep it. A weekly scan across every client project catches deadline risk early. The operations review sits one level above it, and asks why the same risks keep appearing and what to change.
Keep attendance small. The owner, whoever runs delivery or account management, and whoever handles finance or admin. Three or four people is enough, and freelancers do not need to attend because their status should already be in the tracker.
The review should be the same every week. Same day, same time, same order. People start preparing for it without being asked, and gaps become visible because the format does not change.
Prepare the facts before the meeting
The meeting is only as good as what comes into it. If the first twenty minutes go on working out what is happening, there is no time left to decide anything.
Give one person the job of updating the tracker by the end of the day before. That might be a project manager, an operations lead or an account manager. The tracker can be a spreadsheet or a view in your project management tool, as long as it is one place.
The person preparing should flag items, not just list them. Mark each project green, amber or red, with one line explaining any amber or red. List approvals that have been waiting more than three working days, and note anyone whose booked hours for next week are above their available hours.
Pull the money figures from your accounting software, not from memory. That means overdue invoices and any project where logged hours have passed the hours quoted. Left for a month, those overruns turn into the margin problems covered in finding and cutting delivery costs.
If you are not sure which part of your operations needs the most attention, the agency health check scores it in about three minutes.
Send the updated tracker to attendees an hour before. People read it before they arrive, so the meeting starts with questions instead of a readout.
Run the agenda in the same order every week
Forty five minutes is enough if the facts are prepared. Use a timer for each block and move on when it ends. Anything that needs longer gets its own meeting with only the people involved.
| Agenda block | Time | Question to answer | Output |
|---|---|---|---|
| Last week's actions | 5 min | Was each action done? | Done, or a new date and a reason |
| Delivery | 15 min | Which projects are amber or red, and why? | One action per red project |
| Clients | 10 min | Which approvals, complaints or quiet accounts need a response? | A named person to contact each client |
| Team and capacity | 5 min | Who is over or under booked next week? | Work moved or a freelancer booked |
| Money | 5 min | Which invoices are overdue and which projects are over hours? | Chase or scope conversation assigned |
| Systems | 5 min | What broke this week that will break again? | One process fix with an owner |
Copy the table into your meeting notes and keep the columns. The last column matters most. A block that ends without an output was a discussion, not a review.
Spend no time on green items. If a project is on track, it gets read past without comment. The meeting exists for the exceptions.
The clients block deserves care. Quiet accounts and slow approvals can be an early sign that a client relationship is drifting. The review is where you catch that, using the same signals behind operations fixes that improve client retention.
Turn every issue into an owner and a due date
A review that ends with a list of concerns has not done its job. Every item raised needs an action, one named owner and a due date before the meeting moves on.
Write actions as tasks, not topics. "Look into the website project delays" is a topic. "Call the client by Wednesday to agree a new launch date" is an action, and it can be checked next week.
One owner per action. If two people share it, neither owns it. The owner can bring others in, but one name goes next to the task.
Record the actions in the tracker, not in a separate notes document. They then sit next to the projects they affect and get seen every day, not just at the next review.
Start every review by reading last week's actions aloud. Each owner says done or not done, and gives a new date and a reason if not. These five minutes are what build team accountability. People learn that an action raised in the review comes back, so they finish it.
Freelancer issues follow the same rule. If a freelancer missed a handoff, the action belongs to whoever manages them. Clear briefs and named contacts, the same approach used to manage freelancers without chasing them, stop the same issue returning.
Hand the chair to someone else
In the first few weeks, the owner usually runs the review. That is fine while the format settles. The goal is a meeting that happens whether or not the owner is in the room.
Founder dependency shows up clearly here. If every action ends up with the owner, or the team waits for the owner to decide each item, the review is just a queue for decisions. Watch who takes the actions. Over time, fewer should go to the owner.
After four to six weeks, pass the chair to the person who prepares the tracker. They run the timer, read the actions and make sure each item gets an owner. The owner attends as a participant and speaks on items that need their judgment.
Set clear limits on what the team can decide in the review. For example, moving a deadline by up to three working days, or booking a freelancer at an existing rate. Anything above those limits gets escalated with a recommendation, not just a question.
Then test it. Miss one review on purpose and read the notes afterwards. If the actions are clear and owned, the review works without you. The same weekly rhythm makes preparing for time away from the agency much easier, because it keeps running while you are out.
What usually goes wrong
Reporting instead of reviewing. Each person reads out their full task list and the time runs out before any decisions. Fix it by preparing the tracker the day before and discussing only amber and red items.
Actions with no owner. The meeting agrees something should happen and nobody takes it. Fix it by not moving on until a name and a date are written next to the action.
Cancelling it in busy weeks. Busy weeks are when the review matters most. Fix it by shortening it rather than skipping it. A fifteen minute version that covers delivery and last week's actions still keeps the rhythm.
The owner makes every call. The team brings problems and waits for an answer. Fix it by asking whoever raises an issue to bring a recommendation, and by setting limits the team can decide within.
Where to start
This week, set up the tracker with the five areas and pick the person who will update it. Book a 45 minute review in the same slot every week and use the agenda table as written for the first month.
After a month, check who is taking the actions and start handing over the chair. If you would rather have a team keep the tracker current, follow up on actions and support your internal reporting, that is the work ScaleVirtual does for agencies.
Ten questions on how your agency actually runs. You get a score out of 100 and a breakdown of where the friction sits. About three minutes, free.
Common questions
How long should a weekly operations review take?
Forty five minutes is enough when one person prepares the tracker the day before. The time goes on items that are off track, not on reading out status. If a single issue needs longer, take it out of the review and book a separate session with only the people involved, so the rest of the agenda still gets covered.
Who should attend an agency operations meeting?
Keep it to three or four people. That means the owner, the person who runs delivery or account management, and whoever handles finance or admin. Freelancers and junior staff do not need to attend. Their work should already be in the tracker, and the person who manages them carries any actions back.
How is an operations review different from a project status meeting?
A project status meeting looks at individual tasks on individual projects. The weekly operations review looks across the whole agency: delivery risk, clients, capacity, money and broken processes. It asks why problems keep appearing and assigns fixes. Project meetings handle the work itself, while the review handles how the agency runs.
Can the review run without the agency owner?
Yes, once the format is stable. Hand the chair to the person who prepares the tracker, set clear limits on what the team can decide, and ask for recommendations on anything above those limits. Test it by missing one review and reading the notes. The owner still makes the calls that need their judgment.