Discipline Committee

Cases that arrive as a paragraph in an email — 'Player X insulted the umpire at club Y on Saturday' — require weeks of follow-up to gather what should have been captured at the moment of incident. Witnesses move on, memories fade, video is deleted.

Half the cases that should result in clear sanctions end up dropped because the evidence cannot be assembled cleanly. The asymmetry between well-documented and poorly-documented complaints undermines the principle that comparable conduct produces comparable consequences.

Incident Intake provides structured forms for umpires, clubs and players, capturing date, location, parties, witnesses, immediate statements and evidence (photos, video, scoresheets) at submission. The umpire app supports incident filing from the field within minutes of an event.

Required-field validation prevents incomplete intakes from reaching the committee, raising baseline case quality dramatically.

Without a sanction library, every case is decided from scratch and outcomes vary depending on which committee members happen to sit. A first-offence verbal abuse case might draw a written warning from one panel and a six-month suspension from another.

The variance is visible to clubs and players, breeds accusations of bias and favouritism, and undermines the deterrent function of the system. Appeals citing inconsistency frequently succeed even when the underlying conduct is clear.

Sanction Library & Application catalogues offence categories with typical sanction ranges, aggravating and mitigating factors, and links to historical cases. When the committee opens a new matter, the system surfaces comparable past rulings — what was the conduct, what was decided, what was appealed.

Proportionality becomes visible, defensible and consistent across panels.

Appeals follow strict procedural rules — notice periods, deadlines for filing grounds, right to representation, composition of the appeals body. A missed deadline or incomplete notification voids the entire process, freeing offenders on technicalities even when the original sanction was sound.

Today these procedural requirements are tracked manually by an overworked secretary, and slips are common. When the federation is sued in civil court over a disputed sanction, the procedural file determines whether it wins or loses.

Appeals Workflow drives every appeal through configured stages — notice of appeal, grounds, evidence supplementation, appeals hearing, decision — with statutory deadlines enforced and notifications timestamped to verified delivery. The complete case and appeals file is exportable as a court-admissible record.

Sanctions in effect are propagated to the licensing system, suspended pending appeal where applicable.