Almost everyone starts with the same thing: a clipboard by the door with a sheet on it. Name, tool, date out, date back. It works for about two weeks. Then somebody takes a drill at 6am without writing it down, somebody else writes an illegible name, and after the third time the sheet disagrees with reality people stop trusting it. Once nobody trusts it, nobody fills it in, and you are back to asking around.
That failure is not carelessness. It is a design problem. The sheet asked for more effort than the moment allowed, and it gave nothing back to the person filling it in.
What a checkout system actually has to answer
Four questions, and if it cannot answer all four it will not survive contact with a busy week:
- Who has it? A name, not a department.
- Since when? Without a date, "out" becomes permanent.
- Where is it supposed to be? A site, a van, a room.
- Is it back? The return is the half everyone forgets to design.
Notice what is missing: purchase price, supplier, warranty, depreciation. Those belong in an asset register, and mixing them into the checkout sheet is the fastest way to make it too heavy to use. Keep the thing people touch daily as light as it can possibly be.
Where the usual methods break
The clipboard
Breaks on legibility and on honesty. There is no way to check a claim later because there is no history - the sheet gets replaced when it fills up, and last month is in a bin.
The group chat
Breaks on search. "Who has the impact driver" is answerable in a chat for about a day, and then it is forty messages back. Chat is a good way to announce a checkout and a terrible way to store one.
One spreadsheet column that says who has it
This is the common half-step, and it breaks in a specific way: the moment a tool is returned, somebody clears the cell. The current state is right and the history is gone. When a drill goes missing in November you cannot see that the same person had it three times in October.
Doing it properly in a spreadsheet
1. Two sheets, not one
A tools sheet with one row per tool, and a separate log sheet that only ever gets rows appended. The tools sheet shows the current state. The log sheet is the history, and nothing is ever edited or deleted there. This single decision is what separates a system that survives an argument from one that does not.
2. Give every tool an ID
Not a description. "Yellow DeWalt drill" matches four things in most vans. A short code -
TL-014 - printed on a label and stuck to the tool means the log rows refer to
exactly one object. It also means you can scan instead of type.
3. Make checking out take ten seconds
If it takes longer than finding the tool, it will not happen. In practice that means one row: tool ID, person, date, site. A scanner helps enormously here - a USB barcode scanner is about $25 and behaves exactly like a keyboard, so it types the tool ID into the cell for you with no software to install. Phone cameras are less reliable for this than people expect, and a cheap scanner removes the excuse entirely.
4. Design the return, not just the checkout
This is where most systems die. Checking out is exciting - you want the tool. Checking in is admin, and nobody does admin. Two things help: make the return a single row in the same log rather than a hunt for the original entry, and put a visible list of what is currently out where people walk past it. A tool that is on a list with somebody's name against it comes back far more often than one that is quietly absent.
5. Review the "still out" list weekly, not monthly
A five-minute look at what has been out longest, once a week, catches the slow leak. By the time you notice at a quarterly stocktake, the person who had it has forgotten, and so have you.
When a spreadsheet is genuinely the wrong answer
Be honest about this, because the wrong tool wastes more than money:
- Several people need to edit it at the same moment, all day. Shared spreadsheets handle this badly and you will get conflicts and lost rows.
- You need permissions - some people allowed to see costs, others not.
- You need an audit trail that stands up formally, with a record of who changed what and when, for insurance or compliance reasons.
- You want automatic discovery - software that finds equipment on the network by itself. No spreadsheet does that, and nothing pretending to is honest.
If two or more of those apply, buy real software and do not feel bad about it. If none of them do, a spreadsheet is not a compromise - it is the correct answer, and it costs nothing per month to keep running.
A ready-made version
Everything above can be built from scratch in an afternoon, and if you enjoy that kind of thing you should. We also sell it already built: one Excel file with a dashboard on top, the two-sheet structure described here, a check-out log that never overwrites history, and a "currently out" view you can print and pin up. It runs offline, with no account and no monthly fee.
It is $79 once, and there is a live demo you can click through without buying anything or handing over an email address.