The project team that mobilised, and the plant that never stopped: HR for energy and utilities

A commissioning engineer finished a site, was demobilised, and spent three weeks at home waiting for word. None came. They assumed the pipeline was empty, accepted an offer from a contractor, and resigned. Their manager, who had a project coming up that needed exactly their discipline, found out from the resignation letter. The project mobilised with an external hire who took four months to reach the departed engineer's level of site knowledge. Nobody had told the engineer there was a next project, because nobody in the business held a view across projects of who was rolling off and where they were needed.

Energy and utilities businesses run two organisations under one name: a project organisation that forms, delivers and disbands, and an operations organisation that must never stop. They need different HR processes, share people constantly, and fail at the boundary between them, which is exactly where the engineer was standing.

PROJECTS         mobilise by discipline and phase; site and camp
                 allowances; rotation; demobilise to redeploy
OPERATIONS       continuous shifts; authorisation-gated roles;
                 control room; cover cannot lapse
SHARED           the employee master; competency records;
                 safety system; the people who move between

The handover point between project and operations
- commissioning to running - is where structure,
records and people all change hands. Define it.

The structural decision that prevents most of the confusion is defining, in writing, the handover point between project and operations: at what stage a commissioned asset becomes an operated one, which organisation's reporting lines apply on either side, who holds authority for what during the transition, and how competency and authorisation records travel across it. That is organisation design work with a specific sector shape, and businesses that have not done it find the same disputes recurring at every commissioning.

In project-based work a meaningful share of resignations are people who assumed there was no next project because nobody told them there was. The counter is a redeployment view held by someone: who is rolling off which project when, by discipline, and where the next requirements are. Checked before every demobilisation, it converts a release into a planned move and it costs almost nothing. The engineer in the opening would have been told, at demobilisation, that there was a site coming up that wanted them, and they would have waited. The succession and leadership development conversation in a project business is largely this: a visible pipeline, so people do not conclude the work has ended.

1. 1

   Hold one view across projects

   Roll-offs by discipline and date; requirements by discipline and date. A spreadsheet maintained by one named person is enough to start.

2. 2

   Check it before every demobilisation

   And tell the person what it says, even when the answer is 'nothing yet, we will call by this date'.

3. 3

   Fund the short gap for people you want to keep

   Two weeks of bench for a commissioning engineer is cheaper than four months of an external hire's ramp.

4. 4

   Treat project-to-operations moves as career moves

   An engineer who commissioned a plant is the best-informed operator it will ever have. Make that route explicit.

In operations, the question that matters is not who is employed but who is authorised, to operate this plant, isolate that circuit, enter that space, and whether every shift has someone authorised for every task it might need. That makes competency and authorisation the core HR record in the sector: held per individual, with expiry tracked and alerted in advance, and, this is the step that changes behaviour, validated against the roster, so that a person whose authorisation has lapsed cannot be scheduled for the work that requires it. Where the record and the roster are separate, the lapse is discovered on the shift. Where they are connected, it is discovered sixty days before, by the system, and renewed.

• Competency and authorisation per person, with expiry. This is the record, and everything else, training, progression, rostering, hangs off it.
• Roster validated against authorisation. The control that turns the record from paperwork into a safeguard.
• Contractor competency held alongside own staff. A contractor's electrician on your site is authorised by your record or not at all.
• Progression defined by authorisation level, not tenure. It is the most objective ladder in any sector and the one that gets left implicit.

The single exit that most directly threatens continuity in operations is the shift in-charge or control-room lead, and it is the role where readiness takes longest to build, because it is gated by authorisation and by judgement that only comes from time on the plant. Naming successors, starting their authorisation path before the vacancy exists, and building supervisory capability before the appointment rather than after is the difference between a planned handover and a shift run by whoever is available. It deserves its own line in any succession plan the business keeps, separate from the management roles that fill such plans.

Energy sector pay carries layers, base by role, competency and authorisation premiums, shift and night allowances, site and remoteness allowances for project locations, and the recurring monthly dispute is about allowances rather than base. Assembling payroll inputs from the roster and the authorisation record, rather than from a separate collection exercise, removes most of it: a person's allowances follow from where the roster placed them and what authorisation they held. The compensation and rewards strategy question underneath is whether the authorisation premium is transparent enough that people can see what the next level pays, which is what makes the authorisation ladder a career rather than a compliance record.

Project staff at remote sites and shift staff in a control room have almost nothing in common in how they experience the business, and one engagement approach serves neither. Project teams care about rotation and leave predictability, camp conditions, family contact and, above all, visibility of the next project. Shift teams care about roster fairness and advance publication, night-shift facilities, progression through authorisation levels and a voice in operational decisions. Roster predictability is the one issue raised by both, and it is the cheapest to fix, because it is a publication discipline rather than a cost.

Everything in this article sits on the same foundation: one employee master shared by both organisations, a competency record that is the sector's real HR record, and a defined handover point between projects and operations. Building those, and the redeployment view that would have kept the engineer, is what HR for energy and utilities work involves. A business that has them runs commissioning handovers without the recurring disputes, rosters that cannot schedule a lapsed authorisation, and demobilisations that end in a conversation about the next project, which is where energy sector HR work starts, because it is the loss that is easiest to see and cheapest to stop.