Licences and certifications

A position can require specific classes, and the required classes may be spread across several credentials, because some jurisdictions issue them separately.

Rules that are easy to get wrong

• Validity is computed from the expiry date on every read, never trusted from a stored status. A register that is a day stale is a register that is wrong.
• Suspended and revoked are unusable however far off the expiry is. Pending is an application, not a qualification.
• A credential type that does not expire ignores any date on the record. A degree does not lapse, and a stray value must not disqualify somebody years later.
• Expiring is a warning, not a failure. The holder is still qualified; the point is that a renewal often needs a test booked weeks ahead.
• A credential awaiting verification is flagged but still usable. The credential is real; the gap is in the organisation's record-keeping, and blocking would punish the holder for it.
• Advisory requirements never make somebody non-compliant. A register where everything is red is a register nobody reads.
• Where several credentials of one type exist, the best usable one decides — not the newest, which would fail somebody whose replacement is pending while their existing licence is still valid.
• A class the type does not list is recorded and reported, not refused. The vocabulary belongs to the issuing authority, and an organisation's list will lag it.

Verification

Verifying sets the date and the verifier from the session, never from the submitted form: the point is that a named person attests to having seen the original. Credentials are personal data, so a line manager does not see their report's licence number, and there is deliberately no way for the holder to edit their own expiry date — that would make the register self-certified.