Is this person verified, screened and certificated to join?
That is the only question Flarion answers for crew, and it answers it per person and per vessel. Identity verified from a link on their phone, the name screened and rescreened weekly, the certificates the position requires held with their expiry dates, and a readiness position your managers can read at a glance.
Élodie MarchandChief Stewardess · M/Y Sarnia · French
- Identity
- Verified · passport, liveness, face match
- Screening
- Clear · rescreened 22 Sept
- Certificates
- 4 of 4 held · ENG1 expires Mar 2027
Élodie MarchandChief StewardessReady
Marco FerreiraBosunReady
Anja NilsenDeckhandExpiringFlarion is not a crew management system and not a CRM. It does not roster, schedule rotations, plan travel, run payroll or manage a talent pipeline. It works beside the system you already use for those and carries one job: verify the person, screen the name, hold the certificates and say whether they are ready.
Readiness, per vessel
One screen per vessel: who is aboard, who is joining, how many are verified and screened, and which certificates are missing or about to expire. A gap is a red line with a name against it, not a number in a summary.
- Identity verified from a link on the crew member's phone
- Screened on approval, rescreened weekly
- Expiring certificates surfaced before the join date
| Person | Position | Identity | Screening | Certificates |
|---|---|---|---|---|
| J. Brehaut | Second officer | Verified | Clear | STCW, ENG1 |
| A. Le Tissier | Deckhand | Verified | Clear | ENG1 expires 4 Oct |
| P. Duquemin | Engineer | Pending | Clear | STCW missing |
Certificates against the role, not in a folder
Your firm sets what each position requires. A certificate is a document on the person's file with an expiry date, and readiness is derived from what is held against what the position needs, so the answer changes the day a certificate lapses rather than the day someone notices.
- Requirements set per position by your firm
- Expiry dates tracked on the document
- Readiness derived, never typed in by hand
| Position | Required | Held | Status |
|---|---|---|---|
| Master | STCW II/2, ENG1, GMDSS | 3 of 3 | Ready |
| Second officer | STCW II/1, ENG1 | 2 of 2 | Ready |
| Engineer | STCW III/1, ENG1 | 1 of 2 | Gap |
| Deckhand | STCW basic, ENG1 | 2 of 2 | Expiring |
Requirements are set per position by your firm. A certificate is a document on the person's file with an expiry date; the readiness column is derived from what is held against what the position requires. Flarion does not roster, schedule or pay anybody.
Questions from crew managers
Is this a crew management system?
No, and it is not trying to be. Flarion verifies identity, screens the name, holds the certificates a position requires and tells you whether a person is ready to join. It does not roster, schedule, plan rotations, run payroll or hold a CRM. Keep the system you have for those and let this carry the verify-and-screen half.
How does it sit beside the system we already run?
Beside it, not underneath it. Crew are invited to Flarion by a link, complete identity and their documents there, and the readiness position is a screen your managers read. Where you want the two connected, a signed API creates invitations from your system so nobody retypes a name.
What is screened, and how often?
Every crew member is screened against a consolidated sanctions and PEP dataset when their application is approved, and rescreened with the rest of the book every week. A change raises an alert with an owner, the same as for any other name.
What does it cost for crew?
The same £5 per name per month as any other name, with the same £750 minimum. Criminal record checks, where a position needs one, are an add-on at cost plus a £100 handling fee per check, quoted before they are switched on.
Bring one vessel's crew list.
We load it, verify and screen the names, and show you the readiness board for that vessel.