Where it starts
Task lists on paper, competencies on a slide
The authority and the industry expect observable behaviours and a competency framework. The department still grades task by task, instructors grade differently, and the records that would show the change live in binders.
- A framework chosen, but not yet on any form
- Old task-based checks that must stay comparable
- Instructors who need convincing, not just training
What Qualify does
Your framework on every form, one catalogue underneath
Build competency forms, keep task forms for what stays task-based, and use mixed forms during the transition. All of them draw from one catalogue of tasks and manoeuvres, so the history stays whole. Your own codes map to the IATA and ICAO ones, so the summaries the industry asks for come out on their own.
- Frameworks with observable behaviours, yours or the built-in ones
- Threats and errors recorded against the competency that caught them
- Calibration sessions to bring instructors into line
- Competency-based and task-based results shown side by side, never mixed
What you end up with
Aligned with CBTA, with the records to prove it
- Every check carries its framework, its form version and its behaviour-level grades
- Fleet Microscope shows which competency needs a syllabus change
- An industry-style summary, with names removed, ready to share
- Instructors graded against the same standard
How the project runs
Six steps, most of them yours
01
Understanding your training
Which fleets, which framework, which forms first.
02
A demo in a real session
Your instructors grade a real session on the iPad with your forms.
03
Setting up
Frameworks, rating scales, the item catalogue, roles and policy.
04
Bringing the history
Existing syllabi and records brought in, so due dates are right from day one.
05
Training the team
Training managers on the web, instructors on the iPad, a first calibration session.
06
Living with it
Fleet analysis and exports switched on as records accumulate, and a partner who keeps listening.