Integrated facilities management gets sold on the wrong promise. The pitch is usually cost β one supplier, one invoice, one negotiation β and the operational reality, twelve months in, is the same set of services as before, with a layer of contract management on top and the cost saving largely absorbed by the IFM provider's overhead. The contracts that work are the ones procured for technical alignment and governance simplicity rather than for cost. UKFM's IFM proposition is built on that distinction: the model earns its keep through unified technical authority and a single accountable interface, and the cost story is a by-product, not the headline.
What IFM actually is β and isn't
The terminology in this segment of the market is loose. Total Facilities Management (TFM), Integrated Facilities Management (IFM) and Managed FM are used interchangeably by some providers and as distinct models by others. UKFM uses the following definitions, drawn from the BIFM (now IWFM) framework and consistent with PAS 3001:2013 (the publicly available specification for the procurement and management of FM services).
| Model | Scope | Provider role |
|---|---|---|
| Single-service | One discipline (e.g. cleaning only) | Service delivery |
| Bundled | Several disciplines under separate SLAs | Multiple service deliveries |
| TFM / Managed FM | All FM services, prime contractor + sub-contractors | Prime contractor, technical authority retained by client |
| IFM | All FM services, integrated technical authority | Operating partner, technical authority delegated |
| Joint Venture FM | Equity-shared delivery vehicle | Co-owned operation |
The distinction between TFM and IFM matters operationally. TFM is a procurement structure; IFM is an operating model. A TFM contract can be run by a prime contractor with no integrated technical view, simply coordinating sub-contractors against the SLAs. IFM, properly delivered, includes the technical authority β the engineering judgement about how the building is run, what gets prioritised, and how decisions are made between competing service requirements.
The governance architecture
The single largest determinant of whether an IFM contract works is the governance architecture, not the service specifications. UKFM's standard IFM governance structure runs on three layers, with a defined cadence and a documented escalation path between them. The chart below shows the typical effort distribution across the layers in a steady-state contract.
- Operational layer. Daily and weekly service delivery, helpdesk, on-site teams, immediate issue resolution. Reviewed weekly between site lead and client representative.
- Tactical layer. Monthly KPI/SLA reporting, performance trends, minor variations, planned works approval. Reviewed monthly at contract management level.
- Strategic layer. Quarterly business reviews, annual planning, capex pipeline, ESG reporting, contract evolution. Reviewed quarterly at senior level on both sides.
What goes wrong on most IFM contracts is the collapse of the layers β every issue routes to strategic level because the tactical reviews aren't happening, or every issue routes to operational level because the strategic conversations aren't being protected. UKFM's governance contracts include named individuals at each layer, defined meeting cadences, and a documented information flow between them.
KPI and SLA structures β outputs, not inputs
The choice of contract metrics shapes contractor behaviour more than any other structural decision. Input-led metrics (number of cleaners on site, number of PPM tasks completed) reward effort. Output-led metrics (cleanliness audit scores, asset availability, occupier satisfaction) reward result. UKFM's IFM contracts default to output metrics with a small set of input metrics retained where statutory or insurance requirements demand them β for example, fire watch coverage during hot works, or specified guarding levels for high-risk facilities.
The principal output metrics in our IFM contracts are: asset availability (% uptime against agreed criticality bands), helpdesk performance (mean time to acknowledge, mean time to resolve, first-time-fix rate), cleanliness audit score (output-spec aligned to BICSc), security incident response, statutory compliance evidence completeness, energy intensity (kWh/sq m, heating-degree-day adjusted), and occupier satisfaction (quarterly survey). The supplier is rewarded against the metrics, not against the activity that produced them.
Prime contractor vs Joint Venture
The two structurally distinct IFM delivery models are prime contractor and joint venture. The prime contractor model runs the supplier as the accountable party, with the client retaining commercial leverage through the contract. The joint venture model creates a shared delivery vehicle, typically with both parties holding equity, which aligns long-term incentives but reduces the client's ability to exit cleanly if performance deteriorates. The choice is partly philosophical β how much trust the parties want baked into the structure β and partly operational, depending on the duration of the relationship and the strategic significance of the estate.
UKFM operates in both modes. For most mid-market commercial portfolios, the prime contractor model is the right answer: cleaner exit rights, conventional contract law, no equity entanglement. For very large public-sector estates and long-duration commitments (15+ years), the JV model has structural advantages around capex co-investment and long-horizon planning that the prime contractor model can't replicate.
Benefits β and the honest accounting of them
The benefits of IFM that survive contact with the second contract year are: technical alignment between disciplines (the M&E team and the cleaning team are working from the same operational picture), single accountable interface (the client doesn't arbitrate between contractors when a problem touches multiple services), helpdesk consolidation (one ticket per issue, regardless of which trade resolves it), and cost transparency (a single cost stack rather than five separate ones with overlapping margins). The benefit that doesn't always survive is cost reduction β IFM saves money compared with separately procured single-service contracts, but the saving is typically 8β15% in our experience, not the 25%+ figures that occasionally appear in vendor proposals.
Risks β concentration, supplier capability, exit
Concentration risk is the principal IFM risk. A single supplier failing β through financial distress, contract dispute, regulatory action β exposes the client to a simultaneous loss of all FM services. UKFM's IFM contracts include explicit step-in rights, separable sub-contractor arrangements, and a documented business continuity plan that can be operationalised within 30 days if required. The exit clauses are negotiated in detail, including data portability (CAFM data, asset register, statutory compliance records), staff transfer (TUPE 2006 considerations), and the practical mechanics of bringing an alternative provider on stream.
Supplier capability risk is the second principal risk. An IFM provider strong in soft FM and weak in M&E engineering β or vice versa β will deliver the weaker side as a coordination layer rather than a competence layer, with the underlying work sub-contracted out and the technical authority correspondingly thin. UKFM's IFM proposition assumes the technical authority is genuinely held in-house across all disciplines; we sub-contract specialist work where the trade is genuinely specialist (lift engineering, HV, refrigeration), but the engineering judgement on the contract is ours.
BS 8536 and PAS 3001 β the standards backbone
Two BSI documents underpin most institutional-grade IFM contracts in the UK. BS 8536 is the design and construction handover standard, covering the requirements for FM information at handover from a project to operational state β soft landings, asset data, O&M documentation, training requirements. PAS 3001:2013 is the publicly available specification for the procurement and management of FM services, covering requirements gathering, supplier selection, contract structure, performance management and exit. UKFM's IFM contracts default to PAS 3001 as the procurement framework and BS 8536 as the new-asset handover framework, with ISO 41001 (the international FM management system standard) increasingly used as the operating-system specification on larger estates.
Mobilisation β the first 90 days that set the tone
The first 90 days of an IFM mobilisation determine the operational success of the contract more than any subsequent management decision. The work in this window is concentrated and difficult: TUPE transfer of the existing workforce (where applicable), CAFM platform deployment or migration, asset register verification, statutory compliance regime audit and reset, supplier and sub-contractor onboarding, governance cadence establishment, occupier communications, and the parallel running of services with the outgoing provider. UKFM's mobilisation methodology runs each of these as a defined workstream with named ownership, a published timeline, and a daily stand-up cadence in the first six weeks. The objective is a service transition that is invisible to occupiers and a contract transition that is procedurally clean β both of which require disproportionate effort upfront in exchange for materially fewer issues across the remaining contract term.
Data and reporting β what the client actually sees
The single most under-specified part of most IFM contracts is the reporting layer. The contract typically defines a list of KPIs, a reporting frequency and a dashboard tool, and leaves the actual data structure and presentation to the supplier. The result is reporting that satisfies the contractual minimum and tells the client very little that is operationally useful. UKFM's reporting layer is designed against the governance architecture: operational dashboards aimed at the site team, tactical reporting aimed at the contract manager, strategic reporting aimed at the client's senior team β each with its own data structure, cadence and audience. The aggregate effect is that the client's strategic team sees portfolio-level trends and exception reporting, the contract manager sees performance-against-target detail, and the site team sees operational ticket flow β without any of the three being buried in data intended for a different audience.
Integrated FM works when it is procured for the right reasons β technical alignment, governance simplicity, single accountable interface β and managed as an operating model rather than a procurement structure. It fails when it is procured as a cost-reduction exercise and managed as a vendor coordination problem. UKFM's IFM proposition is built around the first model. If you'd like to discuss IFM for your portfolio, contact UKFM at https://ukfm.group/contact/.
Procurement teams: send your RFI, RFP or ITT to UKFM via the contact form β