A chief of staff weekly review that turns priorities into owned commitments

Define what the review must produce

A chief of staff weekly review sits between strategy and the operating day. Its job is to expose where a meaningful result lacks ownership, where an accepted commitment lacks time, and where a decision is preventing progress. It is not a competition to report the most activity. A useful review changes a small set of commitments and makes those changes unambiguous.

Agree the review's output before choosing the agenda. For each important exception, the group should decide to proceed, change scope, re-date, delegate, wait with a follow-up, or stop. Preserve context without turning every decision into a long narrative. An absent decision is itself an exception: record who must make it and when the team will revisit it.

Prepare a small evidence pack, not a presentation marathon

Before the meeting, gather the active outcomes, open actions due soon, blocked or waiting commitments, and the next week's actual availability. Ask owners to update material changes in advance. Do not infer progress from silence or from a task being in motion. A short note explaining what changed and what decision is needed is more useful than a polished percentage without evidence.

Keep sensitive board, customer, hiring, and personnel details in their authorized workspace. A broadly shared review can use neutral labels and link to restricted context where appropriate. The downloadable template is deliberately blank: it does not request private calendar links or access credentials. Distribute only the version appropriate to its audience.

• Outcome: the result that matters and the observable evidence of progress.
• Exception: the blocked, late, unowned, or unscheduled commitment.
• Decision: the choice required, the decision-maker, and the latest useful date.
• Capacity: the time genuinely available after meetings, absence, and transitions.

Use a 50-minute decision-first agenda

The following agenda is a starting template, not a research-backed optimum. Adjust the duration to the organization's complexity, but keep the sequence: results, exceptions, feasible commitments, then confirmation. If a discussion becomes solution design, assign a separate working session rather than consuming the whole review. This protects attention for the decisions only this group can make.

At the start, choose the two or three outcomes that need executive attention this week. At the end, read back the commitments in plain language. Ask whether the owner accepts both the result and the time assumption. A task assigned during a meeting without that check is only a request, not a reliable operating promise.

Worked example: a launch that is busy but not ready

Consider a fictional team preparing a partner launch. The broad outcome is a launch approved for the agreed market, not finish 20 tasks. Three commitments need attention: a decision memo requires 90 minutes, an integration review requires two hours, and a contract decision is waiting on another team. None of these fictional details describe a Critical Path customer or a measured result.

The review finds that the memo owner has only one 60-minute usable opening after transition buffers before Thursday's decision meeting. The team reduces the memo to the two unresolved choices and agrees a 45-minute preparation session. The integration review retains its two-hour estimate and moves to a verified opening. The contract dependency receives a named follow-up owner and a Wednesday check, rather than another vague reminder to chase it.

The improvement is not a prettier task board. Scope changed openly, time was checked, and the waiting state acquired an accountable next move. The review still cannot claim the launch is successful. That requires the agreed approval or result. Closing preparation tasks is evidence of execution, not a substitute for the outcome itself.

Challenge capacity before accepting new promises

Start from the actual week. Subtract fixed meetings, time off, travel, and necessary transitions from the hours a person can reasonably use. Then compare that availability with estimated work. Avoid treating an increased capacity setting as proof that more time exists. If a week already contains too much work, the review must choose what changes instead of asking a scheduling tool to solve an impossible set of constraints.

Check time off explicitly. Google distinguishes out-of-office status events from working-location events; account support varies. The operating question is simpler than the implementation detail: is the person unavailable, and is that absence represented in the calendar being used for planning? A visible office-location label is not enough evidence to answer either question.

Reserve space for uncertainty. Choose a reserve appropriate to your own workload rather than copying an arbitrary universal percentage. Review it the next week against actual interruptions and unfinished work. Keep effort estimates editable, and do not punish owners for exposing a better estimate early. Hidden overruns are harder to manage than visible tradeoffs.

Sources: Google Calendar status-event guide

Translate the review into Critical Path

Use Outcomes to review the broader tracks, then inspect the linked actions rather than relying only on a summary score. Automatic grouping in Critical Path uses task terms and project context; it is a starting classification, not an understanding of your strategy. Rename tracks to state the intended result and move an action when its suggested association is wrong. Manual alignment is part of good judgment, not a failure of the review.

Use Matrix for the importance and urgency decision, Pipeline for execution stage, and Calendar for actual placement. These are different views of the same work. Committed means agreed work; In motion means it is being executed. A task should not need a new copy in each view. Set an owner, a date when needed, and an allocation in the task details, then save and verify the relevant placement.

1. Open Outcomes and select the tracks needing a decision this week.
2. Review blocked, waiting, and overdue actions; name the specific next move for each.
3. Use Matrix to remove low-value commitments from the active focus.
4. Check task allocations against personal weekly budgets and real calendar openings.
5. Review Calendar and provider sync state before describing time as protected.
6. Update Pipeline stages and the agreed follow-up, then share only the appropriate decision summary.

Review the quality of the review next week

Begin the next review with the prior decisions. Which commitments closed? Which moved, and why? Which waiting items received the promised follow-up? This keeps accountability attached to the actual agreement rather than to an impression of busyness. It also reveals whether the review is generating too many simultaneous priorities.

Do not create a reporting burden larger than the coordination problem. Keep the record short enough that owners use it during the week. Start with the template below, run one review, and remove any field that never informs a decision. Retain the essentials: result, owner, next action, effort, date, dependency, and next check.

Common questions