Punishment before repair

Why it is hard to see

Because it usually arrives as a correction of the opposite failure, and it is celebrated.

A community exhausted by years of avoidance decides to take accountability seriously. It writes a policy. It stops tolerating the untolerable. Everybody agrees this is overdue, and for a while it genuinely is better — the thing that should have been addressed four years ago finally is.

What goes wrong is the shape of what got built. Groups correcting for avoidance tend to build a process with one step: a complaint goes in, a judgement comes out. There is nothing below it, because the thing they were fixing was the failure to act.

So the cost of raising anything becomes very high. Mentioning that somebody’s dog is a problem now initiates a procedure with a verdict at the end, and no member wants to do that to a neighbour over a dog. The result is a community that only ever processes serious matters — because the small ones are not worth what raising them costs. Which looks, from the outside and from most of the inside, exactly like the avoidance they just escaped.

The second reason it hides: it produces visible action. Cases get heard, outcomes get issued, and the group can point at the file. Nothing about the metric shows that the docket is short because the threshold is high.

What to check

Look at the bottom of the ladder, not the top. What is the cheapest available response to a minor breach? If the answer is “a conversation with the board”, there is no bottom, and everything below that threshold is being absorbed silently.

Ask what restores standing. A sanction with no stated end and no route back is not a graduated response — it is an indefinite status, and the person under it will eventually leave rather than wait.

Check whether hearing and deciding are the same conversation. A group that determines the consequence in the meeting that first hears the complaint has no space in which repair could have been the outcome.

If it is already happening

Add steps below what you have, rather than softening what you have. The instinct is to make the existing process gentler, which makes serious matters harder to handle without making small ones cheaper. What is missing is rungs, not leniency.

Separate the finding from the response. Establishing what happened and deciding what follows are different tasks, and merging them is what makes every complaint feel like a prosecution.

Give every sanction an end date and a restoration route — including the ones already running. An open-ended consequence is the pattern’s most expensive form, because it converts a conflict into a permanent condition that only departure resolves.

Then say the change out loud. People calibrated to a high-cost process do not recalibrate because the policy changed. They recalibrate when they watch somebody raise something small and nothing terrible happen.

What prevents it

Graduated sanctions Graduated sanctions Responding to a first breach differently from a fifth. One of Ostrom's design principles, and the answer to a rule with no stated consequence. — a first breach not treated like a fifth — and a stated presumption that repair is attempted before consequence. Ostrom found the same thing from an entirely different direction: durable commons have graduated sanctions and cheap, local conflict resolution, and the two travel together.

Sources & further reading

1. 1 RCOS stress test — Punishment Before Repair — the specification this page puts into plain language
2. 2 Ostrom, E. — Governing the Commons (1990) — graduated sanctions: a first breach is not treated like a fifth
3. 3 Membership: getting in, and getting out — stated grounds plus a graduated response, and what a suspension may not be

Written by EcoHubs members, with AI assistance for drafting and editing, and reviewed by a person before publication. Facts are checked against the sources listed; anything we could not verify is marked. How this is written