Contract versus permanent in a tightening energy market

Ask most engineering directors how they split contract and permanent hiring and you will get a version of the same answer: permanent for the enduring core, contract for the project peaks. It is a good rule. The difficulty is that in the current UK energy and infrastructure market, the peaks have stopped behaving like peaks. Programmes overlap, sanction dates move, and a twelve-week spike has a habit of becoming a two-year commitment.

That makes the contract-versus-permanent question less a matter of principle and more a matter of getting the shape of demand right before you commit to an employment model.

Start with the shape of the work, not the role

The most common error is deciding employment model at role level. A lead planner is not inherently permanent or contract. What matters is whether the work behind the role is enduring, cyclical or genuinely finite.

• Enduring work — asset management, engineering standards, safety case ownership, client-side technical authority. Hire permanent. The knowledge compounds and losing it is expensive.
• Cyclical work — turnarounds, outage seasons, AMP-driven delivery peaks, campaign-based commissioning. Build a returning contract population you can call on repeatedly.
• Finite work — a single hook-up, a discrete design package, an HVDC converter station scope, a one-off migration. Contract, or hand the whole scope to a managed team.

Once you classify the work honestly, most of the argument disappears. The awkward cases are the ones where a business wants permanent stability but cannot commit permanent funding — and those tend to resolve into a managed-service or fixed-term arrangement rather than a straight choice.

The real cost comparison is rarely done properly

Day rate against salary is not a like-for-like comparison, and organisations that compare them directly usually reach the wrong conclusion twice over — first deciding contract looks expensive, then discovering permanent hiring in a scarce discipline carries costs of its own.

A fair comparison includes employer NICs, pension, holiday, sick pay, training and certification renewal, equipment, notice risk and the cost of the vacancy period on the permanent side. On the contract side it includes rate, agency margin, the administrative cost of status determination and compliance, and the exposure created if the person leaves mid-scope. Add utilisation to both. A permanent engineer at seventy per cent utilisation on chargeable work is a very different proposition to a contractor billing only when deployed.

Contract capacity is not more expensive than permanent capacity. It is differently expensive — and it is priced for speed and reversibility, which are exactly the things a volatile project pipeline needs.

What has actually tightened

Three things have changed the calculation in the last couple of years. First, competition has broadened. Offshore wind, nuclear, grid reinforcement, water, hydrogen and data centre construction are drawing on overlapping pools, and a commissioning engineer or an HV authorised person has more genuinely attractive options than they did.

Second, off-payroll compliance has made some clients cautious about contract engagement in a way that has, in places, reduced supply. Blanket inside-IR35 determinations pushed a proportion of experienced contractors towards other clients or towards permanent roles, and the ones who stayed priced the change in.

Third, the workforce demographic is genuinely tilted. A significant share of the deep technical population in oil and gas, nuclear and utilities is late-career. That is not a reason for alarm, but it does mean succession and knowledge transfer belong in the resourcing conversation rather than in a separate HR workstream.

A practical way to set the balance

For most clients we work with, a workable pattern looks like this. Hold a permanent core sized to the work you are confident of doing in any plausible scenario, not to the work you hope to win. Maintain a flexible contract layer, ideally with people who have worked with you before and can be re-mobilised quickly. Then use managed scopes for work that is genuinely separable — where you would rather buy an outcome than supervise a set of individuals.

• Review the split every quarter against the live project pipeline, not annually against budget.
• Track how often contract engagements are extended. Repeated extension is a signal that the work was enduring all along.
• Keep leavers warm. Returning contractors mobilise faster and carry your standards with them.
• Decide status determination policy deliberately, and apply it role by role rather than as a blanket position.

Getting this right is not about picking a side. It is about making sure the employment model matches the shape of the work — and revisiting that judgement often enough that it stays true.