The Conversation Nobody Remembers
In April 2024, three members of our Sanctuary spent forty minutes in Council arguing about whether we'd already decided to allow short-term guests in the meditation space.
Half the room remembered approving it. Half remembered rejecting it. One person remembered we'd "tabled it for later." We had no record. The decision (whatever it had been) had vanished.
We re-decided that night. We also adopted a rule: every decision gets documented within 48 hours, with the question, the participants, the outcome, and the reasoning. No exceptions.
That single rule has saved us probably eighty hours of repeated argument over the last two years. Documenting decisions is the most undervalued practice in community life. This piece is about why it matters and how to do it without making it feel like paperwork.
Why Memory Is a Lie
The human brain is excellent at forgetting decisions. Communities are even worse than individuals because each member remembers a different fragment.
Six months after a decision, you'll have:
- One member who remembers it clearly and correctly
- Two members who remember the discussion but not the outcome
- Three members who remember a different outcome
- Two members who weren't there and have no idea what was decided
- One member who insists it was "more nuanced than that"
This is the natural state of group cognition. Memory failures aren't a personal flaw. The only solution is a written record everyone can point to.
A community without documented decisions is rebuilding its own past every six months. That's exhausting. It also makes new members feel permanently behind, because they can't access the institutional memory that lives only in the elders' heads.
What a Decision Record Actually Needs
A decision record doesn't need to be elaborate. It needs five things:
1. The question. What was being decided, in one sentence. 2. The date and the participants. Who was in the room, who was absent. 3. The outcome. What was actually decided. If it was a sociocratic process, who consented, who stood aside, who objected. 4. The reasoning. Why this and not the alternatives. Two or three sentences. 5. The next step. Who's doing what by when, if anything.
That's it. Five fields. Two minutes to fill out for most decisions, ten minutes for big ones.
In our Sanctuary, every Proposal becomes a Scroll in the Library after it passes. Each one is searchable, dated, and linked to the Council Gathering it came from. New members can scroll back through three years of decisions in an hour and have a real grip on how the community got to where it is.
The Hard Part: Writing It While Tired
Most decisions get made at the end of meetings. Everyone's tired. The temptation is to wrap up, go home, and "write it up tomorrow." Tomorrow becomes never.
The fix: write the decision before you leave the room.
We assign a notes-keeper at the start of every Council. Their job is to capture each decision the moment it's made. Two minutes per decision. The room waits while they read it back. Anyone can correct. Then we move on.
This adds about 10 minutes to a typical meeting and saves about 90 minutes of recovery work later. It's the best trade in community governance.
If you're using a tool like ARA, the Council module prompts you to write the decision summary before closing the Proposal. The friction is built in. Without that, you have to manually enforce the discipline.
What Counts as a "Decision"
Communities often miss this: not every Council outcome is a decision. Some are agreements to gather more information. Some are punts. Some are explicit non-decisions ("we discussed it, we're not deciding now").
Document all of them. Especially the non-decisions.
A non-decision is the highest-risk thing to leave undocumented, because two months later half the community will think a decision was made and half won't. The non-decision is the source of the most "wait, what did we decide?" conflicts.
Write it down. "We discussed X. We did not reach a decision. Bringing it back in two weeks with a more concrete proposal."
That sentence prevents twelve future arguments.
Who Sees the Record
Make decisions public to anyone they affect. In a small community, that's usually everyone.
Resist the urge to keep "sensitive" decisions in a private folder. The friction of "should I share this" inevitably becomes "I forgot to share this." Default to open.
We keep three categories of visibility:
- Open to everyone in the Sanctuary (most decisions)
- Open to current members only (rare; HR-style sensitive matters)
- Open to the people involved (interpersonal mediation outcomes, kept narrow on purpose)
About 95% of decisions land in the first category. The visibility itself is the accountability. The record means a steward can't quietly drift the community in a direction nobody approved.
The Annual Re-Read
Once a year, sit down with the last twelve months of decisions and read them.
This is one of the most underrated practices in community governance. You'll notice patterns you couldn't see while making the decisions:
- Three decisions about the same topic, slowly drifting in opposite directions
- A decision you made six months ago that you've quietly stopped honoring
- A pattern of empowering working groups too late
- A pattern of returning the same conflict to Council without resolution
We call ours the "Decision Audit." Two members, three hours, once a year. They produce a one-page Scroll of patterns observed. The community discusses it at the next Council. About a third of our governance changes come from this practice.
Documenting Through Conflict
The hardest decisions to document are the ones where the room is heated.
Here's the discipline: even when emotions are high, capture the question, the outcome, and the next step. Skip the reasoning if it's too charged to write neutrally. Just get the basic facts down.
Two days later, when the room has cooled, the notes-keeper can add the reasoning. By that time, you can write it without bias.
Skipping documentation during conflict is how communities re-litigate the same fight three times. The record short-circuits that loop.
The Record Outlasts the Members
A community that documents its decisions has institutional memory. That memory outlasts any individual member.
When founders leave, the decisions stay. When new members join, they can read what was decided and why. When you're trying to remember whether you really did approve that policy in 2023, you can check.
This is the deepest value of the practice. Documentation is how a community becomes a real institution. Without it, the community lives only in its founders' heads, and every founder departure takes a chunk of the community's memory with it.
In our region, I know two communities that lost their primary stewards in the last five years. The one that documented decisions kept going almost without missing a beat. The one that didn't dissolved within eighteen months. The members were the same caliber. The difference was the record.
Start Today
If your community has no decision documentation practice, here's the smallest possible start:
- Open a shared document or a Scroll
- Title it "Decisions Log"
- The next decision your community makes, write it down with the five fields above
- Repeat at every Council
That's it. Don't wait for a perfect system. Don't try to retroactively document the last five years. Just start with the next one.
In six months you'll have 30 to 50 documented decisions. In two years you'll have a real archive. In five years you'll have something irreplaceable.
If you want the scaffolding without the overhead, ARA's Library runs the Scroll pattern end-to-end: every Proposal in the Council auto-generates a linked decision record, versioned, searchable, attributed. You stop having to remember to document. The system does it.
The quiet power of documenting decisions is that it compounds. Each entry is small. The accumulation is enormous. And the day someone needs to know what you decided about that compost shed in 2024, the answer will be there.
Write it down. Future you will be grateful.