Warn Only Currency

Overview

Introduce the ability to configure a pilot currency (or any currency type) as “WARN Only”, meaning the currency will display as yellow when expired or incomplete, rather than red.

This enhancement would reduce visual fatigue and allow operators to better distinguish between:

• Hard-stop compliance requirements (Red – cannot fly)

• Operationally important but non-grounding currencies (Yellow – warning only)

Problem Statement

Currently, all expired or incomplete currencies display as red, regardless of whether they are a regulatory grounding requirement or an operational best practice.

This results in:

• Excessive red indicators across the system

• Visual fatigue for pilots and operations teams

• Reduced clarity around what truly prevents a pilot from flying

• Increased risk of overlooking critical red items due to over-saturation

Some currencies are operationally important but do not legally or operationally prevent a pilot from flying. These should not carry the same visual severity as grounding items.

Proposed Solution

Add a configuration option at the currency level:

New Setting:

If a currency is set to Warn Only:

• When expired or incomplete → displays as Yellow

• Appears in warnings but not hard compliance stops

Example Use Case

A company may have:

• FAA-required currency (must be current to fly) → Red

• Internal training requirement (strongly encouraged but not grounding) → Yellow

This allows the system to better reflect real-world operational severity.

Acceptance Criteria

• Admins can configure currency severity (Hard Requirement vs Warn Only).

• Warn Only currencies display yellow when expired or incomplete.

Business Value

• Reduces visual overload and “red fatigue”

• Improves compliance clarity

• Better aligns system behavior with operational realities

• Increases customer configurability and flexibility

• Enhances overall UX for pilots and operations teams