Executive office delegation register
A delegation register turns informal permission into a rule that can survive pressure, absence, and staff changes. It should name the action, delegated person, limit, required evidence, effective date, and review owner.
Write permissions as verbs such as accept, decline, reschedule, draft, send, approve, or purchase. Broad labels such as "manage the calendar" leave too much room for conflicting interpretations.
Define limits by consequence
The same task can carry different risk depending on the person, value, confidentiality, or commitment involved. Describe the boundary that changes who must decide.
Include prohibited actions as well as allowed ones when confusion is plausible. The assistant should not infer permission to disclose, commit resources, or waive a control from permission to prepare the work.
Require decision evidence
State which sources an assistant must consult before acting. A calendar rule may require a meeting purpose and attendee list, while a purchase may require an approved budget owner.
When evidence is incomplete, the register should identify the escalation route. It should never encourage the assistant to invent a preference because a deadline is close.
Handle temporary delegation
Travel, leave, and urgent projects often create temporary authority. Give those entries a start time, end time, backup owner, and explicit scope.
Withdraw access and notify affected people when the period ends. Expired authority is dangerous when systems still permit the old action.
Test the register with real cases
Review several recent ambiguous requests and ask two authorized staff members how they would act. Different answers reveal language that needs correction.
Link the register to the executive assistant approval matrix, then preserve who approved each change and when it took effect.