Your Weekly Advisor Operating Review: 45 Minutes, Five Decisions

Most weekly meetings mix reporting with deciding

A small technology advisory firm has plenty to discuss. New prospects appeared. A supplier missed an update. A client asked about another location. A renewal date moved closer. Commission numbers changed. Somebody is waiting on somebody else.

Put all of that into one meeting without rules and the loudest issue gets the time. The team spends twenty minutes reconstructing one account, rushes through the pipeline, and never reaches the renewal that could become next month's fire drill.

The answer is not a longer agenda. It is a tighter purpose.

Your weekly operating review should make five decisions: what moves in pipeline, which client promise needs attention, which renewal needs action, what changed in expected revenue, and which supplier issue needs escalation. Everything else is preparation or follow-up.

This is the meeting that connects the operating pieces. It should not replace a proper pipeline cleanup, delivery call, account plan, or financial close. It decides where the firm will act across those systems this week.

Do not clean the data during the meeting

If the group has to ask who owns the deal, when the client last replied, or whether the contract date is correct, the review has already slowed down.

Each owner should update their records before the meeting. That means open deals have a real stage and dated next action. Client tasks show the owner and due date. Renewals have current terms and decision timing. Supplier issues show the last confirmed response. Revenue records separate estimates from events that have happened.

Perfect data is not the standard. Decision-ready data is.

A record is ready when the team can understand the current state, the evidence behind it, and the decision required. If an owner does not know, mark the gap and assign the work. Do not spend the whole meeting searching email together.

Decision one: which deals move, and which get corrected?

Spend eight minutes on exceptions, not a tour of every open opportunity.

Look at deals with no dated next action, close dates that passed, stages that do not match the evidence, proposals without a client decision date, and new buying triggers that deserve outreach. The owner should be able to explain the next external event that would move the deal.

"Follow up" is not enough. A useful next action sounds more like: send the revised site list to the operations lead by Thursday and ask for written approval to quote. It names an action, person, date, and evidence.

Make one of four decisions for each exception: move it, correct it, nurture it, or close it. If the team needs a separate debate about every deal, the pipeline is not ready for the operating review.

Decision two: which client promise needs attention?

Clients do not experience your internal departments. They experience whether the thing you said would happen actually happened.

Review overdue client commitments, implementation steps that are blocked, unanswered client questions, and accounts where the activity timeline has gone quiet. Pay special attention when work has crossed owners. A handoff that looks clear internally may still feel invisible to the client.

Choose the promise most likely to damage trust if it drifts another week. Decide who owns the outcome, what help they need, and when the client gets an update. If the founder keeps taking routine work back, use the review to clarify the boundary instead of quietly rebuilding the bottleneck. The delegation playbook for advisory firms explains how to separate relationship ownership from task ownership.

A client issue leaves this section with an owner and a communication date. "We are working on it" is not a decision.

Decision three: which renewal needs action now?

Do not wait until a renewal enters a standard notice window to discuss it. Contract timing and client decision timing are different clocks.

Review renewals with incomplete terms, uncertain notice dates, missing usage or service evidence, stakeholder changes, unresolved service issues, or no scheduled client conversation. Ask which one needs work this week to protect the client's options later.

The answer may be confirming contract language, collecting current inventory, scheduling a review, documenting supplier performance, or deciding that the firm should not recommend the incumbent again. The technology advisor renewal playbook covers the full process. This meeting only chooses the next renewal decision that cannot drift.

Do not turn every renewal into a cross-sell exercise. Sometimes the right move is to validate that the current service still fits and leave it alone. The review should protect the client decision, not manufacture activity.

Decision four: what changed in expected revenue?

Advisory revenue gets confusing when quoted value, signed contracts, installed services, earned commissions, and paid commissions get treated as one number.

Use this section to review changes, not celebrate a big total. Which deal was signed? Which order installed? Which commission expectation changed? Which payment is late or disputed? Which assumption still needs written supplier terms?

When a number changes, record why. A verbal estimate from a supplier is not the same as an approved commission schedule. A signed order is not the same as an installed service. Expected revenue can guide planning, but the meeting should not quietly promote it to earned revenue because everybody wants a stronger forecast.

Advisor OS CRM connects deals, suppliers, commissions, contacts, activities, and reporting. The tool can keep the records together. Your team still has to agree on what each revenue state means and what evidence moves an item forward.

Decision five: which supplier issue needs escalation?

A supplier problem becomes a client problem when ownership is vague and updates stop.

Review issues that missed a promised response, threaten an implementation date, change scope or price, or require help beyond the normal channel. Pick the issue that needs a higher level of attention and decide who will escalate it, what evidence they will send, and when the client will hear from you.

Keep the timeline factual. Record what was requested, what the supplier confirmed, what changed, and what decision you need. "Supplier is terrible" may feel accurate in the moment, but it gives the next person nothing useful to act on.

This review also creates evidence for future supplier choices. Your supplier shortlist process gets better when the team can see real support and delivery history instead of relying on memory.

A 45-minute agenda that forces choices

Run the meeting from one shared operating view and keep the same order each week:

1. Five minutes: Open the meeting. Confirm last week's assigned decisions and name any urgent change to the agenda.
2. Eight minutes: Decide which pipeline exceptions move, get corrected, enter nurture, or close.
3. Eight minutes: Choose the client promise that needs ownership, help, or communication.
4. Seven minutes: Choose the renewal action that protects the next client decision.
5. Seven minutes: Record material changes to expected, earned, disputed, or paid revenue.
6. Seven minutes: Choose the supplier issue that needs escalation and define the evidence.
7. Three minutes: Read back every decision, owner, due date, and required external confirmation.

You will not solve every issue in the room. Good. Assign the work. If a topic needs fifteen minutes of problem solving, give it a separate session with the people who can make the decision.

Keep a parking lot for useful topics that do not belong in this review. Product training, detailed proposal design, process rewrites, and long account strategy discussions matter. They simply should not steal the operating meeting.

Measure the meeting by what changed

Do not score the review by attendance or how much the team discussed. Look at the decisions.

At the end of the month, inspect whether assigned actions closed on time, stale deals left the forecast, client promises received updates, renewal gaps were resolved earlier, revenue changes carried evidence, and supplier escalations reached a clear owner. If the same issue returns every week with a new explanation, the meeting is documenting drift.

Start with one rule: no update enters the agenda unless it requires a decision, exposes a broken commitment, or changes the firm's plan. That rule alone will remove a lot of noise.

If your records cannot support this review, run the free Advisor OS agency scorecard. It will show where pipeline, client ownership, follow-up, and operating discipline still depend on memory.