Anchor the note to the client's business day

A handover note should begin with the client's day, not the team's shift. Record the date and time in the client's time zone and the hours the client will be offline. The next shift needs to know what the customer expects while the client sleeps. A note written only in local time creates a mental conversion at the worst moment.

Name the queues that are live, paused, or waiting on the client. A queue can be open while one task type is stopped for a missing approval. Record the state of each queue in one line. The next person should not have to reopen five tools to learn what is running.

Record the last customer-facing promise made during the shift. Include the customer, the channel, the exact promise, and the time it is due. A promise made at the end of a shift is the easiest one to miss. The next owner should see it before reading anything else.

Note any scheduled event that will change the work, such as a release, a payment run, or a holiday. Record the time and the expected effect on the queue. A handover that ignores the calendar sends the next shift into a surprise. The note should also say who will confirm that the event actually happened.

Keep the note in the same place every day and link it from the queue. A handover stored in a new thread each evening will be lost within a week. Record the location and the naming pattern. The next shift should find it without asking.

Record state instead of a diary

Write the current state of each open item, not the story of what happened. A useful line says what is done, what is blocked, and what happens next. Record the case reference beside each line. A diary of effort helps the writer feel finished but does not help the reader act.

Use four states for open work: waiting on us, waiting on the client, waiting on a system, and waiting on the customer. Record the state and the time it changed. The category tells the next shift whether to act, chase, or watch. A state that changes without a recorded time cannot be audited later.

Put the oldest and riskiest item first in each group. Age and risk matter more than the order the cases arrived. Record the age in hours or business days. The next shift should not have to sort the list to find the urgent case.

Leave out cases that are closed and need no follow-up. A handover full of completed work hides the items that still need a decision. Record the closed count in one line if the client asks for volume. The note should carry open state, not a full activity report.

Write the note while the facts are still visible, not at the end of the shift from memory. Update it when a major item changes state. Record the last update time. A note written once at the end is usually a reconstruction.

Name the next action, owner, and deadline

Every open line needs a next action that starts with a verb. Send the revised invoice, call the carrier, or confirm the refund date are actions. Record the action and the person who will do it. Check the case is not a suitable next action.

Name one owner for each action, even when the whole team shares the queue. An owner can be a role, but the note should say who is on that role tonight. Record the backup when the owner is offline. Shared ownership without a name is how items wait.

Give each action a deadline in the client's time zone and a reason for that time. A refund promised by noon should appear as an action due before noon. Record the deadline and the source of the promise. A deadline without a reason gets moved when the queue is busy.

Mark the one question the next shift must answer before it starts other work. A pending approval or a missing address can block several cases at once. Record the question and the person who can answer it. The next shift should not discover the blocker case by case.

Ask the next shift to acknowledge the note at the start of its day. A read receipt is weaker than a short reply that names the first action. Record the acknowledgement time. The handover is complete only when someone has taken ownership.

Keep the note short and searchable

Set a length limit that fits on one screen, such as one page or twenty open lines. A longer note will be skimmed and the important line will be missed. Record the limit in the template. If the work exceeds the limit, group the routine items and keep the exceptions visible.

Use the same headings every day so the reader can jump to the right section. State, promises, blockers, and questions are enough for most desks. Record the template version and the date it changed. A new heading every evening slows the reader down.

Use the case reference in the first few words of each line. A reader searching for a case should find it without reading the whole note. Record the reference format and one example. Search is the most common way the next shift will use the note.

Avoid abbreviations that only the current shift understands. A short form that saves three characters can cost a call to the client. Record the approved abbreviations in the template. The note should be readable by a new team member.

Archive the notes by date and client so a pattern can be reviewed later. A single note is a snapshot, while a month of notes shows recurring blockers. Record the archive location and the retention period. The history is useful for the monthly review.

Audit whether the handover is usable

Ask the next shift to rate the note on four things: state, next action, owner, and deadline. Record the rating and one example of what was missing. A simple score is enough to show whether the template works. Ask for one missing example rather than a general comment.

Count the items that were still open at the next handover with no change. An item that survives two shifts without action is a sign that the owner or deadline was unclear. Record the count and the case references. The pattern points to a template or capacity problem.

Check whether any customer promise was missed during the handover window. Record the promise, the time, and what the next shift knew. A missed promise is the clearest evidence that the note failed. Fix the template before blaming the person.

Review the handover time itself. A note that takes an hour to write is either too detailed or missing a source of truth. Record the median time and the length. The handover should protect the customer without consuming the shift.

Change one thing in the template each month and compare the next score. Record the change and the result. A template that is never revised slowly collects fields nobody reads. The goal is a note the next shift can act on in the first ten minutes.

For the next step, compare this workflow with Create a system outage pause log for a delegated support queue and Add a second verification step to customer address changes in a delegated order desk. For access and oversight, use the authoritative planning reference alongside your own policy.