HOA Voting Software for Elections and Ballots

Elections are the highest-risk governance event a volunteer board runs

Most board operations carry low legal exposure. Elections do not. The combination of fiduciary authority, member rights, and state-specific procedural requirements means that a botched election can produce homeowner lawsuits, court-ordered re-runs, and personal liability for board members who signed off on flawed results.

We built the election workflow in BoardStack because we could not find a system that enforced secret ballot separation at the data layer, tracked quorum in real time, and gave the inspector of elections a governed workflow instead of a pile of paper envelopes.

The three procedural failures that invalidate HOA elections

1. Quorum not documented

A meeting that does not reach quorum cannot conduct binding business, including electing directors. Most boards know the quorum threshold is in their bylaws but track it with a head count and a spreadsheet. When proxies arrive late, when someone forgets to count absentee ballots, or when the count is disputed afterward, there is no reliable record.

California specifically allows mailed and electronically delivered ballots to count toward quorum under Civil Code Section 5115, which means the quorum calculation runs in parallel with ballot collection rather than at the meeting itself. That requires a real-time running count, not a day-of tally.

2. Secret ballot requirement violated

California’s Civil Code Section 5100 requires secret ballots for director elections and specified membership votes. The legal model is a double-envelope system: the outer envelope identifies the voter, the inner envelope holds the ballot, and the two are separated before counting so that no one can link a vote to a voter. Other states do not always mandate this by statute, but most HOA attorneys recommend the practice because commingled records are trivially easy to challenge.

Email-based voting, Google Form elections, and any system that logs votes to voter accounts all fail this test. The secret ballot requirement is not about paper — it is about data separation.

3. No inspector of elections, or an inspector without a workflow

California Civil Code Section 5110 mandates an inspector of elections independent of the board and candidates. The inspector receives ballots, counts them, determines whether quorum was achieved, and certifies the results. Most communities either skip the role entirely or appoint someone who works from a paper printout with no formal chain of custody.

When results are challenged — and in contentious elections they usually are — the inspector needs to show a documented record: when each ballot was received, whether it was valid, how the count was conducted, and when results were certified. Paper does not provide that record.

What the BoardStack election workflow covers

BoardStack handles elections as a governed workflow with four interlocking pieces:

Ballot issuance and voter identity. The system records which homeowner received a ballot. The ballot itself is stored without the voter link. Proxies are recorded in the same workflow and count toward quorum automatically.

Running quorum count. As ballots are returned and proxies are recorded, the quorum meter updates. Boards know before the meeting whether they have sufficient participation to proceed. Late arrivals are added in real time rather than recounted from scratch.

Inspector of elections assignment. The inspector is assigned inside BoardStack and receives a dedicated view for ballot collection and counting. The count is timestamped. Results are recorded against the election record and flow directly into the meeting minutes.

Audit trail. Every step — ballot issued, proxy received, envelope opened, count conducted, results certified — carries a timestamp and is attached to the election record. If a homeowner challenges the result, the board can produce a complete procedural record, not an email thread.

Who this is for

This workflow is built for volunteer boards that run annual director elections and periodic membership votes. The president typically owns election logistics. The secretary manages the meeting record that receives certified results. The inspector of elections, whether a homeowner volunteer or a contracted professional, works directly in the system rather than alongside it.

Multi-community operators running elections across several associations will find the inspector assignment and audit trail features particularly useful for demonstrating consistent procedure across communities.