The Five Handovers That Break a Clinic Day
Most clinic delays aren't clinical. They happen in the handovers between reception, assistants, doctors and the lab. Where they fail, and how to make them reach the right person.
Published

A patient sits in the waiting room for twenty-five minutes. The doctor was free for fifteen of them. Nobody made a clinical mistake; the message that the patient had arrived simply didn't reach the person who needed it.
Most of the friction in a clinic day happens like that — not in the chair, but in the handover between people.
The five handovers that fail most
1. Reception → doctor: "your patient is here." The most frequent handover in the clinic, and the one most often shouted down a corridor or dropped in a busy group. When it fails, the doctor waits and the patient waits, in different rooms.
2. Doctor → reception: "book the next stage." The doctor knows the crown fitting needs to be in ten days. Reception finds out when the patient asks at the desk — if they ask. This is where multi-visit treatment quietly stalls.
3. Lab → clinic: "the case is back." The case arrives, gets put on a shelf, and the person who would call the patient to book the fitting doesn't know.
4. Assistant → reception: "we used the last of the composite." Said in passing, forgotten by the afternoon, discovered the next morning when it's needed.
5. Shift → shift: "here's what's still open." The morning team leaves with three callbacks undone. The evening team doesn't know they exist.
Why they fail
These handovers don't fail because people are careless. They fail for structural reasons:
- They go to everyone instead of someone. A message to a group of twelve is a message each of the twelve can assume someone else saw.
- They aren't written down. A spoken handover depends on the listener's memory at a moment they were doing something else.
- They travel without context. "Can you call him back?" — call whom, about what?
- They arrive in the wrong place. A lab update in a personal chat isn't visible to whoever is covering that day.
Making a handover land
A good handover has three properties, and none of them need a new policy:
| Property | What it looks like |
|---|---|
| Addressed | Sent to a named person, not "the group" |
| Notified | The person gets an alert, even if they're busy |
| In context | It replies to the message it's about, or names the patient |
In practice that means @mentions, replies to the specific message, and a chat where the clinic's people already are.
Some things belong in the record, not the chat
Chat is the nudge, not the record. "Tooth 36 needs a crown after the root canal" belongs on the patient's chart, where it stays with the patient for years. "He's ready for you in Room 1" belongs in chat, where it reaches a person now and is irrelevant tomorrow.
Clinics get into trouble when they mix the two up: clinical facts lost in a scrolling chat, or real-time nudges typed into a record nobody is looking at.
How PDental handles it
PDental puts both in the same system. The team chat handles the real-time side: one-to-one and group conversations, replies to a specific message, and @mentions — including @all — that notify the person named. Pinned chats keep the handover group on top; muted chats stop the noisy ones interrupting.
The record handles the rest, and several handovers stop being messages at all. When a procedure is set up with steps, the follow-up appointment, lab order or prescription for a stage can be created automatically when that stage starts or is done — so "book the next stage" doesn't depend on anyone passing it on. Referring a patient to another doctor in the clinic sends that doctor a notification, and the referral's status updates by itself when the procedure starts or is done.
Where to start
Pick the handover that cost you the most last week — usually the first one, reception to doctor — and make it a rule that it is sent as an @mention in one agreed group. Measure nothing; just ask the doctors after two weeks whether they're still waiting for patients who are already there.
Frequently asked questions
What is a handover in a dental clinic?
Any moment where one person's piece of work becomes another person's responsibility — reception telling the doctor a patient has arrived, an assistant telling reception what to book next, the lab update reaching whoever will fit the case. Each one is a small message, and each one can be lost.
Why do handovers fail even in well-run clinics?
Because they are sent to a group instead of a person, or spoken in a corridor and not written anywhere. A message addressed to everyone is easy for each person to assume someone else handled.
How do @mentions help?
A mention turns a group message into a request for one named person and sends them a notification, even if they have muted the group. The message stays visible to everyone for context, but responsibility is clear.
Should handovers be in chat or in the patient record?
Both, for different things. Clinical facts belong in the record, where they stay with the patient. The nudge — "he's ready", "can you look at this" — belongs in chat, where it reaches a person in real time. PDental keeps both in one system so neither has to be copied.