Most serious incidents on industrial sites involve contractors. Not because contractors are less competent than direct employees, but because the systems designed to keep them safe often assume a level of integration and oversight that does not exist in practice.
A principal contractor managing several specialist subcontractors on a live industrial site is responsible for the safety of people whose competence they did not assess, whose procedures they did not write, and whose interpretation of adequate controls they cannot always verify. That is a significant responsibility, and the systems required to discharge it properly are more demanding than most contractor management frameworks acknowledge.
The multi-contractor problem
The risk on a multi-contractor site is not the presence of individual contractors — it is the interaction between them. Two contractors working in adjacent areas, each with their own permit, each following their own procedure, may create a combined hazard that neither has assessed individually. One contractor's isolation may affect another contractor's safe working assumptions. One contractor's hot work may create an ignition source in an area where a second contractor is handling flammable materials.
These interactions do not appear in individual risk assessments. They only become visible when someone has a complete, consolidated view of all work in progress across the site at the same time. On a paper-based or fragmented permit system, that view does not exist. Each contractor's work is controlled in isolation — which is precisely the problem.
Competency — the assumption that causes incidents
The most dangerous assumption in contractor safety management is that a contractor's presence on site implies their competence for the work they are about to carry out. In practice, competency verification for contractors is one of the most consistently undermanaged elements of any site safety system.
A contractor arrives with a CSCS card, an induction certificate, and a method statement. The principal contractor accepts these as evidence of competency and issues a permit. But the CSCS card covers general site safety, not the specific task. The induction covers the site rules, not the hazards of the specific work area. And the method statement describes what the contractor intends to do, not whether the person doing it has the demonstrated capability to do it safely.
For safety critical tasks — electrical isolation, confined space entry, hot work, work on pressure systems — the competency requirement is specific. The person carrying out the work must be able to demonstrate that they have been assessed as competent for that specific activity, not just for the general category of work. A permit to work system that does not enforce this check at the point of permit issue is carrying a risk that no amount of induction or paperwork can close.
The isolation conflict problem
On a site where multiple contractors are working simultaneously, isolation management is the highest-risk coordination challenge. Each contractor's work scope may require isolations. Those isolations may interact — one contractor's isolation may be the energy source that a second contractor's operatives are depending on, without either party being aware.
A principal contractor who cannot see, in real time, all active isolations across the site cannot identify these conflicts before they become incidents. They can only discover them afterwards — in an investigation report.
The solution is not more meetings or more briefings. It is a single point of authority for isolation management, supported by a system that makes every active isolation visible to everyone who needs to see it. The principal contractor's permit to work system must be the controlling system — not one of several operating in parallel.
Handover between contractors and shifts
On sites where work runs across multiple shifts and multiple contractor teams, handover is the moment when contractor safety information is most at risk of being lost. A permit that was live at the end of one shift, held by a contractor who has gone off site, needs to be formally suspended and the isolation status confirmed before the incoming team can understand the current state of the plant.
In practice, contractor handover is rarely given the same rigour as direct employee handover. The outgoing contractor team departs. The incoming team arrives. The permit status is communicated verbally, if at all. The incoming supervisor has no reliable way to verify what is currently isolated, what work is in progress, and what the safe working conditions are for the areas they are about to supervise.
A permit to work system that treats contractor permits with the same visibility and handover requirements as directly employed operatives closes this gap. The incoming team can see every active permit — contractor or direct — and the current status of every isolation, without depending on a verbal brief that may be incomplete.
What a contractor safety audit looks for
When regulators or major clients conduct contractor safety management audits, the questions are specific and consistent:
- How do you verify that contractors carrying out safety critical tasks are competent for those specific tasks before issuing a permit?
- Can you show a consolidated view of all active contractor permits on the site right now?
- How do you identify and manage conflicts between overlapping contractor work scopes?
- What happens to a contractor's permit and their isolations when they leave site at the end of a shift?
- If a contractor incident occurred today, could you demonstrate from your records what the contractor had been authorised to do, what competency checks had been completed, and what the permit status was at the time?
If any of those questions require significant preparation to answer, the contractor safety management system is not providing the level of control the site requires.
A practical self-assessment
These questions will give you an honest read of where your contractor safety arrangements stand:
- Is there a single system that shows all active contractor permits on the site simultaneously?
- Are competency requirements for safety critical tasks enforced at the point of permit issue, or checked manually and inconsistently?
- When a contractor leaves site, is their permit formally suspended and their isolation status confirmed before they go?
- Do your contractors use your permit to work system, or their own?
- Can you identify, right now, whether any active contractor isolations could conflict with other work in progress on the site?
If the honest answer to any of these involves uncertainty, the gap between your documented contractor safety system and what is happening on the ground is where the risk is accumulating.
Elisian's platform gives principal contractors and site operators a single, consolidated view of all active permits and isolations across a site — regardless of whether the work is being carried out by direct employees or contractors. Competency requirements are enforced within the permit workflow, contractor handover is structured and recorded, and the isolation register reflects the current state of the site in real time. If you want to see how that works for a complex, multi-contractor operation, get in touch.