A crew change day on any offshore installation moves more people than any other shift in the rota. Flights get rebooked for weather. A contractor's induction lapses the day before mobilisation. A cabin gets reassigned because a berth is needed for a specialist coming out for a short campaign. Each of these is routine. The problem is what happens when the person on board register doesn't move with them.
The POB count isn't an administrative tally kept for catering and logistics, though it does that job too. It's the number the OIM relies on to know who needs to be accounted for if the alarm goes. Getting it right, continuously, not just at the start of shift, is a site safety requirement with teeth.
The POB count underpins emergency response, not just headcount
Under PFEER 1995, the duty holder has to be able to establish who is on the installation and account for them during an emergency, including at muster and in the temporary refuge. That means the register has to reflect reality at the moment it's needed, not the plan from that morning's briefing. If a visitor boarded on an unscheduled seat, or someone due to leave on the morning flight is still on the installation because of a helideck delay, the muster list has to catch that immediately, not after someone notices a face that shouldn't be there.
TR capacity is finite. Accommodation and muster station capacity are both built around a maximum POB figure written into the safety case. A tracker that's slow to reconcile arrivals and departures can quietly push the actual number on board above what the emergency response plan assumes, without anyone deciding that should happen.
Separate systems create the gap
On many assets, rotas, flight manifests, accommodation bookings and competency records sit in different systems, sometimes different departments entirely. Logistics owns the flight manifest. HR or the rota planner owns who's due out. Accommodation is booked separately, often by a camp boss working from a spreadsheet. Competency and training records usually sit with a different administrator again, particularly where contractors from multiple companies are involved.
Each system can be accurate on its own and the combined picture can still be wrong. A late flight change updates the manifest but not the rota. A contractor completes an unplanned night shift and the accommodation system still shows the bed as vacant from midday. None of these are dramatic failures individually. Reconciled by hand, at pace, on a busy crew change day, they're where gaps open up.
Competency has to travel with the person, not the rota slot
A person's presence on the installation and their verified competency to do the work they're there for are two separate checks, and both need to hold at the point they accept a permit, not just at induction. Where the POB tracker and the competency record are separate, someone can technically be on board and accepted onto a permit before anyone has confirmed their site-specific induction or discipline training is actually current. We've written before about the competency gap in contractor permit management, and it's worth asking the same question in reverse: does your POB record know, in real time, whose competency has lapsed while they're still sitting in the accommodation block?
Accommodation assignment follows the same logic
Cabin allocation is often treated as a hospitality function, separate from safety systems. But cabin occupancy is one of the cross-checks used to verify a muster count against who's physically on the installation. If the accommodation system and the POB tracker aren't the same record, or aren't kept in step, the duty holder loses one of the practical ways of confirming the number the emergency response plan is built around. A cabin swap made informally after boarding, without updating the master record, is a small administrative shortcut with a safety consequence attached.
What to check if your tracker isn't a single source
A few practical tests are worth running against whatever system currently manages POB, rather than taking the vendor's or the planner's word for it:
- Does a flight rebooking update the POB register automatically, or does someone have to key it in separately
- If a contractor's induction or training expires while they're on the installation, does that flag against their record, or only at the point they next try to board
- Can the OIM or duty holder pull a live, cross-referenced list of who's on board, where they're accommodated, and whether their competency is current, during a drill rather than after it
- If someone's cabin is reassigned after arrival, is that visible in the master record within the same shift, or does it wait for the next admin update
The same discipline applies to shift handover more broadly. Our post on shift handover protocols that keep SIMOPS safe covers some of the same ground from the permit side, and the OIM's visibility over who's actually present is closely tied to the authority they hold under the OIM security guidelines.
If you're looking at how POB, competency and accommodation data are currently reconciled on your asset, it's worth mapping where the handoffs between systems actually happen, and where someone is relying on a phone call or a printed list to close the gap. That mapping exercise tends to surface the risk on its own, before any system change is on the table.