Open with the state of the queue

A handover note should begin with the state of the queue rather than a summary of what the outgoing person did. State the number of open items, the oldest item, and the items that arrived after the last handover. Name the queue or queues covered so the next person knows what the note does not include. A note that starts with activity cannot tell the next shift where to begin.

Separate items that are waiting on the client from items that are waiting on the team. The next shift can act on the second group and can only follow up on the first. Include the time of the last client contact and the channel used. That detail prevents a duplicate message and shows whether the promise is still alive.

Record promises and deadlines

List every promise made during the shift, including the exact time and date the client was told to expect an answer. Put the promise in the client's time zone and in the team's time zone so the next shift does not miss it. Mark whether the promise was written or verbal, because a verbal promise is easier to dispute. A handover that omits a promise forces the next person to guess at the business's commitment.

Include internal deadlines as well as client-facing ones, such as a payroll cutoff or a report that must reach a manager. Note the consequence of missing each deadline in one short phrase. If a deadline has already passed, say so plainly and record what the client was told. The next shift should never discover a missed deadline by reading an angry email.

Name the next action and owner

Every open item needs one next action and one named owner, even when the owner is outside the shift. Write the action as a verb and a specific object, such as send the corrected invoice to the client, rather than a general follow up. Name the person who will do it and the time by which it should be done. An item without a next action is not a handover item; it is a hidden backlog.

If the next action depends on a decision, name the decision owner and the question to be answered. Do not leave a note that says waiting for approval without saying who approves and what exactly is being approved. Include the date the request was sent and the channel used. The next shift can then follow up with the right person instead of starting a new search.

Separate facts from interpretation

Write observable facts first and label interpretation separately, because the next shift needs to know what happened before it hears what someone thinks happened. A fact might be that the client sent two emails and the system shows no reply. An interpretation might be that the client is frustrated. Keeping the two apart lets the next person test the interpretation against the record.

Avoid adjectives that assign motive to a customer or a colleague. Describe the message, the time, and the requested outcome instead. If a judgment is necessary, write it as a question for the next owner rather than a conclusion. A handover note that reads like a story is harder to act on than a short list of facts and open questions.

Attach the source record

Link each open item to the record that supports it, such as the ticket, the order, or the email thread. Use the system reference rather than a screenshot whenever the system holds the authoritative value. If a screenshot is the only evidence, label it with the time and the page it came from. The next shift should be able to verify the state without asking the outgoing person.

Do not paste sensitive customer data into the handover note when a link will do. Keep credentials, payment details, and identity documents in the approved system. If the note must mention a sensitive item, use a reference and state where the detail is held. A handover note is a working document, not a second copy of the customer file.

Confirm receipt

A handover is complete only when the receiving person confirms that they have read it and accepted the open items. Ask for a short acknowledgement that names any item they cannot take. The outgoing person should not leave until the acknowledgement is recorded. A note that was sent but never read is not a handover.

If the receiver disagrees with an action or needs more context, resolve it during the handover rather than after the outgoing person has left. Record the resolution and update the note. The acknowledgement should include the time it was given. That timestamp is useful when a later reviewer asks when ownership actually changed.

Audit one handover each week

Choose one handover each week and compare the note with what actually happened on the next shift. Check whether the queue state was accurate, whether every promise was carried, and whether the next actions were completed. Record one missing field or one unclear instruction. A weekly sample is enough to show whether the template is working.

Share the finding with the team without naming the person who wrote the note. Update the template or the example, then test the change on the next sample. If the same gap appears three weeks in a row, change the queue process rather than asking for more careful writing. The note reflects the process that produced it.

If the queue and decision rights are already defined but need a steady operator, outsourced operations support can turn approved examples, decision lines, and review rules into a draft your manager can check. The manager still owns exceptions and final approval.

For the next step, compare this workflow with Design a weekend coverage rota for a Philippines-based support team and Set a decision limit for refunds in a delegated queue. For access and oversight, use the authoritative planning reference alongside your own policy.