Disciplinary suspension expiry and clearance tracker
Problem
Disciplinary decisions arrive as an email attachment or a phone call from a hearing panel, and someone in the league office notes the sanction — often "three matches" or "until 14 March" — in a spreadsheet tab or a personal notebook. Competition administrators selecting teams or approving team sheets have no single place to check who is currently serving a suspension, so clearance is decided from memory or a hurried search of old emails. Suspensions expressed in matches rather than dates are especially error-prone when fixtures are postponed or rescheduled. A club that fields someone still under sanction is a regulatory problem the league has to answer for, not the club alone.
Product idea
A case register purpose-built for sanctions rather than general documents. Each case records the individual, the offence category, the sanction (a fixed number of matches or a date range), and the trigger event that starts the clock. The tool calculates the expiry automatically, including the matches-based case, and flags any competition submission that includes a still-suspended name. Competition administrators get a single current list of who is ineligible and until when; compliance officers get a case history with the panel decision attached. It does not run the disciplinary hearing itself or replace the panel's written ruling — it starts once a sanction has been decided.
Who it is for
Compliance officers who log panel decisions, competition administrators who clear team sheets before matches, and the general secretary who has to answer for a lapse if one occurs.
Possible first version
A web form to log a case with sanction type, length and trigger date, an automatic expiry calculation for both date-based and match-count sanctions, a live dashboard of currently suspended individuals, and a name-check search competition staff can run before submitting a team sheet. No integration with the competition management or registration database in version one — checking is a manual lookup against the dashboard, not an automated block.
- Build classification
- Workflow application
- Rough effort
- 4-6 week first release
- Roles involved
- Compliance officer, Competition administrator, General secretary, Registration officer
- Relevant to
- League office, Federation / governing body, Women's league, Collegiate athletics
- Systems in play
- Case and disciplinary trackers, Registration and membership databases, Competition management systems, Email and shared drives
- Product framing
- Manage compliance
Questions we get asked
What happens when a sanction is measured in matches and a fixture gets postponed?
This is the case that breaks a plain date field, which is why match-count sanctions are tracked against a count of matches actually played rather than a calendar date. A postponement simply does not advance the count. The compliance officer can see, for any individual, exactly how many qualifying matches remain rather than guessing from a rearranged fixture list.
Does this replace the disciplinary panel process or the written ruling?
No. The panel still hears the case and issues the decision in whatever form your disciplinary code requires. This tool starts once that decision exists — it is a record of the sanction and its expiry, not a hearing system. The written ruling stays the authoritative document; this is what stops that document from being the only place the expiry date lives.
Our competition administrators already check a spreadsheet before selection. Why change that?
A spreadsheet works until two people are editing it, an expiry date was calculated by hand and got the match count wrong, or the tab is not the one that got updated. The check itself does not change — administrators still look something up before clearing a team sheet. What changes is that the expiry is calculated once, consistently, and the list they are checking against is the same one the compliance officer maintains.
What does this deliberately not do?
It does not automatically block a team sheet in the competition management system — version one is a lookup tool, not an enforcement gate, because that requires an integration this build does not attempt. It also does not store the substance of the disciplinary hearing beyond the sanction and its trigger; case notes and evidence stay wherever your disciplinary process already keeps them.
Is this your workflow?
Tell us one sports workflow that still runs on paper, spreadsheets, WhatsApp or an outdated system. We will map it and show you what a simpler product looks like.
Tell us about itMore in League & federation administration
- Club affiliation and safeguarding compliance registerA register that tracks every club's affiliation, insurance, safeguarding checks and coach certifications against expiry dates, replacing the annual email chase.
- Club affiliation application bottleneck mapA dashboard that reconstructs how long new club affiliation applications actually spend at each stage, from timestamps already sitting in email, documents and the registration database.
- Cross-border player eligibility research briefingA research agent that reads a federation's own eligibility regulations and the relevant FIFA RSTP text against one case's details and produces a cited briefing, not a decision.