The site that lost its crew between phases: HR for a workforce that moves
Ganesh HS ·
In brief
Exits happen in waves at phase boundaries; the avoidable loss is the crew that assumed there was no next site.
Own-payroll and contractor labour must be structurally distinct in every record and every report.
Site induction is a condition of entry, and the record of it is part of how the site is run.
Redeployment visibility before demobilisation is the cheapest retention lever the sector has.
A construction firm completed the civil phase on a residential project and released the crew, as it always did. Three weeks later the finishing phase started on the same site, and the firm went looking for tilers, painters and electricians. Most of the released crew had found work elsewhere. The site started short, the finishing contractor charged a premium for speed, and the project manager described it as the nature of the trade. Nobody had told the crew, at release, that there would be work on the same site in three weeks — because nobody had asked whether anyone was going to.
Construction HR is built around a workforce that moves: between sites, between projects, between phases, and between the firm's own payroll and a contractor's. Most of what goes wrong is at the boundaries, and most of it is avoidable with records that cross them.
Phase boundaries are where people are lost
Attrition in a project business does not look like resignation. It looks like release: a phase ends, a crew is stood down, and whether they come back for the next phase, the next site or the next project depends on what they were told and what they believe. A crew told nothing assumes the work has ended and takes the next job offered. A crew told 'finishing starts here in three weeks, we want you back, here is the date' mostly waits. The difference is one conversation at demobilisation and a list that reaches whoever is mobilising the next phase — and it is the cheapest retention measure in the sector, because it costs nothing but the asking.
Demobilisation, done properly
BEFORE RELEASE redeployment checked: is there a next phase,
a next site, a next project - for whom?
AT RELEASE gate pass cancelled; tools, tackle and PPE
returned against issue; attendance reconciled
before final payment; site induction and
safety training record closed
RECORDED skill and performance note per person, by
trade; rehire eligibility; contact that works
CONTRACTOR released through the contractor, recorded
LABOUR separately, never merged into own-payroll
A site file that disperses when the site closes
has not been kept.
Own payroll and contractor labour, structurally apart
The single most consequential record design decision in construction HR is that the firm's own employees and the labour supplied through contractors are held in different structures — different records, different registers, different reports — and never merged into a single headcount. The reason is that every meaningful question has a different answer for each: who is inducted to what standard, who is paid by whom, who the firm is principal employer for, who carries which obligation. A combined figure is wrong for every purpose, and a system that holds the distinction as a note in a field rather than as structure will lose it under pressure on the first busy site.
Two registers, one site. Own staff and contractor labour both inducted, both recorded, in separate registers with the contractor named.
Two attendance flows. Own staff feed own payroll; contractor labour attendance feeds the contractor's bill, and the firm keeps its own copy.
Two exit routes. Own staff through the firm's process; contractor labour through the contractor, with the firm's record of the release.
One headcount report, two columns. Never a single number. The HR reporting for a project has to show both, by site and by trade.
Induction as a condition of entry
On a construction site, induction is not a welcome. It is the thing that has to have happened before a gate pass exists, and the record of who was inducted, when, on what, is part of how the site is run and what it can show if asked. The process is simple to state and hard to hold under schedule pressure: safety induction before the gate pass is issued, gate pass linked to the induction record, PPE issued and signed for, trade skill verified, contractor labour held to the same standard in its own register. The hard part is the site manager, three days behind, waving through a crew that arrived at seven with the induction 'to follow'. The record either has a rule that prevents that, or it has a gap that will be found at the wrong time.
The site file
Everything above depends on a site keeping records that survive the site. A project file that lives in the site office, on the site engineer's laptop and in a box of induction sheets is dispersed the week the site closes, and the questions that arrive later — who was inducted, who was paid what, who was released when — cannot be answered. Records go to a central place as they are made, not at closure. That is the difference between a business that can show what happened on a site two years ago and one that can only say it ran the site properly.
Careers across projects
Project businesses struggle to offer careers because the natural unit of employment is the project, and people conclude their employment ends with it. The counter is to define progression independently of any single project — trade worker to charge hand to site supervisor to site engineer to project manager — with criteria that travel, a redeployment pipeline visible before demobilisation, and the deliberate decision to fund a gap between projects for the key site staff the firm wants to keep. That last decision is the one usually deferred to the site's cost line, and it is cheaper than rehiring and re-inducting a site supervisor every time. The succession and leadership development question in construction is mostly: which site engineers and supervisors do we keep between projects, and how.
Site-level relations
On site, the employment relationship is experienced through the site in-charge, and most disputes are about wages, measurement, advances or conditions, resolved or inflamed within a day. The site needs a grievance route that does not run only through the supervisor, wage and measurement disputes resolved on site quickly, contractor labour issues escalated through the contractor with a record, and a central log by site and trade — because one site producing most of the issues is a supervisor question, and it is invisible without the log.
1
Before the next demobilisation
Ask what the next phase is, for whom, and when. Tell the crew at release. Keep the list where the mobilising manager can find it.
2
This month
Separate own-payroll and contractor labour in every register and report where they are currently merged.
3
This quarter
Put a rule on the gate: no induction record, no pass. Make the site manager's life easier with a fast induction rather than harder with a policy.
4
This year
Define progression that travels between projects, and decide which site staff the firm funds between them.
The site in the opening started short because a crew that could have been kept was released with no information. Everything else in this article is the same problem at a different boundary — payroll to contractor, site to site, phase to phase — and the fix is the same: records and conversations that cross the boundary. Building those is what HR for construction and real estate work consists of, and a firm that has done it stops describing its crew losses as the nature of the trade. The nature of the trade is that people move; construction HR is deciding whether they move with you.
Questions we are asked
Because they were released with no information about the next phase and took the next job offered. One conversation at demobilisation — there is work here in three weeks, we want you back — keeps most of them.
Recorded, yes; merged, never. Own staff and contractor labour need separate registers, attendance flows, exit routes and report columns, because every question has a different answer for each.
A rule at the gate — no induction record, no pass — and an induction fast enough that the site manager does not resent it. The record is what the site will need to show later.
Yes, if progression is defined independently of any project, redeployment is visible before demobilisation, and the firm decides deliberately which site staff it funds between projects.
Everything: induction and training records, attendance reconciled, releases recorded, skill notes per person. A site file that disperses at closure cannot be reconstructed.
A salesperson who funded three months of travel from his own pocket, a depot that reconciled headcount by phone, and a plant that ran its own rules. How FMCG businesses run HR across three operations that share a payroll deadline and little else.
A survey sent to teaching staff during examinations, an appraisal cycle that ignored the term, and administrative staff who felt second-tier. How education institutions run HR on an academic year, and what parity between the three populations actually requires.
A head-office HR policy written for the plant, applied to a showroom, resented in the workshop. How automotive groups run people processes across four workforces that share a brand and almost nothing else.
Read the article
Let’s find your next step
Is your HR process ready to scale?
Identify critical compliance gaps, payroll leaks, and hiring bottlenecks with a free 360-degree HR audit. Get a clear roadmap for your business.