Every AV team has a spreadsheet. It was accurate once, on the day of the audit. Since then a projector was swapped under warranty, two rooms were refitted, a trolley of laptops moved buildings, and a DSP was replaced by a contractor who did not tell anyone. The spreadsheet still says what it said in February.
The problem is not discipline. It is that a spreadsheet has no way of knowing the world changed. An asset register that stays accurate is one that is told about changes by the equipment itself, and that is organised so a human can keep up with the rest.
Start with the hierarchy, not the devices
Most registers fail at the first column. “Location: B2.14” means something to the person who typed it and nothing to the next person. Before you list a single device, settle the structure:
- Campus (or site): City Campus, Clayton, the London office.
- Building: the name people use, with the code the facilities team uses beside it.
- Floor, if your buildings are large enough to need it.
- Room: the timetable name, because that is the name the lecturer, the booking system and the helpdesk ticket will all use.
Every device then hangs off a room. A device without a room is a device you will lose. This is also the structure that lets you answer the questions leadership actually asks: how many projectors in Building B, what did we spend on Level 3, which campus has the oldest fleet.
One record per physical device
The second failure is duplicates. The same projector appears once from the purchase order, once from the vendor cloud, and once from the technician who logged it by serial number. Three records, one device, and nobody knows which to trust.
The rule is one record per physical thing, and every source feeds that record. Serial number and MAC address are the anchors; model, purchase date, warranty expiry, firmware and current status are the fields that sources fill in. When a vendor platform and a manual entry disagree, the register should say which source it trusts for which field, and show the history, rather than silently overwriting.
Let the devices update their own rows
This is the part a spreadsheet cannot do. A networked projector knows its own model, serial, firmware, lamp or laser hours and temperature. A codec knows when it was last online. If the register is connected to the equipment, those fields update themselves, and the “last seen” date on every row tells you, without an audit, whether the device is still where you think it is.
What the devices cannot tell you is still a human job: purchase cost, warranty paperwork, the schematic for the room, the photo of the rack. Attach those to the room or the device so they are findable from the record, not in a shared drive folder called “AV docs FINAL v3”.
Audits become exceptions, not events
With the structure in place and the devices reporting, an audit stops being a two-week walk with a clipboard. It becomes a short list of exceptions: devices that have not been seen in 30 days, rooms where the register says four devices and the network sees five, warranties expiring next quarter. A technician checks the exceptions in an afternoon. Everything else is already right.
A practical first month
- Week 1: agree the campus › building › room structure with the people who own the timetable and facilities. Use their names.
- Week 2: import the existing spreadsheet, deduplicated on serial number, into that structure. Expect to find devices with no room; park them in a holding area and resolve them room by room.
- Week 3: connect what reports automatically: the vendor clouds, the controllers, the networked displays. Watch the “last seen” column fill in.
- Week 4: attach the documents that matter most (warranties and schematics for the big rooms first) and run your first exceptions list.
The register you have at the end of that month will still be accurate in six months, because it is no longer waiting for someone to remember to update it.