The paper list in the quality manager's drawer, as a register: each certifying person, the category and scope they may sign for, their limits, and the date it ends. An authorisation that has lapsed never shows as in force, and every change is saved with who made it and when.
Who holds which authorisation, for which aircraft types and tasks, and until when, is usually a printed list that somebody updates when they remember. On the day of an audit, the question is whether the list on the wall is the list in force.
An authorisation, a licence and a continuation-training date each run on their own clock. The one that lapses is the one nobody was watching.
A regulator can ask who was authorised on a given day. A list that is overwritten cannot answer. A register that is only ever added to, and never deleted from, can.
Each line holds the person, the authorisation number, the category (airframe, engine, avionics, structures, NDT or other), the scope as the authorisation reads, the limitations in words, and the dates it is issued and ends. The person can be a WingsPath account or a visiting inspector with no login. The licence is recorded as sighted: its type, number and expiry, typed in from what the organisation saw, because the licence belongs to the engineer and not to the organisation.
Expiry is read from the date, so a lapsed person never shows as authorised, even if nobody has opened their line. The top of the page counts the people in force and those expiring within 30 days. A suspension is reversible and needs a reason. A revocation is final and needs a reason, and a new authorisation is a new line with a new number.
Every add, change, suspension, reinstatement and revocation is saved with who, when and what changed. The licence number is masked in that history. Ending an authorisation keeps the line, because the line is the answer to the question of who was authorised on a given date.
The register records what your organisation sighted. It is not linked to the person's own licence file, which is theirs and goes with them if they leave.
Anyone with the AMO or engineer role can read the register. Only an organisation admin who holds the module can add, change, suspend or revoke.
Each organisation's records are separated in the database itself, not just hidden on screen, and every change is audited.
We set up maintenance organisations individually while the module grows. Tell us your approval, your certifying staff and your scope, and we will bring the register in with you.