The Problem with Snapshots
A survey is a photograph. It captures opinion at one moment in time, from one sample of people, about one framing of the question. By the time results are published, the community has moved on. New information has emerged. People's views have evolved.
Worse, a survey's questions are designed by the researcher, not the community. The framing constrains the answers. "Do you support or oppose the development?" doesn't allow for "I support it if the affordable housing percentage is increased" or "I need more information about the traffic study."
The Living Requirement Document is not a photograph. It's a living map — continuously updated, version-controlled, and structured to capture the full dimensionality of community perspective.
Anatomy of an LRD
A Living Requirement Document has four sections, each serving a different purpose for decision-makers:
Section 1: Strong Consensus (70%+ Agreement)
These are the items where the community's underlying values converge across demographic groups. Not "70% voted yes" — but "70% of participants, across all demographic segments, express this value or need when their perspectives are analyzed at the values level."
Example:
Business access on Main Street must be preserved or improved
Confidence: 94% | 3,616 of 3,847 participants
Represented across all demographic groups
This tells a decision-maker: whatever you do, this is non-negotiable for the community.
Section 2: Conditional Consensus
These are items where agreement exists but is contingent on specific conditions being met. This is the most valuable section for decision-makers because it reveals how to unlock support.
Example:
Bike lane is acceptable IF alternative parking is provided within 2 blocks
Support with condition: 71% | Support without: 38% | Delta: +33%
A poll would have shown 38% support. The LRD shows 71% support is available — you just need to address the parking condition. That's a completely different decision landscape.
Section 3: Genuine Divergence
These are real value conflicts that cannot be resolved through better communication. They require democratic resolution — voting, compromise, or executive decision.
Example:
Funding source: New dedicated tax (44%) vs. Reallocate existing budget (41%) vs. Undecided (15%)
Note: This is a genuine value divergence requiring democratic resolution.
The LRD is honest about what synthesis can and cannot solve. Not every disagreement is a communication failure.
Section 4: Confidence Gaps
This section flags where the data is weak — which communities are underrepresented and where targeted outreach is needed before the LRD should be treated as representative.
Example:
⚠ Renters under 25: 8% of population, 2% of sample
Recommendation: Targeted outreach through university channels
This radical transparency about data quality is something surveys rarely provide.
Version Control for Community Intent
LRDs are versioned like software. Every new batch of interviews triggers a re-synthesis, producing a new version. Decision-makers can see how consensus has evolved over time, what new concerns have emerged, and whether outreach efforts have closed confidence gaps.
This means an LRD is never "done." It's a living document that grows more representative and more nuanced as more perspectives enter the system. Version 2.4 is more trustworthy than version 1.0, and the system tells you exactly why.
How LRDs Compare
| Feature | Survey | Poll | Town Hall | LRD |
|---|---|---|---|---|
| Input depth | Low (scales) | Very low | High (doesn't scale) | High (scales) |
| Captures conditions | No | No | Sometimes | Yes, systematically |
| Identifies consensus | No | Partially | No | Yes |
| Flags data gaps | Rarely | No | No | Yes |
| Updates over time | No | No | No | Continuously |
| Separates values from positions | No | No | Depends on facilitator | By design |
Who Uses LRDs?
Living Requirement Documents are designed for any entity that needs to understand what a population actually wants:
- ◇City planners use them to design proposals that have community support before the first public hearing
- ◇School boards use them to allocate budgets in alignment with parent and teacher priorities
- ◇DAO governance uses them to write proposals that reflect member values, not just token-holder votes
- ◇Corporate HR uses them to understand employee needs with more fidelity than annual engagement surveys
- ◇Nonprofits use them for community needs assessments that capture conditional support and genuine barriers
The Shift from "What Do You Think?" to "What Do You Need?"
The fundamental innovation of the LRD is that it captures needs rather than opinions. An opinion is brittle — it changes with framing, mood, and information. A need is stable — it reflects what a person actually requires to thrive.
When governance is built on needs rather than opinions, decisions become more durable, more legitimate, and more likely to actually solve the problems they're meant to address.
That's not a incremental improvement on the survey. It's a different paradigm for understanding collective intent.