An appointment slot goes unfilled, or a family turns up on the wrong day. It happens in every busy clinic office, and the first instinct is to ask who dropped the ball. That instinct costs more than the slip did. This page gives you seven plain questions for a blame-free review of a missed appointment, in the order you should ask them. They are administrative questions only. They stay clear of treatment, and this page offers no medical guidance whatsoever. If you run a front desk, a scheduling team or a patient-coordination role, you can use them tomorrow with a notepad and fifteen minutes.
Question one: what is the plain sequence of events?
Write the timeline before anyone offers an opinion. When was the appointment booked, how was the family told, when was the reminder meant to go out, and when did the gap show up? Use times where you have them and “unknown” where you do not. Leave out adjectives. A timeline that says “reminder not sent” is useful; one that says “reminder carelessly forgotten” has already decided the outcome.
Practical tip: ask one person to be the scribe, and let everyone else talk. The scribe’s only job is to keep the sentences neutral.
Question two: what could each person see at the time?
Looking back, every slip seems predictable. To push against that, ask what was on each person’s screen, in their inbox and on their desk at the moment of the decision. If the booking system showed two similar names, or the reminder list had no status column, then what looked like inattention was a reasonable reading of poor information.
This is the single most useful question in the set, because it moves attention from character to conditions. Conditions can be changed by Thursday.
Question three: where did a hand-off happen?
Mark every point on the timeline where a task moved from one person, role or system to another. Missed appointments cluster at hand-offs: from booking desk to reminder team, from a paper note to a digital calendar, from the day shift to the evening shift. Ask what information was meant to travel across each one, and whether anything checked that it arrived.
If a hand-off relied on someone remembering to mention something, circle it. That is a likely contributor.
Question four: what made the slip easy, and what would have made it hard?
Now look at the setup. Was the workload unusually heavy that day? Was the reminder step buried three screens deep? Did the cover arrangement exist only in a conversation? List every factor that made the slip more likely, then ask the mirror question: what single feature, if it had existed, would have made the slip difficult to commit?
This mirror question tends to produce the best ideas. A prompt that appears when a booking has no reminder attached is the sort of feature that comes out of it.
Question five: did we have a safeguard, and did it work?
Many offices already have a second check, such as a daily printout of tomorrow’s list or a weekly audit of unconfirmed bookings. Ask whether it ran, whether it was clear to the person doing it, and whether it catches this specific kind of gap. A safeguard that exists on paper but is skipped when the office is busy is worth more attention than a missing safeguard, because it tells you the check is too heavy or too vague.
Question six: which single change will we make?
One. Not five. A review that produces a long wish list produces nothing, because nobody can carry out a long list. Choose the change that gives the most benefit for the least trouble, write it as a sentence a new colleague could follow, and give it a role and a date.
Examples that work: a “reminder sent” tick on the list, a default that attaches a reminder at the moment of booking, a daily five-minute check owned by the opening shift. Examples that do not work: “be more careful”, “double-check everything”, “pay more attention”.
Question seven: when will we check that it worked?
Book a short revisit in the calendar, usually three or four weeks away. At that meeting ask only two things: was the change made, and has the same kind of slip come back? Where the change went in and the slip still came back, the change was too weak. If the change was never made, find out what stood in the way, which is again a conditions question and not a character one.
A quick worked example
Imagine a coordination desk where a family was told to come on a Tuesday but the entry said Wednesday. The first question gives a timeline: booked by phone, entered into the calendar after the call, confirmation message generated from the entry. The second shows that the person entering the booking was also answering a second line. The third notes the hand-off from spoken words to typed entry with no read-back. The fourth finds that nothing in the system flags a date that differs from the one in the notes. The fifth finds that no safeguard exists. The sixth chooses a read-back of the date and day name at the end of every phone booking. The seventh sets a check in a month.
Nobody was blamed, and the fix took no money. That is typical.
When to skip the full set
Not every missed appointment needs seven questions. If a patient simply rang to cancel and the slot went unused, there is nothing to review. Reserve the full set for slips that repeat, slips that caused real inconvenience to families, or slips where nobody can explain what happened. For small, obvious gaps, a single line in the team log is enough: what happened, what you changed, date.
Common stumbling blocks
The same three problems keep turning up. The first is a facilitator who cannot resist hinting at who was responsible; rotate the role so nobody carries the same bias every time. The second is a list of changes so long that none of them happen; hold the line at one. The third is a meeting that is held but never revisited; the calendar entry for question seven is not optional. If you fix only these three habits, the rest of the process largely takes care of itself, and the review starts to feel like routine housekeeping instead of an inquest.
What good notes look like
Keep the written record short enough that people will actually read it. A useful page has the date, a three-line timeline, a list of contributing factors, the single change with its role and date, and the date of the check. It reads like a log entry, not a report. Store it where the next person who runs into the same kind of slip can find it, because the most valuable thing a review can give a new colleague is a head start on a problem the office has already understood.
Ground rules that keep the seven questions honest
- Keep the group small: the people who touched the process plus a neutral facilitator.
- Thank whoever first raised the problem, out loud.
- Write names as roles in the notes: “the booking desk”, “the evening coordinator”.
- Keep the notes to one page and store them where the team can find them.
- Do not attach review outcomes to performance conversations. Mixing the two makes the next review dishonest.
A small detour: planning a table without the guesswork
Cutting out guesswork matters in ordinary plans as well. Anyone who has turned up at a restaurant to find it closed, or booked for the wrong time, knows how small details derail an evening. A restaurant discovery website like FindMyResto, which lets visitors search listings, browse menus, find directions and reserve a table, collects those details before anyone leaves the house. A good review does the same thing for the office: it gathers the details so the next person has what they need.
Where to read more on this site
Teams often ask how patients and families experience the care coordination that these small processes support. The explanation of how cancer hospitals build personalised treatment plans gives a general picture of how many people and steps are involved, which is a good reminder of why clean hand-offs matter. And if your office also helps families who are weighing overseas options, the piece on why accreditation matters when evaluating cancer hospitals abroad offers general background. Both are informational reading and neither is a recommendation of any provider.
Putting it on one card
If you want a version to pin beside the phone, here is the whole thing in a line each: sequence, visibility, hand-offs, what made it easy, safeguards, one change, a date to check. Seven prompts, fifteen minutes, one page of notes. Run it after the next slip, however small, and you will probably find that the real cause was sitting in the setup all along.
