What to Do When Tools Don't Come Back: A Recovery Routine

Every guide about lending tools ends at the moment the tool leaves. Columns, due dates, a QR label on the gang box. All of it useful, and none of it answers the question that actually costs you money: it is three weeks later, the drill is not back, and the row on your sheet says "Jake, 14th."

Now what?

This is the part nobody writes down, so it gets improvised — badly, and usually by whoever is angriest that morning. What follows is the routine a shop of ten to forty people can actually run: a fixed weekly slot, four escalation steps, a stated point at which you stop chasing, and a write-off that closes the loop. It works on paper, on a spreadsheet, or in software.

Download the free printable overdue chase sheet and write-off log - three pages, letter portrait: a weekly chase sheet with the four escalation steps and the stop rule printed on it, and a write-off log to review each quarter. No signup, nothing uploaded.

This picks up where the setup guides stop. Equipment sign-out sheet template covers the columns, tool crib checkout system fields covers the data model, and how to stop losing tools on the job site covers prevention. This one covers what happens after the due date has already passed.

First, accept the number#

Some percentage of what goes out will not come back. Not because your crew is dishonest — because tools get left in a truck that went to another job, loaned crew-to-crew off the record, or genuinely broken and quietly binned by someone who did not want the conversation.

The mistake is treating each of these as a one-off surprise. If you lend things, losses are a running cost, and a running cost needs a routine, not an emotional reaction. The shops that recover the most are not the strict ones. They are the ones where chasing is boring, scheduled, and obviously not personal.

The weekly overdue slot#

Pick a fixed fifteen minutes. Friday morning works well — end of week, before anyone disappears, and the weekend gives you a natural deadline to offer.

In that slot you do exactly one thing: produce the list of everything past its due date and not yet returned, sorted by how long it has been out. Oldest first. Not by value — by age. Value tempts you to chase the expensive thing and ignore the four cheap ones, and it is the cheap ones that bleed you, because nobody ever chases them.

Then you work down the list with the escalation below, and you stop when the fifteen minutes are up. Anything you did not reach stays on top of next week's list, older still. That is the whole discipline.

The four steps, in order#

Step one, days one to seven: the neutral ask. One message, to the person, no cc. "Hey — the impact driver from the 14th, is that still with you or did it go back?" Note the second half. You are offering them the innocent explanation first, and often it is true: it went back and nobody wrote it down. Never open with an accusation you will have to walk back.

Step two, week two: locate the object, not the person. The question changes from "do you have it" to "where is it." Ask what job it went to and whether it is in a truck. In many shops the overdue items are not missing, they are misfiled — sitting in a van or another crew's gang box, findable in one phone call to a person who is not the borrower. This step often recovers more than the rest, and it is easy to skip, because by week two they have started thinking about blame instead of location.

Step three, week three: put a date on it. "Can you bring it Friday, or should I order a replacement?" That sentence does real work. It gives a deadline, it names the actual consequence, and it hands the decision back to them. Say it plainly and without heat, and say it once.

Step four, week four: decide and close. Either it comes back or you write it off. What you do not do is leave it open. An overdue list that contains items from four months ago has stopped being a work list and become a monument, and everyone stops reading it — including the entries that were still recoverable.

When to stop chasing#

Say the rule out loud before you need it, because deciding in the moment always produces an inconsistent answer that someone will notice.

A workable default: chase for four weeks, or until the chasing costs more than the tool. A twenty-dollar item does not survive three phone calls — you are spending more on the recovery than a replacement, and you are spending it on the thing that makes people dread you. Set a threshold value below which the item is written off at week two with no escalation at all, and be honest that this is a cost of doing business rather than a failure of policy.

The exception is anything with a certificate, a calibration date, or a serial number that appears on a compliance record. Those never get written off quietly. They get escalated as a distinct event, because "we lost a calibrated torque wrench" is a different problem from "we lost a torque wrench," and mixing the two in one routine is how the important one gets treated like the trivial one.

The write-off is a record, not a shrug#

When you close an item as lost, write down four things: what it was, who had it last, how long the chase ran, and roughly what replacing it costs. Thirty seconds. Take the "who had it last" from your sign-out sheet, or from the item's stock movement history if you are running this in software — the Returned line keeps the borrower's name, and so does the activity log's Issued To column.

Do this and after two quarters you have something genuinely valuable: a pattern. It is almost never distributed evenly. It is one crew, or one job site, or one category of item — cordless batteries and hand tools small enough to end up in a pocket. That pattern tells you where to spend your attention, and it is invisible if every loss was handled as a private annoyance and never recorded.

The pattern also tells you when the problem is not the people. If the same item type disappears from the same site repeatedly, you have a storage problem or a handover problem, and no amount of chasing individuals will touch it.

Two things that quietly break the routine#

A check-out with no due date is not overdue. Ever. This is the failure mode that makes every version of this system look like it is working while it does nothing. If the due-back field is blank, the item can never appear on an overdue list, on paper or in a spreadsheet formula. In software it never turns overdue - it sits in the active check-outs list with no due date, and nothing ever flags it. It will not surface until someone goes looking for that specific tool. Make the due date mandatory at handout, with sensible defaults nobody has to think about: end of shift for hand tools, end of week for project equipment. A blank there is not a small omission. It removes the item from your recovery process entirely.

Nobody reads a list they cannot finish. If the weekly list has sixty rows, it will be ignored within a month. Keep it short by closing items — recovered or written off — rather than by letting them accumulate. A list of eight things you will actually action beats a list of sixty you will scroll past.

Where software helps, and where it stops#

If you run this in InventoryQuick, the overdue sweep is automated: a daily job sends an emailed list of items checked out past their due date and not yet returned, with the days-overdue count and who has each one, and the same list is filterable in the app with an overdue-only view and sortable by person (the mobile app also filters by person). Note who receives it — the alert goes to every user on the account who has email notifications switched on, not only the owner, and it is on by default - so if you want one person chasing, everyone else switches the toggle off.

Several things have to be true before any message is sent, and each one is a way the sweep can look enabled while staying silent. The item has to be marked as a trackable asset — that flag is off by default, and without it the item cannot be checked out at all, so it can never go overdue. The check-out needs a due-back date. Email notifications have to be on for that user. That user must not have clicked the unsubscribe link in an earlier alert, because the alerts carry one and it switches them off, and turning Email Notifications back on restores them. And their address must not be sitting under a bounce suppression. And the account must not still be carrying the sample data set — while it is, the daily job skips that user entirely. Check-in and check-out is a Pro-plan feature, and an owner or admin has to switch asset tracking on for the organization first; it is off by default too. Partial returns are handled properly, so three of five drills coming back leaves two genuinely outstanding rather than closing the whole row.

The honest limit, and it decides whether this is for you: it tracks by quantity, not by serial number. You will know five went out and two came back. You will not know *which* three are still out. For hand tools and consumable equipment that is fine — the chase is against a person and a count, which is exactly what the routine above uses. For calibrated instruments, anything with a certificate, or anything where an auditor will ask which specific unit was on which job, it is not enough, and no routine papers over that.

One more distinction worth getting right before you build a procedure on any of this, because it cuts the other way and the useful half is the one people assume is missing. Custody *is* recorded and it *is* searchable. A check-out row stores who took it, who issued it and who received it back, and those names stay on the row after the return. The activity log carries the same names in their own Issued To and Issued By columns, its search box matches on them, and the CSV export keeps both columns — so "everything Jake ever had out" is a search, not an afternoon with a highlighter.

What has no field for a person is every *other* kind of movement. Correct a quantity by hand, receive a delivery, move stock between locations, and the ledger records the item, the amount, the type of movement and the timestamp, with nothing that says who did it. So "who has this tool" and "who had it last" both have answers you can query. "Who changed this number last Tuesday" does not, and that particular accountability has to live in your own paperwork.

Start here#

You do not need software to start, and you do not need to fix the whole system. Take your existing sign-out sheet, add a fifteen-minute Friday slot to chase whatever is oldest, and write down the four things every time you give up on an item. That alone recovers tools this month, and by next quarter the write-off log will have told you where the real leak is.

Related: Equipment sign-out sheet template | Tool crib checkout system fields | How to stop losing tools on the job site | Tool crib software | How to track tools on a job site