Air Maestro ideas

Objective:
Provide administrators the option to enforce that Safety Reports cannot be signed off until all associated Findings/Actions and Forum threads have been completed or closed.

Problem:
Currently, Safety Reports can be signed off even when:

• Findings/Actions are still open, due, or overdue.

• Forum discussions/requests for follow-up are pending.

This creates gaps in closure discipline and can lead to premature report completion, weakening safety assurance and audit readiness.

Proposed Solutions (two complementary options):

1. Global Enforcement (Admin-level setting)

• Location: Setup > Safety Options > Global Settings

• Control: Checkbox — “Require closure of all Findings/Actions and Forum items before report sign-off”

• Behavior:

  • When enabled, the system blocks sign-off if any linked Finding/Action is in Open, Due, or Overdue status, or if any Forum follow-up is pending.

  • The sign-off button is disabled with a tooltip and a clickable “View outstanding items” link.

  • Validation message example: “Sign-off blocked: 3 open actions and 1 forum follow-up pending.”

2. Report-Type Enforcement (Template-level setting)

• Location: Setup > Report Type Options > Sign-Off

• Control: Checkbox — “Prevent sign-off until all Actions and/or Forum follow-ups are closed”

• Behavior:

  • Allow selective enforcement on specific report types (e.g., Hazard Report, Occurrence, Safety Observation) without impacting all report categories.

  • Inherits from global setting unless explicitly overridden at the report type level.

Additional Workflow Recommendations:

• Pre-signoff checklist: Display a compact panel on the Sign-Off screen summarising outstanding items with direct links to close them.

• Grace/exception flow (optional): Admin-configurable override role or reason code with audit log if a critical operational need requires sign-off before full closure.

• Notifications:

  • Auto-remind assignees when sign-off is blocked due to their open items (e.g., daily digest of overdue actions tied to pending sign-off reports).

• Reporting:

  • New filter: “Reports blocked from sign-off” with counts of open actions/forum items.

  • KPI: Average time from last action closure to final sign-off.

Validation Logic (high-level):

• Block sign-off if any associated item meets:

  • Actions/Findings: status in {Open, In Progress, Due, Overdue}

  • Forum items: any “Follow Up Required” thread not marked Resolved/Closed

• Exclude items explicitly marked “Not Applicable” or “Canceled,” with user permissions controlling who can apply these statuses.

Audit and Traceability:

• Log all sign-off attempts that are blocked, including user, timestamp, and list of blocking items.

• Log any admin overrides with reason and approver identity.

Benefits:

• Ensures procedural integrity and strengthens safety governance.

• Improves audit readiness by guaranteeing complete closure prior to sign-off.

• Reduces the risk of lingering corrective actions post-closure.

• Offers flexibility via global and per-report-type controls to fit diverse operator policies.