Kit and equipment issue-and-return workflow
Problem
Kit assignment is tracked in a notebook the kit manager carries between the store cupboard and the changing room — who has which shirt number, which size, which training top, and what has not come back after a loan or a swap. When a player leaves or a size changes, the notebook is amended in pen and the old line stays visible, crossed out. Before an away trip someone has to flick back through weeks of entries to work out who still owes a returned item, and the answer is usually wrong. Deposits owed for lost kit get forgotten until a supplier invoice arrives months later. At season end, reconciling the notebook against the actual stock in the cupboard is a full day's count against a record nobody trusts.
Product idea
A structured kit ledger built around the same request-issue-return cycle the kit manager already runs, but as a queue instead of a notebook. A player or coach raises a request, the kit manager approves and records what was issued against inventory, and the item stays open until it is marked returned or written off. Ahead of any date flagged as a squad deadline or travel departure, the tool surfaces exactly who has an item outstanding and sends a single reminder to the player, rather than the kit manager working it out from memory. Deposits and replacement charges are logged as a note against the player record. It deliberately does not do barcode or RFID scanning in this form — each entry is a manual tap against a known list.
Who it is for
Kit managers who own the store cupboard, team administrators reconciling stock at season end, and travel coordinators who need to know before departure that nothing is still out on loan.
Possible first version
A web app with an imported inventory list (CSV), a player roster, and an issue/return log capturing item, size and date against each player. An outstanding-items view flags anything unreturned past a set number of days or ahead of a marked travel date, with a one-tap email reminder. Deposit and replacement notes are free text, not a payment flow. Out of scope for version one: barcode or RFID scanning, two-way sync with a finance or ERP system, and automatic size-based reordering.
- Build classification
- Workflow application
- Rough effort
- 3-5 week first release
- Roles involved
- Kit manager, Team administrator, Travel coordinator, Assistant coach
- Relevant to
- Professional club, Collegiate athletics, Academy & youth, Women's league
- Systems in play
- Equipment inventory records, Messaging groups, Spreadsheets and slide decks
- Product framing
- Automate a workflow
Questions we get asked
What do we actually need ready to start using this?
A current inventory list — item, size run, quantity — and a player roster, both of which usually already exist as a spreadsheet even if day-to-day tracking happens on paper. Import those two lists and the ledger starts from a true count. If the inventory list is itself out of date, the first weeks will surface discrepancies, which is the reconciliation the season-end count was trying to do anyway, just earlier.
Our kit manager has run this off a notebook for ten years and it works. Why change it?
It works for one person's memory as long as that person is available. It stops working the moment someone else needs the answer — a travel coordinator checking outstanding loans before a trip, or an administrator covering while the kit manager is off. The notebook is not being replaced because it is inaccurate; it is being replaced because only one person can read it.
Who ends up maintaining this once it exists?
The kit manager owns the day-to-day approve-and-issue step, which replaces rather than adds to the notebook entry they already make. The ongoing cost is small: someone has to action the outstanding-items list before it becomes noise, and someone has to keep the inventory count honest after a physical stocktake. If nobody reviews the outstanding list, it becomes exactly as unreliable as the notebook it replaced.
What happens if the kit manager is issuing kit pitch-side with no signal?
Entries queue on the device and sync once connected, so a changing-room issue at an away ground is not lost. What it will not do is give a live outstanding-items answer mid-session if the phone has been offline for a while — that view catches up once the sync completes, and it is a reason not to rely on it for split-second matchday decisions.
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 Team & roster operations
- Fixture congestion squad depth simulatorA scenario tool that projects squad depth across a congested run of fixtures against rest rules, showing where a position group would fall short before the block starts.
- Late-availability squad change cascadeA workflow that updates the travel manifest, kit list and matchday squad sheet the moment a player's availability changes, and tells only the people who need to act.
- Live squad availability threshold boardA live board that tracks confirmed player numbers per position group against a minimum threshold and alerts the team operations manager before a fixture is short.