Every estate has an asset register. Usually it is a spreadsheet, started with great discipline during an audit or a contract mobilisation, accurate for about six months, and quietly abandoned the first time reality got busy. The failure is so universal that it is worth being honest about the cause: most registers are designed for the person who reads them, not the person who has to keep them alive.
The fields that earn their keep
A register only needs the fields that answer real questions. In practice that is:
- Identity: asset type, make, model, serial number. The serial is non-negotiable — it is how warranty claims, recalls and F-Gas records attach to the right unit.
- Location: site, floor or zone, and a photo of where it lives. “Roof plant, east side” saves a lost hour per visit.
- Dates: installation and warranty expiry. Most estates pay for repairs on equipment still under warranty simply because nobody could check quickly.
- Compliance attributes: for refrigerant-bearing kit, the gas type and charge (this drives leak-check frequency); for anything certificated, the certificate and its expiry.
- Condition & history: not a static “condition: fair” field — the actual trail of jobs, worksheets, readings and photos over time. Condition is a derivative of history, not an opinion typed once.
Everything beyond this list should justify itself. Every optional field you add is a small tax on the person capturing the data, and those taxes compound into abandonment.
The register is only as good as the capture moment
Here is the design decision that separates living registers from dead ones: who updates it, and when? If the answer is “someone in the office, later, from notes”, the register is already dying. The only sustainable capture moment is on-site, at the asset, by the person standing in front of it — an engineer photographing the data plate, a site manager snapping a new install, a worksheet that updates the record as a by-product of the job.
That means phone-first capture, with the pieces that make it painless: photograph rather than transcribe, guided fields rather than free text, and offline capability for plant rooms and basements where signal goes to die.
Start with one site, not a survey
The instinct is to commission a full estate survey and load everything at once. Resist it. Load one site — your worst one — and run it properly for a month: issues logged against assets, jobs updating histories, certificates attached. You will learn more about your data model from four weeks of live use than from any survey specification, and the survey you eventually commission will be sharper for it.
FaciliTasker is built around exactly this loop: bulk import to start, phone-first capture to stay alive, and a register where every asset carries its own history, certificates and F-Gas data — owned by you, whoever does the maintenance. Book a demo and bring one site’s spreadsheet; we will show you what it becomes.
