An operator running assets in the Gulf of Mexico, the North Sea and off Western Australia under one corporate safety management system still has to answer three different questions about who is on board and why. BSEE wants evidence that the Safety and Environmental Management System tracks personnel accurately enough to support evacuation decisions. The UK's safety case regime wants headcount and muster arrangements that match stated maximum POB and lifeboat capacity. NOPSEMA wants a safety case that demonstrates the workforce's competency has been verified against the specific hazards of that installation. Same vessel class, same contractor pool in some cases, three separate compliance narratives.
Most published material on safe manning picks one of these regimes and writes as if it's the only one that matters. For operators or marine contractors moving assets, personnel or safety case templates across regions, that's not much use. The practical question is narrower: what actually differs between these regimes, and how much of a single internal process can survive the move from one to another.
What does multi-jurisdiction offshore manning compliance actually involve
Multi-jurisdiction offshore manning compliance means maintaining accurate, verifiable records of who is on an asset, their competency status and emergency response role, in a form that satisfies each regulator's own documentation and reporting expectations, rather than assuming one jurisdiction's paperwork will transfer directly to another.
How BSEE frames the question in the US Gulf
BSEE's approach sits inside the Safety and Environmental Management System framework, built on API RP 75. The emphasis is less on a fixed manning number and more on whether the operator can account for everyone on the installation at any point, particularly during a hurricane evacuation or an incident response. Accurate POB reporting to BSEE during storm events is a well established expectation, and the SEMS audit process looks at whether personnel tracking, training records and job safety analyses are actually being followed rather than just documented. There isn't a single BSEE "manning certificate" equivalent to a marine safe manning document. The obligation is distributed across SEMS elements: hazard analysis, training, and the operator's own procedures for verifying who is authorised to be on the asset and competent for their role.
How the UK safety case regime treats POB and manning
In the UK, safe manning in the maritime sense (a Safe Manning Document issued under flag state rules, tied to STCW) applies to the vessel, not the installation, and is an MCA matter. Offshore installation manning sits instead inside the Safety Case Regulations 2015 and PFEER 1995, which require the duty holder to demonstrate that evacuation, escape and rescue arrangements, including lifeboat and TEMPSC capacity, actually match the maximum number of people who could be on board. OEUK (formerly OGUK) publishes guidance that operators widely use to benchmark workforce and competency practice, but that guidance isn't itself the statutory requirement, it supports how duty holders meet SCR 2015 and PFEER obligations. Conflating OEUK guidance with the legal requirement is a common simplification, and one worth correcting internally before it ends up in a compliance manual.
How NOPSEMA assesses workforce competency in Australian waters
NOPSEMA operates a similar goal setting, ALARP based safety case regime to the UK's, under the Offshore Petroleum and Greenhouse Gas Storage Act framework. Where it diverges is in how directly competency verification is expected to show up in the accepted safety case itself. NOPSEMA's acceptance process looks for the operator to have demonstrated, not just asserted, that the workforce holds the competencies the hazard analysis says the role requires, and that this is checked on an ongoing basis rather than at induction only. For a contractor workforce moving between UK and Australian assets, this often means the underlying competency evidence is similar but the way it has to be presented and justified in the accepted document is not.
Where the regimes converge and where they genuinely diverge
All three regimes share the same underlying assumption: an accurate, current account of who is on an asset and what they're competent to do is foundational to emergency response, and none of them will accept a system that can't produce that picture in real time. Where they diverge is in what evidence satisfies the regulator and how often it has to be produced. BSEE is oriented around demonstrated incident response capability and SEMS audit findings. The UK is oriented around a written, periodically revalidated safety case with specific emergency response performance standards. NOPSEMA sits closer to the UK model but places more weight on the safety case itself carrying the competency justification, not a supporting document referenced from it.
For an operations or HSE lead managing a mixed fleet, the practical risk isn't usually a gap in any single regime's requirements. It's that a record built to satisfy one regulator's expectations gets assumed adequate for another, and the gap only becomes visible when an inspector or auditor asks a question the record wasn't designed to answer.
Building one internal process that flexes across regimes
Running three entirely separate regional POB and competency systems is rarely the answer, not least because it multiplies the places a contractor's certification can go stale unnoticed. A more workable approach is a single underlying data model, covering who is on board, their training and certification status, and their assigned emergency response role, with the reporting layer built to generate whatever output each regime expects from that same record. BSEE's SEMS audit wants to see the underlying process; the UK safety case wants defined roles against PFEER's emergency response standards; NOPSEMA wants the competency justification embedded in the accepted document.
What this takes in practice is treating POB and competency as one dataset rather than three separate registers, so the muster list, the training matrix and the contractor onboarding record don't drift apart the moment an asset moves jurisdiction. We've written before about why a person on board tracker matters offshore in a single asset context, and the same underlying discipline, accurate real time POB tied to verified competency, is what carries across jurisdictions, even as the reporting format around it has to change. The contractor side of this is usually where the gaps show first, particularly on assets running a high proportion of transient or short term contractor personnel, which is also where closing the competency gap on critical equipment becomes a live operational question rather than a documentation exercise.
If you're assessing how your current POB and competency process would hold up across more than one regulatory regime, we can walk through the existing workflow with your operations team and identify where a single underlying record, rather than three parallel ones, would actually reduce the work.