Run an Agency Weekly Review Around Decisions

An agency weekly review should identify the client commitments at risk, the work without a clear owner, the decisions waiting for input, and the actions needed before the next review. Prepare from maintained records, discuss exceptions, and finish with named owners. More charts do not help if nobody can explain what should change.

What should the review achieve?

Choose the decisions the team needs to make. A review might coordinate the next delivery period, identify capacity conflicts, or settle client dependencies. If the objective is simply to see every activity, the meeting can become a recital. Set a narrower purpose that helps people prioritize and leave knowing the next actions.

Keep the review distinct from an individual performance judgment. A late task may reflect an unclear brief, a client dependency, missing access, or a capacity tradeoff. The meeting should uncover the cause and the decision needed. A red status without that discussion can create pressure while leaving the underlying work unchanged.

Identify who needs to attend. A small agency may have the same person covering sales, delivery, and operations. A larger team may need representatives who can make or take decisions. Invite according to the review's purpose rather than assuming every member must sit through every account. Share the resulting actions with the people affected.

Which records should be ready beforehand?

Ask owners to maintain the records used for planning: active client engagements, current milestones, task ownership, pending reviews, and important dependencies. The review should begin with information the team can trust enough to discuss. If each meeting starts by collecting missing data, address that maintenance routine rather than adding another dashboard.

Check the meaning of status labels. People may interpret “in progress” as actively worked on, merely assigned, or waiting for input. Use the supported states consistently and add context when a label cannot explain the situation. Do not invent a complex status taxonomy solely to avoid writing a short explanation of a blocker.

Prepare a short exception list. Include the commitment, why it needs attention, the decision, and the person who can act. Link supporting records so the discussion can go deeper when necessary. A concise list lets the group focus without forcing the organizer to create a second full project-management system in a presentation.

What agenda keeps the conversation useful?

Move from commitments to constraints and then to decisions. Review the work due next, the dependencies that could change it, and the capacity needed to deliver. Keep routine information available outside the meeting. A flexible agenda is more useful than a fixed duration for each person regardless of whether they need a decision.

Treat the agenda as a guide, not a demand to manufacture an issue in every category. If the relevant records are current and no decision is needed, a shorter review may be enough. Conversely, a material client risk may deserve a separate focused discussion with the right people.

How should capacity be discussed?

Compare the work selected for the next period with the people and skills actually available. Include review, coordination, and known client dependencies rather than counting production tasks alone. A person can appear available on a task list while being responsible for several approvals and calls. Make those responsibilities part of the conversation.

Avoid treating estimates as exact promises. Ask what assumptions make the plan plausible and which changes would require another decision. If new urgent work enters, identify what moves or what additional capacity is genuinely available. A plan that accepts every request without a tradeoff is not a reliable account of the team's commitments.

Keep the discussion understandable to the people who need to act. A detailed forecasting report can support a decision where available, but it is not a substitute for naming the conflict. Explain which milestone is affected, what options exist, and who can authorize the change. Record the chosen action in the relevant project.

How do commercial records enter the review?

Include commercial context only where it changes an operating decision. An invoice awaiting issuance, a recorded payment discrepancy, or an approaching retainer renewal may require an owner. Keep this discussion scoped to authorized people and use the actual financial records. A general delivery review should not become an unrestricted sharing channel for sensitive details.

Separate status categories. Work completed, client acceptance, invoice issued, and payment received are related but distinct. A project manager should not infer one from another. Use the responsible commercial or finance process to resolve uncertainty rather than allowing the review's dashboard to become an alternative accounting source.

For renewal work, identify what needs review before the next period: scope, capacity, client priorities, and commercial terms. A reminder tells you to have a conversation; it does not decide the outcome. Keep the next owner explicit so a visible warning does not become an item everyone assumes someone else is handling.

How do you end with actions that survive the meeting?

Write each action as an outcome with one responsible owner and a useful follow-up point. “Check with the client” is vague. “Ask the approval contact to choose the review date for the current draft” makes the next step more concrete. Keep the action linked to the engagement so it can be found later.

Record the decision as well as the task. A date moved because the team reprioritized for an urgent request should not look like an unexplained delay next week. Retain enough context for people who were absent. Avoid a transcript when a short decision and its consequence are sufficient to understand the current plan.

Review previous actions before adding more. If an action remains unresolved, ask whether it has the wrong owner, unclear outcome, missing input, or no longer serves a useful purpose. Repeating the same item in a meeting note does not make it actionable. Change the decision or the next step where the evidence points.

How can Flotick support the source records?

Use client records, projects and tasks, and the reporting features available on your plan. These can provide context for ownership, status, and supported analytics. Plan limits and history windows apply. A chart or assistant-generated summary should be checked against the source before it changes a client commitment.

Keep client-facing summaries appropriate to the shared view. The client portal is separate from internal planning. Decisions made in the review may require a clear external explanation, not exposure of every internal comment. Assign who updates the shared materials after the review so the two views do not drift.

If you want to test the routine, start free with one project and review pricing before expecting advanced analytics. You can also use Atlassian's roles and responsibilities play as background for discussing responsibility; this article's agenda is an original operating worksheet, not a research-backed universal formula.

What should change after a few reviews?

Look at the actions and decisions, not the number of pages produced. Are repeated blockers easier to identify? Do owners know what happens next? Is the organizer still reconstructing status manually? Use those observations to simplify the routine. Add detail only when it changes a decision or helps the people carrying it out.

What questions should the agency answer?

Does every team need a weekly meeting?

No. Choose the cadence based on the work and decisions required. A written exception review may suffice when the records are current and no discussion is needed.

Should every late task be escalated?

Not automatically. Understand the impact, dependency, and next action. Escalate the decision that needs authority rather than a status color alone.

Can an AI summary replace the review?

It can help prepare context where supported, but people remain responsible for verifying the source and making authorized decisions.