Make an enquiry handover understandable to the next person

Preserve the enquiry’s facts, completed actions and unresolved decision for the next authorised person.

Start with a practical question

A handover should let another authorised person understand the enquiry without asking the caller to reconstruct every earlier conversation. It needs the relevant question, known facts, action already taken and remaining decision. More text is not automatically better: a short structured account can prevent important details becoming buried in a long message thread.

Identify the purpose of the transfer

State why the enquiry needs another person or team. Distinguish a request for specialist information from a decision that has already been authorised. If you do not know who should receive it, mark the routing question rather than assigning the matter to an invented department. Follow the actual organisation’s approved referral process.

For a fictional service team in Masvingo, the handover might concern a customer asking which reference is needed to locate an application. The first person has explained the general process but cannot locate the specific record. The note should preserve that boundary, rather than claim the application has been accepted or rejected when no such decision was made.

Separate the record into useful parts

Use headings such as question, observations, action taken and next decision. Add a case reference only if one was actually supplied. A personal working note and an organisation’s reference are different identifiers; label them so the next person does not mistake one for the other. Keep dates clear and avoid replacing an exact known date with an ambiguous phrase such as yesterday.

Include the source of a statement when it matters. “Caller reports receiving no acknowledgement” is different from “system did not send an acknowledgement”. The former records what the person knows; the latter asserts something that may require investigation. Preserving that distinction lets a specialist ask the right follow-up question instead of inheriting an unsupported conclusion.

Share only what the recipient needs

Check that the recipient and channel are appropriate for the information. Do not place passwords, one-time codes or unrelated personal documents into a referral message. Where an official process requires a document, use that process and confirm how it should be handled. A general-purpose team chat should not silently become the only store of sensitive case material.

Ask whether the next person can access the relevant approved record before copying it into several places. Duplicating information can create conflicting versions as well as unnecessary exposure. This guide offers a planning method, not a legal determination of what your organisation may collect or a claim that a particular communication tool is secure.

Check the handover from the recipient’s perspective

Have the recipient explain the question and next decision back in their own words. If they cannot tell what has already happened, revise the note before sending another version to the caller. Record who is now responsible for follow-up and which part remains unresolved. Do not invent a completion time to make the transfer sound final.

A successful handover is a clearer connection between people and records, not a guarantee that the underlying problem has been solved. Keep the caller’s understanding aligned with the actual state: referred, awaiting information, under review or resolved through the organisation’s own process. Those states should remain visibly different.

Sources & further reading

Use these references to check the underlying guidance and any current local requirements. Practical worksheets and illustrative examples in this guide are original educational material.

  1. Mozilla: bug-writing guidelines
  2. W3C WAI: writing for web accessibility

This guide is general information. Source notes are not a claim of independent professional review.