No promise a mining company makes is heard more clearly, or remembered longer, than the promise of jobs. It is made at the first community meeting, repeated in the permitting hearings, and written into the agreement in language that sounds precise and is not. Then it is tested every single week of construction by young men standing at the gate. When the test fails, the dispute that follows is rarely about a number. It is about who counts as local, who decided, and why the man from the next district got the job that was promised to the village.
The research on local content is clear that employment is the central expectation wherever a mine arrives, and equally clear that most projects underdeliver against it. The reason is structural. A mine needs a few thousand people for two years of construction and a few hundred for thirty years of operations, most of them skilled. The village has a few hundred people, most of them unskilled. Between the promise and the arithmetic sits a gap that no recruitment drive can close. How a company handles that gap decides whether local employment becomes the project’s strongest relationship or its most durable grievance.
This article is about the hiring disputes that follow the promise, and how to design a local employment arrangement that survives the arithmetic.
Who counts as local
Almost every hiring dispute starts with the word local. To the company it usually means the province, the district or a radius on a map. To the village on the fence line it means the village. To the district town it means the town. To the national government it means citizens. The agreement said local jobs, everyone signed it, and each party understood a different population. Then the recruitment list is published and the fence-line village finds that a third of the names come from the district capital. The village concludes it has been cheated, and by its own definition it has.
The definition has to be negotiated, written down, and explained before the first hire. A workable approach is tiered. First preference goes to households directly affected by land take and resettlement, second to the settlements within a defined footprint, third to the district, fourth to the province. The tiers are published and the eligibility test for each is stated. A residency register, agreed with traditional and municipal authorities before the influx begins, is the only defence against the newcomer who arrived last month and now claims to be local. Consider a scenario drawn from patterns across many projects: two neighbouring villages, one inside the footprint and one just outside, both told they would benefit. The inside village gets the first jobs and the outside village blocks the road. The dispute was designed in at the moment the word local was left undefined.
The definition also has to survive the influx. A district town that doubles during construction is full of people who now live locally and were not there when the promise was made. Without a register fixed early, the company faces an impossible choice. It can honour the promise to the original residents, or avoid being seen to discriminate against the newcomers who now outnumber them. It cannot do both.
The construction cliff
The second structural dispute is timing. Construction employs many people for a short time. Operations employ few people for a long time, and most of them need skills the village does not have. A company that hires heavily from the village during construction, and says nothing about what happens at commissioning, has set a trap for itself. Eighteen months later several hundred local workers are demobilised in the same month. They have given up farming, taken on debt against their wages and told their families the mine was permanent. The village experiences it as mass dismissal, and the relationship built during construction collapses at the point where the company most needs it. Commissioning is when a project is most vulnerable to disruption and least able to afford it.
The World Bank’s influx guidance and the IFC’s in-migration handbook both treat local hiring as a measure that reduces the incoming workforce and its risks. That is true, and it is also why the cliff has to be planned from the first hire. Be explicit, in every recruitment communication, about the duration of construction jobs. Design the construction workforce so that a defined share of local hires move into a training pipeline for operations roles, selected transparently and early. Time demobilisation in stages and around the agricultural calendar. And build the transition into the agreement rather than leaving it to the contractor’s demobilisation schedule, because the contractor’s incentive is to release people the day the work stops.
The recruitment process is the dispute
Even where the definition is agreed and the numbers are honest, the process by which names become hires generates most of the daily grievances. The complaints repeat across sites. The list was decided in the contractor’s office and nobody knows how. The chief’s relatives are all on it. The recruiter took money. The jobs went to men, and the women who lost their gardens to the pit got nothing. The vacancy was never advertised in the village, only in the town. The interview was in a language the applicants did not speak.
Each of these has a design answer. Publish every vacancy, in the local languages, through channels the villages actually use, with the eligibility tier and the selection criteria stated. Hold recruitment days in the settlements, not only at the site office. Run selection through a panel that includes a community observer, and record the reasons for each decision. Set targets for women’s employment and for households affected by land take, and report against them. Prohibit payments to recruiters and make the prohibition known, because the recruiter who sells jobs is often the first corruption a community meets from the project. And give unsuccessful applicants a reason and a route: a skills register they can join, a training programme they can enter, a date when the next round opens. An applicant who was told why is a future applicant. An applicant who was ignored is a future protester. In my experience the difference between the two is a conversation of five minutes, and most projects do not budget for it.
Community hiring committees, and their limits
Many projects set up a community employment committee to manage the interface, and the model works when its role is precise and fails when it is not. A committee that verifies residency, observes selection panels, receives hiring data and hears complaints about the process adds legitimacy that the company cannot generate alone. A committee that allocates jobs becomes a new site of capture, because whoever controls the list controls the most valuable thing in the village. I have heard the same story relayed by more than one practitioner in my trainings. A committee set up to make hiring fair became, within a year, the reason hiring was seen as unfair. The committee’s members and their families were the ones getting hired.
The design rule is that the committee governs the process, not the outcome. It should have a written mandate and rotating membership drawn from more than one settlement and more than one leadership structure. It should have women among its members, and the right to see the full recruitment data every month. It should have a route to raise a process breach directly with site leadership. And it should be one of the parties in the room when the local employment arrangement is reviewed each year. The broader engagement structures I describe in Building a Stakeholder Engagement Plan give the committee its place in the wider architecture.
Reporting that ends the argument about numbers
Half the hiring disputes I have seen would have been avoided by a monthly page. How many people are employed on the project this month, by contractor, by tier of locality, by gender, by skill level, and how many are local by the agreed definition? How many were hired and demobilised this month, from which settlements? How many local workers are in the operations training pipeline? A page like that, shared with the employment committee and posted in the settlements, replaces rumour with fact. It shifts the conversation from whether the company is lying to whether the arrangement is working. Without it, the village counts the buses from the district town and draws its own conclusions. The same logic runs through the point I make in Reading the Company’s Promises: a promise that cannot be measured cannot be kept, and the community knows it.
Design the arrangement before you make the promise
The Local Employment Arrangement Checklist has 16 points in five sections. They cover the definition of local and the residency register, honest numbers and the construction-to-operations transition, a transparent recruitment process, the committee’s mandate and limits, and monthly reporting. Score each item In place, Partial or Absent before the first recruitment round and again at the construction peak. Absents in the first section mean the word local is still undefined and the first dispute is already scheduled. Absents in the second mean the cliff at commissioning will arrive unannounced. Use it with the employment committee and the main contractors in the room. Download the Local Employment Arrangement Checklist
Jobs are the promise the relationship is built on
A company that handles local employment honestly earns a relationship that survives the disappointments the arithmetic guarantees. Honestly means a negotiated definition, a truthful account of the numbers, a transparent process and a plan for the cliff. One that makes the promise loosely and manages the gap by silence earns a blockade at the gate, staffed by the men it did not hire. The households’ livelihoods and the project’s schedule are lost together in that second case, and both are protected together in the first.
The hiring arrangement is a negotiation, not a policy, and it needs to be treated as one. The Social Accord Architecture puts local employment into the Blueprinting phase. There the definition of local, the tiers, the numbers by phase, the committee’s mandate and the reporting rhythm are agreed by the parties. They are written into the accord as commitments with owners and dates. The commitments register tracks them and the council reviews them. The disputes the process cannot settle, a contested residency, a demobilisation gone wrong, go to the mediation pathway rather than the road. Dual accountability holds the company to the process it agreed and the community’s institutions to governing their side of it, including the committee. Where a hiring dispute has already closed the gate, an independent mediator can usually reopen it faster than security can. The dispute is about fairness, and fairness can be negotiated.
One thing to do before your next recruitment round. Write down, in one sentence, who counts as local for this project, and read it aloud in the fence-line village. If the room disagrees, you have found the dispute before the list is published. To design a local employment arrangement or to mediate a hiring dispute, write to me at thomas@thomasgaultier.com.