State the question
Put the proposal, scope, evidence, and decision rule in one place.
Governance for groups with shared stakes
CivilEdge brings proposals, evidence, votes, approvals, payments, and the final record into one calm workspace.
01DecideReview the proposal
02ApproveApprove the work
03VerifyCheck the record
a2f8…71c0Transparent and reliable by design
Property management handles daily operations. CivilEdge is the place for the shared decision: what was proposed, what supported it, who had authority, whether the group had enough participation, and what happened next.
That lets CivilEdge work beside a property manager, bookkeeper, cap table, or no administrative system at all.
The slash suggests a decision brought to resolution; the dot is what remains: a clear place to return to.
One decision, one clear thread
Put the proposal, scope, evidence, and decision rule in one place.
Give members a clear deadline, role, and way to participate.
Leave behind the decision, next step, and record someone can return to.
A better shared record
Explore how the same planning framework changes for a small association, a larger community, an investment group, a syndication, or a joint LLC.
Open the guided demosOne system, right-sized
The circles on the left show an example size or range: homes, investors, or ownership interests. In Base Ten, joint owners count as one unit unless they hold separate interests. The structure follows the shared stake—not the group-text headcount.
For owners making decisions together. Start with a ten-member Joint LLC, then explore an investment circle and a larger syndication.
Joint LLC
Meet Base Ten: a multifamily LLC with ten voting interests, shared expenses, and a clear record of who may approve what.
Member roles · project approvals · owner drawsExplore this workspaceProperty investment circles
Move from diligence to disclosure, quorum, authorization, and payment without losing the exact record everyone relied on.
Diligence · conflicts · payment gatesExplore this workspaceReal estate syndications
Keep offering terms, capital calls, related-party disclosures, asset decisions, quarterly reports, and distributions connected across the life of a deal.
LP consent · capital events · distribution recordExplore this workspaceFor neighbors managing shared responsibilities. See a small building at Juniper Court and a larger community at Hearthside Commons.
Small associations
Keep repairs, shared expenses, neighbor comments, and decisions together without making a small building feel institutional.
One approver · simple quorum · shared repair recordExplore this workspaceLarger communities
Coordinate elections, statutory deadlines, vendor evidence, and distributed approvals across a larger membership.
Election integrity · records clock · sourced comparisonsExplore this workspaceBase Ten · Multifamily LLC demo
A $24,000 shared entrance upgrade. Review the plan, collect votes, and save the outcome.
Everyone sees this rule before voting. Abstentions count toward quorum, but not approval. These are example agreement terms.
Everyone starts with the same proposal and the same decision rule.
Unit 03 has two joint owners and one ballot. Units 01 and 02 share an owner, but each unit keeps its entitlement. The percentage schedule is an illustrative allocation of shared area; it does not imply that an LLC member owns a particular apartment.
In the automatic example, seven units vote yes: 7 of 10 passes the equal-vote rule, while their combined 58% falls short of the percentage rule. Switch rules and replay to compare.
Simulation only. No real ballots, encryption, bank transfers, or legal eligibility checks. Leaving this demo or refreshing resets the animation and its ballots.
A plan for transparency and accountability
The production system is intended to show the rule, evidence, participation, approvals, and final record without exposing information a member does not need to see. The current site demonstrates that workflow; it does not yet provide production privacy or cryptographic verification.
Planned private-ballot flow
Illustration only. A production receipt needs an independently checkable final record before it can confirm inclusion.
The planned voting design checks eligibility, issues a one-time voting pass, and separates identity from ballot content. A receipt number is intended to let a voter confirm inclusion without revealing the choice.
Goal: confirm acceptance and inclusionThe planned access model gives authorized finance roles individual account details. Other members see useful totals without a public list of names. Payment status and voting rights remain separate.
Goal: show status, not namesEach proposal can state who may vote, when it closes, the participation required, and what it takes to pass. Production enforcement of those rules remains implementation work.
Plan: notice, quorum, and threshold checksThe workflow keeps bids, scope, insurance, conflicts, invoices, milestones, and approvals together. A production payment integration would still need server-side permissions and bank-side controls.
Plan: evidence → approval → paymentThe planned record design gives each canonical entry a timestamp and SHA-256 fingerprint linked to the prior entry. External copies or anchors are still needed to make later changes independently detectable.
Goal: detect changed or missing entriesAn association, investment group, cooperative, or nonprofit can map its own notices, voting, approvals, records, and access rules. Those profiles require review against governing documents and applicable law.
Plan: reviewed, versioned rulesSoftware, implementation, and support
Groups can begin with a workflow review: governing documents, decision types, roles, privacy needs, and payment controls. From there, CivilEdge can be configured as software the group runs itself or paired with implementation support.
A practical launch
Nothing becomes an automated rule until the collective can see it, understand it, and approve it.
Gather the operating agreement, bylaws, policies, ownership roster, signing authority, and the laws that shape the collective.
Translate notice windows, quorum, thresholds, privacy, conflicts, retention, and payment controls into a reviewable workspace profile.
Verify roles, import current records, explain what each person can see, and run a small practice decision before anything consequential.
Move proposals, votes, vendor packets, approvals, transfers, and records requests through the agreed process—with help available when needed.
Publish the outcome, issue individual receipts, export the audit record, and schedule the next review of rules and access.
A planned workspace for proposals, voting, evidence, approvals, payments, records, and member access.
A structured setup for groups that want documents, roles, and real-world procedures translated carefully before launch.
Human help for high-stakes moments such as elections, capital events, contested decisions, vendor reviews, and record production.
Who usually starts the conversation
The organization usually adopts the system because it owns the process and the record. A board member, manager, investor, attorney, bookkeeper, or resident may be the first person to identify the need.
Association boards and management firms; syndication sponsors and fund administrators; LLC managers; cooperative, nonprofit, and investment-committee leaders.
Planning question: where do procedural gaps, unclear authority, or scattered records create the most risk?Association counsel, securities and real-estate attorneys, CPAs, bookkeepers, election inspectors, property managers, and fund-administration partners.
Planning question: which reviewed rules and professional advice should become repeatable workflow?Plain-language guides, receipt checks, decision checklists, and a “bring CivilEdge to your board or manager” path—useful without asking one resident to buy the whole system.
Planning question: what should a member be able to understand, confirm, or question without special access?