Delegation
Key takeaways
- Start with reversible work before granting broad authority.
- Record examples of acceptable and unacceptable judgment.
- Expand access only after a reviewable handoff succeeds.
Operating data
Playbook
Remote assistant onboarding should transfer context in controlled stages. Begin with observation and low-risk coordination, then move to drafting and independent execution. This protects the executive from premature access while giving the assistant real examples instead of an abstract job description.
Create an authority ledger with three columns: act independently, draft for approval, and never act. Booking an internal check-in may be independent; changing investor travel or approving a vendor invoice may not be. When a case feels ambiguous, the assistant records it for calibration rather than improvising.
The first handoff should be bounded, such as preparing one recurring meeting from invitation through follow-up. Compare the result with a written acceptance checklist: correct attendees, current documents, explicit decisions, and assigned actions. Failed checks become onboarding material, not private criticism.
Meeting records are especially useful teaching artifacts. Atlassian's meeting-notes template distinguishes attendees, agenda, discussion, and actions; place the executive's own decision conventions beside that structure so the assistant learns what must be surfaced.
Access follows need. Use individual accounts, multifactor authentication, a password manager, and a revocation list. If a task can be completed with calendar visibility, do not grant mailbox or financial access. The operations follow-through service provides a practical lane for supervised delegation.
End each onboarding week with two examples that went well, one judgment call to revise, and the next authority boundary to test. Continue with the SOP library guide once the workflow is stable. Onboarding is complete when decisions are predictable and reviewable, not merely when credentials have been shared.
FAQ
When should a leader delegate this workflow?
Delegate it when repeated coordination, routing, or follow-up is taking time away from decisions that only the leader can make.
What should the assistant own first?
Start with intake rules, status visibility, and escalation timing so the assistant can act consistently before the workflow expands.