Consensus vs consent
One asks whether everyone agrees. The other asks whether anyone has a reasoned objection. That difference decides how your meetings feel in year three.
The two words are used interchangeably in almost every community that uses either, and the swap is expensive. Groups adopt “consensus” from a handbook, run something closer to consent in practice, and then spend years arguing about a rule nobody has written down.
| Dimension | Consensus | Consent |
|---|---|---|
| The question asked | Do you agree with this? | Do you have a reasoned objection? |
| Bar for passing | Everyone actively supports it | Nobody can name a paramount objection |
| Burden of proof | On the proposal, to win everyone over | On the objector, to say what is wrong |
| Standard applied | This is the best option we can find | Good enough for now, safe enough to try |
| Treats decisions as | Settled | Provisional, with a review date |
| Preference vs harm | Often blurred in practice | Explicitly separated |
| Typical failure | Stalls; whoever stays latest wins | Objections raised but never resolved |
| Scales to | Roughly 8–15 before strain | Larger, if circles are used |
What consent actually changes
Consent narrows the question. Not _do you like this?_ but _can you live with it, and can you point to a way it would harm us?_ A proposal passes when nobody can.That narrowing does two things. It moves the bar from enthusiasm to tolerability, which is a much lower bar — and deliberately so. And it puts the work on the person objecting: an objection has to be reasoned and has to be about the group’s aim rather than about taste. “I would have picked a different colour” is a preference. “This spends the repair fund we agreed to hold for winter” is an objection.
The phrase that carries the rest of it is good enough for now, safe enough to try. Consent expects to be revisited. A decision made this way is provisional by design, and that is precisely what makes it possible to say yes to something you are not thrilled about.
What consensus is actually for
None of that makes consensus the worse method. It is doing a different job, and it is better at that job.
Consensus produces buy-in that consent does not. When a group has genuinely talked a proposal into a shape everyone supports, the implementation is different — people carry it out because they own it rather than because it passed. In small groups doing emotionally loaded work, that is worth the extra hours.
It is also a better teacher. The amendment loop — raise a concern, change the proposal, test again — forces a group to hear each other in a way that a well-run consent round can skip. Groups that start with consensus and move to consent later often keep the listening habits, and they are the reason the second method works at all.
Where each breaks
Consensus fails to fatigue and to scale. Past ten or fifteen people, requiring universal agreement quietly hands a veto to whoever is most stubborn, most tired, or most articulate at eleven at night. The failure is rarely dramatic: attendance drops, decisions drift to whoever stayed, and proposals stop being tabled because nobody wants the meeting.
Consent fails to vagueness. The three common versions, in rough order of frequency: the group adopts the language without defining who may object and on what grounds, so everything is still unanimity wearing a new name; objections get raised but never resolved, so proposals stall in a queue nobody owns; or the review date is never set, and “good enough for now” silently becomes permanent.
When each is the right answer
Consensus suits you if the group is small, the work is relational, and you would rather spend three hours reaching real agreement than twenty minutes reaching a decision. It suits founding groups particularly well, where what you are really building is the ability to disagree safely.
Consent suits you if the group is past a dozen people, decisions are frequent and mostly operational, or your meetings have started to feel like endurance. It is also the right answer if you have noticed that one person’s reluctance can stop anything — consent gives you a principled way to distinguish that from a real objection.
Most communities that last end up using both: consent for the ordinary run of decisions, and something much closer to consensus for the small number that change what the community is. Writing down which decisions are which is the single most useful governance hour you will spend.
Sources & further reading
- 1 Beyond the Vote: Why the Most Resilient Communities are Replacing Consensus with Consent — the longer EcoHubs argument for consent
- 2 RCOS Core — Layer 2: Governance & Decision Logic — both methods specified side by side
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
Terms used here
- Consensus
- A decision method requiring the agreement of all participants. Powerful for trust, slow under scale and fatigue.
- Consent
- A decision passes when no one has a reasoned, paramount objection. Not the same as everyone thinking it is the best idea.
- Sociocracy
- A governance system organising a group into linked circles, each with its own domain, deciding by consent.
Still deciding?
- Cohousing vs ecovillage
They get used interchangeably and they are not the same thing. One is an architecture; the other is a purpose.
- Commune vs cohousing
The dividing line is money. One pools income and decides together how it is spent; the other shares a building and leaves your bank account alone.
- Intentional community vs commune
One is the category, the other is one option inside it — and a minority one. Most intentional communities are not communes.