Skip to main content
By following this guide, you will configure alert thresholds for safety performance indicators, set up notification rules to reach the right people, and define escalation paths for unacknowledged alerts.
Alert configuration requires the Safety Manager role or higher. Alert thresholds apply workspace-wide. Changes take effect immediately for future data points.

Configure SPI Alert Thresholds

Safety Performance Indicators (SPIs) trigger alerts when values cross defined thresholds. Each SPI can have multiple threshold levels.
1
Step 1: Open SPI alert configuration
2
Navigate to Safety > SPIs > Configure. The configuration page lists all active SPIs with their current threshold settings.
3
Step 2: Select an SPI to configure
4
Click an SPI row to expand its threshold settings. Each SPI supports three alert levels:
5
LevelColorPurposeWatchYellowEarly warning that a metric is trending toward a concern.WarningOrangeThe metric has reached a level requiring attention.CriticalRedThe metric has breached the safety action trigger.
6
Step 3: Set threshold values
7
Enter the numeric value for each alert level. For upward-trending metrics (e.g., incident rate), the Watch threshold is the lowest value. For downward-trending metrics (e.g., training completion rate), the Watch threshold is the highest value.
8
Step 4: Configure the evaluation window
9
Set the time period over which the SPI is evaluated:
10
  • Rolling 30 days — standard for high-frequency indicators.
  • Rolling 90 days — smooths seasonal variation.
  • Calendar quarter — aligns with management review cycles.
  • Custom — any number of days.
  • 11
    Step 5: Save the configuration
    12
    Click Save. Thresholds apply to future evaluations immediately. Historical alert states are not retroactively changed.

    Set Up Notification Rules

    Alerts are only useful if they reach the right people at the right time. Configure notification channels for each alert level.
    1
    Step 1: Open notification settings
    2
    Navigate to Safety > Settings > Notifications. The notification matrix shows alert levels on one axis and recipients on the other.
    3
    Step 2: Assign recipients by alert level
    4
    For each alert level (Watch, Warning, Critical), specify who should be notified:
    5
    Recipient typeExampleRole-basedAll safety managers, the Accountable ExecutiveNamed usersSpecific individuals by nameDepartmentAll members of a department (e.g., Flight Operations)
    6
    Step 3: Select notification channels
    7
    Choose how each recipient group is notified:
    8
  • In-app notification — appears in the notification center (always on for all alerts).
  • Email — sends a formatted email with alert details and a link to the relevant dashboard.
  • SMS — sends a text message for time-sensitive alerts (requires Twilio integration).
  • Push notification — sends a browser push notification.
  • 9
    Step 4: Save notification rules
    10
    Click Save. New rules apply to future alerts. Existing unacknowledged alerts are not re-notified.

    Define Escalation Paths

    Escalation paths ensure that unacknowledged alerts automatically escalate to higher authority after a defined period.
    1
    Step 1: Open escalation configuration
    2
    From Safety > Settings, select the Escalation tab.
    3
    Step 2: Define escalation tiers
    4
    Set up escalation tiers for each alert level. A typical configuration:
    5
    TierTriggerEscalates toTier 1Alert unacknowledged after 4 hoursSafety ManagerTier 2Alert unacknowledged after 24 hoursDirector of SafetyTier 3Alert unacknowledged after 48 hoursAccountable Executive (AE)
    6
    Step 3: Set escalation timing
    7
    For each tier, specify the time delay before escalation. Critical alerts should have shorter escalation windows than Watch alerts.
    8
    Step 4: Save the escalation path
    9
    Click Save. Escalation timers begin when an alert is generated and reset when the alert is acknowledged.
    14 CFR 5.71 requires continuous monitoring of safety performance. Ensure that Critical alerts always escalate to the Accountable Executive within a timeframe that allows for timely corrective action. Document your escalation policy in your SMS manual.
    AI suggestions are advisory only. Per 14 CFR Part 5, all safety assessments, investigation findings, and risk evaluations require independent human evaluation by qualified personnel. AI recommendations should be used as one factor among many in decision-making, not as the sole basis for any safety, operational, or maintenance action. See Legal Notices.

    Configure SPIs

    Define and manage Safety Performance Indicators.

    Monitor Anomaly Detection

    Automated anomaly detection that generates alerts.

    SPI Definitions

    All available SPIs, their formulas, and default thresholds.

    Notification Channels

    Supported notification channels and integration requirements.
    Last modified on April 11, 2026