How to measure meeting cancellation rate and rescheduling trends

Your meeting cancellation rate is the share of original bookings that end up canceled. To get it right, count each booking once, by how it finally ended, and track reschedules separately as a history of changes. Mixing the two is the most common way these reports go wrong.

Here's how it happens. One client moves an appointment twice and then shows up. Another cancels once. The report counts three "cancellations", but only one meeting was actually lost. The team then changes its reminder policy to fix the wrong problem.

This guide shows how to set up cancellation and rescheduling numbers that tell you something useful. It uses one 100-booking example you can check line by line.

Decide what one record stands for

In this guide, one row is one original booking. When its time changes, keep the link back to that original booking. A reschedule doesn't count as a new booking, even if your system creates a fresh record for the new time.

Then pick how you group bookings. You can group them by the date they were created and follow them for a set period. Or an operations team might report on meetings scheduled to happen in a given week. Both work, but they answer different questions, so label which one you're using.

Grouping by creation date asks what happened to the bookings people made in that period. Grouping by meeting date asks what happened to the time reserved in that calendar window. If a client moves a meeting into next month, the two reports treat it differently.

Define cancellations, reschedules and no-shows separately

"Ever rescheduled" is a history flag. A booking with that flag can still end completed, canceled or as a no-show, so keep it out of your final outcome totals.

Decide what to do with reopened cancellations and corrected records. This guide uses the status on the cutoff date for the cancellation rate. An "ever canceled" flag would answer a different question. If bookings get reinstated, say which definition you used.

Choose a booking group and a follow-up window

The example uses 100 original bookings created between June 1 and 30, 2026. Each one is followed for 60 days after it was created. The review happens on August 30, after the last booking's window closes, and every example outcome is known by then.

In real data, some bookings won't have an outcome yet, so show pending and unknown counts. A meeting scheduled after the cutoff hasn't failed. It just hasn't happened inside your window.

Keep all timestamps in one reporting time zone, and keep the order of changes. The latest meeting date alone can't tell you how often a booking moved or whether a cancellation came late.

How to calculate meeting cancellation rate without double counting

Three numbers do most of the work:

• Cancellation rate = bookings that ended canceled ÷ all original bookings × 100. Here, 20 ÷ 100 × 100 = 20%.
• Reschedule rate = bookings moved at least once ÷ all original bookings × 100. Here, 25 ÷ 100 × 100 = 25%.
• Reschedules per moved booking = total reschedule actions ÷ bookings moved at least once. Here, 40 ÷ 25 = 1.6.

The 40 actions don't mean 40% of bookings were moved. Only 25 were, and some of them moved more than once.

The completed share is 70%. If you leave cancellations out and only look at meetings that were still on, the show-up rate is 70 ÷ (70 + 10) × 100 = 87.5%. That uses a different base, so label it clearly if you report it next to the 70%.

Pick the measures that fit your team, and print the definitions next to the numbers so nobody has to guess what they mean.

Separate repeat reschedules from lost meetings

Take booking B101 as an example. It moves twice and then gets canceled. It counts as one original booking, one canceled outcome, one ever-rescheduled booking and two reschedule actions. It doesn't count as three canceled meetings.

Booking B102 moves once and then goes ahead. It counts as one completed outcome, one ever-rescheduled booking and one action. The change still created admin work, but the meeting wasn't lost.

To spot repeated disruption, look at how many bookings moved zero, one, two or more times. Check how far meetings move and whether one meeting type keeps needing a new date. An average alone can hide a handful of difficult cases.

Don't guess at motives from a reschedule. Work clashes, unclear prep, host availability and tech problems can all cause one. Use the recorded reasons and a polite follow-up rather than labeling a client unreliable from a single number.

Define late cancellation before you measure it

For example, a policy might call a cancellation "late" if it happens less than 24 hours before the latest agreed start time. That's a house rule to test, not a universal standard or legal advice. Record whether the host or the guest made the change.

Say 6 of the 20 canceled bookings break that 24-hour rule. Late cancellations are then 6% of all 100 bookings and 30% of canceled bookings. Both are correct. They describe different shares, so say which one you mean.

Measure against the start time that was current when the cancellation happened. Using an old meeting time after a reschedule can mislabel the change. If you don't have the change history, say the late-cancellation numbers are incomplete.

Use cancellation reasons you can act on

Make the reason question optional where it makes sense, and don't ask for sensitive details. A short category is usually more useful than a long personal story. Keep an "unknown" option so nobody gets forced into the wrong reason.

Several of these reasons trace back to the confirmation message. If yours is vague about the time, link or prep, start with these appointment confirmation email templates.

Check Caletus meeting status data before you build the report

Caletus's meeting management page describes upcoming, completed, canceled and rescheduled meetings, including any rescheduling reasons the guest gives. Check which history and timestamps you can actually see.^[1]

Caletus's scheduling analytics page covers cancellations, reschedules, host comparisons and exports. Check the definitions and original booking IDs before you combine that data with your own report.^[2]

Then run a quick test. Make one booking that moves twice, one that gets canceled and one that goes ahead. Compare what the export shows with your counting rules. A status label on screen may not come with the full change history in the export, and this test shows you either way.

If you need to match new records to originals, keep an approved mapping. Don't match records by guest name alone, and don't quietly drop awkward canceled rows from the total. Store these records under your usual retention and access rules.

Look into rescheduling trends before you change policy

Split the data by meeting type, host, how far ahead people booked or who made the change, but only when there's enough data. A new service may need different prep from an established one. What looks like a host problem may come from the kind of meetings that host gets.

Compare groups that have had the same amount of time. A recent group with lots of upcoming meetings can show a low cancellation rate simply because those meetings haven't reached the point where people usually cancel. Show pending outcomes and the follow-up window with every comparison.

Look at the raw counts before you react to a percentage. Going from one canceled booking out of 10 to two out of 10 doubles the rate, but it's one extra cancellation. That may be worth a quick look at the booking, while a new policy can wait.

When outcomes are missing, show how many are still unresolved. A lower cancellation rate can simply mean nobody updated the records.

A simple monthly review checklist

1. 1Write down the booking group, time zone, cutoff date and how you confirm an outcome.
2. 2Keep final outcomes apart from reschedule history and repeat-change counts.
3. 3Link new records to their originals, and keep pending or unknown records visible.
4. 4Define late cancellation against the right start time and timestamp.
5. 5Check that totals add up before you split by host, event, source or reason.
6. 6Look at a few real bookings behind each trend, and pick one realistic fix.

A good report tells you whether meetings are being lost, moved successfully or disrupted again and again. That helps you improve scheduling without punishing people for using the change options you gave them. If no-shows are the bigger issue, see how to reduce no-shows with reminders and easy rescheduling.

• meeting cancellation rate
• rescheduling trends
• booking outcome reporting
• appointment changes