Onboarding of Personnel in Platform
Offshore platform personnel onboarding verifies medical fitness, competency, certification, and induction before anyone mobilizes, and keeps persons-on-board visibility current once they arrive. Kissflow runs that verification chain as a governed application alongside your existing systems.
Trusted by energy operators worldwide
Nobody boards a helicopter on an assumption
Getting a person onto an offshore platform means proving several unrelated things at once: that their medical is current, that their survival and escape training has not expired, that their competency matches the job they are flying out to do, that the induction has been delivered, and that there is a bed. Each of those lives with a different owner, and most of them are tracked in a spreadsheet that one person maintains. A certificate that expired three days ago is not a paperwork problem when the person is already on the aircraft.
Kissflow runs personnel onboarding as a governed application. Each mobilization request collects the verifications it needs, routes each one to the owner who can confirm it, and holds the request until every gate is closed. Expiring certificates and medicals surface before the mobilization date rather than at the heliport. Persons-on-board numbers stay current because arrivals and departures update the same record the clearance ran through.
Contractor personnel run through the same gates as your own, under your standard. The clearance record is assembled as the work happens, so when a regulator or an audit asks who was on the platform on a given date and what cleared them, the answer is a report.
Verifications live in separate places
Medical, training, competency, and induction are each tracked by a different owner in a different file, and nobody holds the combined view until someone assembles it.
Expiries are found at the heliport
A certificate that lapsed last week is discovered at check-in, when the alternative to flying is an empty seat and a delayed job.
Contractor personnel follow a different path
Contractor crews are cleared over email against documents sent as attachments, with no consistent record that the same gates were applied.
Persons on board is reconciled by hand
Arrivals, departures, and back-to-back rotations are tracked separately from clearance, so the two views disagree at exactly the wrong moment.
Six process modules
Every module ships with default gates, verification rules, expiry alerts, and dashboards. Configure each one to your mobilization standard in the visual builder.
Mobilization request
A structured request that names the person, the platform, the rotation, and the job to be performed, and derives the verification gates that role and location require.
Medical and fitness verification
Fitness-to-work and medical certificates collected, verified against the required standard, and held with expiry dates that drive alerts before the mobilization date.
Certification and competency
Survival, escape, and trade certifications verified against the job being mobilized for, with competency records held per person and per role.
Induction and briefing record
Platform induction, safety briefing, and acknowledgement captured and retained against the person, with coverage visible before travel.
Travel and manifest readiness
Clearance status feeding travel and manifest readiness, so a person is only booked once every gate is closed.
Persons-on-board register
A live record of who is on the platform, on which rotation, cleared against which verifications, retained with a timestamped audit trail.
From request to system of record in four steps
Submit
A supervisor or contractor coordinator raises the mobilization request naming the person, platform, rotation, and job, and the form derives the verification gates that role requires.
Review
Medical, training, competency, and induction gates each route to the owner who can confirm them, running in parallel rather than in sequence, with expiring documents flagged before the travel date.
Approve
Clearance is granted only when every gate is closed, and any exception is authorized explicitly by a named approver rather than waved through at the heliport.
Record
The cleared person is written to the persons-on-board register against the platform and rotation, with the full verification chain retained for audit.
What changes when platform onboarding runs on Kissflow
| Process | Before Kissflow | On Kissflow |
|---|---|---|
| Verification gates | Tracked separately by four different owners | Derived from the role and routed in parallel |
| Expiry management | Discovered at check-in | Alerted ahead of the mobilization date |
| Contractor personnel | Cleared over email against attachments | Run through the same gates under your standard |
| Exceptions | Waved through under time pressure | Authorized explicitly by a named approver on record |
| Persons on board | Reconciled by hand against a separate list | Updated from the same record the clearance ran through |
| Assurance record | Assembled when a regulator asks | Generated as each verification is confirmed |
Connects to the systems your operation already runs on
.svg){kind=logo}
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
.svg)
Built for how offshore mobilization actually runs
Every gate in one request
Medical, training, competency, and induction run as parallel gates on a single request instead of four separate chases.
Expiries surface before travel
Certificate and medical expiry dates drive alerts against the mobilization date, not against the day someone happens to check.
Contractors under your standard
Contractor personnel clear the same gates as your own crews, with the same record behind them.
An assurance layer, not another HR system
Your HR and competency systems hold the record. Kissflow runs the verification and clearance workflow that feeds them.
Governed from day one
Single sign-on, role-based access, and a timestamped audit log are how the app is built. Kissflow runs in the business-process layer, segmented from the OT and control network.
Live in weeks, not a program
Configure in the visual builder, or describe the standard and let the AI Builder generate the app. Delivery moves from weeks to days.
Related apps
Contractor management and assurance
Verify prequalification, certification, and competency before mobilization, with expiry tracking on every record.
Safety induction completion log
Schedule inductions, capture attendance and acknowledgement, and report coverage by crew and contractor.
Training compliance register
Hold the training and competency record per person and per role, with renewal alerts before expiry.
We help offshore operations and HSE leaders clear people before they travel, not at the gate
.gif)
“If a company cannot enable everybody to use AI, they will never get the true benefit of AI. Platforms like Kissflow allow us to put that capability in the hands of our users in a safe way.”
Vagesh Dave
GVP & CIO at McDermott International, Ltd
See The Full Story
“Advanced automation of all processes is easy to set up. I cannot imagine how to manage workflows without this software.”
Tanay Tiwary
Global Head - Digitalization & Business Improvement
See the Full Story
“Kissflow supports rapid application development by building a working application prototype in the shortest amount of time.”
Maria Theresa Cabigon
CIO, SN Aboitiz Power Group
See The Full Story
See what Kissflow can do for you
Talk to usGot questions? We're here to help.
Get SupportIt onboards personnel to an offshore platform or installation: the medical, training, competency, induction, and travel gates a person must clear before mobilizing, and the persons-on-board record once they arrive. It is not a software account provisioning tool.
No. Kissflow runs the verification and clearance workflow alongside your HR, training, and competency systems, connecting through APIs and integration connectors. Those systems remain the record.
Yes. Contractor crews clear the same gates under your standard, with the same verification record retained, rather than being cleared over email against emailed attachments.
Expiry dates are held against each verification and alert against the planned mobilization date, so a lapsing medical or survival certificate surfaces while there is still time to renew it.
Yes. Fields, categories, routing rules, and escalation thresholds are configured by the process owner in the visual builder, and every change is written to the same audit log as a manual edit.
No. Kissflow runs in the business-process layer alongside the systems you already own and connects to them through APIs and integration connectors. It does not replace your EHS suite, your ERP, or your maintenance system, and it does not operate inside the control system.
No. Kissflow AI maps natural language to platform metadata and produces an inspectable blueprint, so every app is auditable and the process owner can maintain it.
Kissflow is certified to SOC 1, SOC 2, SOC 3, ISO/IEC 27001, HIPAA, GDPR, and CCPA, hosted on Google Cloud with data residency in the US, EU, APAC, and Oceania.
