Task · Part-145
Archive and retrieve certificates
Certificates are the evidence layer of the whole system. Accepting them correctly, filing them findably and retaining them lawfully is daily work — retrieval on demand is the test.
[photo] Close, calm shot over the shoulder of a records coordinator scanning …
Close, calm shot over the shoulder of a records coordinator scanning a paper certificate at a desk scanner, a tidy screen beside it showing the digital record forming. The moment paper becomes record.
BildvorschlagThe work behind it
[illustration] Reuse the challenge-5 before/after intake illustration
Reuse the challenge-5 before/after intake illustration (same asset). Alt as there.
BildvorschlagEvery completed training produces a certificate that has to be checked in detail — name, date of birth, exact course title — because a wrong detail makes it worthless as evidence. Then filed so it can be produced within 24 hours, retained for the required years, and deleted when the retention ends.
It's exacting, high-volume routine — precisely the work where manual handling produces the misfiled document that surfaces at the worst moment.
Where it eats time today
Detail-checking by eye
Hundreds of documents, each needing per-field verification against the participant.
Filing discipline as the system
Folder trees only work until one busy afternoon.
Retention tracked nowhere
Keeping records long enough — and not longer — needs rules, not memory.
How it works in cimoio.aero
-
One intake, automated matching
All certificates land in the central intake; the system reads them, matches person, training and qualification, and files them at the right place — asking for a human check where confidence is low.
[mockup] Reuse intake + match-dialog assets
Reuse intake + match-dialog assets (challenge 5, steps 1–2; two assets, use both). Alt as there.
Bildvorschlag -
[mockup] Reuse the person-record evidence asset
Reuse the person-record evidence asset (challenge 2, step 3).
BildvorschlagRetrieval in seconds, in context
Every certificate is reachable from what it proves: from the person, the qualification, the authorization. The 24-hour window becomes a one-click answer — including exports for the auditor.
-
Retention and deletion run on rules
Retention periods follow policy — best-practice presets aligned with GDPR and EASA record-keeping (3–5 years), every period configurable. Expired records are deleted on schedule, documented.
[mockup] Reuse retention-policy asset
Reuse retention-policy asset (challenge 5, step 3). Alt as there.
Bildvorschlag
The functions behind it
Watch a certificate go from inbox to evidence
In a guided demo we process one of your real certificate types end to end — intake, match, retrieval.
Or start faster with Compliance as a ServiceMore tasks
-
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.
-
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.