Events

The Events area is the template-level part of the Standardization module. Here you define the types of standardization activity your organisation conducts. These event types are not sessions themselves -- they are reusable categories that you link to actual sessions later.

What an event type contains

Each event type has two fields:

• Event name -- a short, recognisable title for this kind of standardization activity. This is what you will see when selecting an event type during session creation.
• Description -- a longer explanation of what the event covers, its purpose, or any relevant context. The description helps colleagues understand the intent of the event type without needing to ask.

Examples of event types

Organisations typically create event types such as:

• Flight instructor refresher session -- periodic refresher covering updated procedures, regulatory changes, or training methodology.
• Internal review event -- a structured review where flight instructors are observed or assessed against internal standards.
• New-procedure briefing -- a focused session to walk flight instructors through a specific procedural change before it takes effect.
• Annual competency check -- a yearly standardization moment tied to regulatory or organisational requirements.

The exact set of event types depends on your organisation's standardization programme. The goal is to create a stable list that reflects the recurring activities in your operation.

Creating an event type

1. Open the Standardization module and navigate to the Events area.
2. Select the option to add a new event.
3. Enter a clear, descriptive event name. Choose a name that will still make sense months or years later when you review session history.
4. Fill in the description with enough detail so that any administrator or flight instructor can understand what this event type covers.
5. Save the event type.

The new event type is now available for selection whenever you create or edit a session.

Editing an event type

You can reopen an existing event type to update its name or description. Keep in mind that changes to an event type affect how it appears in all sessions that reference it. If you rename an event type, existing sessions will reflect the updated name.

When to create a new event type versus reusing an existing one

Before creating a new event type, check whether a suitable one already exists. Creating a new type is appropriate when the standardization activity is genuinely different in purpose or scope. If the difference is only in timing or audience, it is usually better to use the same event type and capture the specifics in the session remarks.

Common tasks

• Review your event type list -- open the Events area periodically to confirm the list is still current. Remove or update event types that are no longer used.
• Standardise naming across your team -- if multiple people create event types, agree on a naming convention. For example, decide whether you use "Annual Flight Instructor Refresher" or "Flight Instructor Refresher (Annual)" and stick with one format.

Good practice

• Use stable, consistent naming for recurring event types. Avoid small variations like "Refresher 2025" and "Refresher 2026" when a single "Flight Instructor Refresher" event type with session dates will serve the same purpose.
• Keep the description focused on the purpose and scope of the event, not on logistics that change from session to session.
• Avoid creating near-duplicate event types for the same kind of standardization activity. Duplicates fragment your session history and make reporting harder.
• Review the event type list at least once a year to retire types that are no longer relevant and to add any new types your programme requires.