A warm welcome can unravel after the visitor leaves reception. A question is passed to another colleague, the original team member goes off shift, and everyone assumes someone else will respond. The visitor experiences the gap as silence. The team experiences it as a search through messages and a conversation about who was supposed to do what.
A useful handover makes the next action visible and confirms that another person has accepted it. For a medspa front desk, that often means handling enquiries, appointment changes and callbacks consistently. Clinical questions still need the appropriate qualified colleague and the practice’s clinical escalation process.
At a glance
- Record the current situation and the action still needed.
- Name the receiving colleague and agree the timing.
- Confirm acceptance; a sent message alone does not finish the handover.
Separate the message from the responsibility
Sending a note is an action by the sender. Taking ownership is an action by the receiver. If the process only records the first, work can sit between people even when everyone believes they have done their part. Start by making the transfer explicit in the communication channel your practice has approved.
AHRQ’s handoff guidance emphasises clear information, transfer of responsibility, acknowledgement and the opportunity to ask questions. The five-part front desk template below is an original administrative adaptation of those principles, not a replacement for a clinical handoff protocol. Read AHRQ’s handoff guidance.
Give the receiving colleague five useful pieces of information
An example administrative handover template. Use the practice’s approved system and information-handling procedures.
- Context: what is the enquiry or task, recorded in the appropriate system?
- Current position: what has already been done, and what remains uncertain?
- Next action: what specifically needs to happen?
- Owner and timing: who accepts the task, and when will they act or review it?
- Confirmation: how will the sender know the task was accepted and completed?
Keep the detail proportionate to the task. A routine appointment query should not require a lengthy narrative, but “please follow up” is too vague to guide the next person. If an essential detail is missing, ask for it before accepting a task that cannot be completed. Use an internal reference where appropriate rather than copying personal details across unnecessary channels.
A worked example: a callback across a shift change
In this fictional scenario, a visitor asks whether an evening consultation slot is available. The morning receptionist checks the current diary but needs the scheduling lead to confirm a pending change. Before leaving, the receptionist records the request, what was checked and the remaining question in the approved system.
Sender: “The evening consultation enquiry is ready for scheduling review. I checked the current diary; the pending change still needs confirmation. Can you take ownership and update the task by the agreed callback time?”
Receiver: “I’ll check with the scheduling lead and update the task before that time. If I cannot confirm the slot, I’ll record that and arrange the next update.”
The sender confirms that this matches the plan. Notice that the receiver accepts an action, rather than promising an appointment that has not been confirmed. If the receiver cannot take the task, the sender and lead need another plan before the shift changes.
AHRQ describes this repeat-and-confirm pattern in its check-back tool. The wording above is our own example of applying it to an administrative task. See the check-back method.
Design for the handover that does not go smoothly
Write down what happens when the expected colleague is absent, the visitor cannot be reached, or the task remains unresolved. The fallback should identify who reviews the task and how the next contact is arranged. “Leave another message” is not enough if nobody knows who is watching the queue.
Decide which tasks need immediate attention under the practice’s existing escalation procedures. Do not turn a routine front desk queue into a substitute for those procedures. A receptionist should be able to recognise that a question belongs elsewhere and reach the designated person without inventing an answer.
Test the fallback with a fictional task during a quiet period. Ask a colleague unfamiliar with the example to explain the next action using only the record. If they need to track down the sender for basic context, identify the missing field and improve the template.
Review the process with a small sample
Choose a short review period and inspect a manageable set of administrative handovers. Count how many needed clarification, how many lacked a named owner and how many were still open at the agreed review point. Record the total number reviewed as well as the count with a problem. A count without a denominator is difficult to compare across a busy and a quiet week.
These measures are suggestions for your own process review, not published benchmarks or proof of a patient outcome. Include the team’s observations: a template might be complete yet awkward to use during a busy arrival period. Improve the workflow with the people who actually use it.
Try this at the next shift change
- Choose one ordinary administrative task and use the five-part template.
- Ask the receiver to explain the next action and accept ownership.
- Check that the agreed fallback is available if the task cannot be completed.
- Review the record together after completion and remove any unnecessary detail.
The goal is a visitor who knows what happens next and a colleague who can pick up the work without starting again. For related practice scenarios, see Three everyday conversations worth practising.
Sources and further reading
- AHRQ TeamSTEPPS: Handoff — clarity, responsibility and acknowledgement.
- AHRQ TeamSTEPPS: Check-Back — repeating and confirming a message.
Sample article for the V-Unite Learn preview. The dialogue, template and suggested measures are illustrative administrative examples. Sources checked 6 October 2026.