Read by the engine.
Watched to the day.
Upload a certificate and the engine reads it — type, number, holder, expiry. A person verifies it. Then every expiry is watched against the rotation, so renewals land on leave, not on charter.
seen
Certificate matrix
M/Y Aurelia · 16 crew · every expiry, one grid
Expiry dates don’t care
about your charter calendar.
Renew on leave, not on charter
The engine lays each expiry over the crew member’s rotation and picks the leave window before it.
AI on watch. People decide.
The engine flags what looks wrong. It never changes a record, never marks anything valid and never books anything on its own.
This ENG1 reads issued 14 Jun 2024, expires 14 Jun 2027. ENG1 medicals run two years, not three — the expiry may be a typo on the certificate. Worth checking the original before relying on it.
Three states. No grey areas.
Every cell in the matrix is one of three things — and only a person can move it to the first.
Every head of department sees every qualification. Three roles verify them.
All qualifications are visible to all heads of department. The Certification Officer, Purser and Captain verify the certificates, and receive an OK-to-sail audit of the certificates every day. Every verification is on record — who, when, against which upload.