Guide
Party primaries without the chaos
Nominations are challenged on process far more often than on arithmetic. This guide is about building a record that answers the challenge.
Start from the challenge, and work backwards
Assume the outcome will be contested and ask what you would be asked to produce. In practice it is four things:
- Who was a member, and since when? A register that can be shown as at a date, not a list that was edited during the process.
- Why was this aspirant cleared and that one rejected? A decision, a reason, a named official and a timestamp.
- How do you know each person voted once? Identity established before the poll, and one ballot per voter enforced.
- Does the announced figure reconcile? A tally that matches the ballots, produced before anything is announced.
If you can produce those four, most challenges do not survive. If you cannot, the strength of your margin will not save you.
The sequence
Build the register before the aspirants arrive
Recruit and verify members well before nominations open. A register that grows sharply during the nomination window invites the accusation that it was stuffed — regardless of whether it was. Verify identity properly, check for duplicate enrolment, and freeze the register at a published qualifying date.
Publish the rules and the calendar
Eligibility for aspirants, required documents, fees, the nomination window, the campaign period, polling arrangements, the dispute window and who hears disputes. Publish once and do not amend mid-process; if you must amend, record why and notify everyone.
Run nominations and vetting on the record
Accept submissions with timestamps and required documents attached. Vet against the published criteria, recording each decision, its reason and its author. Issue rejections in writing with the reason and the internal appeal route. Then gazette the cleared list and freeze it.
Control polling day
Open and close at published times. Accredit agents for each aspirant and give them the same live view your officials have. Watch turnout as it builds so anomalies are investigated during the poll rather than argued about afterwards.
Reconcile, then declare
Tally, reconcile against the register, review any anomaly flags, and only then declare. The pressure to announce early is intense and is the single most common cause of a result being withdrawn.
Use the dispute window properly
Let challenges be filed formally, assign them, resolve them with a recorded reason, and certify only after the window closes. A dispute process that exists on paper but is skipped in practice is worse than none.
Things that reliably go wrong
- Late rule changes. Any amendment after aspirants are known will be read as targeting someone.
- A register still moving on polling day. Freeze it and publish the count at freeze.
- Verbal clearances. If it is not written down with a name against it, it did not happen.
- Officials with a stake. Anyone administering the poll should have no interest in its outcome, and that should be visible.
- Single-day, high-volume polls with no capacity plan. Size it in advance with whoever runs your systems.
- Promising properties your system does not have. Do not tell members the ballot is cryptographically secret or independently recountable unless it is. An overstated claim that is later examined does more damage than a modest accurate one.
Scope
This is practical guidance, not legal advice. Your party constitution, the Political Parties Act and the statutory nomination framework govern your process, and PollGuard is not integrated with or endorsed by any electoral commission. Meeting statutory requirements and deadlines remains your responsibility.
Primaries coming up?
Talk to us while you still have room to plan the register and the calendar.