Inter-club transfer and loan clearance workflow
Problem
A player transfer or loan between two clubs starts as an email: a release form attached as a PDF, sent to the receiving club and copied to the league office. The releasing club has to countersign, usually chased by phone because the email sits unread for days. The league secretary then checks the transfer window dates and outstanding fees against a personal spreadsheet, not the registration database, before manually updating the player's record. Nobody outside that one inbox can see where a request sits — approved, waiting on the other club, or stuck behind a fee query — so club administrators ring the league office to ask, and the competition administrator finds out a transfer has cleared only when someone remembers to tell them before team sheets are checked.
Product idea
A workflow that starts when a club submits a transfer or loan request online: player, releasing club, receiving club, and window dates pulled from a configured calendar rather than typed from memory. The releasing club gets a link to approve or reject with a reason, not an email attachment to countersign and post back. Once both clubs have acted, the league office sees a single review screen showing window eligibility, outstanding fee flag and any prior request for the same player, and clears or queries it in one step. Every request has a visible status — submitted, awaiting releasing club, under league review, cleared, rejected — that both clubs and the competition administrator can see without phoning anyone. Requests left untouched trigger an automatic reminder rather than a follow-up call.
Who it is for
Registration officers who chase signatures today, league operations managers who own the transfer window calendar, and club administrators submitting requests on behalf of players.
Possible first version
A web form for submitting a transfer or loan request, sequential approval steps for the releasing club and the league office, a status tracker visible to both clubs, and automatic reminder emails after a configurable number of days with no response. Window dates and fee-outstanding flags are entered by the league office, not pulled automatically. Out of scope for version one: no live integration with the registration or competition management system — cleared transfers export as a CSV for manual entry — and no automatic fee reconciliation with finance systems.
- Build classification
- Workflow application
- Rough effort
- 4-6 week first release
- Roles involved
- Registration officer, League operations manager, Competition administrator
- Relevant to
- League office, Federation / governing body, Women's league, Collegiate athletics
- Systems in play
- Registration and membership databases, Competition management systems, Email and shared drives
- Product framing
- Automate a workflow
Questions we get asked
What would we need to have set up before this could actually go live?
The transfer window dates for the season, a list of clubs with a named contact for each, and an agreed definition of what blocks clearance — an outstanding fee, an unresolved disciplinary matter, an incomplete registration. None of that is complicated, but it has to be written down and entered before the first request goes through, rather than sitting in the league secretary's head as it does now.
Does this replace our registration database?
No. The registration database stays the system of record for who is registered where. This sits in front of it, handling the request and approval steps that currently happen by email and phone. Version one exports cleared transfers as a CSV for someone to key into the registration database — it does not write to it directly, so you can judge whether the workflow itself is worth having before anyone touches an integration.
Our clubs already handle this by phone and email and it mostly works. Why change it?
It mostly works until it does not — a signature delayed past a window deadline, a request nobody can locate when a club asks where it stands two weeks later. This will not make a slow club faster; a club that ignores an email will likely be slow to click a link too. What it changes is visibility: everyone involved can see the status without ringing the league office, and there is a record of when each step happened.
Who ends up owning this once it exists?
Usually the registration officer owns the request queue and the league operations manager owns the window calendar and clearance rules. It reduces the phone calls but does not remove the person from the loop — someone still has to look at flagged requests and make the fee or eligibility call. If nobody is checking the queue, requests will simply pile up in a different place than the inbox.
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.