Conflict Resolution Ladder

Download this template

Generated 2026-04-29 · Download all templates

  • Layer: 4 — Conflict, Repair & Accountability
  • Status: Template — adapt for your community
  • RCOS reference: §6.1, §6.2, §6.3, §6.5

Conflict Classification

RCOS clauses: 6.1.1, 6.1.2, 6.1.3, 6.1.4, 6.1.5, 6.5.3

Why classify conflicts at all?

Without named classes, every dispute gets treated the same — or worse, treated differently based on who is involved. Explicit classes set the entry point, the response window, and the documentation burden up front, so safety-critical matters cannot be quietly routed through a friendly chat and minor friction cannot be weaponized into a formal review.

How to fill this in

For each class, set entry criteria, the entry step in the ladder, the initial response window, and the documentation burden.

Class Entry criteria Entry point Initial response window Documentation
<…> <…> <…>
<…> <…> <…>
<…> <…> <…> <…>

Safety-critical conflicts override participation rights, role continuity, and operational convenience.

Resolution Ladder Steps

RCOS clauses: 6.2.1, 6.2.2, 6.2.3, 6.2.4, 6.2.5, 6.5.3

Why a stepped ladder instead of a single process?

Most conflict is low-stakes and best resolved between the people involved; forcing everything into formal review would kill trust and flood the governance system. A ladder matches process weight to dispute weight — private conversation first, facilitated dialogue next, written record only when needed, governance vote only when all else fails. It also makes escalation a structural right, not a favour granted by whoever holds social power.

How to fill this in

Define each ladder step: who is involved, what happens, the time window, and the escalation rule. Keep the early steps light and confidential; reserve formal review for later steps.

  1. Direct conversation
  2. Facilitated dialogue
  3. Accountability intake
  4. Accountability review
  5. Governance decision
  6. Separation process

Non-Response, Withdrawal, and Deadlock

RCOS clauses: 6.2.5, 6.1.5

What stops a process from being killed by silence?

The easiest way to defeat any accountability process is to ignore it. If non-response, withdrawal, or deadlock leaves the matter frozen, the party on the receiving end of harm carries the cost of the inaction. Explicit rules for each failure mode convert silence into a documented escalation trigger rather than a veto.

How to fill this in

Define how non-response, mid-process withdrawal, deadlock, and procedural failure are handled. Each should have a documented escalation path.

If a party does not respond within the defined window:

If a party withdraws mid-process:

Deadlock (all resolution attempts exhausted):

Procedural failure review:


Facilitator Selection and Replacement

RCOS clauses: 6.3.1, 6.3.3

Why name how the Facilitator is chosen or replaced?

A facilitator who is implicated in the conflict — or socially aligned with one party — cannot hold the process fairly, no matter how good their intentions. Naming selection and replacement rules up front means the affected party does not have to fight for a neutral hearing while already under stress.

How to fill this in

State the default facilitator role, the rule when the facilitator is a party, the right to decline, and any provision for external facilitation.

Privacy and Information Access Boundaries

RCOS clauses: 6.5.3

Why bound information flow so tightly?

Conflict records contain the most sensitive material the community holds. Leaks, gossip, or casual disclosure cause second-order harm and deter future reporting. Explicit boundaries — what stays with the parties, what reaches Full Members, and when records are destroyed — make confidentiality enforceable rather than aspirational.

How to fill this in

State which steps are fully confidential, what minimum information may be disclosed at the governance step, the retention period, and the non-disclosure obligation.

Safeguards

RCOS clauses: 6.3.1, 6.3.2, 6.3.3, 6.3.4, 6.3.5

Why do safeguards exist on top of the ladder?

Process alone does not protect the party with less power. Retaliation, bad-faith complaints, conflicted facilitators, and unreviewed safety risks can all neutralize an otherwise good procedure. Safeguards are the backstops that keep the ladder functional when incentives push against honest reporting.

How to fill this in

For each safeguard, state the rule and the consequence when it is violated. Power-differential cases need their own intake channel.

  • Anti-retaliation:
  • Bad-faith complaints:
  • Facilitator conflict of interest:
  • Process pause:
  • Safety-critical immediate action:
  • Power differential — separate intake channel:
  • Role suspension during review:

Ratification Record

  • Adopted:
  • Decision type: Strategic
  • Version:
  • Decision record:

RCOS Blueprint by EcoHubs

A modular operating system that defines how intentional communities organize — from governance and roles to resource sharing and conflict resolution — in support of resilience, fairness, and regeneration.

Connect

© 2026 EcoHubs Platform. All rights reserved.