Loading patterns…
Let a defined group weigh in on a decision and apply a rule — unanimous, majority, weighted — to pick the outcome. Good for steering-committee approvals, board decisions, and committee reviews.
Rendering diagram…
Use voting when:
Do not use voting when a clear owner should decide. Committees-by-default slow everything down and diffuse responsibility.
A voting group is defined for the decision type. A proposal is sent to every member. Each member responds with Approve, Reject, or Abstain. A tallying rule determines the outcome:
A quorum can be required — a minimum number of members must vote for the result to count.
Abstentions are tricky. Decide explicitly: do they count toward quorum? Toward the denominator in "majority"? The rules matter when a vote is close, and you don't want to decide them after the fact.
Who votes? What weight does each carry? Record it at the moment the vote starts — changes to the group mid-vote create audit nightmares.
Write it down, including how abstentions and missing votes are treated. Publish it before the vote starts.
A vote that never ends isn't a decision. Typical setups: vote window of 3–7 days, quorum of ≥50% of voters. Non-responders default to abstention.
In sensitive votes, showing the running count influences later voters. Lock vote visibility until the deadline. For routine committee work, open visibility is fine.
The tally, the rule applied, the quorum status, the final decision, and each voter's position (unless you want anonymous). Skip any of these and the losing side will argue the process.
Send approval requests to multiple people simultaneously and proceed when a minimum number approve. Faster than serial chains for peer-level decisions.