On most offshore installations, a large share of the people actually on board at any given moment are not core crew. They are catering staff, scaffolders on a short call-out, a classification society surveyor doing an annual inspection, an auditor flown out for a day, or a specialist contractor brought in for a single task. Their records rarely sit in the same system as the directly employed workforce. That split is the most common reason a POB count and a competency record stop agreeing with each other, and it is where contractor POB verification tends to break down in practice.
What does contractor POB verification actually involve
Contractor POB verification is the process of confirming that every third-party individual counted as on board, whether a contractor, visitor, auditor or agency worker, has a valid induction, the right competency and training records, and an authorised reason to be there, before that person is added to the live headcount. Done properly, no one appears on the roster without having passed that gate first.
Where the data actually lives
A directly employed workforce usually has one competency record, held in one HR or training system, updated by one team. Contractors rarely work that way. Their training and certification records often live with the manning or labour supply agency that employs them. Their site induction might be logged in a client portal specific to that asset. Their access credential gets issued at the gangway or helideck reception, sometimes by a different team again, using whatever identification is presented on the day.
Each of those systems can be accurate on its own terms and still produce a POB entry that nobody has actually checked against competency. A badge system that issues an access card based on a name and a company affiliation has no way of knowing whether that individual's confined space training has lapsed, or whether their H2S certificate expired last month. It wasn't built to know that. It was built to control a turnstile.
The mismatch that only shows up at muster
This is where the practical risk sits, and it's a quieter one than most POB discussions acknowledge. A permit to work system might correctly require a valid competency check before issuing a permit for a specific task. But PFEER 1995 requires duty holders to maintain an effective means of accounting for everyone on the installation in an emergency, not just those currently holding an active permit. A visiting auditor who never picked up a permit, a catering relief worker between shifts, or a surveyor walking the plant with an escort can all be physically present and counted in a muster without ever having passed through the same verification gate that governs permitted work.
Where contractor and visitor data is managed separately from the core workforce platform, that gap tends to widen under pressure, during a turnaround, a vessel changeover, or whenever an agency supplies labour at short notice to cover absence. We've written before about why a person on board tracker matters offshore, and the honest version of that argument has to include the transient population, not just the names that appear on the standard manning schedule.
Pre-boarding verification gates
The operators who manage this well tend to treat boarding, not task assignment, as the control point. Before a contractor or visitor is ever logged as travelling, someone checks that the individual's induction is current, their competency record matches the role they're coming out to do, and their employer or agency has actually confirmed who is being sent. That last point matters more than it sounds. Agencies supplying short-term labour sometimes substitute personnel close to departure, and a verification gate built around a named individual is only as good as the process that catches a substitution before it reaches the helideck or gangway.
This is also where contractor permit management and the competency gap on critical equipment connects directly to POB. A permit system that checks competency at the point of issue is doing useful work, but it's checking too late if the person has already been accepted onto the asset without that same check being run.
Barring logic and a single source of truth
Practically, this means the workforce or POB platform needs to be the authority that decides whether someone can be marked as boarded, rather than a badge system or a travel booking tool making that call independently. If a contractor's certification has lapsed, or their induction has expired, the system should bar them from being added to the manifest rather than flag it as a note for someone to notice later. Alerting after the fact is better than nothing, but it still relies on someone reading the alert before the person is already offshore.
For operators evaluating platforms, a reasonable test is to ask a vendor to demonstrate what happens when a contractor's competency record expires the day before travel, and whether that block is enforced at the point of adding them to the manifest or only reported afterwards. It's also worth asking how the system handles a labour agency submitting personnel data in a different format or on a different schedule to the core HR feed, since that handoff is usually where records go stale without anyone deciding they should.
What to check before trusting the contractor count
A few questions tend to separate a genuinely single source of truth from a collection of systems that happen to agree most of the time:
- Does the platform treat badge issuance, agency data and the competency record as one linked entity, or three systems reconciled manually
- Can a visitor or auditor be added to the live POB count without a completed induction check
- What happens when an agency substitutes a worker close to departure
- Is barring enforced automatically, or does it depend on someone noticing an alert
None of this is really about the contractor population being less reliable than the core workforce. It's that the systems managing them were often built for different purposes, badge control, payroll, labour supply, and POB accuracy was never the thing any one of them was designed to guarantee. We've covered the related payroll and safety tension in contractor management systems, and the same underlying problem shows up here in a different form.
If your current POB process relies on reconciling a badge system, an agency spreadsheet and a training database after the fact, it's worth walking through where a substitution or an expired certificate would actually get caught, and at what point in the boarding process. We can work through that against your existing workflow and identify where a single verification gate would close the gap before someone is ever counted as validly on board.
Source: OEUK's Process Safety Leadership Principles: What the 2025 Strategy Means for Asset Integrity Teams