Most missing tools are not stolen. They are in a van, on another site, in a colleague's locker or in a drawer nobody checks. The fix is rarely more locks or more cameras. It is a simple, fast record of who took what, and when it is due back.
This article explains how to design a check-in/check-out process for tools and shared equipment that people will actually follow — and how to measure whether it is working.
What check-in/check-out means
A check-out records that a specific asset has been issued to a custodian — a person, team, project or site — usually with a due date. A check-in records its return, ideally with its condition. Together they give you three things a static register cannot:
- Custody — who is responsible for the item right now.
- Availability — whether it can be booked or issued.
- History — who had it before, for how long, and what state it came back in.
Which assets need it
Not everything needs formal custody tracking. Good candidates share one or more traits:
- Portable — power tools, test and measurement instruments, radios, laptops, tablets, cameras.
- Shared — pooled equipment used by different people or crews.
- Valuable or attractive — easy to lose, easy to take home.
- Safety- or compliance-relevant — gas detectors, harnesses, calibrated gauges, where you must know who used which unit.
- Keys and access devices.
Furniture, fixed machinery and personal-issue items that never change hands usually do not need check-out — an assignment in the register is enough.
Designing a process people will follow
The most common reason check-out systems fail is friction. If issuing a tool takes longer than taking it, people will take it. Design for speed first.
1. Make identification instant
Every item needs a tag that can be scanned in one motion — a QR code, barcode or NFC tag. Typing asset numbers is too slow at a busy counter.
2. Decide who can issue
Two models work:
- Attended counter — a store person scans items out and in. Highest control; best for high-value tool cribs.
- Self-service — users scan items to themselves with a phone. Lowest friction; best for pooled equipment across sites.
Many organizations use both: attended at the central store, self-service for shared site kits.
3. Set sensible due dates
A due date turns "somebody has it" into "somebody has it and it is late". Default durations by category work well — one shift for consumable-heavy tools, one week for project kit, open-ended for long-term assignments with periodic confirmation.
4. Capture condition on return
A simple choice — OK, needs attention, damaged — at check-in is enough. Anything other than OK should create a maintenance task so the next user does not get a broken tool.
5. Handle kits and bulk issues
Crews often need a set of items. Issuing a kit, or several items to one person in a single action, keeps the process fast. Partial returns — some items back, some still out — should be possible without paperwork.
6. Follow up on overdue items automatically
Nobody enjoys chasing colleagues. Automatic overdue reminders and alerts do it consistently and without awkwardness.
Policies worth writing down
- Who can borrow which categories, and for how long.
- What happens when an item is overdue, damaged or lost.
- Whether items can be passed directly between people (transfers) or must come back to the store first.
- That disposal or transfer of an item is not allowed while it is checked out.
- How calibrated or inspected equipment is blocked from issue when its inspection is overdue.
Measuring whether it works
A few simple numbers show whether the process is healthy:
- Overdue rate — share of active check-outs past their due date.
- Unreturned items — count and value of items overdue by more than, say, 30 days.
- Utilization — how often each item is actually used. Low-utilization items can be redeployed; consistently fully-booked items may justify buying another.
- Audit variance for checked-out categories — if custody tracking works, missing-item counts in audits should fall.
Illustrative example: a store with 400 portable tools has 60 checked out at a given time, 9 of them past due. Overdue rate = 9 ÷ 60 = 15%. If that falls to 3 of 60 (5%) after overdue reminders are introduced, the process is working.
Common failure modes
- "Just this once" borrowing outside the system. Solve with speed and a culture where scanning is normal.
- Returns not scanned — items put back on the shelf without check-in, so they show as still out. Put a return bin by the scanner or make check-in a single scan.
- Group custody — "the crew has it" with no named person. Always issue to a named individual or a project with a named owner.
- No consequence for overdue items. Reminders help, but management follow-up on long-overdue items is what changes behaviour.
Check-in/check-out in Asetavo
Asetavo's check-out feature lets you issue assets to people, departments, projects or sites from the mobile app or the web, with due dates and bulk check-outs for kitting out a crew. Partial returns are supported, an availability badge shows what is free, overdue alerts and reminders chase late items automatically, and disposals are blocked while an item is checked out. Every loan stays on the asset's history in the register, and utilization shows up in reports. Scanning works offline and syncs later. Check-in/check-out is part of the Growth plan and above — see pricing.
Related: what is asset tracking? and asset tag selection.