Chief of staff weekly operating review
A focused weekly review for decisions, risks, commitments, and cross-functional follow through.
- Define the executive support outcome
- Match role scope to leadership cadence
- Use a structured selection process
Define the role
Prepare the review from the decision log, action register, and current project updates. Do not copy every update into the meeting; bring the items that need a choice, owner, or escalation.
Set the operating model
Keep strategic judgment with the chief of staff and executives. Support can prepare the view, flag missing evidence, and maintain the next-action record.
Choose with care
Close the review by naming what changed, who owns the next step, and when the team will look again. The operating rhythm should reduce surprise work, not create a new reporting ritual.
Related resources
Read also: leadership meeting cadence support and executive project status brief template. Source: U.S. General Services Administration project management resources.
FAQ
What should support own?
Support should own recurring coordination and preparation with a clear output, owner, and escalation boundary.
When should support escalate?
Escalate when work creates a new commitment, involves sensitive information, exceeds agreed authority, or has no accountable decision-maker.
How should the workflow improve?
Review real misses and rework, then change one rule, template, or handoff that addresses the evidence.
Discuss executive support