Link reminders to a schedule revision
Synthetic rule: send one reminder two hours before the confirmed start. Booking B-N moves from 18:00 to 20:00 at 15:00. Its queued 16:00 reminder belongs to old revision 1 and is cancelled; a new 18:00 reminder uses revision 2. Already-sent messages are retained as history and may need a change notice.
| Reminder | Revision / due | Before move | After move |
|---|---|---|---|
| N-1 | 1 / 16:00 | Queued | Cancelled: superseded |
| N-2 | 2 / 18:00 | Not created | Queued for new start |
| Change notice | 2 / after confirmation | Not required before move | Record separately |
Recheck the booking before dispatch
- Confirm the move and save schedule revision 2.
- Retire unsent revision-1 reminders and create the revision-2 due time.
- At dispatch, verify the booking is active and still uses revision 2.
If the new reminder due time is already past, use an explicitly agreed late-notice rule; do not invent an immediate duplicate reminder.
Should both N-1 and N-2 be sent because both once belonged to a confirmed booking?
Show the worked answer
No. Only N-2 represents the current 20:00 start. 20:00 - 2 hours = 18:00; N-1’s 16:00 timing is obsolete.
A change notice and a timed reminder have different purposes. Keep separate records so one does not falsely satisfy the other.