Chief of staff cross functional handoff
A handoff pattern for moving leadership work between support and functional owners.
- Define the executive support outcome
- Match role scope to leadership cadence
- Use a structured selection process
Define the role
Start with the work, not the title. For this workflow, include the requested outcome, current state, owner, dependency, deadline, and escalation trigger. Write the expected outcome, accountable owner, and evidence that will show completion.
Set the operating model
Give support a clear rule for preparing, coordinating, recording, and routing the work. Escalate new commitments, sensitive information, policy exceptions, and requests with no clear decision owner.
Choose with care
Review the process after real use. Keep examples of rework, missed response windows, and changed priorities. Use those examples to improve one rule, template, or handoff.
Related resources
Read also: delegation map and dependency log. Source: authoritative reference.
FAQ
What should support own?
Support should own repeatable coordination and preparation with a named owner and a clear output.
When should support escalate?
Escalate when work creates a new commitment, involves sensitive information, needs a policy exception, or has no accountable decision-maker.
How should the workflow improve?
Review real misses and convert repeated questions into a clearer rule, template, or handoff.
Discuss executive support