SFG20 in Practice: How UK Facilities Teams Build Compliant PPM Schedules

Most UK facilities teams already know what SFG20 is. The challenge is not awareness. The challenge is the gap between referencing the standard and actually operating in line with it, every day, across every building, without drift.

That gap shows up in different ways: an Excel sheet with SFG20 codes that was last updated eighteen months ago; a subcontractor managing a set of assets with no codes assigned at all; a PPM schedule running tasks at a weekly frequency when the standard specifies daily. None of these teams would describe themselves as non-compliant. But in a compliance audit, each of those gaps carries real risk.

This post covers what SFG20 compliance actually requires of your operation, why it is harder to maintain than it looks, what UK portfolio teams are doing to close the gap, and what your CAFM or CMMS platform needs to support it properly.

What SFG20 Actually Is and Why It Carries Real Weight

SFG20 was formed in 1990 by the Building Engineering Services Association (BESA) in response to the industry's need for a standardised approach to building maintenance specification. Over 35 years it has become the recognised industry standard for building maintenance in the UK. It is used in 29 countries globally, with the UK as the primary market and the Middle East treating it as the de facto compliance baseline.

At its core, SFG20 is a library of over 1,000 maintenance schedules covering assets and building fabric across virtually all building types. Each schedule is a structured maintenance specification, authored by engineers with over 200 combined years of building services experience, that tells an operator exactly what needs to be done to a specific asset, how often, by whom, and to what legislated standard.

Understanding the architecture of a single SFG20 schedule is important for anyone building a PPM programme on top of it.

What a Single SFG20 Schedule Contains

The Colour-Coded Criticality System

One of the most practically useful features of SFG20 is the four-tier colour coding system that categorises every task by its legal and operational status. This eliminates the hours of cross-referencing legislation that a team would otherwise spend determining which tasks are legally required versus optional.

The SFG20 Task Criticality System

This distinction between tiers matters because it tells your team, at the task level, where the non-negotiable legal floor sits. Conflating red tasks with green tasks is how organisations end up over-maintaining some assets while remaining exposed on the ones that carry statutory risk.

The Living Standard Problem: Up to 700 Updates Per Year

SFG20 is not a document you download once and file. The standard updates monthly, and there can be up to 700 updates per year. In any given three-month window, the majority of the 1,500 schedules may have had at least one change. Those updates are not trivial. An update can change the frequency of a task, the time allocated to it, the task description itself, or the skill level required to carry it out.

The commercial implications of this are real and often overlooked. When SFG20 updates a schedule, it sends automated notifications with a side-by-side comparison of the old and new version. Customers retain the right to choose when to implement the update, giving operations teams control over the timing of any changes to their live schedules. But the decision to accept or reject an update must be documented. If you are audited and your PPM schedule diverges from the current version of the SFG20 standard, you need to be able to show that the divergence was a deliberate, justified operational decision — not an oversight that accumulated quietly over eighteen months.

The Silent Drift Risk

The most common problem we see is not deliberate non-compliance. It is quiet drift. A team uploads SFG20 content into their CAFM platform during implementation, sets everything up correctly at go-live, and then the standard moves on without them. The team believes they are compliant because the schedules were correct when they were loaded. They are not tracking whether those schedules still match the current version of SFG20 months or years later. This silent drift is the core technical failure that a genuine SFG20 integration via API solves. When a CAFM platform connects to Facilities IQ through a live API and keeps that connection active with regular sync cycles, the schedules in the platform stay current because they are connected to the live standard — not a snapshot of it taken at go-live.

The Gap Between Having SFG20 and Being SFG20-Compliant

Even when a team has access to SFG20 and has loaded it into their system, operationalising that into a genuinely compliant planned preventive maintenance programme is harder than it looks. The friction typically comes from four recurring problems.

The asset mapping problem. Referencing an SFG20 code in a spreadsheet column is not the same as mapping an asset to a live SFG20 schedule. If the asset record in your CAFM is not individually linked to the current schedule, you are not getting the right task list, the right frequency, or the right skill requirement for that specific asset. You have the code written down. You do not have the standard applied. A schedule that exists at the template level in your platform but is not connected to individual asset records generates no work orders and provides no compliance evidence.

The ownership boundary problem. Commercial property portfolios face a structural complexity that most CAFM configurations do not adequately reflect. Not all assets in a building belong to the same responsible party. Landlord assets, residential assets, subcontracted assets, and assets under separate statutory obligations sit in the same physical space but carry different maintenance responsibilities, different frequencies, and different evidence requirements. When a PPM schedule treats an entire building as a single undifferentiated list of assets, the compliance picture becomes unreliable.

The frequency mismatch problem. Operational schedules drift from SFG20 frequencies over time. A task that should run daily gets moved to weekly because it is more convenient on site. A six-monthly check slips into an annual one because a contractor could not attend on the scheduled date and the rescheduled visit fell into the following cycle. These changes are rarely documented as deliberate, justified decisions. They accumulate quietly until the portfolio's actual maintenance pattern looks nothing like the compliant PPM schedule on file.

The subcontractor asset problem. When a third party manages an asset, it is common for that asset to exist in the main CAFM as a location reference rather than as a properly coded, scheduled, evidence-generating maintenance record. The subcontractor has their own records. The building owner has a reference to the contract. No one has a live, auditable PPM record with SFG20 codes assigned, frequency planners running, and evidence captured against each completed task. In an audit, that absence of evidence is treated the same as absence of compliance.

How Two UK Portfolio Teams Closed the Gap

The following two examples are drawn from real UK commercial real estate implementations. Both organisations manage multi-building portfolios in Central London. Names and specific identifiers have been removed.

Case A: Large Commercial Property Portfolio, Central London

This organisation manages a portfolio of commercial buildings through a combination of in-house engineers and an M&E managing contractor. When they began their CAFM implementation, the state of their PPM schedule was representative of many established operations: functional in practice but fragile on paper.

Multiple Excel versions existed, held separately by the in-house FM team and the managing contractor, neither of which was the definitive source of record. Subcontracted assets had no SFG20 codes assigned. Emergency lighting schedules were missing the correct annual SFG20 code alongside the monthly routine — meaning the annual statutory check was being performed but not recorded against the correct compliance framework. Landlord and residential assets were not differentiated in the maintenance schedule.

The implementation required dedicated SFG20 mapping sessions to work through every asset category and resolve ambiguous cases. The team also discovered that their portfolio calendar operates on ISO week numbers rather than fixed calendar dates — requiring a custom scheduling configuration.

Case B: Premium Commercial Portfolio, City of London

This organisation held a large SFG20 instruction list but had no system behind it. Scheduling was being done manually, instruction by instruction, one building at a time. There was no way to model whether they had enough of the right engineers and contractors to meet SFG20 requirements across all their buildings — making pre-contract resourcing conversations with vendors effectively guesswork.

A dedicated skill-set mapping exercise was conducted to translate SFG20's granular skill taxonomy — multi-skilled engineer, specialist engineer, refrigeration engineer — into the two operational buckets this organisation actually uses: in-house technician and vendor. That translation made it possible to build a meaningful labour load report projecting how much in-house technician time and vendor time would be required to sustain SFG20 compliance across the portfolio for the financial year.

Today, the annual schedule is configured once and regenerates automatically each year. The SFG20 sync is treated operationally as a routine data update — not a manual project requiring a project manager and three months of coordination.

What to Watch Out For When Evaluating CAFM Platforms

The phrase "SFG20 compatible" appears in many CAFM platform descriptions. Understanding what it actually means in each case is one of the most important due diligence questions a UK software buyer can ask.

The first distinction is between compatible and integrated. SFG20 compatible typically means the platform can accept a data import from SFG20. That is meaningfully different from an API connection to Facilities IQ that keeps your schedules current as the standard updates. Ask specifically whether the platform is a registered SFG20 Digital Partner — the designation given to platforms that maintain an active API connection to Facilities IQ.

The second thing to test explicitly during any demo or proof of concept is what happens when SFG20 updates a task set and you trigger a sync. Does the updated job plan overwrite the existing one, or does it create a duplicate record alongside it? The duplication problem is a real defect in some implementations — invisible in normal operations, but corrupting the schedule silently underneath.

Third, ask about multi-frequency planners. Some platforms only support a single planner per asset. For complex building services assets that carry tasks at monthly, quarterly, semi-annual, and annual frequencies, a single-planner constraint forces teams into workarounds that break the connection between a physical asset and its complete compliance record.

Fourth, understand the difference between a work order completion dashboard and a compliance dashboard. A closed work order with no attached certificate, no sign-off, and no task-level audit trail is not a compliance record that holds up in an audit.

Fifth, consider labour load visibility. SFG20 includes estimated task durations for every schedule item. A platform with genuine SFG20 integration can use that duration data to generate a resource load report showing how much technician time your compliance programme requires, by skill level, across the financial year.

What Your CAFM Must Do: Seven Non-Negotiables for SFG20 Compliance

If you are evaluating CAFM software or reviewing your current platform's capability against SFG20, the seven capabilities below distinguish a system built for genuine compliance from one that only appears to support it.

7 CAFM Capabilities for SFG20 Compliance

Getting Your Schedule Right Before You Go Live

There are things that a CAFM platform, however capable, cannot do for you. The most important is building your asset register. No software compensates for an asset list that is incomplete, inconsistently categorised, or does not reflect the actual ownership boundaries across a portfolio.

The Standard Exists. The System Has to Back It Up.