HOA Voting Software with Audit Trail: Introducing Community Voting
How to Run HOA Votes Without the Drama: Introducing Community Voting
Every HOA board has had this Tuesday night.
Three of seven members made it in person. Two are on speakerphone. One sent a hand-signed proxy by text. The seventh forgot. The motion is whether to raise dues 4 percent. Someone scribbles “4 yes, 1 no, 2 abstain” on a yellow legal pad and slides it into the binder. The motion carries. Six months later a homeowner sues, claims quorum was never reached, and asks to see the records.
You go looking for the legal pad.
If you have served on an HOA board, you know exactly which legal pad you are looking for. You also know the answer: it is in a box, in a closet, behind a stack of pool maintenance receipts. And even when you find it, the pad does not actually prove anything. It does not timestamp itself. It does not list who voted which way. It does not survive cross-examination.
This is the part of HOA governance that almost nobody talks about until something goes wrong. Voting is supposed to be the most legally significant thing a board does, and most communities run it on paper, by show of hands, with notes that would not pass an audit at a lemonade stand.
We just shipped Community Voting to fix that. This post walks through why HOA voting is broken today, what we built, and what we deliberately did not build (yet).
The Real Problem with HOA Voting Today
The Community Associations Institute puts the number of community associations in the U.S. at roughly 369,000, housing about 77 million people. The vast majority are still voting the same way they did in 1995: paper ballots, in-person headcounts, hand-signed proxies, and a minute-taker who writes “motion carried” in a notebook.
That worked when every owner could walk to the clubhouse. It does not work when:
- A meaningful share of your residents have full-time jobs, kids, and cannot make a Tuesday night
- The vote involves real money (a dues hike, a special assessment, a vendor contract)
- A homeowner challenges the result and you have to reconstruct what happened
- You need to know who voted, when, and how
The standard objections to digital voting in an HOA boil down to two things: trust (“I do not know who actually cast that ballot”) and audit (“I cannot prove what happened”). Both are reasonable. Both are exactly what we focused on.
Most existing HOA voting platforms approach the problem from the opposite direction: anonymous ballots, single-purpose tools, and a separate login that residents have to remember. We think that is wrong. HOA case law strongly favors transparent records, and most disputes turn on whether the vote can be reconstructed after the fact. So we built voting around the audit, not around the secrecy.
What We Shipped: Two Vote Types, One Audit
Community Voting lives on the admin Dashboard, right next to Announcements. One tile, two choices when you tap it: start a new vote, or review past votes.
When you start a new vote you pick one of two scopes:
Community Wide votes give one ballot per property, cast by the primary resident on file. This is for things every owner gets a say on: dues changes, rule amendments, board elections, capital projects. Co-residents in the same household do not get separate ballots. The property is the unit of voting, and the primary speaks for it.
Board Only votes give one ballot per active board seat, plus admins (your property manager or community manager). This is for everything the board decides on the community’s behalf: vendor contracts, budget approvals, formal resolutions, hiring decisions. Admins are included by default because in most professionally managed associations the manager is part of the governing body. If your bylaws say otherwise, the admin simply does not cast a ballot, and the audit shows them as not having voted.
The two scopes are mutually exclusive. A board member who lives at a property casts a board ballot on a board vote and a community ballot on a community vote. They never get to vote twice on the same vote. There is no math to second-guess.
Eligibility Is Locked at Open Time
This is the most important detail and the one most likely to be missed.
When you click Save and Open Now, the system snapshots the eligible voter list at that exact moment. Every active board member’s user ID. Every property’s primary resident ID. That snapshot is what the tally is computed against.
If a resident moves out three days into a 7-day vote, their property is still on the eligible list, and the tally still expects N voters. If a new board member joins mid-vote, they are not on the list, and they cannot cast a ballot. The eligibility is anchored to the moment the vote opened, not to whoever is in the system at the moment the vote closes.
This sounds boring. It is not. It is the single thing that makes the audit hold up under challenge.
Yes, No, Abstain (and That Is It)
Every vote in HomeHerald has the same three choices: Yes, No, Abstain. We considered multi-choice and ranked-choice for v1 and decided against. Almost every motion that matters in an HOA is a yes-or-no question, and Abstain is the legally significant third option that lets a board member recuse on a conflict of interest without leaving a blank.
Multi-choice elections (think: pick three candidates from a slate of five for the board) are on the roadmap. We will ship them when the audit is just as strong for them as it is for the binary vote, which means correctly handling cumulative voting, quorum on each seat, and tie-breaking. None of that is cheap, and getting it wrong invalidates a board election. So: ranked-choice and multi-candidate later, binary votes now.
The Audit Trail: Non-Anonymous, Timestamped, Printable
Every ballot in HomeHerald carries the voter’s name, the voter’s email at cast time, the property address (community votes) or board title (board votes), the choice, and an ISO timestamp accurate to the second.
These records are immutable. The Cloud Function that writes them uses a transactional document create with the voter ID as the document key, so a duplicate cast collides on the document itself rather than racing. You cannot accidentally cast twice. You cannot edit a ballot after submission. You cannot delete one.
When a vote closes, the system reads every ballot, computes Yes / No / Abstain counts and percentages, and writes a frozen tally to the vote record. The tally is permanent.
The admin audit panel shows every ballot in a table: name, identifier, choice chip, cast time. The Download Audit (PDF) button generates a multi-page PDF with your community letterhead, the vote metadata, the motion text, the full tally, and the ballot list. Page footers carry the generation time and page numbering. That PDF is what you attach to your meeting minutes, file with your insurer, or hand to a lawyer.
This is the part that survives litigation. A printout of timestamped ballots, with names, signed by the system at the moment they were cast, is exactly the kind of record courts want to see. The legal pad is not.
The ballot-level audit is visible to admins and board members. Residents never see who voted which way. The published tally (Yes / No / Abstain percentages plus turnout) is what residents see.
The 7-Day Resident Result Banner
When a vote closes, a results banner pins to the top of every eligible viewer’s home screen for 7 days.
For community-wide votes, the banner shows to every resident. They see the tally percentages, the turnout (how many of the eligible properties responded), and a clear “X days left” countdown showing exactly when the banner will auto-clear. They can dismiss it manually if they have already read it. The dismissal persists across reloads.
For board votes, the admin chooses at create time whether the result is public to all residents or restricted. This is a checkbox in the create form: Make results public to all residents. Default is checked.
This gives boards two real-world modes:
Public board vote. The board votes on a new pool maintenance vendor. Residents deserve to know. Checkbox stays on. When the vote closes, every resident sees the resolution on their dashboard for 7 days, the same way they would see a community-wide vote.
Restricted board vote. The board votes on a personnel matter or a sensitive contract negotiation. Residents do not need to see the tally yet. Checkbox off. The result banner only appears for board members and admins.
The ballot-level audit stays restricted to board and admin in both modes. The checkbox controls only the public tally.
The AI Recall Angle
HomeHerald already has Herald Chat, the AI assistant that reads your community’s CC&Rs and answers resident questions. We wired closed votes into Herald Chat’s context.
Residents can now ask:
- “What was the result of the dues vote?”
- “Did the pool repair vote pass?”
- “What did the board decide about the new gate?”
The chat pulls the title, scope, motion text, and full tally from the closed-vote record. The visibility rules for the chat are identical to the visibility rules for the resident banner: if a resident would not see a board vote on the dashboard, the chat will not surface it for them either.
Net effect: your community has institutional memory that does not depend on whether you remember which Tuesday in March the vote happened. New residents can ask “What did the HOA decide about parking?” and get a real answer with the tally and the date.
For a self-managed board, this is the single biggest reduction in repeat questions you can ship. For a managed community, it removes one of the most common “ping the manager” tasks from the manager’s queue.
What HomeHerald Voting Is NOT in v1
We made deliberate choices about scope. Knowing what we left out matters.
No quorum logic. The system records ballots and computes a tally. It does not declare a vote “valid” or “invalid” based on a percentage threshold. Quorum is a governance question, and your bylaws define it. The tally and turnout percentage are right there for you to apply your own rules.
No tie-breaking. A 50-50 vote shows as 50-50. We do not auto-declare a winner. Your bylaws or your board chair decide what happens.
No proxy votes. A resident cannot cast on behalf of another resident in v1. The primary on file casts the ballot. If your community runs heavy on proxies today, this is a meaningful change in practice. We are watching feedback on whether to add a structured proxy mechanism with its own audit trail.
No anonymous ballots. Every cast carries the voter’s name. This is intentional and will remain the default. Anonymous voting is on the roadmap as an opt-in for specific use cases, but adding it weakens the audit for everyone, so we are taking it seriously before shipping.
These constraints are what make the audit trustworthy. We will add the missing pieces when we can keep the audit just as strong.
Why Self-Managed and Managed HOAs Both Win
For self-managed boards, Community Voting is one of the simplest ways to retire the legal pad and the email vote (“reply Yes or No to this thread”). You get an audit trail you can defend, a result residents can see, and a record you can hand to a future board member who needs to understand why dues went up in 2026.
For professionally managed communities, Voting is a clean handoff. The manager runs the meeting, opens the vote, and the board casts ballots on their phones in real time. The manager downloads the PDF the same evening and attaches it to the minutes. The PDF goes in the binder. The vote record lives in the system forever.
Both modes use the same feature, the same data model, and the same audit. There is no upgrade path or “managed HOA edition.” If your HOA is on HomeHerald, you can vote.
Pricing and Availability
Community Voting is included in every HomeHerald plan, including the Free tier (up to 50 properties). No per-vote charge, no per-ballot charge, no separate add-on. Open a vote, run a vote, download the PDF. That is the whole pricing model.
You also get Herald Chat, unified email, amenity bookings, dues management, and the rest of HomeHerald in the same Free tier. There is no voting-specific upsell.
The Bigger Picture
HOA boards do not need more software. They need software that makes the things they already have to do less painful. Voting is one of those things. It happens whether or not you have a tool for it. The question is whether you have a record afterward.
We built Community Voting because the Tuesday night legal pad is not how 369,000 communities should be deciding the things that affect 77 million people. The audit should be automatic. The tally should be instant. The PDF should be one click. The motion text should still be there in five years when somebody asks why the dues changed.
If you run an HOA, start a vote today and see what an audit-grade record looks like.
Related Reading
Ready to simplify HOA management?
Start free with up to 50 properties. No credit card required.
Start Free