Agreement Documentation

Part of Conflict Resolution

How to write, store, and enforce the agreements that emerge from mediation and conflict resolution processes — turning verbal commitments into durable records.

Why This Matters

Mediation that ends with a verbal handshake is mediation that will need to be repeated. Memory is selective, especially in conflict: people remember what they agreed to in ways that favor their own interests. Without a written record, what felt like resolution becomes the seed of the next dispute — each party convinced the other is failing to honor commitments that were never clearly articulated.

Written agreements serve multiple functions. They force specificity: a vague verbal commitment (“I’ll do better”) becomes a concrete obligation (“I will return the tools to the storage shed within two days and will ask before borrowing in the future”). They create accountability: there is a document to reference when checking whether obligations were met. They build institutional memory: the community accumulates a record of how similar disputes were resolved, creating precedents that make future decisions more consistent.

Documentation also dignifies the resolution process. A written, signed agreement signals that the community takes the resolution seriously and expects both parties to do the same. Treating agreements with the same formality as other important community documents — land agreements, work assignments, resource allocations — integrates conflict resolution into the fabric of community governance.

Elements of an Effective Agreement

Parties and date. Name every person bound by the agreement and record the date. If the agreement involves ongoing obligations, record the date range over which those obligations apply.

Statement of the harm. A brief, neutral description of what happened and who was affected. This is not a blame statement; it is the shared factual foundation. “On [date], [person A] used [person B]‘s tools without permission, resulting in a lost chisel and damaged saw” — not “person A deliberately stole and destroyed person B’s tools.” The factual statement should be something both parties can accept as accurate.

Acknowledgment. A statement from the person who caused harm acknowledging their role. This need not be elaborate: “I acknowledge that I used the tools without asking and am responsible for the damage.” The acknowledgment is distinct from the factual statement — it is personal, first-person, and explicitly accepts responsibility.

Obligations. The core of the agreement: what will be done, by whom, by when. Obligations should be:

• Specific (not “make it right” but “replace the chisel with one of equal quality”)
• Time-bound (not “soon” but “within two weeks, by [specific date]”)
• Verifiable (something observable, not a state of mind)
• Proportionate (matched to the harm, not punitive)

List obligations separately. Number them. If there are obligations on multiple parties, clearly label who is responsible for each.

Consequences of non-compliance. What happens if an obligation is not met by the specified date? This should be specified in the agreement, not left to future improvisation. Common options: a formal community hearing, additional obligations, escalation to the law-and-justice process.

Verification process. Who will check whether obligations were completed? When? How will completion be recorded?

Signatures. Both parties and the mediator sign. In communities where signatures carry less weight than witnessed oral affirmation, have witnesses present and named in the document.

Format and Storage

Agreements should be written in plain language that every signatory can read and understand. Legal formality can create distance and confusion; what matters is clarity. Use short sentences. Avoid jargon.

Keep two copies: one held by each party, one held by the community’s record-keeper (whoever maintains community documents — a designated archivist, a council, a community ledger). The community copy creates an accessible record for future reference.

Store agreements in a dedicated section of community records, separate from other documents. Label them with date and parties for easy retrieval. After obligations are completed, annotate the record: “Obligations completed as of [date], verified by [name].”

Following Up

The most important moment in agreement documentation is often the follow-up visit. Schedule it at the time of signing: “On [date three weeks from now], we will check in to confirm the obligations have been completed.” The person responsible for follow-up should be named in the agreement.

At follow-up, review each obligation: was it completed? If yes, annotate the record and acknowledge completion — publicly, if possible, as this signals to the community that the process works. If an obligation was not completed, initiate the consequence specified in the agreement immediately. Delayed consequences teach that agreements are optional.

If circumstances changed between signing and the follow-up date and an obligation could not be completed for reasons outside the person’s control, reconvene the parties to renegotiate. Changed circumstances are not a justification for ignoring the agreement; they are a reason to modify it through the same process that created it.

Common Mistakes

Vague obligations. “Will show more respect” cannot be verified. Push for specificity: “Will ask before using any shared tools” is verifiable.

No timeline. Open-ended obligations are never completed. Every obligation needs a date.

Missing consequences. An agreement without specified consequences for non-compliance is a suggestion. Name what happens next, before it needs to happen.

No follow-up. Written without follow-up is theater. The agreement only has value if someone checks.

Imbalanced obligations. Agreements that place all obligations on one party often fail because the other party feels no investment in the outcome. Where possible, find something both parties commit to, even if small — it transforms the document from a sentence into a mutual commitment.