Labour force management: the plan usually covers the wrong workers

Labour force management plans are typically drafted from an HR policy, and HR policies describe employees. The people most exposed to labour risk on a large civil works project are not employees. They are casual community labour hired at the gate, subcontracted crews working to somebody else's programme, and drivers whose hours are set by a haulage schedule.

The result is a plan that governs the population least likely to be harmed, and is silent about the population most likely to be. That is rarely deliberate. It is a drafting artefact, and it is fixable in one structural move.

State the worker categories first

International practice distinguishes direct workers, contracted workers, primary supply-chain workers and community workers, with core protections applying across the categories rather than to the first one only.[1] Put that classification at the top of the plan and make every subsequent section declare which categories it covers.

The exercise is uncomfortable in a useful way. A section on accommodation that applies to direct workers and not to the subcontracted crews actually living in the camp is a section that has just told you something.

Three records a labour audit goes to first

• Contract copies issued, not merely signed. A contract filed only by the employer leaves the worker bound by terms they cannot check. Retain the signature; issue the copy; record that you issued it.
• Traceable payment. Cash with no record makes a non-payment claim unprovable in both directions. That protects nobody and leaves the project unable to rebut an allegation it may well not deserve.
• Age documents retained at hiring. A check that leaves no artefact is indistinguishable afterwards from no check. Child labour is the finding that ends a lender relationship rather than generating a corrective action plan.

The worker grievance mechanism is not the community one

The complaints differ and so does the retaliation risk. A community mechanism handles land, access and nuisance. A worker mechanism handles pay, hours, safety and treatment by a supervisor — and routing those through the line manager the complaint is usually about is the single most common design failure in this area.

It produces a mechanism with no complaints in it, which is then reported as evidence that nothing is wrong. An empty worker grievance log on a two-thousand-person site is a finding, not a result.

Everything depends on the flow-down clause

Every requirement in the plan is only as real as the contract clause that passes it to the party performing the work. A project can hold an exemplary LFMP and a subcontract silent on wages, age verification and accommodation — at which point the plan governs a workforce the project does not employ, with leverage it does not have.

Check the flow-down before the plan is finalised. The clause costs nothing at tender and is close to impossible to insert once the subcontractor has mobilised.[2]

Plan demobilisation before mobilisation

Notice periods, final payments, certificates of service and any severance due are cheap to plan and expensive to improvise. A workforce released at project end with unresolved dues has no forum left to resolve them, and the project has no presence on site with which to fix it.