← System Documentation Results and disputes

Objections and officer complaints

Separate candidate/process objections from complaints against appointed officers and route each to the competent reviewer.

Objections and Complaints Guide

1. Two separate dispute channels

CivitasVote distinguishes between:

  • an election objection, concerning a candidate, voter register, nomination, ballot process, result or other election matter; and
  • an officer complaint, concerning the conduct, independence or performance of an appointed election officer.

They must not be merged. The subject, competent reviewer, evidence and recusal requirements differ.

2. When public submission is available

The public submission views accept challenges while the election has one of the configured public challenge statuses, including nominations, ready, open, closed, tallying, awaiting approval, published, cancelled or invalidated. Draft elections are not exposed for public challenge through these views.

Rate limiting restricts repeated submissions. A public submitter should receive and retain the generated public reference.

3. Election objections

Typical subjects

Depending on the choices implemented in the model and form, an objection may concern:

  • a candidate or nomination;
  • voter eligibility or the register;
  • polling or verification procedure;
  • ballot configuration;
  • tally, result or declaration;
  • another stated electoral-process issue.

Submission procedure

  1. Open the public election page.
  2. Follow the objection link.
  3. select the appropriate objection type;
  4. select the candidate where the form requires one;
  5. provide accurate complainant contact details;
  6. state the facts, dates and relevant rule;
  7. state the remedy requested;
  8. submit once and save the public reference.

Do not include a member PIN, one-time voting code, passkey secret, voting ticket or ballot choices.

Commission review

The objection queue is available to the roles authorised by the view: Commissioner, Deputy, Secretary, Returning Officer and Registration Officer. The reviewer should:

  1. confirm jurisdiction and timeliness;
  2. check whether the objection identifies the correct election and candidate;
  3. preserve all related evidence;
  4. obtain any required response without exposing protected voter data;
  5. record the decision and reasons;
  6. mark the matter resolved or dismissed only when the record is complete;
  7. assess whether the decision requires register recertification, candidate-list republication, recount, cancellation or another controlled action.

4. Officer complaints

Purpose

An officer complaint challenges the conduct of a person appointed to an election role. It is not the correct mechanism for ordinary disagreement with a candidate decision unless the complaint specifically concerns officer misconduct or conflict of interest.

Submission fields

The public form records the officer, complaint type, description, requested remedy, recusal request and optional evidence. Evidence is stored in protected media and is not publicly downloadable.

Competent review authority

The form and model assign the complaint to either:

  • the association appointing authority; or
  • the Appeals Panel.

The accused officer is excluded from reviewing their own complaint. Where an Appeals review would otherwise be appropriate but no current Appeals reviewer has been appointed, the current project provides an appointing-authority fallback so that the matter remains reviewable.

Recusal

A recusal request should identify the conflict or reason. The system records the request, but governance officers must still make and document the substantive recusal decision under the association’s rules.

Evidence access

Only an authorised reviewer may download the evidence. The evidence route checks the current user, competent authority and accused-officer exclusion. Evidence filenames and hashes should be retained in the audit record.

5. Status and decision discipline

Do not mark a matter resolved merely because an acknowledgement was sent. A complete determination should record:

  • issue and jurisdiction;
  • evidence considered;
  • response received;
  • applicable rule or authority;
  • findings;
  • remedy or reason for dismissal;
  • reviewer identity and date;
  • effect on the election, candidate list, register, tally or declaration.

Where the matter remains active, retain an open or under-review status rather than using a final status prematurely.

6. Independence and separation

A Commission member should not determine a complaint concerning their own conduct. A person serving in the Commission should not simultaneously serve as an Appeals reviewer for the same election cycle. Association governance should appoint optional independent reviewers where the risk and governing rules justify them, even though the software minimum committee does not mandate an Appeals Panel.

7. Relationship with election control

An objection or complaint does not automatically stop the election merely because it exists. The competent authority must determine whether to:

  • continue operations;
  • pause a step under the governing rules;
  • correct the register or candidate list;
  • require recusal or replace an officer;
  • conduct a recount;
  • cancel the election before completion; or
  • invalidate a concluded election.

Cancellation and invalidation are Commissioner exceptional actions in the current interface and require a reason. Use them only under documented authority.

8. Audit events

Public submissions and internal decisions create audit events with the election, object identifier, actor where authenticated, type/status metadata and request context. The audit log should be verified after any high-impact dispute decision.

9. Privacy

Complaint and objection records may contain personal or reputational information. Apply these controls:

  • collect only information required to determine the matter;
  • use protected uploads for evidence;
  • do not publish complainant details without lawful authority;
  • do not place secret voting credentials or selections in a complaint;
  • restrict evidence access;
  • retain the record while a review, petition, audit or legal hold remains active;
  • document any lawful redaction or disposal.

10. Operational examples

Candidate eligibility objection

Record an election objection against the candidate, review eligibility evidence, decide the matter, update the nomination/candidate status where required and republish the final candidate list before voting.

Complaint against a verification officer

Record an officer complaint, assign the competent independent reviewer, protect the evidence, assess recusal or suspension, document the decision and review whether any issued credentials or participation records require investigation.

Result challenge requesting recount

Record the objection, preserve the current tally snapshot, review reconciliation and incident records, and use the Commissioner’s recount action with a specific recount reason where authorised. A recount creates a new version rather than overwriting the prior snapshot.

11. Troubleshooting

Public page returns Not Found

Confirm the election status is within the public challenge statuses and the public identifier is correct.

Reviewer receives Permission Denied

Confirm the user has a current election appointment or association appointing-authority role, is not the accused officer and is assigned to the correct review authority.

Evidence is unavailable

Confirm the protected-media path, filesystem permissions, stored file record and backup. Do not move complaint evidence into public media.

No Appeals Panel exists

Review the complaint’s assigned authority and the appointing-authority fallback. Do not create a fictitious Appeals decision.

Continue the procedure