An agency operations review should identify stalled work, unresolved decisions, unowned handoffs and commitments that need a change. Prepare from current project records, give each decision an owner and record the result where delivery happens. Use the meeting to resolve exceptions instead of having everyone read their task list aloud.
- Prepare exceptionsUse current records to identify unresolved operational work.
- Invite decision ownersInclude people able to resolve or authorize changes.
- Record the decisionCapture action, owner, review point, and condition.
- Improve recurring issuesSeparate immediate recovery from process improvement.
Routine task updates can remain in the work system.
Define the purpose of the review
The review exists to make decisions that work records alone have not resolved. A routine task update can often happen in the project system. Cross-team blockers, competing commitments and unclear ownership need discussion.
Choose a rhythm that fits your work. A weekly review is a useful starting format, not a rule every agency must follow. During a short launch or a complicated handoff, a different rhythm may be appropriate. Keep the purpose stable even when the schedule changes.
Prepare the exception list
| Review item | Preparation needed | Decision to make |
|---|---|---|
| Blocked delivery | Dependency, effect and current owner | Who resolves it and what can proceed |
| Unowned handoff | Sending and receiving roles | Who accepts the next step |
| Changed commitment | Current scope and capacity issue | Continue, adjust or escalate |
| Pending client decision | Request, reviewer and review date | Follow-up or alternate action |
| Automation failure | Affected records and attempted recovery | Repair owner and temporary process |
| Repeated exception | Recent examples | Which process needs improvement |
Give participants enough context to decide. A list that only says “client issue” or “automation broken” will spend the meeting reconstructing facts.
- Blocked deliveryBring dependency, effect, and current owner.
- Unowned handoffBring sending and receiving roles.
- Pending client decisionBring request, reviewer, and review date.
- Automation failureBring affected records and attempted recovery.
Each item needs enough context for a decision, not just a problem label.
Invite the people who can resolve the issue
Each item needs an accountable owner and, where appropriate, the person authorized to change the commitment. A team member may explain a capacity problem without being able to renegotiate a deadline. Include or route the decision to the right person.
For an illustrative agency project, production is ready but approval has stalled. The review should establish which client contact is responsible, what has already been requested and who will make the next contact. Repeating that the task is blocked does not resolve the handoff.
Record decisions in the work system
For each decision, record the action, owner, intended review point and any condition. Update the project or workflow record while the context is clear. Meeting notes can preserve discussion, but they should not become a parallel source of task instructions.
- Write the actionRecord the agreed next action.
- Name the ownerAssign responsibility for the action or missing input.
- Set review pointState when the record should be checked again.
- Close or supersedeClose completed items or replace them with a new decision.
Meeting notes may preserve discussion but should not be the sole task instruction.
If the group cannot decide, record the specific information needed and who will obtain it. “Discuss next week” is only useful if someone owns the missing input. Close items when the agreed action is complete or a new decision supersedes it.
Separate immediate recovery from process improvement
Resolve the immediate issue first, then identify whether it is recurring. A one-time missing asset may need a client follow-up. Repeated missing assets at kickoff may justify revising intake and readiness checks.
The handoff checklist helps inspect responsibility and completion. The exception handling guide addresses failed automated work. Keep improvement tasks bounded so the review does not become a discussion about replacing every tool.
Check whether the review helps
Track decisions made, actions left without an owner and issues that recur without a process change. Ask whether participants leave knowing which commitments changed and what they need to do next.
- Decisions madeTrack whether prepared issues reached a decision.
- Unowned actionsTrack actions left without an owner.
- Recurring issuesTrack issues repeating without a process change.
- Operational recordCheck whether commitments and next actions became clearer.
Shorter meetings alone do not establish a useful review.
Shorter meetings are not automatically better, and more discussion is not automatically progress. A useful review produces clear actions and a more accurate operational record. If nothing is decided, improve preparation or move routine updates out of the meeting before adding another dashboard.
Questions and answers
Who should attend the agency operations review?
Invite the people needed to resolve the prepared exceptions and authorize relevant changes. Broader visibility can come from the resulting records. Avoid requiring everyone to attend simply to hear information already available in the project system.
Should the review cover every active task?
Focus on work that needs a decision, has a blocker or crosses an unclear handoff. Routine task progress can remain in the work system. Review a full project when its commitments need attention, rather than reading every task by default.
What should be recorded after the meeting?
Record the decision, next action, owner, review point and any condition in the relevant project or workflow record. Preserve context in meeting notes when useful, but avoid leaving operational instructions only in a separate notes document.