Asset tracking in 2026 is less about new technology than about using established technology well. QR codes, NFC and UHF RFID are all mature. Smartphones are capable scanners. What separates organizations that trust their registers from those that do not is almost always process and data design, not hardware.
This report works through the main areas of physical asset management, describes the approaches we see working, and ends with a maturity model and a prioritized checklist you can use to plan your own year.
1. Identification: every asset needs a scannable identity
The first step in every successful program we see is the same: give every asset a unique, permanent ID and a tag that can be scanned. Until that exists, every other process relies on people recognizing items and typing numbers, which is slow and error-prone.
What works:
- Meaningless, permanent IDs. IDs that encode location or department break when things move or teams reorganize.
- QR as the default. Every smartphone can read it, labels are cheap, and error correction tolerates wear.
- Technology by category, not by organization. NFC for keys and covered surfaces; UHF RFID for dense, valuable or mobile assets; QR everywhere else.
- Human-readable ID printed on every tag, as a fallback.
What does not: tagging before agreeing categories and locations, and choosing one technology for everything. The RFID vs NFC vs QR guide covers the decision in depth.
2. Tracking: event-based is enough for most equipment
A common early assumption is that tracking means knowing an asset's location continuously. For vehicles and some high-value mobile plant, that may be true, and GPS telematics serves it. For the vast majority of equipment — tools, IT, instruments, furniture, medical devices — we see teams get most of the value from event-based tracking: recording location and custody when something happens.
The events that matter most:
- Check-out and check-in of shared equipment.
- Transfers, recorded by scanning at the destination.
- Reads at choke points — doorways, store counters, docks — by fixed RFID readers where movement is frequent or losses are costly.
- Audit scans, which confirm location periodically.
The design question is where to place checkpoints, not how to track everything everywhere. See what is asset tracking?
3. Custody matters more than location
For portable equipment, who has it is usually a more useful fact than where it was last seen. A named custodian can be asked; a location in a busy warehouse often cannot.
In our experience the single process change with the largest effect on missing portable items is a fast check-in/check-out routine with due dates and automatic overdue reminders. The critical design constraint is speed: if issuing a tool takes longer than taking it, people will take it.
4. Audits: from annual event to continuous verification
The traditional audit is an annual, wall-to-wall count on paper, followed by weeks of reconciliation. The approach we see replacing it has three parts:
- Scan-based counting on phones, so results are timestamped, attributed and reconciled as the count happens.
- Risk-based cycle counts — high-risk items counted often, low-risk items less often — so the register is verified continuously rather than once a year.
- Bulk RFID reads in the dense areas where one-at-a-time scanning is the bottleneck.
The full audit does not disappear where policy requires it, but it becomes confirmation rather than discovery. Our physical asset audit guide covers the method.
5. Maintenance: records before optimization
Many teams want predictive maintenance. Most first need something simpler: a record of every repair and service against the asset it was done on. Without that history, it is impossible to know which assets fail, how often, or what they cost to keep.
The sequence we see work:
- Log every repair as a work order against the asset.
- Rank assets by criticality.
- Put preventive plans on critical assets with predictable wear.
- Use the history to tune intervals and decide repair-or-replace.
- Only then consider condition monitoring for the few assets where it pays.
See building a preventive maintenance program.
6. Finance and operations on one register
A persistent pattern: finance keeps a fixed-asset ledger, operations keeps a separate equipment list, and the two drift apart. Assets are disposed of on the floor but keep depreciating on the books; assets are bought and deployed but never capitalized correctly.
The fix is structural: one register, with financial fields on the same records as location and custody. Depreciation — book and, where needed, tax — runs from that register, and valuation reports reconcile to the ledger each period. Physical audits then directly test the balance sheet. See fixed asset depreciation explained.
7. Lifecycle: disposal is the weakest link
Acquisition is usually well controlled: purchases need approval, and invoices are recorded. The other end of the lifecycle is not. Scrapped, sold, donated or lost assets often leave the building without leaving the register.
What works:
- A disposal process that cannot be completed without a register update.
- Disposal blocked while an asset is still checked out.
- Gain or loss calculated against net book value at the date of disposal.
- Evidence (e-waste certificates, sale records) attached to the asset record.
8. Security and governance
As registers move from spreadsheets to shared systems, governance becomes practical:
- Role-based access — not everyone should be able to change costs or dispose of assets.
- A full audit trail on every record.
- Authenticated device events — reader and scanner inputs change the register, so they should be signed and checked, not trusted blindly.
- Revocable device sessions, so a lost phone or retired reader can be cut off immediately.
- Single sign-on, increasingly expected by larger organizations.
9. A maturity model
Use this model to locate your organization honestly. Most organizations sit at different levels in different areas.
| Level | Identification | Tracking and custody | Audits | Maintenance | Finance |
|---|---|---|---|---|---|
| 1. Ad hoc | No consistent IDs | Memory and asking around | Rare or never | Fix when broken, no records | Ledger only, not linked to physical items |
| 2. Listed | IDs in a spreadsheet; some labels | Location column, rarely updated | Annual, paper-based | Some repair notes | Separate finance and operations lists |
| 3. Tagged | Scannable tag on every asset | Check-out for shared items | Annual, scan-based | Work orders against assets | Financial fields on the register |
| 4. Managed | Technology chosen per category | Transfers scanned; overdue alerts | Risk-based cycle counts | PM plans on critical assets | Book and tax schedules from the register; monthly reconciliation |
| 5. Automated | RFID where it pays | Reader-based zones and movement alerts | Continuous verification; full audit as confirmation | History-driven intervals; condition monitoring where justified | Integrated reporting to finance systems |
Moving up one level in the weakest area usually delivers more than moving up in the strongest.
10. Priorities for 2026: a checklist
If you do nothing else this year, work through this list in order:
- Agree your register structure — IDs, categories, locations, custodians, statuses. (How to build an asset register)
- Tag every asset with at least a QR label.
- Put check-out on shared and portable equipment.
- Make disposals and transfers update the register.
- Run a scan-based baseline audit and reconcile it properly.
- Start risk-based cycle counts.
- Log all maintenance against assets; add PM plans for critical equipment.
- Move depreciation onto the register and reconcile to the ledger monthly.
- Pilot RFID only where the scoring framework says it pays.
- Review access roles and audit trails.
How Asetavo approaches these areas
We build Asetavo around the approaches in this report: one register for operations and finance; QR, barcode, NFC and UHF RFID tags side by side; check-outs with overdue alerts; scan-based audits with variance reports; maintenance work orders and PM due lists; depreciation with separate book and tax profiles; readers, zones and alerts where automation pays; and role-based access, audit trails, signed reader events and revocable device sessions throughout. SSO and data residency for Enterprise are coming soon.