Crew, qualification, validity — held against the same operational picture as your safety, quality and compliance work. The matrix updates itself. A training gap raised by an occurrence becomes a training requirement automatically, and an expiring qualification surfaces on the dashboard before anyone goes off-rotation.
Role × competency × validity, against the regulator your fleet flies under. Cells light by status. One click drills into the qualification record behind any cell — the certificate, the instructor authorisation, the session date.
Validity windows are tracked against every qualification on every crew member. Thirty days out the row turns amber on the matrix, and the rostering team sees the same signal you do — long before someone shows up for a duty they cannot legally fly.
An investigation lands on a knowledge gap, a procedural drift, an unfamiliar fleet variant. The finding’s closure path opens a typed training requirement against the affected role. No separate spreadsheet, no second entry.
A role definition lists the qualifications it requires, the recurrent windows for each, and the evidence accepted. Onboarding a new captain means assigning the role — the matrix populates from that single act.
Each recurrent qualification has a regulator-defined window. eAviora opens the slot the moment the window does, proposes session dates against crew availability, and freezes the result against the qualification’s validity period.
No PDF assembly, no last-minute spreadsheet rebuild. The competency matrix is a live view; you scope it to a fleet, a role, an audit period — it prints regulator-ready, signed and time-stamped.
Every qualification, every session, every gap flows into the rest of your safety system without an integration project. Four examples that matter on Monday morning.
Walk through the role definition, the recurrent windows, and a regulator-ready export — with the founder, on your fleet shape, in 30 minutes.