Cancel related reminders and resources when bookings change

What this means for your practice

List everything cancellation should change and check the result in each connected system. Sending a notification is only one step; reminders, resources and tasks must reflect the agreed outcome.

Questions to take to your supplier

Cancel a fictional appointment with both a room and a reminder attached. Inspect the outcome in each system. Ask who handles an update that fails, and how the team knows the exception is resolved. A sent cancellation notice alone does not prove the connected work changed.

Agree the working process

Make a list of everything a cancellation is expected to change in your particular process. Reminders and allocated resources may be obvious, but there may also be internal tasks or messages waiting to run. Give each connected outcome an owner and agree which cancellation record is the main source. Ask the supplier to demonstrate what happens when one dependent update fails while the others succeed. Staff should see the remaining work rather than assume the whole cancellation failed or completed as a single block.

Include a cancellation close to a scheduled reminder in testing. That is a useful way to check work already prepared for dispatch. Plan recovery carefully so a later retry does not reverse a deliberate manual correction or repeat an unnecessary message. In reviews, distinguish appointments correctly cancelled in the diary from connected tasks still active. The aim is a consistent working picture across the systems people use, with exceptions clear enough for the responsible team to resolve without reconstructing every step from scratch.

How to check the result

Count cancelled appointments with active dependent tasks.