Task · Part-145
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.
[photo] A compliance manager
A compliance manager (50s, polo shirt) at a desk with the EASA regulation open on one screen and a notepad beside it, mid-thought — the interpretive work this task really is. Office adjacent to hangar, daylight.
BildvorschlagThe work behind it
[illustration] Regulation paragraphs on the left flowing through a "translation" …
Regulation paragraphs on the left flowing through a "translation" funnel into a structured profile card (qualification list + competence entry) on the right. Thin-line.
BildvorschlagDefining requirements is the foundation everything else stands on: interpreting Part-145 and company standards, deciding which trainings, licenses, experience and competence checks a role genuinely needs — and writing it down so it can be applied consistently. It's done when a new role appears, when regulation changes, and whenever an auditor asks "why exactly these requirements?"
Done well, it is the CMM's most valuable work. Done informally, it exists only in one expert's head — and every authorization decision becomes a fresh interpretation.
Where it eats time today
Every definition starts from scratch
No reusable structure means every role is a new document, a new debate.
Interpretation lives with one person
The reasoning behind requirements isn't captured, only the outcome.
Changes don't propagate
A regulation update means finding every affected role definition by memory.
How it works in cimoio.aero
-
Model the target as a profile
Requirements are captured as reusable profiles: qualifications bundled per role, competences with their observable behaviors, the assessment that verifies them. Defined once, referenced by every authorization that needs them.
[mockup] Profile editor for "Certifying Staff B1"
Profile editor for "Certifying Staff B1": qualification list, one competence entry expanded showing linked observable behaviors.
Bildvorschlag -
[mockup] A requirement row expanded with a "basis" field showing a regulation …
A requirement row expanded with a "basis" field showing a regulation reference and a free-text rationale.
BildvorschlagAttach the reasoning
Each requirement carries its basis — the regulation reference, the company standard, the note explaining the decision. The interpretation is documented with the outcome, audit-ready.
-
Change once, apply everywhere
When a requirement changes, the profile is updated in one place — every role and authorization referencing it reflects the change, and affected staff become visible immediately. With Compliance as a Service, the profiles come pre-built and are kept current for you.
[mockup] A profile change screen with an impact panel
A profile change screen with an impact panel: "used in 4 authorizations · 61 persons affected · 7 gaps created".
Bildvorschlag
The functions behind it
Start from proven profiles, not a blank page
In a guided demo we show the best-practice profiles behind Compliance as a Service — and how they map onto your organisation.
Or start faster with Compliance as a ServiceSound familiar?
The challenges behind this task
-
Authorizations expire — or exist when they shouldn't
In a Part-145 organisation, only authorized staff may perform and release work. Every authorization that lapses unnoticed — or was granted without full backing — puts you in violation of aviation law.
-
Your qualification experts are retiring
The colleague who knows which training leads to which authorization — and which provider can deliver it by next month — is leaving. The knowledge was never written down.
More tasks
-
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.
-
Grant, renew and revoke authorizations
Granting an authorization is a legal act: it says this person may perform and release this work. It has to rest on verified evidence — every time.
-
Notify staff about expiring qualifications
Everyone with a stake — the employee, their supervisor, the training team — has to know an expiry is coming while there's still time to act.