Industry

How to run a tool library or equipment pool, unit by unit

6 min read

Whether you run a makerspace, a construction crew, a field team, an AV or rental outfit, or a community tool library, you share the same headache: gear goes out, and someone has to know where it is. A drill, a laser level, a generator, a microphone kit. The hard part isn’t how many you own. It’s which specific one is out, who has it, and what shape it’ll be in when it comes back.

Why a count fails the moment gear gets loaned

Counting works fine for screws and filament: you have forty, you use six, you have thirty-four. But the moment you lend shared equipment, a count stops answering the question that matters. “We own eight impact drivers” tells you nothing when a crew lead calls asking where driver number three went, or when one comes back with a cracked housing and you need to know who used it last.

A pooled count hides exactly the details a library needs: which unit, with whom, in what condition. You end up keeping that in your head, on a whiteboard, or in a notebook by the door, and all three drift out of date the first busy week. The fix is to stop tracking a number and start tracking each tool as its own thing.

Set up each tool as a named unit with an asset tag

Instead of one item that says “Impact driver: 8,” give every physical tool its own identity. With unit-level tracking you turn on per-unit tracking for an item and then list each one individually: Impact driver #001, #002, #003, and so on. Each unit gets an asset tag (the number you stamp, engrave, or stick onto the tool itself) so the thing in someone’s hand matches the record exactly.

Now the system holds what the whiteboard never could: a row per tool, each one ready to carry a status, a holder, a condition, and a history. The pooled count still works (it’s simply derived from the units), but you can finally drill into a single piece of gear.

Use statuses to model where every unit is

The state of a tool in a lending operation is a short, predictable list. Map each unit to a status that says, at a glance, where it stands:

  • Checked in – on the shelf, available to lend.
  • Out on a job – loaned to a person or assigned to a crew or site.
  • In for repair – pulled from circulation while it gets fixed.
  • Damaged – flagged as not lendable until someone decides what to do with it.
  • Retired – written off, kept on record but no longer in the pool.

With statuses in place, “what’s actually available right now” is a filter, not a guess. You can see the whole pool, the three units out on the Riverside job, and the one sitting in the repair bin without walking the room.

Track condition and keep damaged units separate

A tool that comes back bent isn’t the same as one that comes back clean, and your records shouldn’t treat them as interchangeable. Record condition on the unit itself: good, worn, needs service, damaged. When a unit is flagged damaged or in for repair, its status keeps it out of the “available” list automatically, so nobody grabs the broken one and discovers the problem on site.

This is the real payoff of tracking each item individually rather than as a count. A number can’t tell you that two of your eight ladders are unsafe. A set of units can, and it can keep those two parked in a damaged status until they’re fixed or written off.

Checkout and return are just status moves

You don’t need a separate lending app bolted on. Checking a tool out is moving a unit from checked in to out on a job and noting who has it. Returning it is the move back, plus a quick condition check. Because every move is recorded, each unit carries its own history: when it went out, to whom, when it came back, and what state it was in each time.

That logged history is what turns “I think Dave had it” into a fact. When a generator goes missing or comes back damaged, you open the unit and read its trail. The same approach scales from a single makerspace shelf to a multi-site crew, which is why it’s the foundation for tool and equipment tracking for construction and for managing van stock across a mobile fleet.

Simple Inventory Management does this with unit-level tracking: flip on per-unit tracking for an item, give each unit an asset tag, and run checkout and return as status moves with a full history per unit.

A few habits that keep a tool library honest

The system only stays accurate if the floor habits back it up. A short routine goes a long way:

  • Label every unit with its asset tag. Put a QR code on the tool so anyone can scan it and update its status from a phone, no typing required.
  • Make checkout a two-second scan. If logging a loan is slower than just walking off with the tool, people will walk off with the tool.
  • Run periodic reconciliation. Once a month, scan the shelf and compare it to what the system says is checked in. Chase down anything “out” that’s been gone too long.
  • Act on damaged flags. Don’t let units sit in a damaged status forever. Repair, replace, or retire them so the pool reflects what’s usable.
Learn more: when to track each item individually, makerspace inventory, and QR codes for scan-and-go checkout.

Set up your equipment pool