Establish the period and available capacity
Write the dates and the people or workstreams included. Account for scheduled time, approved leave, known availability changes, and any deliberately excluded capacity. Use the same definition across the review and the reports it references.
Keep missing information visible. If a schedule is not confirmed, mark it as unresolved instead of assuming full availability. A capacity plan is only as reliable as the assumptions supplied by the people who will do the work.
Identify the skills or permissions that constrain a task. Ten spare hours elsewhere in the agency may not help a workstream waiting on one qualified reviewer. Avoid treating all hours as interchangeable when the work requires specific ownership.
List commitments and remaining work
For each project, record the next deliverable, acceptance criteria, owner, due date, and estimated remaining work. Distinguish a contractual commitment from an internal target and an unconfirmed request.
Ask what must happen before the deliverable can finish: client feedback, a design decision, a technical dependency, or a release approval. Put those prerequisites beside the work rather than burying them in a separate chat thread.
If a requirement is still changing, label the estimate accordingly. A precise total built from unresolved scope is less useful than a range and a clear decision needed to narrow it.
Review last week for context
Look at tracked time, completed deliverables, and the questions that prevented progress. Use the project variance guide to separate changes in scope from differences against the original plan.
Review non-billable work as well as client work. Administration, recruiting, documentation, and internal improvements can be deliberate responsibilities. The review should explain their effect on capacity rather than automatically characterize them as wasted time.
Use a billable utilization calculation only with its denominator and period stated. It can describe allocation, but it cannot prove the quality of delivery or establish that every unbilled hour should have been invoiced.
Make bottlenecks a first-class item
Create a list of work waiting on review, access, information, or an external response. Record how long it has waited and who can resolve it. A developer may have capacity while being unable to advance the task assigned to them.
Ask whether a different task can proceed without creating more unfinished work. Starting many additional tasks can make the review queue harder to manage. Decide deliberately rather than rewarding the appearance of activity.
If the same bottleneck recurs, assign a process change with an owner. That could be an earlier client review, a clearer brief, or a backup reviewer. Keep the action specific enough to check at the next meeting.
Use a compact review template
The working record can contain six headings: available capacity, committed deliverables, blocked work, scope changes, decisions, and follow-up owners. Keep the supporting reports linked beneath it.
For every decision, write what changes, who owns it, and when it will be checked. “Improve communication” is not an actionable decision. “Send the client the two scope options by Tuesday, owned by the project lead” is concrete enough to review.
Carry unresolved items forward with their original context. Do not remove a blocker from the record merely because the meeting ended. The next review should be able to distinguish a resolved issue from one that was forgotten.
Improve the review over time
After several cycles, ask which decisions the process helped make and which reports nobody used. Remove redundant material and improve the inputs that repeatedly cause confusion. The goal is a reliable coordination loop, not a longer weekly meeting.
Use Colabio's agency workflows and the utilization calculator as inputs where they fit. Pair the data with project context and accountable decisions so the review turns visibility into a practical plan for the coming week.