Grouping for analysis

Within the Ops & Safety Suite, all report types are accessed and submitted through the “Lodge a Safety Report” function. While this provides a single point of entry for reporting, it creates an issue with how the system categorizes, counts, and displays reporting activity. The primary concern is that every report submitted through this function appears to contribute to the overall safety report totals. This results in the displayed number of safety reports being higher than the number of reports involving an actual safety event, hazard, operational concern, or safety-related observation. Several report types housed within this area serve primarily administrative or operational-support functions, such as Public Relations reports and Landing Zone reports. Although these reports remain important to the organization, they should not automatically be counted as safety reports when calculating safety reporting activity, performance indicators, or trends. As a result, I have to manually review the individual reports and separate safety-specific submissions from administrative reports to determine the actual number of safety reports received during a given period. This significantly reduces the value of the automated reporting and dashboard functions within the Suite. The associated graphs and statistical outputs also become less meaningful because the underlying dataset combines reports with different purposes and classifications. This issue creates a larger concern regarding trend analysis. At present, there does not appear to be an effective method to select and open a defined group of reports for side-by-side review or collective analysis. For example, if I need to examine all flight reports, ground reports, defect reports, or transport debriefs from a specific quarter, I must review the reports individually rather than analyze the selected dataset as a group. This makes identifying recurring hazards, common causal factors, locations, departments, aircraft, event types, or emerging trends unnecessarily difficult. The same limitation applies to risk assessment forms. Risk assessments generate valuable Safety Assurance data, particularly when reviewing recurring risk levels, fatigue indicators, operational conditions, elevated scores, and changes over time. Without the ability to filter, group, compare, and analyze multiple assessments collectively, much of the analytical value of the information is lost. Ideally, the system should distinguish between safety-specific reports and administrative or operational-support reports at the reporting and analytics level. It should also allow reports and risk assessments to be filtered by report type, date range, location, department, aircraft, risk level, status, and other relevant fields. The ability to select a group of records and generate comparative data, summaries, or trend graphs would significantly improve the usefulness of the Suite for Safety Assurance and management review. The issue is therefore greater than the accuracy of the report count. The current structure affects data integrity, performance measurement, trend identification, and the ability to use collected information effectively for Safety Assurance. The Suite is capturing the information, but the present reporting structure makes it difficult to convert that information into meaningful safety intelligence.