An agreement holds when breaking it is noticed and has a predictable, graduated response administered by the community and not by the aggrieved party. Make compliance visible, agree the steps for a first breach before it happens, keep sanctions small and proportionate at first, and write only promises the parties can realistically keep, since a rule nobody can enforce is a wish.
Part of Community Conflict Resolution
What turns a signed agreement into a durable commitment: visibility, graduated response and community legitimacy.
Three Conditions: Visible, Graduated, Legitimate
Political scientist Elinor Ostrom studied communities that managed shared resources over long periods and found recurring features, including monitoring by the users themselves, graduated sanctions, and cheap ways to resolve conflicts (Governing the Commons, 1990; recalled from memory and not verified for this article). The corpus article on Commons Management covers the resource side. The three features carry over to personal agreements:
- Visible. Breaches must be noticeable by someone with standing to act.
- Graduated. The first response is mild and the severity rises with repetition.
- Legitimate. The response comes from the community’s process, not from the aggrieved person.
Method: Make an Agreement Enforceable
Step 1: Write only what can be checked. “Return the tools within two days” can be checked; “be more considerate” cannot. See Creating Agreements and Agreement Documentation.
Step 2: Say who checks. The mediator at the follow-up, or a named person such as the storekeeper or a work-team lead; see Follow-Up & Accountability.
Step 3: Agree the response to a first breach beforehand. Write it in the agreement: for instance “the mediator will meet both parties within a stated period”. A reminder and a conversation come first.
Step 4: Add steps if the breach repeats. A stated sequence such as a reminder, a meeting with the mediator, a loss of a privilege tied to the breach, then referral to the council. The council’s powers are in Council-Based Decision Making.
Step 5: Keep each step proportionate to the breach. See Proportional Consequences. A late return of a tool does not justify exclusion.
Step 6: Hear the party in breach first. Sometimes the cause is illness or a changed circumstance, and the term should change, not the person be punished.
Step 7: Record the outcome and report it to the community in neutral terms.
No self-help
The aggrieved party must not punish, seize property or take revenge. Private action restarts the conflict and puts a second grievance on top of the first. Send the breach to the agreed process.
The Limits of Enforcement
- It depends on legitimacy. A sanction the community does not accept will be resisted. Consent beforehand matters; people tend to accept agreements made in their own process.
- It cannot fix every breach. Where a party simply refuses, the agreement has failed and the matter goes to the next step.
- Power affects it. A powerful person may ignore weak sanctions; a vulnerable one may be punished harshly. Apply the same steps to everyone.
- It costs the community. Monitoring takes time; keep it light, and match it to the stakes.
For agreements between communities, enforcement is weaker because no common authority exists; see Mutual Defense Agreements and Treaties & Alliances.
Common Mistakes
- Promising sanctions you will not apply. The first unenforced breach teaches that terms are optional.
- Surprising people. A consequence not written beforehand reads as arbitrary.
- Overusing exclusion. Reserve it for danger.
What’s Next
- Learn next: Proportional Consequences — matching response to breach
- Combine with: Community Justice Systems — the wider system