A stronger fit
- A named owner can define the decision and its boundary.
- People need shared context before choosing.
- Participation and result release need clear authority.
- The organisation wants to retain the reason and evidence.
Evaluate fit with one decision
Run one real decision. Learn whether Votegrain fits.
Start with one decision your organisation already needs to make. See how people prepare it, vote and review the result, then decide whether the workflow fits.
A paid pilot, scoped and agreed before it starts.
Share the printable buyer overview →Start with the job
When the process matters as much as the result.
Votegrain is designed for a decision that needs clear authority, structured alternatives, controlled participation and a record people can return to.
Use a simpler route when
- The job is a quick pulse or general research survey.
- The group needs discussion rather than a formal ballot.
- The alternatives are not ready to compare.
- No one can name the authority or permitted audience.
The evaluation sequence
Six stages, with a clear handoff at each one.
Your organisation stays in control of who prepares, publishes and closes the decision, and who can review the result.
Your organisation and Votegrain
Fit and scope
Choose one contained decision, name the people affected, define what is outside the evaluation and agree the evidence that will be used to judge fit.
Customer Organisation Admin
Customer-owned setup
Your organisation chooses its administrators, participants, visibility and decision standards. Agree who people should contact if they need help.
Initiative Editor to Organisation Admin
Prepare and review
An Initiative Editor prepares the question, context, options and audience, then previews the voter path. An Organisation Admin checks readiness and owns publication.
Eligible voters
Vote
Voters see the decision context, compare the options, check whether the vote is named or anonymous and cast one write-once ballot. A receipt confirms that the ballot was recorded without showing the choice.
Organisation Admins, Analysts and permitted readers
Evidence review
Authorised people inspect the released aggregate result, its limitations and the permitted reporting behind it. The customer then records its evaluation of whether the workflow fits the organisation.
Roles and handoffs
Give each person the access they need.
These are the roles in Votegrain. People only see or change what their role and access allow. A job title alone does not grant permission.
See each role's permissions
People, settings and decisions
Organisation Admin
Manages people and settings for their organisation. Can prepare and publish decisions, close voting and release results under the agreed rules. Cannot bypass ballot privacy.
Decision preparation
Initiative Editor
Prepares the question, options and voter list for decisions they can work on. Cannot publish, close or archive a decision.
Taking part
Voter
Reads the options, casts one eligible vote and sees results when they are released to them. Cannot change the decision or see other people's ballots.
Results and trends
Analyst
Explores results, trends and the evidence behind them within their permitted scope. Cannot edit decisions, manage people or generate AI analysis.
Invited reader
Read-only Invitee
Reads only the published decisions or reports shared with them. Cannot vote, edit, export or manage settings.
Account ownership
Tenant Owner
Looks after account billing and organisation setup, and reviews account audit history and reports. Separate permissions are needed to vote, edit decisions or change an organisation's settings.
Capability boundary
Keep the scope focused.
The scope should be small enough to understand the result and complete enough to exercise the real voter and governance path.
What the evaluation can test
- Structured context and comparable option criteria.
- A defined electorate or authenticated organisation-code participation.
- Single-choice or ranked voting and a write-once ballot.
- Preview, review, publication, closing and release handoffs.
- Deterministic aggregates with permission and privacy limits.
Outside a one-decision evaluation
- Connections to other systems or imported decision history.
- An organisation-wide rollout or a custom operating model.
- Cross-decision learning produced by a single record.
- An automated judgement or disclosure of individual choices.
- Completion of separate activation and agreement checks.
Eligibility and scope details
One decision and decision history
Test one journey now. Learn across decisions as history grows.
Evidence from one decision
Evaluate setup, voter clarity, role handoffs, the released aggregate result and whether authorised readers can understand the evidence and its limits.
Evidence across decisions
Cross-decision views need multiple compatible released decisions that the reader is permitted to see. Draft, open and closed-but-unreleased work can contribute lifecycle status, not outcome evidence. Groups define administration and visibility, not reporting segments.
Measurable success
Decide what success looks like.
Can people vote confidently, follow the right approvals and understand the result? Agree what you will measure before starting.
Choose your evaluation measures
Decision definition
The customer can state the question, boundary, owner and closing condition before setup begins.
Content quality
The agreed context and option criteria are complete enough for the intended participants to compare the alternatives.
Voter clarity
Representative voters can find the context, understand the ballot setting and submit without a process workaround.
Governance
Preparation, publication, voting, closing and release move through the intended roles and permissions.
Result trust
Authorised reviewers can follow the deterministic result, privacy treatment and evidence limitations without seeing individual choices.
Fit decision
The customer records what worked, what blocked the process and whether another decision is an appropriate next step.
Before activation
Check the essentials before starting.
Before starting, agree the scope, access, privacy requirements and operating arrangements. The relevant technical and legal checks must be complete; a demo request does not replace them.
Security and trustInspect access boundaries, write-once ballots, aggregate privacy and deterministic results.→Decision standardsSee how an organisation can structure context and compare options consistently.→AI governanceUnderstand why AI stays optional, server-side and outside voter choice.→Product questionsReview common questions about the journey, privacy, reporting and product boundaries.→
Released legal documents
Review the agreement, pilot order and data terms alongside your organisation's procurement requirements.
Operating boundary
Make ownership and the end point explicit.
Support ownership
Agree who supports participants, who administers the decision and how issues reach Votegrain. Record the support arrangements for your engagement before it starts.
Exit and record ownership
Agree which decision records you need to keep and who handles the handover at the end. Confirm available exports and retention arrangements before relying on Votegrain as your only copy.
Use your decision
See whether the journey fits your governance.
Tell us the decision you have in mind, who needs to take part and what you want to learn. Keep confidential details out of the initial request.