> ## Documentation Index
> Fetch the complete documentation index at: https://docs.planeconnection.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Triage Safety Reports
> Classify, prioritize, and route incoming safety reports through the triage workflow to ensure timely review and appropriate response.
By following this guide, you will triage incoming safety reports by classifying event types, assigning priority levels, routing reports to the appropriate reviewer, and tracking triage throughput.
Triage access requires the **Safety Manager** role or higher. Reports arrive in the triage queue
from all submission channels -- web form, natural language, ASAP, and anonymous submissions.
## Access the Triage Queue
Navigate to **Safety > Triage** in the sidebar. The triage dashboard displays all incoming reports that have not yet been classified and prioritized. Reports are sorted by submission date, with the oldest unprocessed reports at the top.
The queue displays summary information for each report:
| Column | Description |
| ------------- | ---------------------------------------------------------------- |
| Tracking code | Unique report identifier for reference. |
| Submitted | Date and time the report was received. |
| Reporter | Name of the reporter (or "Anonymous" for anonymous submissions). |
| Type | Preliminary event type, if the reporter selected one. |
| AI suggestion | AI-recommended classification and priority, if available. |
| Time in queue | Elapsed time since submission, highlighted red after 24 hours. |
## Triage a Report
### Step 1: Open the report
Click a report in the triage queue to open its detail view. Review the narrative, contributing factors, and any attached evidence.
### Step 2: Classify the event type
Assign the appropriate event classification from the taxonomy (e.g., ground event, flight deviation, maintenance finding, security concern, environmental, operational). If the reporter's initial selection is incorrect, update it here.
### Step 3: Assign a priority level
Set the priority based on severity and urgency:
| Priority | Criteria | Response target |
| ------------ | ------------------------------------------------------------------------ | ---------------- |
| **Critical** | Immediate safety threat, potential for serious injury or aircraft damage | Same day |
| **High** | Significant safety concern requiring prompt investigation | 48 hours |
| **Medium** | Moderate concern, trend indicator, or process deviation | 5 business days |
| **Low** | Minor observation, informational, or suggestion | 10 business days |
### Step 4: Route to a reviewer
Assign the report to the appropriate reviewer based on the event type and your team structure. Safety managers can assign reports to investigators, department heads, or specific subject matter experts.
### Step 5: Add triage notes
Document your triage rationale -- why you assigned this classification and priority. These notes become part of the report's audit trail and are visible to the assigned reviewer.
### Step 6: Complete triage
Click **Complete Triage**. The report exits the triage queue and appears in the assigned reviewer's workload. The reporter receives a notification that their report is under review.
When AI suggestions are available, they appear alongside the report. AI recommendations are based
on the report narrative and historical classification patterns. Use them as a starting point, but
always apply your professional judgment -- classification decisions must be made by a qualified
safety professional.
## Monitor Triage Performance
Track triage throughput from the triage dashboard header:
* **Queue depth** -- number of reports awaiting triage. A growing queue indicates a staffing or process bottleneck.
* **Average triage time** -- mean time from submission to triage completion. Target is under 24 hours for all reports.
* **Reports by priority** -- distribution of triaged reports across priority levels. A spike in Critical or High reports may warrant additional resources.
14 CFR 5.71 requires timely processing of safety data. Reports that remain in the triage queue
beyond your organization's defined response targets may indicate a gap in your Safety Assurance
processes. Monitor queue depth daily.
**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](/en/reference/legal-notices#ai-and-automated-features-disclaimer).
## Related
How reports enter the triage queue.
What happens after a report is triaged and assigned for investigation.
All report lifecycle statuses including triage states.
Configure classification taxonomies and routing rules.