SportsFirst

Kit and equipment stock threshold monitor

Internal dashboardWorkflow application3-5 week first releaseMonitorPrototype-ready

Problem

Kit and equipment stock is tracked in a spreadsheet on one laptop, or simply known by whoever last walked into the store. Counts are updated when someone remembers, usually after a delivery, rarely after issue. A junior side turns up for a fitting and the size run for one shirt size is gone, discovered on the day rather than the week before. Training bibs, balls, first aid consumables and matchday kit all run down at different rates and nobody is watching the rate, only the shelf. Reordering happens because someone noticed a gap, not because a threshold was crossed. The procurement lead finds out when the kit manager sends a message asking for an emergency order, and the emergency order costs more and arrives slower than a planned one would have.

Product idea

A live board showing stock on hand for each kit and equipment line, by location, against a reorder threshold set per item. Stock changes are entered as quick counts or check-out events rather than a full inventory system: a kit manager taps 'issued 12' after a training session instead of updating a spreadsheet that evening. When an item crosses its threshold, the tool escalates to a named procurement lead by email or message with the item, location and current count, before the shelf is actually empty. The board shows red, amber and green per item rather than a wall of numbers. It does not place orders, generate purchase requisitions or talk to a finance system: it tells the right person that something needs ordering, in time to order it properly.

Who it is for

Kit managers and equipment officers who count stock day to day, and the procurement lead who owns reordering and would sponsor the threshold rules and alert routing.

Possible first version

A web dashboard with a configurable item list per location, a manual count and check-out entry screen, a reorder threshold per item, and an email alert to a named owner when an item crosses it. Historical count entries build a simple depletion view so thresholds can be adjusted from real usage rather than guesswork. Out of scope for version one: barcode or RFID scanning, automatic stock deduction from a point-of-sale or procurement system, and purchase order generation. Counts are entered by hand, which is the trade-off that keeps this buildable in weeks rather than months.

Build classification
Workflow application
Rough effort
3-5 week first release
Roles involved
Kit manager, Equipment officer, Procurement lead
Relevant to
Professional club, Academy & youth, Collegiate athletics, Federation / governing body
Systems in play
Spreadsheets, Inventory and stock tools, Messaging apps
Product framing
Monitor

Questions we get asked

What do we need ready before this can start tracking anything useful?

An item list with a reorder threshold for each line, and a location list if you hold stock in more than one store or ground. Historical counts help but are not required: the board is useful from the first count entered, and thresholds can start as a guess and be tightened once a few weeks of real depletion data exist.

We already keep a stock spreadsheet. Does this replace it?

It replaces the spreadsheet as the place counts are entered and thresholds are set, because a spreadsheet has no way to notice a threshold has been crossed and tell someone. It does not replace a procurement or finance system: version one has no purchase order capability, so an order still gets raised through whatever system already handles that.

Our kit staff barely have time to log kit as it is. Won't this just be another thing to update?

Only if entering a count takes longer than not entering one. The entry screen is built for a quick tap after a session, such as issued, returned or counted, rather than a full stocktake, and it is worth testing against how your kit room actually works before committing to it. If keeping counts current takes more time than it saves, the alerting on top of it is worthless.

What happens if nobody logs a count for a week because the season is quiet?

The board shows the last known count and how long ago it was entered, rather than pretending to know a current figure it does not have. A stale count is flagged as stale, not hidden. Alerts are only ever raised against the last entered figure, so if nobody has counted an item in a month, the tool says so rather than guessing.

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 Equipment, inventory & logistics