An asset register is only as accurate as the last change recorded against it. A multi-site roll out makes many changes in a short window, usually through engineers who will never use the register. The programme is built to install equipment, not to record it, and the register drifts as a result.
Why registers drift during a programme
Drift often starts at planning. The register is exported to a spreadsheet, the spreadsheet becomes the working copy, and field changes land there rather than in the system of record. At programme close there are two versions and neither is complete.
A replacement unit ships with a different serial from the one on the pick list. A switch goes into a different rack because the planned one had no spare power. A device due for removal stays on site because the courier did not arrive. Each is a reasonable decision on the day. None reaches the register unless someone is required to record it.
What per-site completion data must capture
A report that says “site complete” tells the register nothing. For each site, the engineer’s completion record should hold:
- Serial number and asset tag of every device installed, read from the device
- Serial number and asset tag of every device removed, and where it went
- Location at the level the register uses: building, floor, room, rack and U position
- Any deviation from the site plan, with the reason
- Photographs showing labels and position
- Engineer name, date and work order reference
Format matters as much as content. Free text in an email has to be re-keyed, and re-keying is where transposed characters enter the register. A form whose fields match the register’s fields removes that step. Before a multi-site roll out programme starts, ask to see the completion template and check it against your register’s schema.
Capture serials and tags at the point of work
Serials should be captured while the device is in the engineer’s hands, not reconstructed later from a delivery note. Delivery notes list what was shipped, which is not always what was installed. Once a server is racked and cabled, the chassis label may be hard to reach.
Scanning a barcode is more reliable than typing. Manufacturers also label identifiers differently: Dell systems carry a Service Tag, while HPE systems show a serial number alongside a product number. Agree in advance which field the register treats as the key, and tell engineers which label to read. Apply the asset tag before racking, then photograph tag and serial together so the pairing can be checked.
Reconcile before the site is signed off
Sign-off is the last point at which a discrepancy is cheap to fix. The engineer is on site or recently departed, removed kit has not been mixed with other sites’ returns, and the photographs are fresh.
Reconciliation compares three lists: what the plan said would be installed and removed, what the completion data says happened, and what the register now shows. Any line that does not match across all three should hold the site open. Ask any provider: what stops a site being marked complete when a serial on the completion form does not match the register? If the answer is that someone checks it later, the register will drift.
