The equipment tracker spreadsheet that reconciles itself.

Give every asset one ID at intake and keep a register that covers what the ERP ignores — the tools and instruments under the capitalization threshold. The register reconciles against accounting records weekly, so small equipment stays visible without forcing it into the ERP.

One row per physical asset: a single ID, a description, a location or custodian, purchase date, cost, and status. Anything that can move — tools, instruments, rental units — belongs on it, whether or not the ERP capitalizes it.

Start with a one-time field audit that matches physical assets to records using explicit match rules. After that, enforce one ID per asset at intake and let exceptions surface weekly, instead of reconciling everything again at audit time.

Tag at intake, before the asset reaches the field, and make the ID a condition of dispatch — no ID, no dispatch. A tag operations depends on gets maintained; one that only accounting reads does not.

As a rule of thumb, the moment more than one person edits it or assets live at more than one location. Past that point the spreadsheet becomes one more conflicting list instead of a system of record.

Checkout is an event, not an app. When equipment leaves the yard, an AI agent ties the unit to a job and a custodian at that point — from the delivery ticket, a photo, or a scan — and the return closes the loop in the same register when it comes back. Dedicated equipment checkout software sells that event as another subscription with one more list to reconcile; encoded into the systems you already run, the register is the record.

Yes — that is the normal case. A photo of the delivery ticket or the stamped plate is enough: AI agents read the hand-written serial number, match it against the register, and route low-confidence matches to a person instead of guessing. Accounting stops deciphering handwriting, and the serial becomes the link between the yard and the books. When you are ready for QR code asset tracking, the same register is already in place — the tag just makes the scan faster.

One governed register where every asset has exactly one row — one ID, one location or custodian, one status — spanning what the ERP’s fixed-asset module capitalizes, what the resource list tracks, and what the spreadsheet holds today. Most fleets keep three versions of this list; we collapse them into one, and AI agents keep it reconciled against every source, so the answer to “where is it” comes from the register, not from walking the yard.