Registration-day ID and age document verification log
Problem
On a club or academy registration day, a volunteer sits at a table with a laptop showing the online registration form and a stack of birth certificates, passports and parental consent letters. They glance at each document, tick a name off a paper sign-on sheet, and move to the next family in the queue. Nothing records which document was shown, who checked it, or whether the details actually matched what was typed online. Months later, when an age-group eligibility question is raised or a federation audit asks for evidence that identity was verified at registration, the answer is whoever was on the table that day trying to remember, because the paper sheet only shows a tick.
Product idea
A mobile checklist built for the registration table. The official pulls up a pending registration, selects which document was sighted (birth certificate, passport, national ID, parental consent), confirms the name and date of birth match what was submitted online, and signs off with their name and a timestamp. A free-text note captures anything unusual, such as a name spelt differently or a document nearing expiry. It works offline for registration halls with poor signal and syncs once reconnected. Each event produces an exportable verification log, one row per athlete, that a compliance officer can hand to an auditor or a federation without reconstructing the day from memory. It does not photograph or store the document itself; it records that the check happened and by whom.
Who it is for
Registration officers and volunteers running sign-on days, league operations managers who own the registration process, and compliance officers who need evidence that identity checks happened, not just that a box was ticked.
Possible first version
A mobile web app listing pending registrations pulled in by CSV import from the registration database, a document-type picker, a match confirmation toggle, a free-text note field, digital sign-off with name and timestamp, offline queuing, and CSV or PDF export per event. Version one does not write back into the registration database automatically; the export is reconciled manually. There is no document scanning or OCR, and no automated matching against the rulebook's age-grade rules. It covers one thing: proving a document was checked, by whom, and when.
- Build classification
- Micro-tool
- Rough effort
- 10 day prototype
- Roles involved
- Registration officer, League operations manager, Compliance officer
- Relevant to
- League office, Federation / governing body, Academy & youth, Women's league
- Systems in play
- Registration and membership databases, Paper sign-on sheets, Spreadsheets
- Product framing
- Verify or inspect
Questions we get asked
What do we need to have ready before a registration day to use this?
A list of that day's pending registrations, exported as a CSV from whatever system you already register players in. Version one imports that list rather than connecting live, so anyone can run a session by exporting a spreadsheet the morning of the event. The document types you expect to see (birth certificate, passport, national ID, parental consent) are configured once and reused for every event after that.
We already have a registration and membership database. Does this replace it?
No. It sits in front of it, for the minutes a document is actually being checked. The database remains the record of who is registered. This produces a separate, exportable log proving that a specific document was sighted at a specific time by a named official, which most registration databases were never built to capture.
Our sign-on days run on volunteers, not staff. Will they actually use another app?
That depends on it being faster than a paper tick sheet, which is the bar it has to clear. The screen is deliberately narrow: pick a name, pick a document type, confirm the match, sign off. There is no login screen between families, and it works without signal, which matters in a sports hall with poor reception and a queue building up.
Does this check whether the player is actually eligible under the age-grade rules?
No. It records that a document was checked and by whom, not whether the athlete meets an eligibility rule. Age-grade and eligibility decisions stay with your registration officer and the rulebook. Building automated rule matching on top of this would be a separate, later piece of work, and a riskier one, since it means encoding your eligibility regulations into the tool rather than just recording that a human looked at a document.
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.
- Club ground grading inspection app for affiliation renewalA mobile checklist that captures what a grading inspector actually sighted at a club ground, replacing paper forms and emailed photos with a timestamped, exportable record tied to the affiliation decision.