Helicopter Contracting: You're Employing a Contractor, Not Adopting a Child.
You've finally chosen a contractor!
They've got the certificates, submitted all the forms, proved their training, demonstrated their competency and produced a health and safety system
endorsed by international standards. You've spoken to their referees and had several rounds of coffee with their team.
You're 110% confident they've got the people, equipment and expertise to do the job your own team can't do, or doesn't have the capacity to do.
Yay!

Now, let's tell them how to run their business.
Because apparently, after all that checking, we still don't trust them to do the job we hired them for.
Welcome to helicopter contracting.
First, we'll give them our contractor handbook. It's only 86 pages, but don't worry, most of it won't apply to the work they're doing. Then we'll need them to rewrite their risk assessments into our templates, attend our meetings, complete our inductions and demonstrate that their workers have been trained in our procedures.
We'll approve their work plans, review their competency records and decide whether their internal processes meet our expectations.
And if something goes wrong? They'll need to complete an incident report for their own system, another for ours, and a third for the main client. Because apparently one incident needs three different versions of the same story. God help us if it needs investigating. That's three more layers of complexity nobody needs, with everyone wanting their own forms, findings and corrective actions.
And if the contractor already has perfectly good systems for doing all of this?
That's lovely. But we need them to use ours.
Before long, the contractor has abandoned their own systems and is operating under ours. We've effectively turned them into third-party labour hire rather than the capable, independent contractor we went to so much trouble to hire in the first place.
And we're calling this good contractor management.
How did we get here?
I don't think most businesses deliberately set out to interfere in their contractors' operations. Nor do I think most H&S people are consciously trying to take control.
In fact, I think most genuinely believe they're doing the right thing.
We've spent years talking about overlapping duties, due diligence, contractor management and the consequences of getting it wrong. Unfortunately, somewhere in those conversations, the fear of prosecution has become louder than the discussion about managing risk.
What if something goes wrong? What if we didn't check enough? What if we're held responsible for something the contractor did?
So we add another requirement. Another approval. Another document to demonstrate that we've done our bit. And because nobody wants to be the person who recommended doing less, the requirements keep growing.
The result is an extraordinary amount of time and effort spent managing the fear of what might happen, rather than the risks associated with the work itself.
Whose job is it anyway?
Contracting work doesn't magically remove a business's health and safety responsibilities. Where duties overlap, businesses need to consult, cooperate and coordinate. And the extent of each business's responsibility reflects the influence and control it has over the work.

Let me repeat that.
Responsibility reflects the influence and control a business has over the work.
Sounds sensible - one could almost say (gulp) common-sense?
If a contractor is working around your people, your plant or your operations, you need to understand the risks to your people and to their people and make sure there are arrangements to manage those risks. But that doesn't mean you automatically need to manage the contractor's entire business.
There's a difference between agreeing how people and machinery will be separated on a shared worksite and telling a contractor how to run their internal training programme. Between checking that an operator is competent and insisting that competency must be assessed using your preferred form.
And there's a difference between making sure critical controls are working and approving every procedure a contractor has ever written.
One is managing the risks associated with the work.
The other is getting rather involved in someone else's business.
All care. No responsibility.
Here's where things get particularly interesting.
Some principals want to specify exactly how contractors must carry out their work. They dictate procedures, impose additional training requirements, approve work methods and reserve the right to intervene whenever something doesn't meet their expectations. Then they include a clause in the contract making it very clear that the contractor is entirely responsible for their own health and safety.
Righto.
Except you can't contract out of your legal duties. And the influence and control you exercise over work matters when considering those duties. That doesn't mean giving a contractor instructions automatically makes you responsible for everything they do. But it does raise an interesting question.
If you're so concerned about liability, why are you so keen to take control of someone else's work?
There is a certain irony in trying to protect yourself from prosecution by increasing your involvement in activities you engaged another business to manage. Especially when that involvement has little to do with controlling the risks that matter.
More paperwork. Same risks.
None of this is an argument for leaving contractors to their own devices. It's an argument for being clear about what you're trying to achieve.
If the work involves mobile plant operating alongside pedestrians, I want to know how those interactions will be managed. If someone is entering a confined space, I want confidence that the hazards have been identified, the controls are appropriate and the people doing the work know what they're doing. If a contractor is working alongside another contractor, I want to know they've sorted out where their activities might affect each other.
What I don't particularly care about is whether their risk assessment has two columns or eight, whether their toolbox meeting minutes are recorded on my preferred template, or whether their internal training matrix looks like mine. Unless there's a genuine reason those things matter to the work, what exactly are we achieving by insisting on them?
We can spend an extraordinary amount of time checking documents without ever checking whether the controls described in those documents are working.
And reviewing a contractor's entire H&S management system simply because they're a contractor?
That's another article altogether.

Let contractors be contractors.
If you've gone to all the trouble of finding a competent contractor, checking their credentials and convincing yourself they're the right people for the job, perhaps you could give them a little room to get on and get the work done.
You're employing a contractor. Not adopting a child.
Maybe stop checking their homework and start paying attention to all work.







Comments