Does an LFMP cover subcontracted workers?

It has to. On most infrastructure projects the direct workforce is a small minority and the labour risk sits almost entirely in subcontracted and community labour. A plan that covers direct hires only is covering the population least likely to be harmed. The standards recognise four worker categories — direct, contracted, primary supply-chain and community — and the plan should state which protections apply to each.

Is a signed contract enough to evidence terms of employment?

No. The test is whether the worker holds a copy, in a language they read. A contract signed and filed only by the employer leaves the person bound by the terms unable to check them, which is exactly the condition under which wage disputes become unresolvable. Retain the signature; issue the copy; record that you issued it.

Why does the plan need a worker grievance mechanism separate from the community one?

Because the complaints are different and so is the risk of retaliation. A community GRM handles land, access and nuisance; a worker mechanism handles pay, hours, safety and treatment by a supervisor. Routing worker complaints through the line manager they are usually about is the single most common design failure, and it produces a mechanism with no complaints in it — which is then reported as evidence that nothing is wrong.

What does age verification actually require?

A document retained on file, checked at hiring. Verification by appearance or self-declaration leaves no evidence the check happened, which means it cannot be demonstrated later and, in practice, often did not happen. This is the row a lender's labour audit goes to first.

When should demobilisation be planned?

Before mobilisation, not at the end. 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 to fix it.

CSVFree · no registration

Labour Force Management Plan (LFMP) Template

A 10-section structure for the workforce plan — worker categories, terms, wages, child and forced labour, worker grievance mechanism, accommodation, supply chain and demobilisation.

10 sections · with the responsible tier, common failure and standard reference for each

The risk is where the plan usually isn't

Labour force management plans are commonly written by the employer's social team and describe the employer's own staff. The people most exposed to labour risk on the project — casual community labour hired at the gate, subcontracted crews, drivers working to a schedule set by someone else's programme — are frequently outside its scope entirely.

That is not usually a deliberate omission. It happens because the plan is drafted from an HR policy, and HR policies describe employees. The correction is structural: state the worker categories first, before anything else in the plan, and make every subsequent section say which categories it applies to.

Three rows that decide whether the rest is credible

Contract copies issued. Not signed — issued. The distinction is the whole of a worker's ability to hold the employer to the terms.
Traceable payment. Cash payment with no record makes a non-payment claim unprovable in both directions, which protects nobody and exposes the project to allegations it cannot rebut.
Age documents retained. A check with no artefact is indistinguishable from no check at all, and child labour is the finding that ends a lender relationship rather than generating a corrective action plan.

Flowing obligations down the contract chain

Every requirement in this plan is only as real as the contract clause that passes it to the party who will actually perform the work. A project can hold an exemplary LFMP and a subcontract that says nothing about wages, age verification or accommodation — at which point the plan governs a workforce the project does not employ, using leverage it does not have.

Check the flow-down before the plan is finalised, not after the first audit finding. The clause is cheap to insert at tender and close to impossible to insert once the subcontractor is mobilised.

Questions

Does an LFMP cover subcontracted workers?: It has to. On most infrastructure projects the direct workforce is a small minority and the labour risk sits almost entirely in subcontracted and community labour. A plan that covers direct hires only is covering the population least likely to be harmed. The standards recognise four worker categories — direct, contracted, primary supply-chain and community — and the plan should state which protections apply to each.
Is a signed contract enough to evidence terms of employment?: No. The test is whether the worker holds a copy, in a language they read. A contract signed and filed only by the employer leaves the person bound by the terms unable to check them, which is exactly the condition under which wage disputes become unresolvable. Retain the signature; issue the copy; record that you issued it.
Why does the plan need a worker grievance mechanism separate from the community one?: Because the complaints are different and so is the risk of retaliation. A community GRM handles land, access and nuisance; a worker mechanism handles pay, hours, safety and treatment by a supervisor. Routing worker complaints through the line manager they are usually about is the single most common design failure, and it produces a mechanism with no complaints in it — which is then reported as evidence that nothing is wrong.
What does age verification actually require?: A document retained on file, checked at hiring. Verification by appearance or self-declaration leaves no evidence the check happened, which means it cannot be demonstrated later and, in practice, often did not happen. This is the row a lender's labour audit goes to first.
When should demobilisation be planned?: Before mobilisation, not at the end. 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 to fix it.

All RAP templates →

The software behind this

SmartLARMS keeps this as a live record, not a spreadsheet

A template is a starting point. The version that survives a completion audit is one where every change is attributed to a person and a date, and where the numbers reconcile to what was actually paid.

Talk to us → olules@smartlarms.com