The Wednesday a Block Wasn't a Block
It was a Wednesday evening in February 2024. Our Council had spent forty minutes on what should have been a fifteen-minute proposal: replacing the kitchen's plastic 30-liter compost bin with a steel 50-liter one. Someone had brought a brochure. Someone else had brought pricing. The room was warm and slightly bored.
When the consent round started, Eva said, "I block this."
The room stopped. Henrik, who was facilitating, took a careful breath. "What's your objection?"
"I just don't think we need a new one yet," Eva said.
We spent another twenty-five minutes untangling that single sentence. Eva didn't mean she was blocking. She meant she preferred the current bin. She had reached for the word "block" because it was the loudest no in our vocabulary and she wanted to be heard.
The proposal eventually passed. Eva felt unheard. Pat, who'd brought the proposal, felt frustrated. The room felt confused. All because we hadn't agreed on what each of our words for no actually meant.
That night I started a Scroll. It became, across the next year, the field guide we wish we'd had at the start. This piece is that guide: a vocabulary for disagreement that holds across blocks, stand-asides, vetoes, and the principled objection that sits between them.
Why the Vocabulary Matters
Most communities use the same four or five words to mean wildly different things. A "block" in one Sanctuary is a hard halt of a proposal. In another, it's a strong concern. In a third, it's interchangeable with "stand-aside." The words drift.
When the vocabulary is fuzzy, three predictable things happen.
The strongest no in the room gets used too often. People who want to slow something down reach for "block" because it's the only verb that gets attention.
The weakest no gets ignored. Someone says "I stand aside" and the proposer hears "fine, that means yes." Six months later the stand-aside-er feels unheard and the proposer is confused about why.
Real principled objections get lost in the noise. By the time someone has a structural concern with a proposal, the room has heard so many vague "I'm not sure" reactions that the genuine objection sounds like more of the same.
Fixing this is mostly a vocabulary problem. Get the words right, write them down once, coach the room until they stick, and your decision-making changes texture inside a quarter.
The Four Forms of No
After running about three hundred consent rounds across two Sanctuaries, the working vocabulary I'd commit to for any community is four words.
Veto. A structural halt held by a specific role or body. Rare. Exists for safety, legal, or trust-preservation reasons.
Block. An individual member's full stop. Stronger than a preference. Carries an obligation to help find a way forward.
Objection. A specific, principled concern that the proposal harms the group or violates an agreement. Comes with a willingness to amend.
Stand-aside. A public reservation. The proposal proceeds. The member's concern goes on the record.
Most other terms ("I'm not on board", "this doesn't sit right", "I'm uncomfortable") collapse into one of these four. Coach people toward the precise word. The mush is most of the problem.
The Veto
The veto is the rarest tool in community decision-making. It belongs to a role or a body. An individual member can't hold it alone.
Examples that show up in practice:
- A Treasurer vetoes an expense that would exceed the agreed reserve floor.
- A Steward vetoes a guest-policy change that breaches an existing safeguarding agreement.
- A Council body vetoes an operational decision made by a working group that exceeded its mandate.
A veto is a structural check. The role exists precisely so the community has a guardrail on certain kinds of drift, and the person holding the role is expected to use it sparingly and with explanation.
We've used a veto four times in five years. Three were financial. One was safeguarding. Each one was unwelcome in the moment and obviously right within a month.
If your community has no vetoes anywhere in its structure, you're betting that consent rounds alone will catch every structural risk. That bet usually loses by year five. Build in two or three narrow vetoes. Make their scope explicit. Then trust them.
The Block
The block is the heart of consensus tradition. It's the individual member's full no. A blocked proposal cannot pass in its current form.
A real block carries weight. Three things have to be true.
The blocker has heard the proposal and the discussion. They aren't blocking on first read.
The block names a harm or a violation of an agreement the community has already made. A preference doesn't qualify.
The blocker is willing to participate in finding an alternative. A block opens a different conversation; it doesn't end the conversation.
Blocks should be rare. In our Sanctuary, we've had maybe seven real blocks across five years of Council. Each one halted something that turned out to be worth halting. The few that aged badly are still worth honoring; the cost of one preserved bad decision is much smaller than the cost of a community where members feel they can't stop something they truly believe is harmful.
If your community hasn't had a single block in three years, your block bar is probably too high. People are swallowing concerns. Lower the bar. Let blocks happen. Trust the process to resolve them.
The Principled Objection
The objection is the sociocratic cousin of the block. Subtly different. Important.
A block halts a proposal outright. An objection holds the proposal in place until the concern has been heard and addressed.
The framing matters. A block says "this can't go through." An objection says "this can't go through yet, here's what we need to figure out first."
In practice, most concerns that surface in a consent round are objections. The proposal is mostly right. There's a specific clause or implementation detail that worries someone. The amendment round addresses it. The proposal passes in a revised form.
Objections do the slow, careful work of refining proposals into things the whole room can live with. They sit between yes and no, and most members default to one or the other, which is why objections are the most underused tool in community governance.
Coach the room into using one specific phrase: "I have a concern that needs addressing before I can consent." Repeated enough, it becomes reflex. New members pick it up by the third Council.
For the broader practice these terms sit inside, What Consent-Based Decision Making Actually Looks Like is the companion piece, and Sociocracy vs Consensus covers when each tradition's vocabulary applies.
The Stand-Aside
The stand-aside is the quietest of the four and, in my experience, the most powerful.
A stand-aside means: I am not going to block this, and I am also not going to pretend I'm enthusiastic. The proposal passes. The community proceeds. My concern is documented.
Stand-asides do three things at once.
They let dissenters stay honest without halting the work. Members who would otherwise vote yes with hidden reservations get a public place to put the reservation.
They create accountability if the decision ages badly. Six months later, when the kitchen renovation has overrun by €1,800, the stand-aside is there in the record. Nobody has to argue about who warned whom.
They protect the proposer. A proposal that passes with two stand-asides is being approved with eyes open. That visibility makes implementation easier and prevents the silent backlash that comes when a decision quietly disappoints half the room.
If your community is averaging zero stand-asides per quarter, members are flattening their concerns into yeses they don't fully mean. Coach toward more stand-asides. Treat their presence as a sign of health.
The Quiet No
The fifth thing is silence that should have been a word.
Most disagreement in community life never gets expressed in any of the four forms above. It shows up as quiet drift: a member who stops coming to Council, a working group that stops meeting, a chore that stops getting done, a member who slowly, across six months, becomes a kind of ghost in their own home.
The quiet no is the most expensive form of disagreement. It can't be addressed because it hasn't been named. It corrodes everything around it.
The fix is upstream. Build a culture where the four explicit forms feel safe enough to use. If a member would rather drift than object, your community has trained them that objecting is more costly than disappearing. That training can be undone, but only by holding a few hard moments well, in public, so the next person knows the room will catch them.
Coaching the Room
Vocabulary takes hold through coaching, repeatedly, until the words become reflexive. Writing it on a wall isn't enough.
Three coaching moves that work.
When someone says "I'm not sure about this," the facilitator gently asks, "Is that a preference, an objection, or a stand-aside?" Most people pause and pick one. The pause itself is the practice.
When someone says "I block," the facilitator follows with: "Can you name the harm or the violation?" If they can, the block is real. If they can't, it's usually an objection that hasn't quite been formed yet.
When someone says "I consent" with visible reluctance in their body, the facilitator gives them an opening: "Are you sure that's a consent and not a stand-aside?" People often reach for the wrong word out of habit. The opening lets them choose more honestly.
Expect this coaching to be awkward for the first six months. Expect it to become natural by year two. Expect new members to learn the vocabulary in their first onboarding cycle, because the room around them is already using it.
Where the Record Lives
A vocabulary is only as durable as the record it sits inside. Each Proposal in ARA's Council module carries an explicit field for each member's response: Consent, Stand-aside, Objection, Block. The history persists. New members can scroll back a year and see exactly how the room voted, which concerns were named, and how the proposal evolved.
That visibility is what lets the vocabulary calcify into culture. Without it, the words drift back into mush within months. With it, the next person to facilitate a consent round inherits the discipline of the last twenty rounds.
One Last Note
Spend an evening this month writing your community's four words down. Talk about what each one means. Disagree about them. Land somewhere. Stick the page on the wall of the room where Council happens.
Six months later, your consent rounds will be shorter, your blocks will be rarer, your stand-asides will be more frequent, and the quiet no will start to thin. That's the trade for a single evening of vocabulary work.
Eva left our Sanctuary in late 2024, for reasons unrelated to the compost bin. Before she left, she told me the night of the bin was the moment our Council got serious. The bin was incidental. What mattered was that we finally agreed that the word "block" meant something specific, and that her real concern hadn't been a block at all. It had been a stand-aside she didn't yet know how to name. Once she had the word, she used it three more times across the next eight months. Each time, the room received it well.
That's the gift of a clear vocabulary. The room can hear you accurately. You can speak to it the same way. The disagreements don't disappear. They get smaller, faster, and much less expensive.