Thomas Gaultier
Menu

Closing the Loop: Verifying Satisfaction and Non-Repetition

Thomas Gaultier 8 min read

A grievance is not closed when the file says closed. It is closed when the complainant says so, and when the thing that caused it has stopped happening. Every other definition is administrative convenience dressed up as performance. I have reviewed registers in which dozens of cases were marked closed on the day an agreement was signed. For a large share of them there was no evidence anywhere that the remedy was ever delivered. Each of those files recorded a broken promise as a success, and the dashboard built on them told management the mechanism was working.

The community keeps a different register. It remembers whether the wall was repaired and whether the water truck kept coming after the first week. It remembers whether the payment arrived in full and on time, and whether the same thing happened again to the neighbours. That register decides whether the next grievance is filed or shouted, and it is the one the company should be trying to match. Closing the loop means three things. Verifying that the remedy was delivered. Confirming that the complainant accepts it. Checking that the cause has been removed so the harm does not repeat.

This article sets out how to do each, and why the last one is the part most mechanisms never reach.

Verification before closure

The first rule is simple and widely ignored: no case closes until the remedy has been verified as delivered. For a physical remedy, that means a site inspection. Someone goes to the repaired cistern, fills it and watches whether it holds. For a payment, it means receipt confirmed with the complainant, not a transfer confirmed by finance. For a procedural remedy, a changed blasting schedule or a rerouted haul road, it means evidence that the change was made and that the people affected were told.

Phased remedies need interim milestones. A livelihood restoration measure or an environmental rehabilitation runs for months or years, and closing the case on the day it is agreed hides everything that follows. Define the milestones at agreement, verify each, and close only at the last. Some remedies carry a standing commitment: dust suppression that has to continue, a watering schedule that has to be kept. Those close only after a follow-up visit has confirmed the commitment is still being honoured weeks later. Target formal close-out within ten business days of the remedy being delivered, and record the closure date, the outcome and the complainant’s status. That is the step that turns a signature into a result.

Verification also protects the officer who did the work. A remedy that was delivered and recorded cannot be disputed a year later by a new complainant, a new manager or a lender’s auditor. The file that holds an inspection photograph, a dated visit and a signed confirmation is the file that survives. The one that holds a signed agreement and nothing else is a liability waiting for its moment.

Satisfaction is a conversation, not a tick

Verification tells you the remedy was delivered. It does not tell you the remedy was right. The second rule is that the complainant’s confirmation is recorded in their own words, in a conversation held for that purpose. A no sends the case back rather than closing it with a note.

The conversation has a shape. Was the remedy delivered as agreed? Did it address what you actually lost? Has anything happened to you since you complained? Would you use the mechanism again? The third question is the non-retaliation check, and it belongs in every close-out for cases involving contractors, security providers or anyone with power over the complainant. The fourth is the single most useful indicator a mechanism produces, because it predicts intake and trust a quarter ahead of any other measure.

Incomplete implementation sends the case back to verification. An inadequate remedy sends it back to negotiation or onward to the escalation ladder, to senior review, mediation or appeal. What it should never do is close with a note that the complainant was dissatisfied, as though dissatisfaction were an outcome.

Timing matters here too. The satisfaction conversation belongs a few weeks after delivery, not on the day. A repaired wall looks fine on the afternoon the plaster dries. Whether it holds through the next blast is what the household will judge it by, and a confirmation taken too early records the wrong verdict. The ladder I described in Intake to Close-Out: Timelines, Tiers and the Escalation Ladder exists precisely so that a refused remedy has somewhere to go.

Record the answer either way, and disaggregate it. Satisfaction that is high among men and low among women, or high near the gate and low behind the hill, is a message. It says the remedies are being sized to the wrong losses. The average will not show it. The close-out conversation, held with each complainant, will. On more than one site the first honest satisfaction figures came from exactly that conversation, and they were lower than the dashboard and far more useful.

Non-repetition is the remedy most mechanisms forget

The UN Guiding Principles describe remedy broadly: apology, restitution, rehabilitation, compensation, sanctions, and the prevention of harm through measures such as guarantees of non-repetition. Most operational mechanisms deliver the middle of that list and skip both ends. They pay and repair, and they neither acknowledge nor prevent. The result is a mechanism that settles the same grievance from the same source every quarter. The community concludes that the company would rather pay for dust than stop making it.

Non-repetition starts at close-out. Every closed case should feed forward with two flags: is this a recurring issue, and what is the systemic cause? A cracked wall from blasting is a case. Six cracked walls in one settlement in one quarter is a blasting-design problem. The remedy for the seventh household is not a repair but a change to the bench sequence or the charge weights. A complaint about a contractor’s water truck is a case. A pattern of them is a supervision failure with a contract clause attached. The root-cause review that follows the flag is where the mechanism stops being a cost centre and starts reducing the operation’s exposure. It is also where the grievance officer needs an ally in operations, because the officer can flag a pattern but cannot change a bench sequence. Name that ally in the procedure, so the flag has somewhere to land. I set out how the register becomes that kind of intelligence in Grievance Data as Early Intelligence for Management.

The guarantee of non-repetition should also be visible to the complainant. When a blasting schedule changes because of a household’s complaint, the household should be told that its complaint changed it. When a haul road is watered on a new schedule, the village should know why. Nothing recruits the next complainant like a remedy the whole village can see. Nothing confirms the mechanism’s purpose like a company that treats a grievance as information rather than as a liability.

Acknowledgment closes what money cannot

The other end of the remedy list is acknowledgment, and it matters more at close-out than anywhere else. A remedy delivered without anyone saying that the harm was real, and that it should not have happened, is experienced as a transaction. A remedy delivered with that sentence attached is experienced as repair. The difference costs nothing and decides whether the complainant would use the mechanism again.

Acknowledgment is not legal admission, and counsel can help draft the line that keeps the two apart. What the complainant needs to hear is that the company understands what happened to them, takes it seriously, and has changed something because of it. I made the fuller argument in The Role of Apology and Acknowledgment in Mining Conflict Resolution, and the close-out conversation is the operational place where it lands.

Auditing your own closures

Once a quarter, pull a sample of closed cases and test them against the three rules. Is there evidence the remedy was delivered? Is there a recorded confirmation from the complainant in their own words? Was a root-cause flag raised, and did anything change because of it? A mechanism that passes on paper and fails on this sample is closing files, not grievances. The general manager’s version of this audit takes ten minutes on a site visit: ask to see the last three close-out verifications. If the evidence takes an hour to find, cases are being closed at the desk. That single question, asked on a site visit, exposes a hollow mechanism faster than any formal audit, because a mechanism that verifies its remedies can produce the proof in minutes.

Test your close-outs against what the community remembers

The Grievance Close-Out Verification Checklist has 15 points in five sections: verification of delivery, the satisfaction conversation, the non-retaliation check, root cause and non-repetition, and acknowledgment and communication. Score each item In place, Partial or Absent against a sample of closed cases rather than against the procedure. Absents in the first section mean the register is recording promises as outcomes. Absents in the fourth mean the mechanism is settling the same grievance repeatedly. Run it quarterly, and share the result with community representatives, because they already know which cases were really closed. Download the Grievance Close-Out Verification Checklist

The loop closes with both sides holding the record

A mechanism that verifies delivery, records the complainant’s own verdict and removes the cause is doing what the standards describe and what the community expects. It protects the household by making sure the remedy is real. It protects the operation by stopping the grievance from becoming a pattern and the pattern from becoming a blockade. Livelihoods and investments are served by the same discipline, and the discipline is not complicated. It is just rarely done, because the file can be closed faster than the loop.

Sometimes the loop has been left open for years, and a community holds a long list of remedies promised and not delivered. Closing it is then no longer an administrative task. It is a negotiation over trust, and it needs a structured process with an independent hand. The Social Accord Architecture carries every agreed remedy into a single commitments register that both company and community can read. Each entry has an owner, a date and a verification step. Its Feedback Loop is where root causes go, and its mediation pathway is where a contested closure is resolved rather than imposed. Dual accountability is the point: the company is accountable for delivering and proving what it promised, and the community for testing it through the process rather than the road. When both sides hold the same record of what was closed and how, the mechanism has done its job.

One thing to do this week. Pick five cases closed in the last quarter and visit the complainants. Ask whether the remedy arrived, whether it was right, and whether anything has happened since. What you hear is the real status of your mechanism. To audit your close-out practice or to mediate a backlog of unfulfilled remedies, 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.