FM Contract SLA, KPIs and Penalty Deductions

What an FM contract SLA is

An FM contract SLA is the part of a facilities management or operation and maintenance (O&M) contract that sets measurable service levels, such as response time, resolution time, planned maintenance completion and asset availability, and the money consequence when they are missed. It matters because, without measured service levels and agreed deductions, a client pays the full monthly fee whatever service it actually receives.

This guide is for public-sector clients and contractors: estates teams, hospital and ministry FM departments, procurement officers and the contractors who bid for O&M work. It covers scope, clocks, KPI design, penalty pools, a worked payment certificate, disputes, procurement rules in the EU and Saudi Arabia, and a contract checklist. It explains common practice; it is not legal advice on whether a particular penalty clause is enforceable in your jurisdiction.

Why the contract, not the work order, is the unit of control

A work order tells you whether one job was done. A contract tells you whether the service the public body paid for was delivered: all the planned visits, within the agreed times, across every site in scope, for the agreed price. Performance management that stops at the work order produces a pile of closed jobs and no answer to the question the finance director asks at month end: should we pay the full invoice?

So every work order in an outsourced estate should carry the contract it falls under, and the contract should hold everything needed to judge the job: scope, priorities, clocks, KPIs and the deduction rules. Jobs that fall outside any contract should be visible as a separate list, because they are either extra work to be quoted or scope that the contract missed.

Defining scope: the site and service matrix

Scope disputes cause more friction than performance disputes. Write scope as a matrix: sites down one side, services across the top, and in each cell whether the service is included, excluded or priced on request, with any limits such as a cap on parts per job. Then list the assets covered in each service, because a 'mechanical services' line means nothing until it names the chillers, pumps and air-handling units it covers.

Each contract also needs a working calendar per site (hours of cover, weekends, public holidays) and a priority scheme with response and resolution times. An illustrative scheme for a public building:

• Priority 1, emergency (risk to life, building closure, critical service lost): respond in 1 hour, make safe in 4 hours, 24/7 calendar
• Priority 2, urgent (service degraded, single critical asset down): respond in 4 hours, resolve in 24 hours, 24/7 calendar
• Priority 3, routine (fault with workaround): respond within 1 working day, resolve within 8 working hours of logging, working calendar
• Priority 4, planned (minor or cosmetic): schedule within 20 working days, working calendar
• Planned maintenance: each visit due in a defined window, for example the scheduled week
• Exclusions written out: vandalism, client-caused damage, works above a value threshold, items under manufacturer warranty

Response, resolution and the clock

Response time runs from logging to attendance; resolution time runs from logging (or attendance, if the contract says so) to the fault being fixed or made safe. The contract must say which calendar each clock uses, which events pause it (no access, waiting for the client's decision, parts the client supplies), and whose timestamp counts.

Worked example. A site's working calendar is Monday to Friday, 07:00 to 19:00. A Priority 3 fault is logged on Friday at 16:00 with a resolution target of 8 working hours. Friday 16:00 to 19:00 uses 3 hours, so the remaining 5 hours run from Monday 07:00 and the deadline is Monday 12:00. The job is completed on Monday at 14:00, 2 working hours late. If the technician was refused access for 1 hour on Monday morning and the contract pauses the clock for that, the deadline moves to 13:00 and the job is 1 hour late.

The calendar choice changes the result completely. On a 24/7 calendar the same 8-hour target would have expired on Friday at midnight, and completion on Monday at 14:00 would be 62 hours late. Clients and contractors who skip this paragraph of the contract argue about it every month.

Designing KPIs that survive a dispute

A good KPI has a written formula, a data source both parties can see, a measurement period, a target and a weighting. Calculate it from the work-order and asset records, not from a satisfaction survey alone. Typical O&M contract KPIs, with the formula your contract should spell out:

• Response compliance: jobs attended within the response time ÷ jobs logged in the period, by priority
• Resolution compliance: jobs resolved within the resolution time ÷ jobs due in the period, by priority
• PPM completion: planned visits completed in their window ÷ planned visits due in the period; state whether late visits count
• Statutory compliance: assets with a current certificate ÷ assets requiring one, measured on the last day of the period
• Critical asset availability: hours available ÷ hours required for each named critical asset
• Repeat faults: jobs on the same asset and fault within 30 days ÷ all corrective jobs
• Reporting: monthly report and evidence pack delivered by the agreed working day

Sum at risk, deductions and retention: a worked payment certificate

Many O&M contracts cap performance deductions at a share of the monthly fee, often called the sum at risk, split into pools per KPI. Deductions for work not done at all, called non-execution deductions here, are usually separate from performance deductions, and retention is a share of each payment held back until a later milestone.

Worked example in SAR, before VAT. The monthly fee is SAR 400,000 and the sum at risk is 10 per cent, SAR 40,000, split into pools: response 30 per cent (SAR 12,000), resolution 30 per cent (SAR 12,000), PPM completion 25 per cent (SAR 10,000) and reporting 15 per cent (SAR 6,000). For each percentage point below target, 20 per cent of that KPI's pool is deducted, up to the whole pool. Targets are 95 per cent for response, resolution and PPM completion.

Results for the month: response 92 per cent, 3 points short, so 60 per cent of SAR 12,000 = SAR 7,200; resolution 96 per cent, no deduction; PPM completion 88 per cent, 7 points short, so 140 per cent, capped at the full pool of SAR 10,000; reporting on time, no deduction. Performance deductions total SAR 17,200, within the SAR 40,000 cap. Six planned visits were not carried out at all, priced in the contract at SAR 1,500 each, a non-execution deduction of SAR 9,000.

The certified value is 400,000 − 17,200 − 9,000 = SAR 373,800. Retention of 5 per cent of the certified value is SAR 18,690, so the amount payable this month is 373,800 − 18,690 = SAR 355,110, before VAT.

Drafting traps: double penalties, caps and incentives

Look again at the six missed visits. They were deducted as non-execution (SAR 9,000) and they also pulled PPM completion down to 88 per cent, which cost the full SAR 10,000 pool. The contractor will argue it has been penalised twice for the same failure. That may be intended, but the contract should say so explicitly, or state that visits deducted as non-execution are excluded from the PPM KPI.

Other traps recur in public-sector contracts. A pool that is fully lost at 7 points short gives the contractor no reason to improve from 88 to 90 per cent that month, so steep slopes need a gentler tail. Targets of 100 per cent turn every single miss into a deduction and push contractors to dispute rather than report honestly. And a sum at risk that is too small to matter, or so large that the contractor prices it into the bid, defeats the purpose. Some contracts add an earn-back: deductions are returned if performance recovers for a set number of months.

Evidence, disputes and the monthly review

Every KPI result should be traceable to records both parties can inspect: work-order timestamps, technician sign-offs, photos, checklist readings, meter readings and certificates. The contract should fix a dispute window, for example 10 working days after the monthly KPI report, after which unchallenged results stand.

A disputed item needs a reason code (clock should have paused, job out of scope, wrong priority), the evidence, and a decision recorded by the client's contract manager. The monthly review meeting then covers the KPI scores, disputes, deductions, variations to scope and any rate-card work, and its minutes become part of the contract file. For public bodies that file is what an auditor or a procurement review will read years later.

Procurement rules: the EU and Saudi Arabia

In the EU, Directive 2014/24/EU requires award on the most economically advantageous tender (Article 67). Award criteria may include after-sales service and technical assistance, cost can be assessed by life-cycle costing under Article 68, which includes maintenance costs, and the weightings must be stated in the procurement documents. For 2026 and 2027 the service threshold is €140,000 for central government authorities and €216,000 for sub-central authorities, and €432,000 for utilities under Directive 2014/25/EU (as of October 2026). ISO 41012:2017 gives guidance on strategic sourcing and the development of FM agreements.

In Saudi Arabia, the Government Tenders and Procurement Law (Royal Decree No. M/128 of 13/11/1440H, 16 July 2019, in force 1 December 2019) and its Implementing Regulations (Minister of Finance Decision No. 1242 of 19 November 2019, amended by Decision No. 3479 of 5 April 2020) apply to ministries, government agencies and public organisations. Tender procedures and documents are posted on Etimad. EXPRO acts as the entity in charge of unified procurement and runs framework agreements for items needed by more than one government entity, including a Medical Equipment Maintenance Framework Agreement whose guidelines and templates were published in February 2026.

FM and O&M contract checklist

Before signing, or before the first monthly certificate, check that the contract and your records can answer each of these:

• Is scope written as a site and service matrix with the covered assets listed?
• Does each priority have response and resolution times, a calendar and written pause rules?
• Does each KPI have a formula, data source, period, target and weighting?
• Are the sum at risk, the pools, the deduction slope and any earn-back defined with a worked example in the contract?
• Is it explicit whether non-execution deductions also count against KPIs?
• Are retention, its release milestone and price adjustment rules stated?
• Is there a dispute window and a named decision-maker on each side?
• Are the procurement references (for example the Etimad tender reference in Saudi Arabia) recorded against the contract?

How Skyline Nexus ERP handles maintenance contracts and SLAs

In the Skyline Nexus ERP CMMS, Contracts hold each service or maintenance contract with its type, start and end dates, renewal type and reminder date, value, payment terms, scope of work, covered assets and excluded items, response time hours, resolution time hours, visits per year, and whether parts, labour and calibration are included. Work orders link to the contract and record when the job was scheduled, started and completed, the downtime hours, costs and the technician sign-off, which is the evidence a KPI calculation needs.

For outsourced FM and O&M programmes, Skyline Nexus ERP Contract Operations is available on request, in English and Arabic. It models client, contract, sites and a scope matrix of service items, with working calendars, SLA policies and pools, KPI periods scored from evidence, KPI disputes, penalties, sum-at-risk pools, non-execution deductions, retention release, variations and rate cards. Monthly payment certificates become sales invoices through the normal sales path, with agreed deductions shown as a discount, and a government client can carry its Etimad agency code and the contract its Etimad reference for the procurement file.

Try the free month with your CMMS contracts, or book a demo and bring one month of your contract data; we will rebuild your payment certificate with you.