The dispute started six months into the contract. The client claimed the FM team wasn’t maintaining the AHUs properly. The FM company said AHU servicing wasn’t in the scope. Both sides went back to the contract document — a five-page Scope of Work that said “provide full facilities management services” and listed four bullet points. The legal bill that followed cost more than three years of the contract value.
Vague scopes of work are one of the most expensive problems in FM contracting. They create disputes, expose both parties to unexpected liability, make pricing impossible to validate, and destroy relationships that took years to build. And almost all of them start the same way — someone wrote a scope quickly, used generic language, and both sides assumed the other knew what was included.
This guide explains how to write a scope of work for FM contracts that actually works — what to include, how to structure it, the specific language that protects both parties, and the common mistakes that turn a good FM relationship into a contract dispute. Whether you’re writing a scope as the client or pricing one as the FM provider, this is the practical guidance you need before either party signs.
What Is a Scope of Work in Facilities Management?
A Scope of Work (SOW) in an FM contract is the document that defines exactly what the FM provider is responsible for delivering — which services, to which assets, at what standard, at what frequency, and within what response times. It is the technical foundation of the contract. The commercial terms (price, payment, escalation) sit on top of the scope; but if the scope is wrong, no commercial term can fix what follows.
A well-written FM scope of work has three qualities: it is specific (naming assets, frequencies, and standards rather than describing services in general terms), it is measurable (you can objectively determine whether each item is being delivered), and it is complete (everything the client expects and the FM provider has priced is written down, not assumed).
The Scope of Work is different from the Service Level Agreement (SLA). The SOW defines what will be done. The SLA defines how well it must be done — response times, completion targets, KPI thresholds. Both documents are needed, and they must be consistent with each other. A scope that promises weekly filter checks and an SLA that measures monthly compliance are contradictory — and that contradiction will cause a dispute.
What to Include in an FM Scope of Work: Section by Section
A complete FM scope of work for a commercial building has seven sections. Each one has a specific purpose — missing any of them creates a gap that will eventually become a problem:
Section 1 — Building Description and Asset Schedule
The scope must start with a clear description of the building being maintained — its location, gross floor area, number of floors, building type (office, hotel, hospital, retail), and occupancy hours. This context frames everything that follows.
More importantly, the scope must include or reference a full asset schedule — a list of every maintainable asset the FM team is responsible for. Not “HVAC systems” but: 4 × Trane centrifugal chillers, 18 × AHUs, 142 × FCUs, 6 × cooling towers, 4 × chilled water pump sets. Not “electrical systems” but: 1 × MDB rated 3200A, 4 × SMDBs per floor, 47 × DBs.
Without a specific asset schedule, the scope is open to interpretation from day one. The FM team services what they know about. The client expects what they assumed was included. The gap between those two things is where disputes begin.
Section 2 — Services Included (and Explicitly Excluded)
List every service the FM team is responsible for, grouped by discipline. Be explicit about what is included and equally explicit about what is excluded. Assumptions kill FM contracts. If specialist lift maintenance is excluded, write it down. If pest control is the client’s responsibility, write it down. If reactive electrical work above a certain value requires client approval before proceeding, write it down.
Structure the included services under clear headings:
• Planned Preventive Maintenance (PPM) — all scheduled maintenance tasks, frequencies, and standards for each asset category
• Reactive Maintenance — response to faults and breakdowns, including response time categories and escalation procedure
• Minor Works — small repairs and modifications within a defined cost threshold (e.g. works under AED 2,000 / £500 — include without further approval)
• Statutory Compliance — which legal inspections and certifications the FM team is responsible for procuring and managing
• Specialist Services — lift maintenance, fire suppression, specialist HVAC (if subcontracted) — state whether included in scope or client-direct
• Helpdesk and Reporting — service request management, monthly reporting, KPI reporting frequency
Section 3 — PPM Schedule and Frequencies
This is the technical core of the scope. For each asset category, the scope must define what maintenance tasks are performed and at what frequency. The SFG20 standard — the industry reference for maintenance task specifications — is the most defensible basis for this section. Referencing SFG20 task codes means both parties are working from the same independent standard rather than debating what ‘service the chiller’ actually includes.
At minimum, the PPM schedule section should specify:
1. Asset category — e.g. centrifugal chillers
2. Maintenance frequency — e.g. monthly inspection, quarterly service, annual full service with performance test
3. Task content reference — SFG20 code, manufacturer specification, or written task list
4. Responsible party — in-house FM team or specialist subcontractor
5. Certification required — e.g. F-gas for refrigerant work, LOLER for lifts, gas safe for gas systems
| 📌 For how PPM schedules are structured and what frequencies are appropriate for each system, see the PPM Programme Guide. |
Section 4 — Response Time Categories
Every FM contract needs a defined set of priority categories for reactive work, with clear response time commitments for each. The most common structure uses three or four priority levels:
| Priority | Definition | Typical Response Time |
| P1 — Emergency | Life safety risk, total system failure, flooding, power loss to critical areas | Attend within 1–4 hours |
| P2 — Urgent | Significant impact on building operations or occupant comfort — partial system failure | Attend within 4–8 hours |
| P3 — Routine | Minor defects, nuisance faults, tasks that can wait without significant impact | Attend within 24–48 hours |
| P4 — Planned | Non-urgent works that can be scheduled — minor repairs, replacements, modifications | Complete within 5–10 working days |
Define each priority clearly with examples relevant to the building — what constitutes a P1 in a hospital is different from a P1 in an office. Vague priority definitions are one of the most common sources of SLA disputes — the client says the chiller fault was a P1, the FM team categorised it as P2. If the definition is written down with examples, the argument doesn’t happen.
Section 5 — Reporting Requirements
Specify exactly what reports the FM team must provide, in what format, and by when. The minimum for most commercial FM contracts:
• Monthly performance report — PPM completion rate, reactive job count, SLA compliance, open defects, planned works for next month
• PPM completion records — signed job cards or CMMS records for every completed PPM task, available on request
• Statutory compliance register — current status of all legally required inspections, with certificate expiry dates
• Incident reports — formal report for every significant incident within 24 hours, with root cause and corrective action
• Annual report — full-year summary including asset condition assessment, budget analysis, and recommendations
Specify the reporting date (e.g. 5th of each month), the report format (PDF, CMMS-generated, or specified template), and the escalation procedure for reports that show KPI failure. A reporting requirement without a defined format and date is never consistently met.
Section 6 — Staffing and Resource Requirements
The scope should define the minimum staffing the FM team must maintain on site — not the commercial detail of who pays for what, but the operational requirement. This includes:
• Minimum on-site personnel — number and skill level during normal hours and out-of-hours
• Required qualifications — F-gas certification, electrical competency level, Legionella responsible person, first aid
• Out-of-hours cover — how emergency response is provided outside standard working hours, response time commitment
• Key personnel — if the contract requires a named FM manager or contract manager, specify this and the approval process for changes
Section 7 — Exclusions, Assumptions and Conditions
The exclusions section is as important as the inclusions. Everything not explicitly included in the scope should be listed here. Common FM contract exclusions that must be written down:
• Capital replacement works — the FM team maintains assets; replacement when they reach end of life is typically a client CAPEX item
• Works above agreed minor works threshold — require client approval and separate instruction
• Client-direct contracts — list the specialist services the client manages directly (lifts, fire suppression, pest control, cleaning if separate)
• Works caused by third-party damage or modification — not covered under normal PPM or reactive rates
• Out-of-scope building areas — if specific areas are excluded from the FM contract, name them
The Most Common Scope of Work Mistakes in FM Contracts
These are the gaps that create the disputes. Every experienced FM manager has lived at least one of these:
| Mistake | What Goes Wrong |
| No asset schedule — just system descriptions | Six months in, both parties disagree on what was included. FM team says ‘we maintain the chillers’. Client says ‘what about the cooling towers?’ |
| Generic task descriptions with no frequency | ‘Service all HVAC equipment’ means monthly to one party and annually to the other. No frequency = no accountability. |
| No exclusions list | FM team prices for a defined scope. Client expects everything. The gap between the two becomes a dispute about what was ‘implied’. |
| SLA not aligned with scope | Scope says weekly filter checks. SLA measures monthly PPM completion. The SLA doesn’t capture the most frequent tasks. |
| No minor works threshold defined | Every small repair becomes a negotiation. FM team has no authority to fix anything without approval. Client frustrated by slow response. |
| Response times not matched to building criticality | A hospital and an office have different emergency definitions. Using the same response categories for both creates either over-commitment or under-protection. |
| No reporting format specified | Reports arrive in different formats every month. Client can’t trend performance data. FM team has no clear standard to meet. |
Practical Tips for Writing a Scope That Protects Both Parties
Walk the building before writing the scope
No scope should be written from drawings alone. Buildings are modified. As-builts don’t match reality. Assets get added, removed, and relocated without the contract documents being updated. Walk every plant room, every riser, every roof level before committing the asset schedule to paper. What you find on site is what the FM team will be maintaining — not what the drawings say should be there.
Use specific numbers, not general descriptions
“Maintain all HVAC equipment” is not a scope. “Monthly PPM inspection of 4 × York centrifugal chillers, quarterly performance test, annual third-party thermal imaging” is a scope. Every item in your scope should answer: what asset, what task, what frequency, who does it, to what standard. If any of those four questions is unanswered, the scope line is incomplete.
Price from the scope, not the other way around
The most common commercial mistake in FM tendering: price first, then write a scope to fit the price. This produces a scope that is vague by design — because specificity would reveal that the price doesn’t cover what the client actually needs. It also produces disputes, because the client’s expectations were never captured in writing. Write the scope first. Price the scope second.
Review the scope annually
Buildings change. Tenants move in and out. Systems get upgraded. Staff change and institutional knowledge gets lost. A scope that was accurate at contract award may be significantly wrong by year three. Build an annual scope review into the contract — a documented process where both parties confirm the scope still reflects the actual building and service requirements. This prevents scope creep in both directions and keeps the contract grounded in site reality.
| 📌 For the KPI framework that sits on top of your SOW and measures delivery, see the FM KPIs Guide. |
Frequently Asked Questions
What is the difference between a scope of work and an SLA in FM?
A Scope of Work (SOW) defines what the FM team will do — which services, which assets, at what frequency, to what standard. A Service Level Agreement (SLA) defines how well they must do it — response times, completion rates, KPI targets, and consequences for failing to meet them. Both documents are needed, and they must be consistent. The SOW is the technical specification; the SLA is the performance measurement framework. Writing an SLA without a clear SOW underneath it is building performance metrics on a foundation that isn’t defined.
How detailed should an FM scope of work be?
Detailed enough that there is no ambiguity about what is and isn’t included. For a medium-sized commercial building, a complete FM scope of work is typically 15–30 pages, including the asset schedule, PPM frequency matrix, priority categories, reporting requirements, staffing requirements, and exclusions list. One-page scopes are invitation for disputes. A scope that both parties can use to resolve a disagreement without going to lawyers is the right level of detail.
Who should write the FM scope of work — the client or the FM provider?
Ideally both parties contribute to it, but the client should own the final document. The client knows what the building needs, what their occupants expect, and what regulatory requirements apply. The FM provider knows what is realistically achievable within a given budget and what specialist support is needed. The best scopes are written collaboratively — the client drafts the service requirements, the FM provider reviews and flags gaps, ambiguities, and unrealistic requirements, and both parties agree the final version before pricing.
What should the PPM section of an FM scope reference?
The PPM section should reference either SFG20 task codes (the industry standard for maintenance task specifications in the UK and internationally), manufacturer service documentation for specific plant, or a written task specification developed specifically for the building. Referencing SFG20 is the most defensible approach because it’s an independently maintained, industry-recognised standard — if there’s a dispute about what a quarterly AHU service should include, the answer is in the SFG20 specification, not a matter of opinion.
How do I handle scope changes during the contract period?
Scope changes — new assets added, services extended, areas changed — should always be handled through a formal contract variation process: a written instruction from the client describing the change, a written response from the FM provider with the commercial impact, and a signed variation order before work begins. Never carry out work outside the agreed scope on the assumption it will be paid for later. The conversation about who pays for what is far easier before the work is done than after it.
Conclusion
A scope of work that is specific, complete, and agreed by both parties before contract start is the single most important document in an FM contract. It defines what success looks like, sets the standard the FM team will be measured against, and prevents the disputes that destroy otherwise good working relationships.
For the reporting framework that sits on top of your SOW, see the FM Reports Guide . For the PPM structure that drives the maintenance section of your scope, use the PPM Checklist Generator on mepmasterguide.com to build system-specific maintenance schedules.
