The Dashboard is the high-level operational view of an Event. It helps you quickly assess the Event’s current state and gives you access to common event-level actions.
Use the Dashboard when you need a fast read on the Event before making changes elsewhere. It is the best place to orient yourself, spot issues that need attention, and then move to the tab that controls the detail you want to manage.
What the Dashboard is for
- reviewing the Event at a glance
- checking high-level operational indicators and warnings
- confirming whether the Event looks ready for the next stage of delivery
- moving quickly into the tab where detailed work is done
- using event-level actions such as duplication and one-off messaging
When to use the Dashboard
Use the Dashboard:
- when opening an Event for a quick health check
- before editing setup, sessions, students, or finances
- when investigating an operational issue on a live Event
- when you want to create a similar Event quickly
- when you need to send an event-specific one-off email
Dashboard versus tab-based work
The Dashboard is a summary and action layer. It helps you decide where to go next, but most detailed work happens in the Event tabs.
- Use Setup for structural settings such as registration controls, personnel, resources, and key configuration.
- Use Outline for sessions, scheduling detail, documents, and content-related setup.
- Use Students for bookings, attendance, results, participation, and feedback.
- Use Finances for revenue, costs, and event-level financial review.
- Use Communications and Audit for messaging and event activity history.
Common actions
Duplicate Event
Duplicating an Event is useful when you need to create another delivery that is similar to an existing one. This can save time by carrying forward core configuration, after which you can adjust the new Event as needed.
After duplicating an Event, review the new record carefully before using it.
- Open the source Event.
- Use the duplicate action to create a new Event from it.
- Review the new Event’s dates, sessions, assignments, and any Event-specific overrides.
- Confirm registration settings, learner-facing details, and financial settings are correct.
- Save and continue setup before publishing or enrolling learners.
Caution
A duplicated Event should always be reviewed before use. Dates, sessions, personnel, resources, prices, registration rules, and communications may all need adjustment for the new delivery.
Event ad-hoc emailer
Use the Event ad-hoc emailer to send a one-off communication related to the Event. This is useful for operational exceptions or event-specific updates that do not belong in your repeatable communication setup.
Common examples include:
- last-minute joining instructions
- venue or logistics updates
- special reminders for a specific delivery
- exception handling for a live Event
Use ad-hoc email when the message is specific to this Event instance. Use the Communications tab for repeatable or managed event messaging.
Operational checks to make from the Dashboard
- Confirm the Event status is correct for its current stage.
- Review dates and other high-level delivery details.
- Check whether bookings, capacity, or other warning indicators need attention.
- If your organization uses target fill rate, review any warnings surfaced on the Event.
- Move to the appropriate tab to correct issues rather than relying on the summary view alone.
Best practices
- Use the Dashboard first when opening a live Event.
- Duplicate an Event when reusing a delivery pattern, but review the new Event fully before use.
- Use ad-hoc email for exceptions, and keep repeatable messaging in Communications.
- After major changes, return to the Dashboard to confirm the Event still looks correct at a glance.