Skip to content

Main content

Single Choice Ballot Count Tally

Explicit supplied candidate IDs and finite ballot observations only; no voter authenticity, eligibility, audit certification or election-result guarantee. Tally occurrence count of single-choice ballots; empty ballots are abstentions, more than one choice rejects.

Loading tool…

Description

Count single-choice ballots per candidate and report empty ballots as abstentions.

A ballot record is an explicit selection or ordered list of literal candidate IDs. A tally depends on its rule: first choice, approval, positional scores and pairwise comparisons use different evidence. Partial rankings do not by themselves define a preference for or against omitted candidates. Counts and weights describe supplied records, not certified voters.

Count single-choice ballots per candidate and report empty ballots as abstentions.

When to use this tool

Use simple single-choice counts when each nonempty record contributes one unit to one candidate.

How to use the tool and how it works

  1. Enter candidates, ballotsJson using the definitions below. Serialize JSON text fields in the decoded shape shown below.
  2. Run the operation. Resolve input-format errors before interpreting an output.
  3. Read result.tally, result.abstentions, using the stated boundary, ordering, sign and absence conventions.

Require zero or one known candidate per ballot. Count each nonempty ballot for its selected candidate and count empty ballots as abstentions.1

Input fieldMeaning and unitsAccepted input
candidatesDistinct literal candidate IDs in the output row/column order.Dense list of at most 128 literal strings, each at most 8,192 UTF-16 units.
ballotsJsonJSON array of ballot arrays of literal candidate IDs. Each row is a selection or partial ranking according to this operation; empty ballots are allowed.Text, at most 8,192 UTF-16 code units; narrower grammar/range rules also apply.

These decoded structures show the examples inside JSON text fields. Supply their serialized JSON strings as input.

json
{
  "ballotsJson": [
    [
      "a"
    ],
    [
      "b"
    ],
    []
  ]
}
Output fieldInterpretation
resultObject containing the fields below.
result.tallyCandidate records in declared bank order with support, count or score fields determined by this operation.
result.abstentionsNumber of empty ballot records, without weighting.
json
{
  "input": {
    "candidates": [
      "a",
      "b"
    ],
    "ballotsJson": "[[\"a\"],[\"b\"],[]]"
  },
  "output": {
    "result": {
      "tally": [
        {
          "candidate": "a",
          "support": 1
        },
        {
          "candidate": "b",
          "support": 1
        }
      ],
      "abstentions": 1
    }
  }
}

Limitations and assumptions

  • Repeated or unknown candidate entries fail validation. The tool checks the supplied records, not voter eligibility, duplicate people or election-law compliance.
  • Candidate banks use distinct exact string IDs. Unless an audit explicitly accepts them for reporting, unknown IDs and repeated IDs within a ballot are rejected. Rankings may be partial. These operations do not authenticate records, infer voter intent or apply jurisdiction-specific election rules.
  • Every declared outer field is required and unknown outer fields are rejected. Strings and JSON text have size limits, lists are bounded to 128 entries, and JSON nesting/node counts are bounded. Tighter operation-specific bounds stated above take precedence.
  • Numeric outputs must remain finite and within safe-integer magnitude. Original record indexes and cell coordinates are zero-based; stated half-open ranges exclude their end.

Alternative or Complementary methods

Choose a tally rule before comparing outcomes. Audit candidate identity and repeated entries first, retain the treatment of empty and partial ballots, and apply any election-specific eligibility or tie-breaking procedure separately.

References

  1. Tool behavior and example: Single Choice Ballot Count Tally — tool.io

Similar or alternative tools