Running a tool crib: checkout, calibration and the tools that walk
How to set up tool checkout so kit comes back, calibration never lapses, and you can prove who had what.
5 min read
One tag, one record
Every tool gets a tag number and one record: what it is, where it lives, its condition, its calibration or service due date, and its whole history. Two records for one tool is how a missing spanner becomes an argument.
Checkout is a name and a time
Record who took it, when, and for which job or shipment. Nothing else is needed at the hatch. Check-in records the condition, so damage is attached to a person and a job while it can still be discussed.
Calibration is a date, not a memory
Measuring kit — torque wrenches, gauges, meters, load cells — carries a due date. Overdue calibration quietly invalidates the work done with it, so the due date needs to surface on its own rather than waiting for an audit.
Chase overdue returns daily
A tool that is one day late is findable; one that is a month late is gone. A short daily list of overdue returns recovers more kit than any policy.
What the history is worth
Per-tool history tells you which items break, which crews break them, and when replacing beats repairing. That is the argument you take to the budget.
Copy this table
| Tag number | Tool | Location | Checked out to | Job or shipment | Out at | Due back | Returned at | Condition on return | Calibration due | Service due | Status |
|---|---|---|---|---|---|---|---|---|---|---|---|
| — | — | — | — | — | — | — | — | — | — | — | — |
Keep these records without the paperwork — Unity & Utility logs drills, inspections and incidents, and flags what is overdue on its own.
See how it works