Track company equipment by deciding what to include, giving every portable item a named holder, tagging it with a QR label, and making the update a by-product of scanning rather than a separate task. Count on a cycle rather than annually so discrepancies surface while they are still recoverable.
Most equipment tracking projects fail the same way. Someone decides to get organised, builds an exhaustive spreadsheet over a fortnight, and it is wrong within a month because keeping it right is nobody's job. The problem is not the tool — it is that the method asked for effort with no immediate payoff for the person doing it.
This guide describes an approach that survives contact with a working week. It is deliberately tool-agnostic: the sequence matters more than the software, and steps one to three are worth doing before you buy anything.
1. Decide what you are actually trying to prevent
Write down the specific thing that went wrong recently. The honest answer shapes everything else, and different answers lead to different systems:
- Things disappear and nobody knows who had them — you need custody, not a catalogue.
- Two teams need the same item on the same day — you need availability and bookings.
- Equipment fails because servicing was missed — you need maintenance scheduling, and possibly a CMMS rather than an asset tracker.
- Finance or an auditor wants a verified list — you need counts with sign-off, which is a different artefact from a register.
- You genuinely do not know what you own — you need a register first, and only that.
If you cannot name a recent incident, the project will not get adopted. Wait for one — there will be one — and use it as the reason.
2. Choose what to track, and what to leave out
The instinct is to track everything. Resist it: the effort of registering an item is roughly constant, and the value is not. Two tests decide it.
Does it move? Equipment that sits in one room and never leaves generates no useful history. Registering it is a data-entry exercise, not a control.
Would you notice it gone this week? If not, it does not need individual tracking. It may still need stock levels — which is a different, lighter treatment.
That usually leaves a middle band: not the fixed furniture, not the consumables, but the portable, valuable, shared equipment that crosses a threshold. This is where nearly all preventable loss happens.
One exception worth naming: if your tool prices by item count, you will be tempted to exclude cheap equipment to stay inside a tier. That is exactly the equipment that disappears quietly. Choose pricing that does not push you into a gap.
3. Decide who is accountable, before you decide how to record it
A register records facts; accountability changes behaviour. The two are different and only the second reduces loss.
Practically, that means every tracked item should have a named holder at all times — a person, not a department and not a location. "The warehouse has it" is not accountability, because a warehouse cannot be asked about it.
Where equipment genuinely lives in a place rather than with a person — a fixed store, a vehicle, a site cabin — treat that place as a location and count it periodically instead. Just be honest about which items are in which mode.
4. Label, in the right order
- 1Start with high value and high movement
Work down from the items that would hurt most to lose and move most often. You will cover the majority of the risk with a minority of the labels, and you will have a working system in an afternoon rather than a fortnight.
- 2Use QR codes unless you have a reason not to
Every phone reads them, which means everyone already carries a scanner. Barcodes work too. RFID is a real advantage for bulk counting without line of sight, but it means tags, readers and a budget — justify it before choosing it.
- 3Bind the label to the record once
Scan each new label against its asset a single time. This is the step that makes every future scan a two-second lookup rather than a search.
- 4Print on stock that matches the environment
Standard address labels are fine for desks and IT equipment. A stores cupboard, a workshop or anything handled roughly wants a tougher polyester label — one that falls off has cost you the whole record's usefulness.
5. Make the update a by-product, not a task
This is the step that decides whether the register is still accurate in six months.
Every register decays at the speed of how much effort an update takes. If updating means opening a laptop and finding a row, it will not happen. If it means scanning a code you were going to scan anyway — because scanning is how you look the item up — then the record updates itself as a side effect of something useful.
The same logic applies to handovers. A signature captured on the device at the moment of the handover takes fifteen seconds and happens. A form to be filled in later does not.
6. Count, on a cycle rather than annually
A once-a-year full inventory is an event everyone dreads and most organisations do badly. Cycle counting scopes to one location, category or department and runs in an afternoon, repeatedly.
The coverage is the same over a year, no single week is consumed, and discrepancies surface while they are recent enough for someone to remember what happened — which is the difference between a count that produces a number and a count that produces actions.
A realistic first month
- Week
1What to doName the problem. Export whatever list you already have, however bad. Decide the top 50–100 items to track. - Week
2What to doImport the list. Agree your location and category structure — this is worth doing deliberately rather than copying a structure you had outgrown. - Week
3What to doPrint and apply labels for those items. Scan each one once to bind it. - Week
4What to doRun real handovers with signatures. Count one location. Fix what the count exposes.
| Week | What to do |
|---|---|
1 | Name the problem. Export whatever list you already have, however bad. Decide the top 50–100 items to track. |
2 | Import the list. Agree your location and category structure — this is worth doing deliberately rather than copying a structure you had outgrown. |
3 | Print and apply labels for those items. Scan each one once to bind it. |
4 | Run real handovers with signatures. Count one location. Fix what the count exposes. |
Notice what is not in that month: tagging everything, custom fields, reports, integrations. All of those are easier once the system is already in daily use, and all of them are reasons projects stall before they deliver anything.
Frequently asked questions
What equipment should a company track?
Anything that moves and would be missed within a week. That usually means laptops, monitors, docks, phones, tools and instruments — including the cheap accessories, which are where quiet loss concentrates.
Who should be responsible for tracking equipment?
One named person accountable for the register's accuracy, with everyone who physically handles equipment able to record movements. The reverse arrangement — many accountable, few able to record — is what produces drift.
How do you track equipment without software?
A spreadsheet works while items sit still and one person maintains it. It breaks once equipment changes hands, because it cannot record that somebody accepted responsibility and cannot be updated where the equipment is.
How often should equipment be counted?
Scoped counts through the year rather than one annual sweep. Monthly or quarterly by location finds discrepancies while they are weeks old and often still recoverable.