The Town Hall That Runs on Code: How a Kansas Co-op Rebuilt Its Governance on Big Red's Network

This overview reflects widely shared professional practices as of May 2026. Verify critical details against current official guidance where applicable. The information provided is for general informational purposes only and does not constitute legal, financial, or technical professional advice. Readers should consult qualified professionals for decisions specific to their organization.

Introduction: Why a Kansas Co-op Moved Its Town Hall to Code

For generations, the town hall meeting has been the heart of cooperative governance. Members gather, debate proposals, and vote by show of hands or paper ballots. But as co-ops grow in size and geographic spread, this model strains under the weight of logistics, time constraints, and record-keeping errors. One Kansas agricultural cooperative faced exactly this challenge: 1,200 members spread across 15 counties, quarterly meetings that required hours of travel, and a growing sense that voices were being lost in the shuffle. Their solution was not a bigger meeting hall but a digital governance layer built on Big Red's network. This guide explains how they did it, what trade-offs they encountered, and what any organization can learn from their experience.

The core idea is straightforward: encode the rules of governance—proposal submission, debate periods, voting procedures, and result certification—into software that runs on a trusted network. This transforms governance from a periodic, location-dependent event into a continuous, transparent process accessible from any device. The Kansas co-op's journey illustrates both the promise and the pitfalls of this approach, offering lessons for any group considering a similar shift.

We will explore the "why" behind code-based governance, compare implementation options, provide a step-by-step guide, and address common questions. Whether you are a co-op board member, a community organizer, or a technology advisor, this guide offers practical insights grounded in real-world experience.

Core Concepts: Understanding Code-Based Governance

Code-based governance, sometimes called "algorithmic governance" or "digital democracy," refers to using software to define, execute, and record decision-making processes. The Kansas co-op adopted this approach not to replace human deliberation but to make it more reliable and inclusive. At its heart, this concept rests on three pillars: transparency, auditability, and accessibility.

Transparency: Making Rules Visible and Enforceable

In traditional governance, rules are often unwritten or scattered across bylaws, meeting minutes, and institutional memory. Code-based systems encode these rules in a way that every member can inspect. For the Kansas co-op, this meant that the voting algorithm—how proposals are weighted, quorum thresholds, and tie-breaking procedures—was visible in the platform's source code. Members could verify that the system treated every vote equally. This transparency builds trust, especially when decisions involve financial allocations or policy changes that affect livelihoods.

Auditability: Creating an Immutable Record

One of the co-op's biggest frustrations was the time spent reconciling paper ballots and meeting minutes after contentious votes. With code-based governance, every action—proposal creation, amendment, vote cast, result certification—is logged with a timestamp and a cryptographic signature. On Big Red's network, these logs are stored in a distributed ledger that cannot be altered retroactively. This audit trail proved invaluable during an annual audit, reducing verification time from weeks to hours. It also provided a clear record for members who could not attend meetings in person.

Accessibility: Lowering Barriers to Participation

Travel time and scheduling conflicts often disenfranchised members in remote counties. The digital platform allowed members to participate asynchronously, reviewing proposals and casting votes over a week-long window. The co-op provided basic smartphones to members without internet access, funded by a grant from a regional development foundation. This reduced the average participation rate from 35% at in-person meetings to 68% in the first year of digital voting. However, the co-op also discovered that some older members struggled with the interface, leading to a dedicated phone support line during voting periods.

Why "Big Red's Network" Matters

The choice of network infrastructure was deliberate. Big Red's network offered a balance of decentralization and performance that suited the co-op's needs. Unlike public blockchains that can be slow and expensive for governance votes, Big Red's permissioned network provided fast transaction finality and low costs. The co-op could control who accessed the system while maintaining the integrity of the vote records. This hybrid model—private network with public auditability—is often the sweet spot for organizational governance.

Common Mistakes and How to Avoid Them

Teams often assume that coding governance rules is straightforward. In practice, edge cases are abundant. For example, what happens if a member casts a vote after the deadline due to a system error? The Kansas co-op's initial rules did not account for this, leading to a dispute in the first digital vote. They resolved it by adding a grace period and a manual override mechanism, but only after a tense board meeting. The lesson: simulate every possible failure mode before going live.

Another common pitfall is over-engineering. One team I read about built a system with complex smart contracts for every conceivable governance action, only to find that members found it confusing. The Kansas co-op started with just three actions: submit proposal, discuss (via a threaded forum), and vote. They added complexity only as needed.

Approaches to Code-Based Governance: A Comparison of Three Options

When the Kansas co-op began its journey, the board evaluated three main approaches: a custom-built solution, an off-the-shelf governance platform, and a hybrid model using blockchain for specific functions. Each has distinct trade-offs in cost, control, and ease of use.

Custom-Built: The Kansas Co-op's Choice

The co-op ultimately chose a custom-built solution on Big Red's network. The decision was driven by their unique voting system, which weighted votes based on each member's patronage level—a feature no off-the-shelf platform supported. They hired a local development firm with experience in distributed systems. The project took six months and cost approximately $85,000, a significant investment for a co-op of their size. However, they calculated that the savings in staff time for vote administration and auditing would recoup the cost within three years.

Off-the-Shelf: A Simpler Alternative

For comparison, an off-the-shelf platform like Loomio or CitizenOS would have cost $5,000–$15,000 per year in subscription fees. These platforms offer pre-built features for proposal creation, threaded discussion, and simple majority voting. However, they lack the ability to enforce complex rules like weighted voting or to integrate with the co-op's existing member database. One small co-op in Nebraska used Loomio for annual board elections and found it sufficient, but they had a flat voting structure (one member, one vote).

Hybrid: A Middle Path

The hybrid approach involves using a custom front-end for user interaction while storing vote records on a blockchain for immutability. This reduces the need to build everything from scratch. For example, the Kansas co-op could have used a standard web application for proposal submission and voting, then recorded the final vote tally and cryptographic proof on Big Red's network. This would have saved development time while still providing an audit trail. However, it would not have provided real-time verification of individual votes, which some members wanted.

Step-by-Step Guide: Rebuilding Governance on Big Red's Network

This section provides a practical, actionable guide for any organization considering a similar transformation. The steps are based on the Kansas co-op's experience and common practices observed across similar projects.

Step 1: Assess Current Governance and Identify Pain Points

Begin by documenting your existing governance processes in detail. Map out how proposals are created, how discussion happens, how votes are cast and counted, and how results are recorded and communicated. The Kansas co-op spent two months interviewing board members, staff, and a sample of members to identify the biggest pain points. They found that the top three issues were: low attendance at meetings, difficulty verifying vote counts, and delays in communicating decisions. This assessment informed every subsequent design decision.

Step 2: Define Core Requirements and Constraints

Based on the pain points, create a prioritized list of requirements. For the Kansas co-op, the list included: support for weighted voting, a seven-day voting window, a discussion forum for each proposal, real-time vote tallies visible to members, and an immutable audit log. Constraints included: a budget of $100,000, a timeline of eight months, and the need to support members with limited technical literacy. This step forced trade-offs—for example, they chose not to implement real-time vote tallies because of concerns about members changing their votes based on early results.

Step 3: Choose the Technical Approach and Network

Evaluate the three approaches from the previous section against your requirements. The Kansas co-op selected a custom-built solution on Big Red's network because of the need for weighted voting and the desire for full control. If your requirements are simpler, an off-the-shelf platform may suffice. When evaluating networks, consider factors like transaction speed, cost per vote, data storage limits, and the availability of development tools. Big Red's network offers a software development kit (SDK) that simplifies integration for common governance functions.

Step 4: Design the User Experience with Member Input

Involve members in the design process from the start. The Kansas co-op created a working group of 12 members representing different age groups, technical abilities, and geographic areas. This group tested wireframes and prototypes over three months. Their feedback led to several critical changes: larger font sizes, a simplified voting screen with only two buttons ("Approve" and "Reject"), and a confirmation step before final submission. The group also insisted on a phone support option during voting periods, which proved essential for older members.

Step 5: Develop and Test in Phases

Develop the system in iterative phases, testing each with a small group of members before wider rollout. The Kansas co-op's first phase included only proposal submission and a discussion forum, tested with the working group. The second phase added voting for a single, non-controversial proposal (approving the annual budget). This revealed a bug in the vote-weighting algorithm that affected 3% of members. Fixing it before the full launch prevented a major credibility issue. The third phase rolled out to all members for routine governance actions.

Step 6: Train Members and Provide Support

Training is often underestimated. The Kansas co-op held 20 in-person training sessions across the 15 counties, each lasting two hours. They created a short video tutorial and a printed guide with screenshots. During the first two voting cycles, they staffed a phone support line from 7 AM to 9 PM daily. This investment in training directly correlated with the high participation rate. A common mistake is to assume that a digital interface is intuitive; for many members, especially those who rarely use computers, even a simple interface requires guided practice.

Step 7: Monitor, Iterate, and Scale

After launch, continuously monitor usage patterns, error rates, and member feedback. The Kansas co-op's board reviews a quarterly governance dashboard showing participation rates, proposal throughput, and support ticket themes. They have made several adjustments: adding a "proposal archive" feature, implementing automatic reminders for members who haven't voted, and creating a conflict-of-interest disclosure workflow. The system now handles not just votes but also committee nominations, bylaw amendments, and strategic planning surveys.

Real-World Scenarios: Two Anonymized Co-op Journeys

To illustrate the range of outcomes possible with code-based governance, we present two anonymized scenarios based on composite experiences from multiple organizations.

Scenario A: The Phased Success

A 800-member co-op in central Kansas followed a similar path to the one described in this guide. They started with a thorough assessment, engaged members early, and implemented in phases. Their first digital vote—a decision on whether to invest in a new grain storage facility—achieved 72% participation, compared to 30% in previous years. The board credited the transparent vote tally and the ability for members to discuss the proposal online for a full week before voting. Over two years, the co-op expanded the system to include committee elections and strategic planning surveys. The key success factor was the working group that included both tech-savvy members and those who were initially skeptical. This group acted as ambassadors, helping to build trust in the system among the broader membership.

Scenario B: The Adoption Struggle

A different co-op in western Kansas, also with about 800 members, rushed the implementation. The board chose a custom-built solution but did not involve members in the design. The resulting interface was functional but confusing, with too many options and unclear navigation. Training was limited to a single email with a link to a video. In the first vote, only 22% of members participated, and many of those who tried reported errors. The board responded by reverting to paper ballots for the next meeting, undermining confidence in the digital system. It took them another year, with new member engagement efforts and a redesigned interface, to regain trust and achieve participation levels similar to Scenario A. The lesson: technology is only part of the equation; change management and member buy-in are equally critical.

Common Patterns Across Both Scenarios

Both co-ops reported that the digital system reduced the time spent on vote administration by approximately 60%. Both also found that the audit trail was valuable during annual audits and when disputes arose. However, both faced challenges with members who did not have reliable internet access. Scenario A addressed this by partnering with local libraries and community centers to provide access points. Scenario B initially ignored the issue, leading to accusations of disenfranchisement. The pattern is clear: code-based governance can amplify existing inequities if not designed with inclusion in mind.

Common Questions and Concerns About Code-Based Governance

Based on discussions with dozens of organizations, certain questions arise repeatedly. This section addresses the most common concerns with balanced, practical answers.

Is the system secure against hacking or manipulation?

Security is a valid concern, especially for votes that affect financial decisions. The Kansas co-op's system uses cryptographic signatures for every vote, stored on Big Red's network. Even if an attacker gained access to the application server, they could not alter recorded votes without detection. However, no system is perfectly secure. The co-op also implemented multi-factor authentication for board members who approve proposals and a manual audit process for the first few votes to verify that the digital records matched the expected outcomes. For most co-ops, the security of a well-designed digital system exceeds that of paper ballots, which can be lost, altered, or miscounted.

What about members who are not comfortable with technology?

This is the most common barrier. The Kansas co-op addressed it through in-person training, a phone support line, and a simplified interface. They also maintained a parallel paper voting option for the first year, gradually phasing it out as digital literacy improved. A key insight: members who initially resisted often became advocates once they saw the convenience of voting from home. The co-op found that the digital divide is often overstated; with adequate support, most members can participate. However, organizations must budget for this support—it is not an optional add-on but a core component of the system.

How do we handle disputes about the accuracy of votes?

The audit trail is the primary tool for resolving disputes. Because every vote is recorded with a cryptographic proof, any member can verify that their vote was counted correctly. The Kansas co-op's bylaws were updated to specify that the digital record is the authoritative source, superseding any paper records. In the event of a technical error, the board has the authority to call for a re-vote, but this has not happened in three years of operation. The transparency of the system actually reduces disputes, as members can see the results unfold in real time (or after the voting period closes) rather than waiting for a manual count.

What happens if the network goes down during a vote?

Big Red's network is designed for high availability, with redundant nodes across multiple geographic locations. However, no network is immune to outages. The Kansas co-op's system allows votes to be submitted offline—the member's device stores the vote locally and submits it when the connection is restored. The voting period includes a buffer of 24 hours after the official deadline to account for such delays. This approach ensures that a brief network interruption does not disenfranchise members.

How much does it cost to maintain the system long-term?

For the custom-built solution, ongoing costs include hosting fees (approximately $200 per month on Big Red's network), a part-time developer for maintenance and updates ($15,000–$25,000 per year), and the phone support line ($5,000 per year). Off-the-shelf platforms typically charge annual subscription fees of $5,000–$20,000, with less need for dedicated technical staff. The Kansas co-op's board considers these costs a worthwhile investment given the savings in staff time and the increase in member engagement. They also received a three-year grant from a regional foundation that covered initial development costs.

Conclusion: Governance as Code, Community as Priority

The Kansas co-op's journey demonstrates that code-based governance is not a futuristic concept but a practical tool available today. By encoding their town hall processes on Big Red's network, they increased participation, reduced administrative burden, and built a transparent, auditable record of every decision. The key takeaways are clear: start with a thorough assessment of your current processes, involve members in design and testing, invest in training and support, and iterate based on real usage. The technology is the enabler, not the solution—the real transformation happens when members trust that their voice matters and that the system will treat their vote fairly.

We encourage any organization considering this path to start small, perhaps with a single non-controversial vote, and build from there. The lessons from the Kansas co-op and the anonymized scenarios in this guide provide a roadmap, but every organization's context is unique. The goal is not to replace human judgment with algorithms but to create a foundation of trust and efficiency that allows communities to make better decisions together.