Keep a meeting delegation note that survives a handoff

On this page
  1. How to approach: Keep a meeting delegation note that survives a handoff
  2. Record decisions, not opinions
  3. Name the owner and the date
  4. Keep the open questions visible
  5. Make the note findable
  6. Review the note at handover
Delegation Operations

Published November 8, 2026

Cover image for article: Keep a meeting delegation note that survives a handoff

Keep a meeting delegation note that survives a handoff

How to approach: Keep a meeting delegation note that survives a handoff

A meeting note is useful when it preserves decisions, owners, and dates. A transcript of the discussion is not a working record. The next assistant should be able to open the note and know what to do. Ask whether a new reviewer could act on the record without a conversation.

Use four fields: decision, owner, due date, and open question. Add a short context line so a reader who missed the meeting understands the purpose. Keep the format the same across meetings. Separate what was observed from what was assumed.

Record decisions, not opinions

Write what was decided in a sentence that can be tested. A note that says the team discussed the timeline is not a decision. A note that says the timeline moves to the fifteenth and the client will be told by Friday is. Separate what was observed from what was assumed.

If no decision was made, say so and name the next meeting or the person who will decide. An ambiguous note invites the next assistant to assume a decision that never happened. Review the first few notes together before the process expands. Write the deadline as a date and a local time.

Name the owner and the date

Every action needs one owner and one due date. A team name is not an owner. A date without a year or time zone is not a date. Record the owner in the same line as the action.

If an action depends on someone outside the meeting, record the dependency. The next assistant should know whether the action is waiting on a client, a manager, or a system change. Keep the original note beside the corrected version. A short note with four fields is easier to use than a long narrative.

Keep the open questions visible

Open questions show where the work could stall. Write the question, the person who can answer it, and the date the answer is needed. Do not bury it in a paragraph. A short note with four fields is easier to use than a long narrative.

Review the open questions at the start of the next meeting. A question that has been open for weeks is a signal that the owner or the scope is wrong. A short note with four fields is easier to use than a long narrative. Keep the evidence with the record rather than in a separate log.

Make the note findable

Store the notes in the same place with a consistent title and date. A new assistant should not have to search three tools to find the last decision. Link the note to the task or client record. Write the deadline as a date and a local time.

Keep the raw transcript separate from the summary. The summary is the working record, while the transcript is the archive. A reader should not have to read the transcript to find the decision. Keep the original note beside the corrected version.

Review the note at handover

When the assistant changes, read the last few notes together. Ask the new assistant to explain the open decisions and actions. If the notes do not support that explanation, improve the format. Record the exception and the person who approved it.

A good note format reduces the time a new assistant needs to become useful. It also protects the team when the person who took the notes is unavailable. Keep the boundary visible in the place where the work is assigned. Keep the evidence with the record rather than in a separate log.

Ready to delegate this kind of work?

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

Get Free Consultation
Keep a meeting delegation note that survives a handoff | Delegation Assistant