Electronic voting software for member organizations

Encrypted, anonymous electronic voting for board elections, general assemblies, and statutory decisions, run inside the same platform that holds the member register.

  • Administrators see who voted, never what they voted
  • Every voter gets an integrity hash to verify their own ballot after the fact
  • Eligibility scoped to a chapter, a board, a role-based group, or a named list

Built for federations, professional associations, political movements, and international networks that vote under their own statutes.

Electronic voting at a glance

Anonymity Ballots are encrypted at submission; a cast ballot cannot be read or altered by anyone, including Orgo engineers with direct database access
Voter verification Each voter receives an integrity hash and can confirm afterwards that their ballot is recorded and valid; database tampering invalidates the check
Turnout visibility Administrators see which eligible voters have voted, never their choices; the voter list itself can be hidden
Eligibility scope The whole organization, any group (chapter, board, committee, or role-based group), or a manually curated list of named voters
Ballot format One or more questions per vote, one option selected per question, counted as a popular vote; single transferable vote for multi-seat elections arrives in September 2026
Scheduling Start and end date and time, multi-day windows, manual close by an admin, or automatic close once every eligible voter has voted
Live assembly mode Full-screen view for in-room assemblies; participant names turn green as they vote, results reveal at close
Records Permanent archive of every past vote and result; results downloadable for minutes and reports

The voting system for

Federations that elect at every level

National assemblies, regional boards, and chapter committees each run their own vote, scoped to their own electorate.

Associations voting on a fixed cycle

Organizations electing a board every two or three years replace borrowed ballot tools and video calls with one repeatable process.

Tiered memberships with unequal rights

Where full members vote and associate or observer tiers do not, eligibility follows the membership record rather than a hand-built list.

Everything a formal vote requires

Anonymity & integrity

Orgo separates the fact that a person voted from the content of their ballot, and makes that separation verifiable rather than a matter of trust.

Ballots are encrypted at submission through a centralized cryptographic architecture built on the same principle as a blockchain. A cast ballot cannot be read or altered afterwards, including by Orgo engineers with direct access to the database.

Each voter receives an integrity hash when they cast their ballot. They use it afterwards to confirm their vote is recorded and valid. Any tampering with the underlying database invalidates the check, so verification tests the record rather than restating a promise.

Administrators see which eligible voters have already voted, so they can chase turnout before the window closes. They never see how anyone voted. The voter list itself can be hidden when even turnout should stay private.

The voting system has been externally audited. Orgo runs on AWS in Frankfurt and platform data does not leave the European Union.

Encrypted anonymous voting and non-anonymous polls are two distinct formats. A statutory election uses the encrypted format. A sentiment check, such as picking a date for the next assembly, uses the open one, where responses are attributable.

Who can vote

Eligibility comes from the member record and the organizational structure, not from a list somebody maintains by hand between elections.

A vote is restricted to one of four audiences:

  • The entire organization
  • Any group: a chapter, a parent chapter, a board, or a committee
  • A role-based group that populates itself, for example every chapter president
  • A private, manually curated list of named voters

A role-based group fills itself from role data. When someone gains or loses a role, their place in that group changes with it. The electorate for a board vote is therefore correct on the day the vote opens, without anyone rebuilding it from a spreadsheet.

Membership status governs platform access. A lapsed member loses access and is routed to a payment screen, so they cannot reach an open ballot until the fee is settled. Member types, such as full member against associate or observer, define the groups a vote is scoped to.

Voting happens inside an authenticated member account, not through a link that can be forwarded. One account casts one ballot per vote.

A vote can be restricted to a named list built for the occasion, such as an eleven-person board or an election commission. Members outside that list never see the vote at all.

Running the vote

A vote moves from draft to published on the administrator's schedule, and closes on a rule set before it opens rather than a decision taken in the moment.

Votes are built in draft and stay invisible until published. Publishing notifies every eligible voter by email and mobile push notification. An open vote is flagged with a marker in the interface so it is not missed among other activity.

Each vote defines its own window:

  • A start date and time, an end date and time, or both
  • Multi-day windows for an electorate spread across countries
  • Manual close by an administrator
  • Automatic close once every eligible voter has voted

Eligible voters receive a reminder before a scheduled vote opens.

One vote can carry several questions, with one option chosen per question. A general assembly agenda with four resolutions runs as a single ballot instead of four separate votes.

Orgo counts by popular vote today. Single transferable vote arrives in September 2026.

Single transferable vote is on the roadmap for release in September 2026, for organizations whose statutes require a proportional method to fill several seats at once. Voters rank candidates in order of preference instead of picking one, and the count transfers surplus and eliminated preferences until every seat is filled.

Organizations whose statutes already mandate this method should confirm timing with us before committing to an election date.

Every member sets a time zone at first login. Voting windows, reminders, and closing times display in that time zone, so an international electorate reads the same deadline correctly and nobody misses a vote to a conversion error.

Members choose how they receive vote notifications, by push, by email, or both, alongside their preferences for discussions, events, and tasks. Organizations set the defaults.

Assemblies & congresses

Votes run in the room as well as online, including inside the event that hosts the assembly.

The vote projects full screen for an in-room assembly. Participant names turn green as each person votes, so the chair reads live turnout from the front of the room. Results reveal when the vote closes.

A vote can run inside an event and surfaces in the event app during a congress or general assembly. Delegates vote from the same app they used to register and check in, and stay signed in throughout.

Results update in real time as ballots arrive. Administrators choose whether results display live or stay hidden until the vote closes, which is the difference between a working session and a contested election.

Members vote from the web platform or the Orgo mobile app on iOS and Android. There is no separate voting product to procure, no credentials to distribute, and no attendee list to re-import before the assembly opens.

Records & traceability

Every vote stays on the record, which is what makes a past decision defensible when someone asks years later how it was reached.

Past votes and their results stay in a permanent archive. When a member asks how a decision was taken, or how a person came to hold a position, the answer is the vote record rather than a recollection.

Results download from the platform for the minutes, the annual report, or a file kept for a supervisory body.

The vote sits beside the member register that defined the electorate, the event that hosted the assembly, and the documents signed around it. Nothing has to be reconciled afterwards between a separate voting tool and the membership database.

Orgo logs profile changes, data exports, and report generation with the user, timestamp, and IP address. The member data that determined eligibility carries the same trail as the vote it fed.

Fit with your governance documents

Organizations vote under rules written long before the software, so terminology and structure follow the organization rather than the platform.

Every label in Orgo is text your organization controls. If your statutes say ballot, resolution, or motion rather than vote, the interface says that instead, in your own language.

Admin roles exist at organization, parent-chapter, and local-chapter level, each isolated to that level's data. A regional board therefore runs its own vote without a national administrator setting it up on its behalf. Role names are yours to define and map onto documented permission levels.

Orgo counts popular votes today, with single transferable vote arriving in September 2026. Proxy and delegated voting are not available. Orgo does not certify the legal validity of a vote under any national association law. The platform produces the record, an anonymity guarantee, and a verification mechanism; your statutes govern what that record means.

“With an organization of 8,000 members and more than 80 chapters coordinated almost exclusively by volunteers, Orgo is at the heart of our digitisation process, allowing us to focus on our mission - learning by doing, nature, and personal development.”

Photo of Andrei Avram

Andrei Avram

President, Romanian Scouts

Electronic voting FAQ

Electronic voting software runs an organization's formal votes online, covering ballot creation, eligibility, the voting window, counting, and the record kept afterwards. It differs from a general poll or survey tool in that a ballot is anonymous, tied to a verified identity, and countable only once per voter. Member organizations adopt one when a general assembly or board election has to reach people who cannot all be in the same room on the same day.

Ballots are encrypted at the moment of submission through a centralized cryptographic architecture built on the same principle as a blockchain. Once cast, a ballot cannot be read or altered, and that applies to Orgo engineers with direct access to the database as well as to your own administrators.

Administrators see which eligible voters have voted, because turnout has to be chased before a window closes. They never see how anyone voted. Where even turnout should stay private, the voter list can be hidden.

Yes. Each voter receives an integrity hash when they cast their ballot and can use it afterwards to confirm that their vote is recorded and valid. Any tampering with the underlying database invalidates the check, so the verification tests the stored record rather than restating an assurance.

The voting system has been externally audited. Results also download from the platform, and every past vote stays in a permanent archive.

The administrator creating the vote sets its scope. A vote can be opened to the entire organization, to any group such as a chapter, a parent chapter, a board, or a committee, to a role-based group that populates itself from role data, or to a manually curated list of named voters.

Membership status also governs access. A lapsed member loses platform access and cannot reach an open ballot until the fee is settled, so eligibility follows the member register instead of a separately maintained list.

Administrators see who has voted and who has not, which is what makes turnout chasing possible during a voting window. They cannot see any individual's choice. The voter list can also be hidden entirely, so that not even participation is visible.

Single transferable vote is scheduled for release in September 2026. It fills several seats at once by proportional count: voters rank candidates in order of preference, and surplus and eliminated preferences transfer until every seat is filled. Until then Orgo counts by popular vote, where a single ballot can carry several questions with one option selected per question, so a general assembly agenda with multiple resolutions runs as one vote. Proxy and delegated voting are not available.

Yes. A vote projects full screen for an in-room assembly: participant names turn green as each person votes, and results reveal when the vote closes. Delegates vote from their own phones. A vote can also run inside an event, surfacing in the event app during a congress alongside registration and check-in.

That depends on your own statutes and on the law of the country you are registered in, not on the software. Orgo provides the anonymity guarantee, the per-voter verification mechanism, the eligibility scoping, and the permanent record. Whether those satisfy a particular statutory requirement is a question for your governing documents and your legal counsel.

Closed votes and their results move into a permanent archive. That archive is the traceability layer for governance: when someone asks how a decision was reached or how a person came to hold a position, the vote itself is the answer. Results also export from the platform for minutes, annual reports, or a supervisory filing.

See an election run end to end

  1. 1 Pick a 30-minute slot. You talk to the people who built Orgo, not an account executive working from a script.
  2. 2 We set up Orgo on your real organization during the call and configure a vote with your own eligibility rules and quorum.
  3. 3 You keep the sandbox to evaluate with your team, plus a written plan for migrating the data you already have.
Get a demo