Compliance Visibility in Scheduling

Overview

Compliance status appears inline when you add or edit a scheduled event, before you save. Separate from that, the Schedule view surfaces a banner when upcoming flight events have compliance or grounding issues. This article covers both surfaces.

Compliance panels on Add/Edit Event

When you select an instructor or student, collapsible compliance panels always appear beneath the selector. When all records are current, chips show green. When there are gaps, chips show yellow or red depending on severity.

Instructor panels:

• Compliance — certificates, medical, FIRC, TSA, flight review
• Qualifications — course and aircraft authorizations

Both panels appear beneath the instructor selector. Each is collapsed by default; click to expand and see individual chips per record type.

Student panel:

• Compliance only — one panel appears beneath the student selector

A Status Legend info button appears in the dialog footer whenever any panel is open with issues. It documents chip colors and icons for reference.

Panels are informational. You can save the event regardless of what the panels show — they surface gaps, they do not block saving.

Aircraft status on Add/Edit Event

Grounded aircraft are not excluded from the aircraft picker. They appear in the dropdown list with a red Grounded chip inline so you can see the status before selecting.

When any aircraft is selected, an Aircraft Status row renders below the selector showing either Airworthy (green) or Grounded (red). This row always appears for the selected aircraft regardless of status — it is not conditional on an issue existing.

To change the grounded state, update the aircraft record in the fleet. See Managing Organization Aircraft.

Squawk panel on Add/Edit Event

When an aircraft is selected, a Squawks panel also appears below the aircraft selector — separate from the Aircraft Status row. It shows the current open squawk state for that aircraft at the time of booking. When the aircraft is clear, the panel shows a green card labeled "Squawks — No open squawks." When open squawks exist, the card is tinted by the highest severity and shows a count and summary (e.g., "Squawks (2) — 1 do not fly · 1 discrepancy"). Click the card to expand and see individual squawk entries with severity chip and description.

This panel is informational only. Open squawks do not block saving the event. A Do Not Fly squawk will block dispatch checkout at flight time — see Filing and Resolving Squawks for how to resolve it before the flight.

Schedule Alerts

Schedule Alerts appear as a banner at the top of the Schedule view when upcoming flight events have compliance or airworthiness issues. They are separate from the inline panels in Add/Edit Event.

The banner reads: "Schedule Alert: Upcoming event(s) require attention"

Opening the dialog

Click Review on the banner. The Events Requiring Attention dialog lists affected upcoming flight events only — ground school and other event types are not included. Events are sorted chronologically.

How the dialog is organized

Each event entry groups issues by actor in this order: Instructor → Student → Aircraft. Actor rows are hidden when that actor has no issues on the event.

• Instructor — compliance records and qualifications
• Student — compliance records
• Aircraft — four possible chips, each shown only when issues exist: Compliance (N) for airworthiness document issues, Maintenance (N) for inspection issues, Squawks (N) colored by highest open severity, and Grounded (always red)

Severity model

Schedule Alerts uses the same five-tier model as Member Alerts:

Resolving alerts

Compliance alerts resolve automatically when the underlying record is updated — by the member in the iOS app or by an admin in the portal. There is no manual dismissal. Alerts recompute from data.

For grounded aircraft: open the aircraft record, click Edit, and toggle Aircraft Status back to Airworthy.

Relationship to Member Alerts

Both surfaces use the same severity model and chip colors, but they are scoped differently.