Thomas Gaultier
Menu

Grievances About Contractors and Security Providers

Thomas Gaultier 9 min read

“That was not our employee.” I have heard the sentence from operations managers, from lawyers and from grievance officers, and it has never once helped. The woman whose goat was hit by a contractor’s water truck does not read the badge. Nor does the young man detained at the fence by a private security patrol, or the family whose fields were crossed by a drilling crew that nobody briefed. They see a vehicle with the project’s colours, or a uniform paid for by the project, and they hold the project responsible. In the field, the contractor’s conduct is the company’s conduct. The grievance mechanism has to be built on that fact rather than against it.

The standards agree. The UN Guiding Principles extend a company’s responsibility to impacts directly linked to its operations through its business relationships, which is precisely what a contractor or a security provider is. IFC Performance Standard 4 requires a grievance mechanism specifically for community concerns about security arrangements and the acts of security personnel, contracted or not. And the Voluntary Principles on Security and Human Rights, in place since 2000, set the expectations for vetting, conduct and the investigation of allegations against both private and public security. None of these frameworks allows the company to stop at the boundary of its own payroll.

This article is about making the mechanism reach conduct the company did not directly commit, and about the special handling that security cases demand.

Why contractor grievances are different

Contractor grievances are different in three ways, and each one breaks a mechanism designed around the company’s own staff. First, the chain of information. A community relations officer knows what the mine’s own crews are doing this week. She often does not know that a subcontractor’s earthworks team started on the eastern boundary on Tuesday, because nobody told her, so the first she hears is the complaint. Second, the chain of authority. The officer can walk into an operations meeting and change a blasting schedule. She cannot instruct a contractor’s foreman, and the contractor’s site manager answers to a contract, not to the community relations plan. Third, the chain of incentive. A contractor on a fixed price and a tight schedule experiences every community interaction as a delay. Its workers are often housed in a camp, are not from the area, and will be gone in eighteen months. The community will still be there, and so will the company’s name on the gate.

The World Bank’s guidance on labour influx sets out the consequences. Workforce conduct toward host communities, including harassment and gender-based violence, is one of the main risks of the construction phase. The construction peak is the highest-conflict window of a project’s life, and most of the people on site during it work for someone other than the company.

Flow-down that actually flows

The contractual answer is flow-down: the company’s community commitments, code of conduct and grievance obligations are written into every contract and subcontract. Most projects have the clause. Fewer make it operate. Flow-down works when four things are true. The contractor’s code of conduct is the project’s code, in the contractor’s languages, signed by each worker and explained on induction rather than handed out with the boots. The contractor’s site manager is required to attend the community relations coordination meeting and to notify the community team before any new area is entered. The company’s grievance mechanism applies expressly to contractor conduct, and the contractor is required to cooperate with investigations and to implement remedies. A defined share of the cost of a remedy caused by the contractor is recoverable from it. And the contract carries consequences: a corrective action plan on a pattern of complaints, a payment hold on failure to deliver it, and termination for serious or repeated misconduct.

The community team should also see contractor grievance data as its own category. A cluster against one contractor is a supervision failure that the contractor will not report on itself. It is also the pattern that most often moves a general manager when it is put on one page. I have watched a payment hold do more for a contractor’s community conduct in a fortnight than a year of induction sessions. Contractors respond to the incentives in their contract. If the contract prices community harm at zero, that is the value the site manager will assign to it.

Investigation when the company did not do it

A grievance about a contractor needs a joint investigation, not a referral. Referring the complainant to the contractor tells them the company has washed its hands. Investigating without the contractor produces findings the contractor will dispute. The workable model is a company-led investigation with the contractor’s manager present, the complainant’s account taken first and on their own ground, and a remedy agreed by all three. The company signs the remedy as the party the community holds responsible, and recovers from the contractor as the contract allows. Consider a drilling crew that crosses a family’s field without notice and breaks an irrigation channel. The family should not have to learn the name of the subcontractor to get the channel repaired. The company repairs it that week, and the invoice follows the contract.

Two protections matter more with contractors than with the company’s own staff. Confidentiality, because the complainant may live next to the contractor’s camp and the contractor’s workers may know who complained. And non-retaliation, because a contractor with a grievance against it has an incentive to make the complainant’s life difficult, and no community relations plan to lose. Both should be stated at acknowledgment and checked at close-out, with a follow-up visit weeks later to ask whether anything has happened since. Criminal matters, an assault, a theft, a serious road accident, go to the police as well as into the register. The complainant should be told that both routes exist and that neither cancels the other.

Security providers: the highest tier, every time

Security grievances are the category where a mechanism’s legitimacy is won or lost, and they need rules that leave no discretion. Any allegation involving a security provider, private or public, is classified at the highest severity level automatically. The investigation is assigned to someone independent of site security management. The conflict of interest in letting security investigate security is visible to everyone, and most of all to the complainant. The case gets senior visibility from the first day, and board-level reporting where the allegation involves force, detention or injury.

Performance Standard 4 sets the frame the investigation applies. Proportionality, use of force only for preventive and defensive purposes, conduct rules, training, and reasonable inquiry that providers are not implicated in past abuses. The Voluntary Principles add the expectation that allegations be recorded, reported to the relevant authorities where appropriate, and followed up. A company that has signed up to neither still owes its community the substance of both, because the community will judge it by what its guards do.

Public security forces raise the bar again. A grievance officer cannot shield a complainant from the police, and pretending otherwise endangers the people the mechanism claims to protect. Screen at intake: would filing this grievance expose this person to actors beyond the company’s control? Adjust the handling: heightened confidentiality, anonymous routing, careful choices about where and when to meet, no documents that travel with the complainant. And put one rule in writing and keep it: complainant identities and case details are never shared with public security forces. Where national law compels disclosure, involve counsel early and tell the complainant what the law may require before they decide to file. The wider security and human rights obligations I set out in Security and Human Rights on Site are the context for all of this.

Reading silence in security cases

A register with no security grievances beside an operation with an armed private force and a public security detachment is not a clean record. It is more often a measure of fear. Where the complainant would be a human rights defender, or where civic space is closed enough that any complaint is an act of courage, silence means something else. A quiet quarter is not good news by default. Assess before any outreach whether contact itself creates risk, make contact only on the complainant’s terms, and treat the silence as the loudest indicator the mechanism produces. Community perception interviews, conducted by someone visibly independent of the security function, are the only way to read it. The broader point about quiet registers that I make in Grievance Data as Early Intelligence for Management applies here with more force than anywhere else.

Check that your mechanism reaches beyond the payroll

The Contractor and Security Grievance Reach Checklist is a 16-point checklist in five sections: contractual flow-down, information and coordination, joint investigation and remedy, security-specific handling, and protection of complainants. Score each item In place, Partial or Absent against the last year’s contracts and cases. A cluster of Absents in the flow-down section means the mechanism has a clause and no reach. Absents in the security section mean the cases that most threaten the operation’s legitimacy are being handled on the routine track, or not filed at all. Review it whenever a new contractor mobilises and whenever the security arrangement changes. Download the Contractor and Security Grievance Reach Checklist

The community holds the whole project responsible, so the process must too

A mechanism that stops at the company’s own staff has drawn a boundary the community does not recognise. The contractor’s truck and the guard’s uniform are the project. Every grievance about them that goes unanswered teaches the community that the mechanism is a device for protecting the company rather than for resolving harm. That lesson costs both sides. The household is left without remedy, and the project loses the trust that keeps its roads open during the construction peak, when it is most exposed.

The structured answer is a process that puts the company, the contractor and the affected people at the same table. An independent hand joins it where the stakes or the power gap require one. The Social Accord Architecture builds contractors and security providers into the Actor Map from the start. Their conduct is governed by the same Rules of Engagement as the company’s, and their grievances flow through the same mechanism and the same mediation pathway. Dual accountability holds all three parties. The company answers for the conduct of those it brings onto the land. The contractor answers for the code it signed, and the community for using the process rather than the roadblock. Where a security allegation has already hardened into a standoff, an independent mediator trusted to keep identities safe is often the only person who can get the account heard.

One thing to do this month. Take your three largest contracts and find the grievance clause. If it says the contractor will comply with the company’s policies and nothing more, it has no reach. Rewrite it to require cooperation with investigations, implementation of remedies, cost recovery and consequences. To design a mechanism that reaches contractors and security providers, or to mediate a case that already involves them, write to me at thomas@thomasgaultier.com.

I am Thomas Gaultier. I mediate company-community disputes in mining, oil and gas, and energy projects, and I have resolved more than 2,000 claims across Sub-Saharan Africa and Europe. More about the work, or tell me what you are dealing with.

If the relationship around a project is under pressure, or heading there, let us talk.

A 30-minute call is enough for me to understand the situation and tell you honestly whether I can help. Active opposition, a social license problem, an FPIC process that needs an independent facilitator, a negotiation a community has to prepare for, or a conflict that is not public yet but will be. It makes no difference which side of the table you are on. No obligation, no generalist pitch.

Every first conversation is confidential.

Cover of Legacy Grievances and Historical Claims by Thomas Gaultier

New release, and the last one

Legacy Grievances and Historical Claims

The tenth and final volume completes the library. It is the field guide to harm that outlived the operation: transitional justice adapted to corporate disputes, successor liability when the asset changes hands, and the pathway behind more than two thousand resolved claims.