Review the commitments already on the calendar, decisions waiting
Review the commitments already on the calendar, decisions waiting on the founder, active projects, and promises made to stakeholders. Put each item beside a next action or a clear choice.
Keep support responsible for the view and the reminders
Keep support responsible for the view and the reminders, not for deciding the founder's strategy. Escalate when two commitments cannot both fit or when a new promise changes the plan.
End the reset by protecting a small number of priority blocks
End the reset by protecting a small number of priority blocks. The value comes from fewer hidden commitments, not from filling every open minute.
Related resources
Read also: founder weekly review with a virtual assistant and executive priority management support.
Frequently asked questions
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.
Ready to define the role?
Use a recent leadership week to scope the support that would make the biggest difference. The consultation is a working conversation, not a generic pitch.
Book a consultation