Task · Part-145
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.
[photo] A CMM at his desk in the formal moment of approval — reviewing a …
A CMM at his desk in the formal moment of approval — reviewing a record on screen, hand on the mouse, focused gravity (not smiling-at-camera). A mechanic's helmet or hi-vis on a hook behind him connects office and hangar.
BildvorschlagThe work behind it
[illustration] A balance/seal motif
A balance/seal motif: an authorization seal resting on a pedestal of stacked evidence blocks (qualifications, competence, assessment); one panel beside it shows a block pulled out and the seal lifting off.
BildvorschlagThis is the governance core of the CMM role: checking that every required qualification and competence is present and valid, formally granting the authorization, keeping it alive while its basis holds — and revoking it, promptly and demonstrably, when the basis is gone.
Every step must be defensible later: who granted what, when, on which evidence. And revocation is the harder half — the person must know immediately, and downstream systems must stop accepting their release.
Where it eats time today
Evidence assembly per decision
Checking a grant means collecting proofs from lists, folders and inboxes — for every single authorization.
Paper certificates as the medium
A revoked scope means re-issuing documents and trusting they replace the old ones everywhere.
Revocation doesn't reach the shop floor
Between the decision and the systems where work is released lies a manual gap.
How it works in cimoio.aero
-
Grant on a verified basis
The approval workflow presents the complete basis: every required qualification and competence, each green and evidenced. Granting is one act on one screen — recorded with grantor, date and the evidence state at that moment.
[mockup] Reuse the authorization detail asset
Reuse the authorization detail asset (challenge 1, step 1) extended by an approval footer: "Grant authorization" button with grantor and timestamp line.
Bildvorschlag -
[mockup] Reuse rolling-renewal timeline asset
Reuse rolling-renewal timeline asset (challenge 1, step 2).
BildvorschlagRenewal runs rolling
While the basis stays valid, the authorization simply lives on — each incoming training or assessment extends it. No two-year re-issuing waves, no gap between expiry and paperwork.
-
Revoke with immediate, visible effect
If the basis breaks, revocation is one decision with system-wide consequences: the employee sees it in their record instantly, and connected MRO/ERP systems can block the release steps that depended on it.
[mockup] Reuse revocation split-view asset
Reuse revocation split-view asset (challenge 1, step 3).
Bildvorschlag
The functions behind it
Compliance as a Service
The fastest way out: Compliance as a Service
Pre-configured software, best-practice processes and qualification content — ready to operate in 4 weeks.
[photo] Reuse the challenge-1 CTA photo
Reuse the challenge-1 CTA photo (quality manager with tablet at hangar edge) — same asset. Alt as there.
BildvorschlagSound familiar?
The challenges behind this task
More tasks
-
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.
-
Plan and run training events
Every course is a small logistics project: the right people, a room, a trainer, invitations out, changes handled, attendance and results recorded.
-
Procure external trainings
Type courses, specialist trainings, short-notice seats: buying training well means knowing the providers, comparing real offers — and moving fast when the need is urgent.