Registration exception request routing and precedent log
Problem
A club emails the registration officer asking for an exception — a player registering after the deadline, a dual registration, an age-group move. The registration officer forwards it to whoever on the committee happens to answer email that week, sometimes the general secretary, sometimes the competition administrator. The decision gets typed into a reply and the thread is filed, or not, in a personal inbox. Nobody keeps a record of what was decided or why, so when a near-identical request arrives eight months later, a different person decides it differently. Clubs notice the inconsistency before the federation does, and the person who remembers how the last three cases were handled is one resignation away from taking that memory with them.
Product idea
A structured intake form replaces the email: exception type, competition, player and club, supporting detail. The workflow routes the request to the correct approver based on exception type, shows it in a shared queue rather than an inbox, and escalates to the next person up if it sits unactioned past an agreed number of days. Every decision requires a recorded reason, not just approved or declined. Before deciding, the approver sees past requests of the same type and how they were resolved, surfaced by keyword and category rather than by memory. Once decided, the requesting club is notified automatically. It does not interpret the rulebook or recommend a decision — it makes the precedent visible and leaves the judgement where it belongs.
Who it is for
Registration officers who field the requests, compliance officers and general secretaries who decide the harder ones, and league operations managers who sponsor it to stop inconsistent rulings reaching clubs.
Possible first version
A web intake form with configurable exception types, a routing rule per type (who reviews, who escalates to), a queue view per approver, mandatory decision-plus-reason recording, keyword search across closed cases, and an automatic email to the requesting club once a decision is logged. Out of scope for version one: no write-back into the registration or membership database — approved exceptions are applied there manually — and no automated interpretation of competition rules or suggested decisions.
- Build classification
- Workflow application
- Rough effort
- 4-6 week first release
- Roles involved
- Registration officer, Compliance officer, General secretary, League operations manager
- Relevant to
- League office, Federation / governing body, Women's league, Collegiate athletics
- Systems in play
- Registration and membership databases, Email and shared drives, Document and rulebook repositories
- Product framing
- Automate a workflow
Questions we get asked
What do we need to have sorted before we could actually start using this?
Before build, someone needs to write down the exception types you actually see — late registration, dual registration, age-group move, whatever your rulebook allows for — and who is meant to decide each one today, even informally. That becomes the routing table. You do not need to digitise the whole rulebook first; the tool routes and records, it does not interpret rules. A handful of past decisions, even reconstructed from old email threads, is enough to seed the precedent log so it is useful from week one rather than starting empty.
Does this replace our registration database?
No. Your registration and membership database stays the system of record for who is actually registered. This tool sits in front of it, handling the request, the decision and the reasoning. In version one, an approved exception still has to be applied in the registration database by hand — there is no write-back. That is deliberate: getting the decision workflow right and proving people will use it matters more at this stage than an integration that assumes the workflow is already correct.
We handle this fine by email already. Why would we bother changing it?
If you handle two or three exceptions a season, honestly, email is probably fine and this is not worth building. The problem shows up at volume, or across a committee where different people pick up different emails, or when a club challenges a decision and nobody can show what was decided for a similar case last year. If that has happened to you in the last year or two, the case for it is real. If it has not, wait until it does rather than building it speculatively.
Once it exists, who has to keep it running and what does that cost them?
Usually the registration officer or compliance officer owns the routing table and updates it when competition rules change season to season — maybe an hour at the start of each season, not an ongoing burden. The bigger cost is discipline: someone has to actually write a reason for each decision rather than just clicking approve, or the precedent log fills up with decisions nobody can learn from. That habit has to be enforced by whoever sponsors this, not by the tool itself.
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.