Equipment & Gear Inventory Tracking

Every club sports team that issues its own gear (jerseys, pads, sticks, a shared set of goalie equipment) eventually hits the same moment: someone asks "who has the size L away jersey" and nobody knows. It's not on anyone's desk. It might be in a car trunk. By the time equipment gets counted again, whatever's actually missing gets discovered as a surprise expense, not a tracked loss.

Here's what it actually takes to know what you have, who has it, and what it costs the club when it doesn't come back.

Track the SKU and the individual item separately

"We have 20 jerseys" and "we have jersey #14, a large, currently issued to one specific player" are two different levels of information, and a club needs both. The catalog level, jersey, in whatever sizes you carry, with a total count, is what you plan a season's equipment budget around. The individual-item level, this specific unit, this size, issued to this specific person right now, is what actually answers "who has it."

Tracking only the first gives you a number that's right in September and wrong by November, because nothing connects a missing jersey to a person. Tracking only the second, with no aggregate view, means answering "how many mediums do we have left" requires counting by hand.

Issuing and returning: keep it simple, keep it accurate

Issuing equipment should be a straightforward action, this item, to this roster member, and it shouldn't be possible to issue something that's already checked out to someone else. That sounds obvious until it's week three and two different officers have both handed out the same numbered jersey to two different players because neither checked first.

Returns should be equally simple: mark it back, and it becomes available again. The friction that kills equipment tracking programs isn't the concept, it's officers deciding a two-minute process isn't worth doing after a long practice. Whatever system you use, the issue-and-return action needs to be fast enough that it actually happens.

When something is actually lost, it should hit the budget automatically

This is the piece that's easy to build wrong or skip entirely: reporting a lost item and updating the budget are two different tasks in most clubs, done by two different people, on two different timelines. The equipment officer knows what's missing. The treasurer finds out about the cost weeks later, if at all, usually when the equipment budget line doesn't add up at the end of the season.

The better model is one action: an officer marks an item lost, and the replacement cost shows up as a real expense in the team's actual budget in the same motion, no separate finance entry, no relying on someone to remember to tell the treasurer. And it should be safe to mark the same item lost more than once without double-charging the club if someone reports it twice by accident: a genuine idempotent write, not something that trusts everyone to only click the button once.

What the stock view should actually tell you

The useful number isn't "how many jerseys do we own." It's the breakdown: how many are currently issued, how many are sitting available, how many are gone for good, and ideally, all of that broken down by size, because "we have three large jerseys" and "we have zero larges and eight extra-smalls" are very different situations heading into a season.

The liability check that stops gear from walking off the roster

Here's the failure mode equipment tracking exists to prevent: someone quits mid-season, gets removed from the roster in five seconds by an officer who's cleaning things up, and the jersey they had checked out leaves with them because nobody thought to ask for it back first.

A system that actually connects roster and inventory should refuse that removal outright (not warn about it, block it) until whatever's checked out to that person is returned or otherwise resolved. It's a small piece of friction at exactly the right moment: the point where an officer is about to remove someone is also the point where they should be reminded that person still has the team's stuff. For more on how removal itself should work, see our roster management guide.

Be honest about what this doesn't cover

Two things worth knowing before you count on them: a system's underlying data model might have room for "damaged" or "in maintenance" as a status without actually giving officers a button to set it, worth checking rather than assuming, and something to track in a note field until it's a real workflow. And equipment tracking is often a feature reserved for a higher plan tier than the free tier; confirm your team's plan actually includes it before you build a season's process around it.

How TeamBasin handles this

TeamBasin tracks equipment at both levels, the catalog and the individual item, and ties loss directly into the team's actual finances.

• Catalog plus individually tracked units. Each item type is a catalog entry with a size breakdown; each physical unit (this specific jersey, this specific stick) is tracked separately, with its own status.
• Issue and return in one action each, with a check that stops the same item from being issued to two people at once.
• Reporting something lost automatically books the cost. The replacement cost lands as a real expense line in the team's budget in the same action with no separate finance entry, and reporting the same item lost twice by accident won't double-charge the club.
• A real stock summary: available, issued, and lost counts, broken down by size, in one view.
• Roster removal is blocked until equipment is resolved. A member with anything still checked out to them can't be removed from the team until it's returned.
• Straightforward about tier and scope. Equipment tracking is part of our Pro plan and above, and damage/maintenance status is on our roadmap, not a live workflow today; track that in notes for now.

If your club is still tracking gear on a whiteboard that gets erased every August, request access and we'll show you what it looks like tied to the actual roster and budget.