FM providers are selling lifecycle and CapEx forecasting to their clients, and most of them are trying to deliver it from a spreadsheet that goes out of date the day it is sent. A forecast a client can plan a budget on has to be a living model built on a validated asset register, tied to recognized life expectancy data and recalculated every time an asset is replaced or its condition changes.
Get the register and the logic into one database and the report stops being a quarterly fire drill and starts being something you can sell with confidence.
Spreadsheets got lifecycle costing off the ground
Every engineer and quantity surveyor knows Excel, it handles NPV and discount rates out of the box, and for a one-off condition survey of a single building it does the job well. Plenty of good lifecycle plans have started life as a well-built workbook.
The trouble starts when the forecast has to outlive the survey. A client contract runs for years. Assets get replaced, conditions change, interest rates move and the estate grows. The spreadsheet captured one moment, and every one of those changes has to be typed back in by hand, by whoever still understands how the formulas connect.
Spreadsheet models are also fragile in ways that are hard to spot. A 2008 analysis of multiple studies by University of Hawaii professor Ray Panko found that close to 90% of spreadsheets contain errors, as MarketWatch reported. Even Harvard economists Carmen Reinhart and Kenneth Rogoff acknowledged in The New York Times that a spreadsheet coding error had left five countries out of one of their most widely cited calculations.
A lifecycle report is a snapshot, a lifecycle model is a commitment
This is the distinction that decides whether you can deliver what procurement sold. A report answers "what did the estate look like when we surveyed it?" A model answers "what will we need to spend, and when, based on what we know today?" Clients buying CapEx forecasting are buying the second one, even if the contract only says "report".
A model needs three things a spreadsheet keeps separate. It needs a validated asset register, so every forecast line maps to a real asset. It needs recognised standards, such as CIBSE Guide M life expectancy and SFG20 maintenance codes, attached to each asset type. And it needs logic that recalculates remaining life, condition adjustments and replacement cost whenever any of those inputs changes.
When those three live in different files, the forecast inherits every gap in the register. In SFG20's 2026 report, just 15% of nearly 200 FM professionals said their asset registers were fully accurate. A CapEx forecast that finance doesn't trust is one they won't budget against.
That leaves providers in an uncomfortable spot. FM technical services teams tell us the same story: lifecycle reporting gets sold to clients before the asset data underneath is ready to support it. That gap is a contract risk, not a reporting inconvenience.
Put the register, the standards and the forecast in one database
Ninox is an AI-native low-code platform, which means your engineers can build the lifecycle model on top of the same database they use to capture and validate assets. There is no export step between the survey and the forecast, because they are the same records.
The structure follows the three things a model needs. The asset register holds every asset with its photos, condition and install date. Linked tables hold CIBSE Guide M life expectancy, SFG20 codes and NRM codes, so each asset type carries its standard automatically. Logic fields and scripts then calculate remaining life, adjust it for condition, and work out replacement cost and NPV using the discount rate your client agrees. When a surveyor updates a condition score on site, the forecast moves with it.
The output is something a client can use. Charts can group a date field by month or quarter, so a CapEx profile by quarter comes straight from the replacement dates. Print layouts and document templates turn the same data into exception reports with photos, costs and calculated values included, without anyone rebuilding the figures in Word.
None of this is a ready-made lifecycle costing module, and that is the point. Your team models lifecycle the way your contracts define it, on a low-code platform your own engineers can adjust when a client changes the brief.
Capital is scarce, so forecasts have to be right
The demand for credible forecasting is only going to grow. BCIS analysis of NHS estates data shows the estimated cost to clear the NHS maintenance backlog reached £15.9 billion in 2024/25, up 15.7% in a year, while just over £1 billion was invested in reducing it. When the gap between what needs doing and what can be funded is that wide, estate owners need to know exactly which assets to replace first.
For FM providers, that turns lifecycle and CapEx forecasting from a nice extra into table stakes on the next contract. The providers who win that work will be the ones who can show a forecast built on validated assets and recognised standards and update it the moment the estate changes. Build that model on a low-code platform your engineers own, and the report you sell becomes the report you can deliver.
Take the next step.
Let's figure it out together.
