Single-team equipment management is hard enough. Multi-team programs play the game on expert mode: one pool of gear, five or six squads, a dozen coaches, overlapping practice schedules, and a single shed everyone has a key to. The result is a phenomenon every program administrator knows by heart: gear that is never lost, exactly, but is permanently somewhere else. The 10U coach swears the 12U team has the pop-up goals. The 12U coach is positive they went back to the shed. The shed disagrees.
Nothing was stolen. Nothing was even misplaced, really. The program just has no concept of custody, and custody, not inventory, is what shared gear management is actually about.
The core idea: gear is always in someone's custody
A package in transit is never "out there somewhere." It's scanned to a truck, a driver, a facility: at every moment, one named party holds it. The package company doesn't achieve this with trust; they achieve it with handoffs that get recorded.
Shared gear needs the same rule: every item is in the custody of exactly one named person or location at all times. Not "the 12U team": teams can't answer texts. A person: Coach Rivera. Or a location: Shed A, Bin 3. The whole system reduces to making every custody change cheap to record, because the version of this that requires a committee meeting per cone bag will be ignored by week two.
Decide what's pooled, what's assigned, and what's duplicated
Before building custody chains, sort the inventory into three buckets: most programs lump everything together and create work for themselves:
- Assigned gear (uniforms, helmets, personal pads): issued to individual members for the season via signed checkouts. This never enters the sharing problem at all. Get it out of the shared pool conceptually.
- Team kits (a bag of balls, a cone set, a first-aid kit, scorebooks): issued to each head coach for the season, by checkout, exactly like a player's uniform. The coach signs for kit #3 in August and returns it in November. Most "shared gear" chaos evaporates when you realize 70% of the shed contents should just be seasonal coach checkouts, and that cheap duplication beats elaborate sharing. If two teams fight over cone sets weekly, buy a second $30 cone set. Sharing infrastructure should be reserved for things worth sharing.
- Truly shared assets (portable goals, pitching machines, EZ-Up tents, sound system, field-lining kit, the good radar gun): expensive, used episodically, genuinely impractical to duplicate. This short list is what needs a custody system.
That triage usually shrinks the hard problem from 300 items to 15.
Run the shared list like a tool crib
For the truly shared assets, borrow the model from any well-run workshop tool crib:
- Every shared item gets an ID and a home location. "Pitching machine PM-1, home: Shed A." The home location is the default custody: an item not signed out is presumed home, which makes audits a five-minute walk.
- Sign-out on the way out, sign-in on the way back. Whoever takes PM-1 records their name and expected return: a sheet hanging in the shed works; a shared digital log works better because it's readable from a phone when the shed is across town. The test of your system is whether the question "where is PM-1 right now?" is answerable without calling anyone.
- Direct handoffs get logged too. The failure case isn't shed checkouts; it's the parking-lot transfer, where the 10U coach hands the goals straight to the 14U coach to save a trip. Fine! Efficient, even. But the transfer is a custody change: thirty seconds to log "goals G-1/G-2: Rivera → Patel, 10/14" or the chain breaks exactly where it's most likely to.
- Seasonal reconciliation. At season end, the shared list should read all-home (or in known custody for winter storage). Anything else goes on the chase list with a name attached, which is the entire payoff: a chase list with names instead of a shrug.
If your program already runs member and coach checkouts through HometownLift's Equipment Accountability, the same machinery covers all three buckets (assigned gear signed out to families, team kits signed out to coaches, shared assets checked out and transferred with the trail kept for you) so "who has it right now?" is one lookup instead of three text threads.
A scenario: one soccer club, six teams, two fields
Picture a soccer club with six teams from U8 to U14, practicing across two parks. Shared assets: four portable goals, two ball-pump kits, six corner-flag sets, one lining cart, three tents.
Before: everything lives in two sheds, both coaches' WhatsApp groups serve as the tracking system, and every Saturday begins with someone driving between parks hunting goals. In November, one tent and a flag set are simply gone, last seen "at the jamboree, maybe?"
After triage: flags and pump kits become team-kit items: each coach signs for a set in August, returns it in November, done. The shared list shrinks to goals, lining cart, and tents: eight items. Each gets an ID and a home shed; a sign-out log hangs inside each door, mirrored in a shared sheet. The jamboree, the highest-risk event of the year, gets an explicit custody plan: one named volunteer signs out all tents and goals for the weekend and signs them back in Monday.
The Saturday goal hunt ends because the log answers the question before anyone drives anywhere. And when a tent is missing in November, the log says whose custody it was in, which turns "gone, maybe?" into a specific, polite conversation and, per the club's penalty schedule, a recovered cost if it stays gone.
Keep the friction lower than the chaos
Multi-team systems die from overdesign more often than underdesign. Three rules of thumb:
- Log custody changes in under a minute or coaches will route around the system. Phone-readable, two fields, done.
- One person owns the system per program, not per team: the equipment manager arbitrates, audits monthly (walk the shed, compare to the log, ten minutes), and is the human fallback when the chain breaks.
- Duplicate before you litigate. Recurring contention over a cheap item is a purchasing decision, not a scheduling negotiation.
The bottom line
Shared gear across teams isn't an inventory problem; it's a custody problem. Triage the closet into assigned gear, coach-checkout team kits, and a short list of truly shared assets; give that short list IDs, home locations, and a sign-out habit; log direct handoffs; and reconcile each season with names attached to whatever's outstanding. The "other team has it" era ends not with more trust or more texts, but with a chain of custody anyone can read.
When you want family checkouts, coach kits, and the shared-asset trail in one place, see how Equipment Accountability handles it.
