Build a handover note for a delegated role change

On this page
  1. How to approach: Build a handover note for a delegated role change
  2. Record the open work and the decisions
  3. Record the contacts and the boundaries
  4. Set the first review
  5. Review the handover after the transition
Delegation Operations

Published November 9, 2026

Cover image for article: Build a handover note for a delegated role change

Build a handover note for a delegated role change

How to approach: Build a handover note for a delegated role change

A handover note should let the new owner continue without the old owner. Start with the open work, the decisions, the contacts, and the first review. A note that only lists tasks is not a handover. Review the first few notes together before the process expands. The review should end with one owner and one date.

Keep the note short enough to read before the first day. The new owner should know what to do first. A short note with four fields is easier to use than a long narrative. Separate what was observed from what was assumed. The assistant should record the owner before the next task starts.

Record the open work and the decisions

Write each open item with the status, the next action, and the owner. Record the decisions that are still open and the person who can make them. A decision without an owner will sit. Keep the original note beside the corrected version. The review should end with one owner and one date. The handover should say what the next person may decide.

Record the source for each item. A later reviewer should see the evidence. Use the same format for every handover so the next reader can scan it. If the source is unclear, route the question instead of guessing. The assistant should record the owner before the next task starts. A commitment that is not checked is not a control.

Record the contacts and the boundaries

List the key contacts, the escalation path, and the preferred channel. Record what the new owner may decide and what requires approval. A boundary that is only in a policy file will be missed. Separate what was observed from what was assumed. The handover should say what the next person may decide. The principal should see the decision and the evidence on one page.

Record the access the new owner needs. A handover without access is not complete. Keep the evidence with the record rather than in a separate log. Keep the original note beside the corrected version. The review should end with one owner and one date. The assistant should record the owner before the next task starts.

Set the first review

Record the date and the person who will review the new owner's first work. The review should be specific and short. Ask whether a new reviewer could act on the record without a conversation. Use the same format for every handover so the next reader can scan it. The principal should see the decision and the evidence on one page. The assistant should record the owner before the next task starts.

Record the questions the new owner should ask. A good handover invites questions. Ask whether a new reviewer could act on the record without a conversation. Keep the original note beside the corrected version. The principal should see the decision and the evidence on one page. Test the brief on one real task before expanding the role.

Review the handover after the transition

Ask the new owner what was missing. Update the template. A handover that improves after each change is more useful than a perfect document. A short note with four fields is easier to use than a long narrative. The review should end with one owner and one date.

Ready to delegate this kind of work?

A free consultation takes 30 minutes. Leave with a clear delegation plan.

Get Free Consultation
Build a handover note for a delegated role change | Delegation Assistant