Delegation fails when the handoff is verbal
A principal explains a recurring task in a hallway and assumes the message landed. Three weeks later the task is late, and both people remember a different instruction. Verbal delegation feels efficient because it avoids a document, but it transfers ambiguity instead of work. A delegation log gives the handoff a shape that can be checked.
The log is not a performance record. It is a shared description of what has moved, what remains with the principal, and how success will be judged. That description protects the assistant from unclear expectations and protects the principal from surprises. It also makes a temporary handover much easier.
Review the log with the principal at the start of each quarter. Ask which entries are still accurate and which tasks have changed. A ten-minute conversation prevents the document from becoming a historical record. The log should reflect the current division of work, not last year's.
List the recurring tasks before assigning them
Start with the tasks that repeat weekly or monthly rather than the one-off projects. Include the preparation, the decision, the follow-up, and the record keeping as separate steps. Many tasks are partly delegated and partly retained, and the log should show the boundary. A task list that says manage the board cycle is too broad to be useful.
Group the tasks by the outcome they serve, such as calendar control, board support, or vendor management. This grouping makes it easier to see gaps and overlaps. It also shows where one person is carrying too much. Review the list with the principal before writing detailed entries.
Record decision rights with each task
For each task, state what the assistant can decide, what requires a recommendation, and what remains with the principal. A scheduling conflict below a certain level may be resolved by the desk, while a client commitment may need approval. Write the threshold and an example. Decision rights are the part most often missing from a delegation note.
Include the escalation path for exceptions. If the assistant cannot reach the principal, who else can approve, and within what limit? The log should name a deputy and the conditions for using them. This prevents a delegated task from stalling whenever the principal is unavailable.
Set a quality bar and a check point
Describe what a good output looks like for each task. A board brief may need a recommendation, a source date, and a one-page limit, while a travel booking may need a confirmed itinerary and a backup option. The quality bar should be observable rather than a general instruction to do a good job. Add one example of an acceptable output.
Choose a check point where the principal reviews the work before it goes out. Early on, the check point may be every instance; later it can move to a sample. Record the change so both people know the current expectation. A quality bar without a check point is only a hope.
Review the log when the principal travels
Travel exposes every unclear delegation. A task that depends on a quick hallway question will stall when the principal is in another time zone. Before a trip, review the log and confirm which decisions the desk can make without contact. Update the deputy and the escalation path for the travel period.
Send the principal a short list of items that will wait for their return. This prevents the desk from guessing on matters that genuinely need the principal's judgment. It also gives the principal a chance to move something to the deputy before departure. A travel review takes minutes and prevents days of delay.
Retire tasks that no longer earn their place
Recurring tasks accumulate long after their purpose has gone. A weekly report may continue because it was once requested, even though nobody reads it. The delegation log should include a review date and an owner who can cancel the task. Removing low-value work is as important as delegating it well.
Ask what would happen if the task stopped for a month. If the answer is nothing, the task is a candidate for retirement. If the answer is a compliance or relationship risk, keep it and document why. This test is faster than a full workload study and often more honest.
Use the log during onboarding
A new assistant should be able to read the log and understand the shape of the role. The entries should explain the task, the decision rights, the quality bar, and the people involved. Pair the log with a walkthrough of the systems and a first-week shadowing plan. This reduces the period when the desk depends on memory.
For related guidance, see our article on training a new executive assistant on decision rights and our executive support services. The O*NET profile for executive assistants describes the coordination and information duties that make a written handoff useful. Use it to check that the log covers the full role rather than only the visible tasks. A log that is clear to a new reader is also clearer to the principal who delegated the work.
Key takeaways
- Write down recurring tasks and show which steps are delegated and which stay with the principal.
- Record decision rights with a threshold and an example for every task.
- Define an observable quality bar and a review check point.
- Review the log before travel and name a deputy with clear limits.
- Retire tasks that no longer earn their place and use the log for onboarding.