SportsFirst

Club affiliation application bottleneck map

Data & reportingWorkflow application4-6 week first releaseFind the bottleneck

Problem

A new club's application arrives by email as an attached form and a handful of PDFs: proof of insurance, a safeguarding policy, sometimes a bank statement. It lands in the general secretary's inbox and gets forwarded to whoever handles compliance that quarter. There is no single record of when it arrived, what has been checked, or what is still missing. A club chasing an answer rings the office and someone has to search old emails to work out where things stand. Some applications clear in under a month; others sit for a full season because an insurance certificate expired mid-review or a document got buried under newer messages. Nobody can say, across the season, which stage of the process actually eats the time.

Product idea

A dashboard built from the timestamps already sitting in the inbox, the document folder and the registration database, not a new form for anyone to fill in. It reconstructs each application as a sequence of stages, first contact, documents received, compliance check, committee decision, record created, and shows how long each one actually took against the pattern for every other application that season. Applications open longer than the typical run for their current stage are flagged with who last touched them. It does not chase clubs, approve anything or replace the committee's decision. It only answers one question reliably: where is this application, and how long has it been there.

Who it is for

League operations managers and general secretaries who own the affiliation process end to end, and compliance officers who want to know their queue is not the one holding things up.

Possible first version

Version one takes a manual export from each source, an email inbox search, a folder listing, a spreadsheet of registration dates, rather than a live feed. Applications are matched by club name and reference number, staged against a small fixed set of milestones, and shown as a distribution chart with a flagged list of anything stalled beyond the season's typical time for its stage. There is no automatic reminder to clubs or staff in this version, no write back to the registration database, and no live connection to the email system. Refreshing the picture means running the export again.

Build classification
Workflow application
Rough effort
4-6 week first release
Roles involved
League operations manager, Compliance officer, General secretary
Relevant to
League office, Federation / governing body, Women's league, Collegiate athletics
Systems in play
Registration and membership databases, Document and rulebook repositories, Email and shared drives
Product framing
Find the bottleneck

Questions we get asked

What do we actually need in place before this is worth building?

Dated records, somewhere, for each stage: when an application email arrived, when a document was uploaded or saved, when a committee decision was minuted, when the registration record was created. It does not need to be one clean system. If none of that exists in a form that can be exported or searched, there is nothing to reconstruct from and this is not the right first project.

Does this become our registration database?

No. It reads dates out of the registration database and other places, it does not hold club records itself and is not where anyone would look up a club's status. If it started taking on that role it would duplicate a system you already run and maintain, which is not the point of it.

We already know applications stall with the compliance committee. Why measure what everyone can already tell you?

Sometimes that belief is correct, in which case the dashboard confirms it quickly and is not worth extending further. More often the stage everyone blames is not the slowest one on the numbers, or it is slow for one reviewer and fast for another. The value is testing the assumption against timestamps rather than building on top of it.

Who has to keep this current once it exists?

Someone needs to re-run the export on a regular cadence, monthly is typical for a seasonal process like this. If nobody is assigned that task it will show one accurate season and then quietly go stale, which is worse than not having it, because a stale chart still looks authoritative.

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 it

More in League & federation administration