Tools: Available and Compliant

If you've ever heard "it's on the other site," you already know the truth: most tool problems aren't inventory problems. They're handover problems.

On paper, the tool exists. In reality, it's either sitting in a container on Site A, in someone's van, back at the yard — or it moved last week and nobody wrote it down.

And when you add compliance (test tags, expiry dates), the cost isn't just money — it's downtime and risk.

Here are three controls that keep tools available and compliant without turning your foremen into clerks.

Why spreadsheets fail for tools

Spreadsheets are great when the world is stable. Tools aren't. Tools move. People move. Sites change. Plans change.

A spreadsheet wants "perfect records." Site life produces "good enough, updated often."

                    So the target isn't perfection. It's operational truth:
                    
                            •
                            What's on this site today?
                        
                            •
                            What's overdue / missing?
                        
                            •
                            What's expiring soon?

Every movement needs a named owner (not "the team")

The fastest way to lose a tool is to make the handover collective.

For any transfer (yard → site, site → site, site → repair), pick one default owner:

Two names:

Issuer: the person releasing the tool
Recipient: the person accepting responsibility at the destination

That's it. Even if the record is just "Issued by A to B, on date," you've created ownership — and ownership prevents ambiguity.

Keep the site list "true enough" with a daily reality check

You don't need to scan every item every day. You need a rhythm that catches drift before it becomes chaos.

Practical version:

Each site has a simple "Tools on site" list.
Once per day (or per shift), the foreman confirms: "List matches reality" or flags exceptions.

Tools are managed as part of the day's work, not as an end-of-month audit.

Expiry should surface as an exception, not a calendar chore

Tag expiry becomes a fire drill when it's hidden.

Use a simple window:

Expiring in 30 days = warning
Expiring in 7 days = urgent

Then you only act on exceptions:

Schedule re-test
Swap with a compliant tool
Pull from site before it causes downtime

Mistakes to Avoid

Tracking too much detail

Serial + tag + site + status is plenty.

No "missing" state

Tools disappear because nobody is allowed to say "we don't know where it is."

Expiry ownership unclear

If nobody owns compliance, everyone owns it — which means nobody owns it.

The smallest system that works

If you're starting from scratch, the minimum viable setup is:

1) A site tool list
2) An owner for every transfer
3) An exception view for missing/overdue/expiring

Question for you

What hurts more in your world: tools being unavailable, tools being damaged, or tools failing compliance at the worst time?