Class cancellation and reschedule content update record
Treat the changed session as one concrete record, then update its actual public and participant routes. A cancellation, a replacement session and a change to a person's booking are different outcomes. Announce only the arrangement the organiser has actually confirmed.
Your working document
Review the actual material
- The exact affected session is identifiable.
- A replacement date is stated only when confirmed.
- Existing participants have the actual contact or booking-management route.
- The current timetable and booking destination agree.
- Old active date-specific material is reviewed.
- Any participant booking terms are handled through the actual arrangement, not an invented generic promise.
Handle the specific situation
| Situation | Useful information | What to distinguish |
|---|---|---|
| Session cancelled without a replacement | Confirmed next step for existing participants | Do not invent a future session date |
| Session moved | New date, time, location and what happens to existing bookings | Keep the old and new references distinguishable |
| Online joining details changed | Actual participant delivery route | Do not expose private joining credentials in a public post |
| Only one person's booking changed | The person's actual booking-management process | Do not announce a whole-session cancellation |
Complete the handoff
A single caption can announce the change, while this record helps locate every destination that still carries the old arrangement. It complements the existing timetable caption pack rather than creating another set of synonymous cancellation captions.