The Asset Register Problem: Why the Foundation of Every Hard FM Contract Is Built on Data Nobody Has Verified
Before SFG20 can schedule a single task, it needs a list of assets to schedule against. That list — the asset register — is the foundation of every Hard FM contract, every PPM programme, every compliance report, and every pricing model. In the UK Hard FM market, that foundation is almost universally wrong. This article explains why, what it costs, and who carries the liability when it fails.
The Register Is Wrong Before the Contract Starts
Every Hard FM contract begins with an asset register. It is provided by the client, or transferred from the incumbent contractor, or both. It lists the maintainable assets on the estate: plant and equipment, M&E systems, fabric elements that require planned maintenance. SFG20 task codes are mapped against it. The PPM schedule is generated from it. The engineer team is sized from it. The price is built on it.
The register that arrives at mobilisation is almost never accurate. It is not a question of negligence or bad faith on the part of the client or the outgoing contractor. It is a question of how asset data degrades over the life of a contract and how the current UK contracting model provides no mechanism to arrest that degradation or verify the register at each transition point.
Baachu's experience across more than 300 Hard FM contracts and 4 million validated labour loading hours is that the gap between the register provided at mobilisation and the verified asset count on the actual estate runs routinely between 15 and 25 percent. On estates that have been outsourced multiple times without a physical survey, the gap can reach 30 to 40 percent. Some assets are missing entirely. Others appear on the register but no longer exist. Others are listed incorrectly: wrong asset class, wrong SFG20 task code, wrong service frequency.
The asset register is the most important document in a Hard FM contract. It is also the document that is most likely to be wrong, least likely to be independently verified, and most likely to be carried forward from one contract to the next without anyone checking it.
Five Reasons the Register Is Always Wrong, and Why SFG20 Makes Each One Worse
TUPE Transfers People, Not Assets
When a Hard FM contract changes hands, TUPE regulations ensure that the workforce transfers to the new contractor. There is no equivalent obligation covering asset data. The outgoing contractor is not legally required to deliver a verified, accurate asset register at contract end. What transfers is whatever register exists on the CAFM system at the point of handover — which reflects the data quality of the outgoing contract, including all the degradation that occurred during it.
The incoming contractor receives a dataset that was last fully verified at the previous mobilisation, which may have been five or seven years earlier. Every fit-out, refurbishment, plant replacement, and minor works project that occurred in the intervening period may or may not be reflected in the register, depending on whether someone updated the CAFM at the time. Most did not.
SFG20 makes this worse because its task codes are not asset identifiers. An SFG20 task code describes a category of maintenance activity — fan coil unit service, AHU inspection, chiller maintenance. It does not create a unique identifier for a specific physical asset on a specific floor in a specific building. When the CAFM is populated at mobilisation, someone maps SFG20 task codes against asset entries under time pressure, by engineers who have just arrived on site. Errors introduced at that stage persist for the life of the contract.
The Retender Cycle Destroys Data Continuity
The average Hard FM contract runs for five to seven years. Many estates have been outsourced continuously for twenty to thirty years, through four, five, or six contract changes. Each contract change is a data discontinuity. The new contractor brings a new CAFM platform, a new SFG20 mapping methodology, and a new mobilisation team. The asset data migrates from one system to another, with manual re-entry, re-mapping, and re-validation at each transition.
There is no mandated standard for asset data transfer in Hard FM contracts. There is no requirement for the client to hold a golden copy of the asset register independent of the contractor's CAFM. In most cases, the client does not hold asset data at all — the data lives in the contractor's system, and the client's visibility is through reports generated from that system. When the contract changes, continuity of that data depends on the goodwill and capability of both parties during a transition that is always pressured, often contentious, and rarely given the time it requires.
Estate first outsourced. Physical survey conducted. Register: 1,200 assets. Register is broadly accurate. PPM schedule generated from SFG20 mapping.
First retender. TUPE transfer. New contractor, new CAFM. Register migrated manually. Fit-outs in years 3–5 not all captured.
Register: 1,180 assets. Actual estate: ~1,290 assets.
Gap: ~110 assets. No physical survey. Register carried forward.Second retender. Major refurbishment in year 9 added M&E plant. Some captured, some not. Register migrated again.
Register: 1,240 assets. Actual estate: ~1,410 assets.
Gap: ~170 assets. Still no physical survey.Third retender. Three buildings added to the estate during contract. Two buildings partially surveyed at mobilisation. One was not.
Register: 1,680 assets. Actual estate: ~2,050 assets.
Gap: ~370 assets — 18% of actual estate unscheduled. No physical survey since year 0. Every SFG20 schedule since year 5 built on unverified data.Buildings Change Continuously; Registers Do Not
An occupied estate is never static. Tenants move in and fit out. Offices are reconfigured. Server rooms are expanded. Clinical areas are repurposed. Each of these changes alters the M&E plant on the estate: new fan coil units are installed, old ones are removed, new electrical distribution boards are added, cooling capacity is upgraded. Each of these changes should trigger an update to the asset register. In practice, the trigger is rarely pulled.
The process by which minor works or tenant fit-outs update the Hard FM asset register is, on most estates, informal and inconsistent. The project manager who commissioned the fit-out is focused on completion and handover. The Hard FM contractor's site team may or may not be notified. When they are notified, the CAFM update may or may not be made in real time. On a busy commercial office estate or an NHS trust with a continuous minor works programme, the register can diverge by 5 to 10 percent per year. Over a five-year contract, that compounds. SFG20 schedules generated in year five of a contract may be based on asset data that is materially wrong — not because of systemic failure, but because nobody built the process to keep the register current.
SFG20 Task Codes Are Not Unique Asset Identifiers
SFG20 operates at the level of asset categories and maintenance task types. It describes what should be done to a fan coil unit, an AHU, a chiller, a boiler. It does not create a unique identifier — a serial number, a barcode, a location code — for each specific physical asset on a specific estate.
The consequence is that when a CAFM system is populated from SFG20 task codes, the resulting register is a list of task categories, not a list of physical assets. Two fan coil units on the same floor may be indistinguishable in the SFG20 mapping. If one is replaced and the other is not, the register may not reflect which one was replaced. If one is decommissioned, the task against it may continue to be generated and closed by an engineer performing the task against the remaining unit — or by an engineer closing the task without accessing either.
Proper asset management requires a unique identifier for each physical asset: an asset tag, a QR code, a barcode linked to a specific location in the BIM model or the floor plan. SFG20 does not provide this. CAFM systems can provide it, but only if configured to do so and maintained through every contract transition and register migration. In most cases, it is not.
The Building Safety Act 2022 Requires a Golden Thread — No Mechanism Delivers It Across Contract Changes
The Building Safety Act 2022 introduced the concept of the golden thread of building information: a complete, accurate, and continuously maintained record of the building's assets, safety systems, and maintenance history. For higher-risk buildings, this is now a legal obligation on the Accountable Person. The obligation applies regardless of how many times the FM contract has changed, how many contractors have held the data, or how many CAFM systems it has passed through.
The gap between the legal obligation and the operational reality is significant. The golden thread requires continuity of asset data across contract transitions. The current UK Hard FM contracting model provides no mandated mechanism for that continuity. The client who holds ultimate responsibility for the golden thread under BSA 2022 typically does not hold independent asset data — they hold a contract with an FM provider who holds the data in their proprietary CAFM system. When the contract changes, the data transfers incompletely, manually, and without independent verification. The golden thread is broken at every retender. The legal obligation continues.
What a Wrong Register Costs: The Commercial Case
The asset register problem is not an abstract data quality issue. It has direct and quantifiable commercial consequences across the contract lifecycle.
| Register problem | Direct commercial consequence | Who carries the cost |
|---|---|---|
| 15–25% of assets missing from PPM schedule | Engineer team undersized at bid. Labour budget insufficient from day one. Contractor absorbs gap or service quality drops. | Hard FM contractor (margin) and client (service quality) |
| Assets on register that no longer exist | Engineer time spent raising and closing tasks against phantom assets. PPM completion rate artificially inflated. Compliance position overstated. | Client (false assurance) and contract manager (liability) |
| Wrong SFG20 task code mapped against asset | Wrong maintenance task performed at wrong frequency. Asset either over-serviced (cost waste) or under-serviced (failure risk and statutory exposure). | Client (statutory risk) and contractor (variation claims rejected) |
| Asset class wrong in register (e.g. FCU logged as AHU) | SFG20 generates wrong task, wrong time allowance, wrong frequency. Engineer on site finds wrong task. Either performs wrong task or raises variation. | Both parties — wasted time, disputed variations, contract friction |
| New plant installed during contract not registered | Unregistered assets receive no PPM. Warranty conditions may require manufacturer-specified maintenance. Failure during warranty: manufacturer may reject claim. | Client — uninsured asset failure, voided warranty, unbudgeted reactive cost |
The aggregate commercial impact of these five failure modes on a large Hard FM contract is measurable. On a contract with a register that is 20 percent short of the actual estate, the cumulative effect of undersized labour, inflated completion rates, wrong task frequencies, and unregistered new plant amounts to a contract that is not performing the maintenance the estate requires — while reporting that it is.
For the client, the risk is regulatory and operational: statutory compliance gaps, asset failures, warranty voidance, and BSA 2022 golden thread obligations that cannot be met with broken data. For the contractor, the risk is commercial: a pricing model built on a register that understates the estate by 20 percent is a model that will lose money, generate friction, and produce disputes over scope that consume management time on both sides.
The PPM completion rate means nothing if the schedule it measures is incomplete. A contractor achieving 98 percent completion against a register that covers 80 percent of the estate is maintaining 78 percent of the estate. Nobody's dashboard shows that number.
What an Accurate Register Actually Requires
An accurate Hard FM asset register is not produced by inheriting the outgoing contractor's CAFM export and mapping it to SFG20 task codes. It is produced by a physical survey of the estate, conducted by engineers who understand what they are looking for, cross-referenced against existing documentation, and recorded against a unique identifier scheme that survives contract transitions.
The components of a register that is genuinely fit for purpose as the foundation of an SFG20 PPM schedule are not complicated. They are simply not standard practice in the UK Hard FM market, because nothing in the current contracting model requires them.
- Physical survey: Every maintainable asset physically located, identified, and recorded by trade-competent engineers. Not an office exercise. Not an inherited CAFM export. A walk of the estate.
- Unique asset identifier: Each asset tagged with a unique ID — barcode, QR code, or NFC tag — linked to a specific location reference. Survives contract transitions because it is on the physical asset, not in a contractor's proprietary system.
- Correct asset class: Asset class verified against manufacturer documentation, not inferred from a CAFM entry. Determines which SFG20 task codes and frequencies apply.
- Condition assessment: Basic condition rating at survey — good, fair, poor, end of life. Identifies assets where SFG20 default frequency is insufficient and where capital replacement planning should begin.
- Client-held golden copy: The verified register is held by the client independently of the contractor's CAFM system. Survives any contract change. Forms the base for the next mobilisation.
- Change management process: Defined process for updating the register when plant is installed, replaced, or decommissioned during the contract. Not informal. Not optional. Built into the contract KPI framework.
None of these components is technically difficult. The physical survey of a typical medium-sized office or healthcare estate takes two to four weeks with the right team. The tagging exercise is straightforward once the survey is complete. The change management process is a contractual requirement, not a technical challenge. What is missing in most Hard FM contracts is not the capability to do this. It is the requirement to do it, and the commercial model that funds it.
The typical Hard FM contract does not include a line item for independent asset register verification at mobilisation. The typical client does not require one. The typical contractor does not offer one. Everyone inherits the previous register and proceeds. The first indication that the register is wrong comes when the engineer team is undersized in year one, when the first contract review reveals completion rates that do not reflect the estate's actual maintenance position, or when a regulatory inspection asks for evidence that cannot be produced because the data chain is broken.
Baachu's Approach to Asset Register Validation
Baachu's Hard FM practice has developed a systematic approach to asset register validation as part of bid support and contract mobilisation advisory. The process begins with a gap analysis between the provided register and available documentation — as-built drawings, O&M manuals, previous survey reports, BMS asset lists — to identify the likely scale of the discrepancy before the physical survey begins.
The physical survey is conducted by trade-competent engineers working to a defined asset classification framework aligned to SFG20 task codes, but using unique asset identifiers rather than category codes. The output is a verified register that the client can hold independently of any contractor CAFM system, with condition assessments against each asset class and a capital replacement forecast for assets identified as at or approaching end of design life.
The commercial case for this investment is straightforward. A bid built on a verified register prices the right estate. A contract mobilised from a verified register starts with an accurate PPM schedule. A client holding an independent verified register retains control of their asset data through every contract transition. The cost of the verification exercise is recovered many times over in avoided pricing disputes, avoided warranty failures, and avoided regulatory exposure.
If the answer is 'at the last mobilisation' or 'I'm not sure', your PPM schedule is built on data that may be 15 to 25 percent wrong.
Baachu's register gap analysis starts with your existing CAFM export and available documentation. In most cases we can quantify the likely gap before committing to a physical survey.
If you are going into a retender, mobilisation, or due diligence process in the next six months, now is the right time. Contact us: hello@baachu.com · baachurain.com
Frequently Asked Questions
Five structural reasons: TUPE transfers staff but not verified asset data; the retender cycle fragments data across multiple CAFM systems with no mandated transfer standard; buildings change continuously but registers rarely update in real time; SFG20 task codes are category identifiers, not unique asset identifiers, so mapping errors compound over time; and the Building Safety Act 2022 golden thread obligation has no corresponding contractual mechanism to maintain data continuity across contract changes.
TUPE legislation protects the employment rights of the transferring workforce. It does not cover asset data. The outgoing contractor has no legal obligation to deliver a verified, current, or complete asset register at contract end. What transfers is a snapshot of the CAFM system as it stood at the handover date — with all the data degradation, incomplete updates, and mapping errors accumulated during the contract. The incoming contractor inherits that data and typically begins the new contract without independent verification of its accuracy.
The Building Safety Act 2022 places a legal obligation on the Accountable Person for higher-risk buildings to maintain a golden thread of building information — a complete, accurate, and continuously maintained record of assets, safety systems, and maintenance history. This obligation does not pause when the FM contract changes. In practice, most clients do not hold asset data independently; it sits in the contractor's CAFM system. At every retender, the golden thread is at risk of being broken. Clients who rely on their FM contractor to hold the golden thread on their behalf are carrying a legal obligation that depends on a commercial relationship that may not survive the next procurement cycle.
A proper asset register verification starts with a gap analysis — comparing the existing CAFM export against available documentation (as-built drawings, O&M manuals, BMS asset lists) to estimate the likely scale of discrepancy. This is followed by a physical walk of the estate by trade-competent engineers, physically locating and recording every maintainable asset against a unique identifier scheme. Each asset is verified for correct classification against manufacturer documentation, given a basic condition rating, and tagged if not already tagged. The output is a verified register held independently of any contractor CAFM system, with condition assessments and a capital replacement forecast.
Based on Baachu's experience across more than 300 Hard FM contracts and 4 million validated labour loading hours, the gap runs routinely between 15 and 25 percent on estates that have been through one or two contract changes without a physical survey. On estates that have been outsourced multiple times — four or more contract changes over 20+ years — without an independent survey at any transition point, the gap can reach 30 to 40 percent. The gap grows with each retender cycle, each period of high change activity on the estate, and each year that passes without a CAFM update process in place.
- Art. 1 Is SFG20 Outdated? The Hard FM Baseline That Built an Industry and Why It Is Now Costing You Money
- Art. 2 SFG20 Labour Hours: Why Your PPM Pricing Is Wrong Before the Contract Starts
- Art. 3 Who Owns SFG20? BESA, Facilities-iQ, and the Hard FM Commercial Risk
- Art. 4 What SFG20 Compliance Actually Costs: Five Hard FM and TFM Perspectives
- Art. 5 The Asset Register Problem: Why the Foundation of Every Hard FM Contract Is Built on Data Nobody Has Verified (this article)
- Art. 6 Is There a Credible Alternative to SFG20? ISO 55001, condition-based maintenance, and the hybrid model.
- Art. 7 What Does Technology Do to the Case for SFG20? IoT, BMS integration, digital twins, and AI maintenance analytics.
- Art. 8 How to Build a Defensible Hard FM Maintenance Framework Without SFG20 as the Anchor.
- Art. 9 SFG20 State of FM Report 2026: What the Data Actually Shows About SFG20 Compliance, Asset Registers and Hard FM Dependency.
Going into a retender, mobilisation, or due diligence process? Your register gap analysis starts with one email. → hello@baachu.com
Next: Article 6 · What Credible Alternatives to SFG20 Exist for Hard FM?
Read Article 6 →