Purpose: This article explains how Event cancellation works in Administrate, when cancellation should be used instead of deletion, and how to safely manage the operational impact of closing an Event.
In Administrate, cancellation is the standard operational approach for Events that should no longer proceed. Event records are normally preserved to maintain learner history, financial integrity, reporting accuracy, communication traceability, and audit history.
Before you begin: Managing events in Administrate | Understanding the Event Screen
Cancel versus delete
Cancellation and deletion are not equivalent actions.
- Cancel an Event when the delivery was valid but will no longer proceed.
- Delete an Event only in exceptional situations where the record should never have existed operationally.
In most real operational workflows, cancellation is the correct and preferred approach because it preserves the historical truth of the delivery record.
Caution
Event deletion is intentionally restricted in Administrate to protect learner, financial, reporting, communication, and audit integrity. In many environments, Events cannot be deleted directly by administrators and instead require review through Administrate Support.
Cancel an Event
Cancelling an Event stops the delivery while preserving the Event record for operational history, auditability, reporting, and learner traceability.
- Open the Event.
- Navigate to the Setup tab.
- Change the Status to Cancelled.
- Save changes.
What cancelling does
- prevents further delivery of the Event
- stops new enrollments
- preserves learner participation records
- preserves audit and reporting history
- retains financial and communication traceability associated with the Event
Cancellation is generally the correct operational action for published or active Events.
Operational impact of cancellation
Cancelling an Event does not automatically reverse operational activity that already occurred.
Depending on the Event state, administrators may also need to review:
- learner communications and scheduled reminders
- invoices, credits, or refund processes
- attendance and participation records
- achievements or completion outcomes
- instructor, room, or resource allocations
Event deletion
Event deletion is intentionally limited because Events often become connected to operational records across the system.
These dependencies may include:
- learner enrollments and attendance
- achievements and completion records
- communications and communication history
- invoices, payments, and financial reporting
- audit and operational traceability
Because of this, deletion is usually reserved for Events that:
- were created accidentally
- never became operationally active
- contain no learner, attendance, communication, or financial activity
Note
In many Administrate environments, deletion is not a standard administrator workflow and may require involvement from Administrate Support to ensure dependent records are handled safely.
When to cancel versus delete
| Scenario | Recommended action |
|---|---|
| Event was created accidentally | Delete (if operationally empty) |
| Event has no learners or financial activity | Delete may be appropriate |
| Event was valid but will not proceed | Cancel |
| Learners are already enrolled | Cancel |
| Invoices or operational history exist | Cancel |
| Communications or attendance already exist | Cancel |
After cancellation
After cancelling an Event, review related operational workflows to ensure the organization and learners have accurate information.
- confirm learner communications reflect the updated status
- review invoices, credits, or refunds where applicable
- verify reporting and forecasting assumptions
- review any automated reminders or scheduled communications
Best practices
- Use cancellation for operational Events with real learner activity.
- Treat deletion as an exceptional workflow rather than a routine administrative action.
- Review communications and financial impact before changing Event status.
- Preserve audit and reporting history whenever possible.