A “slots filled” report is a useful starting point for reviewing cancellation software. It is not enough to justify expanding it. An owner needs to distinguish three possible benefits: patients getting earlier appointments, more work being booked and attended, and reception spending less time arranging it.
Start by establishing what the software counts as a success. An existing appointment brought forward is different from an appointment made for someone who was previously unbooked. A report that combines them cannot tell you how much of the result came from moving existing work and how much came from adding bookings.
Are patients getting earlier appointments?
For patients with existing appointments, record how far each booking was brought forward. If the intended benefit is earlier care, include attendance in the review.
For someone previously unbooked, record the time from their request to the appointment. That gives you a waiting-time measure; showing that the software shortened the interval requires a comparison.
Earlier access may be the practice’s main reason for using the feature. It can justify keeping the setup even when an increase in total appointments remains unproven.
Did the practice gain an appointment?
Consider a fictional example: a patient booked for 10 November takes a cancellation on 28 October. October gains a booking; November loses one. An October-only report shows an increase, while the diary across both dates still contains the same number of appointments.
What happens to 10 November determines the next result. If another already-booked patient takes it, follow the slot they release too. If someone previously unbooked takes it, there is an additional booking in that sequence. That still does not establish how much business the software generated: the patient might otherwise have booked through reception or another route.
Choose a review period that includes the dates affected, and record the later vacancies whose outcomes are still pending. A monthly reporting boundary should not turn an unfinished sequence into a completed gain.
Exchanging an imminent gap for a later vacancy gives the practice more time to find a suitable patient. That scheduling benefit is worth recording even while the later slot remains empty. Whether it leads to additional attended work depends on what happens next.
For a broader assessment, look at booked and attended appointment time alongside the number of cancellations and the time available to refill them. Raw appointment counts can conceal differences in duration. Raw monthly totals can also change because more clinician time was available or demand increased.
Comparable periods or a limited rollout can help, provided those differences are considered. They will not provide perfect attribution, but they offer a firmer basis than crediting every accepted offer to the software. Keep the booking result separate from the attendance result: filling a gap on screen does not establish that the work took place.
How much work does reception still do?
The relevant question is how much staff involvement remains between identifying a gap and reaching a settled appointment.
Some existing features already complete substantial parts of that journey. One documented short-notice workflow moves the accepted booking, releases its original slot, confirms the change and stops further offers. This is a reason to inspect the functionality and configuration already available before buying another product.
The reply-handling documentation for another short-notice feature describes manual matching when a response fails its keyword rules, including responses that contain the keyword alongside extra wording. Include that remaining staff work when assessing the feature.
A sample of completed bookings and unsuccessful attempts can show where staff involvement remains: clarification, replies that do not lead to bookings, abandoned attempts and corrections. To assess time saved, compare staff handling time with a comparable period or process, allowing for the number and type of gaps. Counting only successful automated bookings would omit work that may determine whether expansion is worthwhile.
The practice should retain control over suitability. From an investment perspective, what matters is whether the setup can apply the practice’s requirements and whether exceptions reach staff with enough context to resolve them efficiently. A high response rate is less useful if staff must repeatedly discover that the offered appointment cannot work.
Before expanding the setup, identify which benefit supports the decision and how much staff work it still requires. If reception spends too much time resolving exceptions, check whether existing configuration or the supplier’s setup services can reduce it. Further software investment needs a specific reason: a demonstrated benefit worth extending, or an important requirement the current system cannot meet. Where the evidence is incomplete, measure the missing result before deciding.
