A guide to facilities management — archived version

If the short answer is "everything a building needs in order to function", the useful answer is a great deal more specific. Facilities management has an international standard, a recognised body of practice, and a set of failure modes that repeat across almost every estate. This URL is retained from the previous site; the fuller version lives at /post/what-is-facilities-management-1.

The standards that actually govern it

ISO 41001 sets out the requirements for a facilities management system, and ISO 41011 provides the vocabulary. For maintenance itself, SFG20 is the industry standard library of task schedules in the UK, maintained by the Building Engineering Services Association, and it is what a competent provider builds a planned maintenance regime from. None of these is a legal requirement. All of them are what a buyer should expect to see referenced in a proposal, because the alternative is a schedule someone invented.

The core functions

• Planned preventative maintenance, built from an asset survey rather than a template
• Reactive maintenance, with priority bands agreed per site rather than one blanket response time
• Statutory compliance and the record that evidences it
• Asset management: knowing what is installed, its condition, and its remaining life
• Space and occupancy management
• Energy and environmental performance
• Supplier and subcontractor management
• Financial control: budget, forecast, and the variance conversation

Why it matters commercially

Facilities management is usually one of the larger lines in an operating budget and almost always the least examined. That is because its value is mostly negative space: the outage that did not happen, the enforcement notice that was never issued, the plant that reached its design life instead of failing at eight years. Those are difficult to celebrate and easy to cut, which is why reactive spend so often rises quietly in the two years after a planned maintenance budget is reduced.

What good practice looks like

• An asset register that exists before the contract starts, not six months after
• Maintenance tasks referenced to SFG20 or an equivalent recognised basis
• Statutory obligations tracked separately from planned maintenance, because they are legally different
• Certificates and completion evidence held in one place and available to the client
• Reactive jobs categorised by consequence, not by how urgent the caller sounded
• A named point of contact with authority, not a ticket queue
• Recurring faults visible as a pattern, so they become replacement decisions

The questions worth asking a provider

Three questions separate providers quickly. Which parts of this scope do you deliver directly and which do you subcontract, and will you put that in writing? How did you arrive at these response times for this site? And: when a statutory test fails, what happens next, and who owns closing it out? The answers are more revealing than any case study.