Task · Part-145
Conduct competence assessments
A qualification says someone learned it. Competence says they can do it — observed, evaluated and recorded in a way that stands up later.
[photo] An assessor with a tablet observing a mechanic performing a task at …
An assessor with a tablet observing a mechanic performing a task at an aircraft component — respectful distance, both concentrated; the observation situation itself.
BildvorschlagThe work behind it
[illustration] A structured assessment sheet motif splitting into three labelled …
A structured assessment sheet motif splitting into three labelled bands — Prerequisites (checklist), Elements (task card), Observable Behaviors (criteria list) — converging into a single result seal. Thin-line.
BildvorschlagPart-145 requires competence to be established, not assumed. That means structured assessments: verifying the prerequisites are in place, setting a realistic piece of work, observing how it is performed, and judging both the result and the manner against defined criteria — then recording it all so the judgement is defensible years later.
Run on paper, assessments are hard to standardise between assessors, harder to file, and hardest to defend when an auditor asks how exactly competence was established.
Where it eats time today
Every assessor their own form
Without shared templates, comparability between assessments is a matter of luck.
Paper capture, double work
Observations noted in the hangar, typed up at the desk, filed somewhere third.
The judgement without its basis
"Competent" on a signed sheet, with the criteria and observations lost to the archive.
How it works in cimoio.aero
-
Assess against a Scenario
Every assessment runs against a versioned Scenario: the prerequisite qualifications to verify, the Elements — practical assignments or question sets — to perform, and the Observable Behaviors to evaluate. Same structure, every assessor, every time.
[mockup] A Scenario overview
A Scenario overview: three sections (Prerequisites ticked, 2 Elements, 6 Observable Behaviors), version tag, assessment type "Continuous".
Bildvorschlag -
[mockup] Tablet capture view
Tablet capture view: an Element with scale selector and threshold marker, an OB below with comment field and photo attachment chip.
BildvorschlagCapture digitally, where the work happens
The assessor evaluates on the device: one scale across all Elements and Behaviors, defined pass thresholds, comments and photo evidence per item. Only qualified assessors can conduct — the system enforces it.
-
A result both sides stand behind
The outcome is binary — competent or not competent — confirmed by the assessor and acknowledged by the assessee, with a signed record and form number. The resulting competence carries its validity and feeds the authorization directly.
[mockup] Completion screen
Completion screen: result "Competent", validity date, two acknowledgement status chips (assessor confirmed / assessee acknowledged), generated PDF reference.
Bildvorschlag
The functions behind it
See a Scenario run end to end
In a guided demo we walk one assessment from prerequisites to acknowledged result — on the device it would really run on.
Or start faster with Compliance as a ServiceSound familiar?
The challenges behind this task
More tasks
-
Report qualification status
The Monday question from management, the annual question from the authority, the daily question from the shop floor — reporting is the same task at three altitudes.
-
Define qualification requirements for a role
Before anyone can be authorized, someone has to decide — and document — what the role requires: which qualifications, which competences, verified how.
-
Assign qualifications by profile
New hires, transfers, new roles: someone has to connect people with the requirements that apply to them — and keep that connection current.