Type "contractor management system" into a search engine and the results split into two quite different products on the same page. One group is built around prequalification, RAMS review, site induction and competency records, the controls an operator needs in place before a contractor sets foot on an asset. The other is built around onboarding a contractor workforce, paying them correctly across jurisdictions, and keeping HR paperwork current. Both call themselves contractor management. Only one has anything to do with keeping people safe on a live site.
For an HSE manager or operations lead trying to tighten up how contractors are managed on an offshore platform or onshore process plant, that overlap wastes time. It's worth being specific about which problem you're actually trying to solve before you look at a single product demo.
Two categories wearing the same name
The payroll and HR category exists because engaging contractors internationally is genuinely complicated: tax status, right to work, currency, local employment law. Those platforms do that job well. They are not designed to answer the questions a duty holder actually needs answered before a contractor starts work on a pressurised system or a confined space: has this person's RAMS been reviewed against the actual task, is their competency current for the specific permit type, and who signed off their induction to this asset.
A procurement or digitalisation lead evaluating software against the search term "contractor management system" needs to filter for that distinction early, because the two categories don't converge on any of the functionality that matters for safety case compliance.
What a safety-led contractor management process actually covers
On assets running a live permit to work system, contractor management usually needs to cover more ground than a single onboarding gate:
- Prequalification against the scope of work, including RAMS review, relevant insurance, and prior incident history where it's held
- Site-specific induction, separate from any general industry induction the contractor arrives with
- Competency and authorisation records tied to specific task types, not a single blanket "approved contractor" status
- Technical Authority or Area Authority sign-off for higher-risk work categories before a permit is issued
- Ongoing visibility during the work itself, not just at the point of entry to site
That last point is where a lot of contractor management processes quietly fall over. A contractor approved on day one of a shutdown isn't automatically still appropriately competent and authorised for a different task introduced on day eight. If the system treats approval as a one-off event rather than something that's checked at the point each permit is accepted, the gap opens exactly where the work changes.
Training records that hold up when someone asks for them
"Contractor management training" as a search term usually means something specific: can the operator demonstrate, for any given contractor on site at any given time, which competencies are current, which have lapsed, and which were never verified in the first place. HSE's guidance on permit-to-work systems (HSG250) is clear that competency and authorisation of people accepting permits is part of a functioning control of work system, not a separate HR exercise that happens once a year.
In practice this means refresher cycles need to be tracked against expiry dates, and ideally those expiry dates should actively restrict what a contractor can do rather than sitting in a spreadsheet someone checks when they remember to. A certificate that lapsed three weeks ago shouldn't still be accepted by a permit issuer simply because nobody cross-referenced it that shift.
Where this connects to permit to work
This is the point where contractor management and control of work stop being separate systems in practice, even if they're sold as separate products. If a contractor's competency record lives in one system and permit acceptance happens in another, someone has to manually check the first against the second every time a permit is raised. On a site running a high volume of concurrent permits during a turnaround, that manual check is exactly the kind of step that gets harder to sustain consistently as volume increases.
We've written before about closing the competency gap on critical equipment, and the underlying issue is the same one that shows up whenever contractor records and permit systems sit apart: the control that's supposed to stop an unqualified person accepting a permit only works if the two records are checked against each other every single time, not just when someone thinks to look.
What to check before you commit to a system
Rather than taking a vendor's word for which category their product sits in, there are a few things worth asking them to demonstrate directly:
- Show what happens when a contractor's competency record expires while they have an open permit
- Show how a Technical Authority sign-off is recorded against a specific scope of work, not a general approval
- Pull the full induction and authorisation history for a contractor who left site some months ago
- Demonstrate how the system flags a contractor attempting to accept a permit for work they aren't authorised for
If a vendor can't answer any of these without describing a manual workaround, it's a reasonable sign the product was built for a different problem. Our buyer's guide to permit to work software covers a similar set of questions in more depth if you're running a formal evaluation.
Contractor management and payroll compliance are both real problems worth solving properly. They just aren't the same problem, and an asset running concurrent permits with multiple contracting companies on site needs the safety side solved first. If you're reviewing how contractor competency currently feeds into your permit process, we're happy to work through the existing workflow and point out where the gaps actually sit.