The third call-out this month
The entry gate at one development has failed again. The property manager calls the gate company, who send an engineer, who resets it and invoices for the visit. A few weeks later it happens again. The property manager has a feeling this is the fourth time this year, but the works history just says 'gate fault' against a handful of dates, mixed in with every other job at the block.
The directors ask whether the gate should be replaced. Nobody can say how much it has cost to keep it running.
Why the pattern stays hidden
Jobs are recorded against the block, not the thing that failed. Descriptions vary: 'gate stuck', 'entrance not opening', 'access issue'. Invoices are coded to a repairs heading, not an asset. And maintenance contract visits sit separately from reactive call-outs.
So the data needed to spot a failing asset exists, but in a form nobody can read as a history. Contractors, who do know the pattern, have little reason to point it out.
The cost of not seeing it
Repeated reactive repairs to a failing asset can cost more over time than replacement, and residents live with the inconvenience each time. Without evidence, property managers cannot challenge a contractor whose fixes do not last, and directors cannot make a replacement decision with confidence. Budgets for repairs keep being exceeded without a clear reason.
The asset history we build
We build an asset register for each block and link your existing jobs and invoices to it, going forward and, where possible, backwards through history.
- Asset register: the main assets at each block are listed, such as each lift, door entry panel, gate, pump set, communal boiler and fire alarm panel, with installer, age and maintenance contractor where known.
- Job linking: new jobs are linked to an asset when raised. For past jobs, a language model reads descriptions and invoices and proposes which asset they concerned, for a person to confirm.
- Invoice linking: contractor invoices are attached to the asset through their job, so cost per asset builds up automatically.
- Failure history: each asset shows its call-outs, fixes, parts and costs over time, and the gap between failures.
- Repeat alerts: when an asset passes the number of call-outs you set in a period, the property manager is alerted.
- Director summary: a simple report per asset for directors, showing history and cost to date, to support a repair or replace discussion.
| Asset | Typical hidden pattern | What the history shows |
|---|---|---|
| Lift | Frequent call-outs for the same fault | Call-out dates, faults and costs |
| Door entry system | Repeated resets without a lasting fix | Visits and time between failures |
| Automatic gate | Frequent engineer visits | Total spent this year and last |
| Booster pump | Seasonal failures | Failure dates against time of year |
What property managers can do with it
When the gate fails again, the property manager can see it is the fifth time and what each visit cost. They can ask the contractor for a proper diagnosis with the history in hand, or take a replacement proposal to the directors with numbers. Budgets for next year can reflect known problem assets rather than a flat repairs figure.
The same history also feeds into reserve fund planning, because the assets failing most often are usually the ones approaching replacement.
Is this happening at your blocks?
- The same lift, gate or door entry system fails repeatedly.
- Jobs are recorded against the block, not the equipment.
- You cannot say how much an asset has cost in repairs this year.
- Directors ask about replacement and you lack the figures.
- Contractor fixes do not seem to last.