Common service level agreement examples for field service and facilities maintenance contracts include a one-hour emergency response and a four-hour urgent response. Others set reactive repairs within two working days and planned preventive maintenance (PPM) visits within the agreed window. Each target sits alongside a minimum performance threshold, such as 90% of reactive visits attended within eight hours, and a consequence for missing it. Once a customer signs, those terms become the standard your business is measured against.

The figures in this article are illustrative examples, so adapt them to your own capacity, sites, and contract terms.

What should every service level agreement include?

Every service level agreement (SLA) needs targets, clock rules, exclusions, and remedies defined in writing before work begins.

How do response and resolution targets work?

Response time is how quickly you attend or acknowledge a job. Resolution time is how quickly you complete it. Categorising jobs by priority is the most practical way to assign both, as this example shows:

How do you define availability, exclusions, and service credits?

The SLA must specify when the clock starts and when it pauses, or disputes arise over whether a breach occurred. Define these areas clearly in every agreement:

• Business hours and out-of-hours cover: state when the SLA clock runs and pauses, including bank holidays and site access restrictions
• Exclusions: name circumstances outside your control, such as customer-caused access delays or third-party utility failures
• Service credits: set out the financial remedy for missed targets, such as a percentage reduction on the following invoice

Which types of SLA are used in field service?

SLAs come in three main structures, depending on whether you cover a single customer, a specific service, or both. If you are still shaping the contract itself, this guide to providing maintenance contracts covers the full structure beyond the SLA.

Customer-level SLA

A customer-level SLA covers all services delivered to one customer under a single agreement. A facilities management (FM) contractor running mechanical, electrical, and fabric maintenance across one estate would use this structure, often through facilities management software.

Service-level and multilevel SLAs

A service-level SLA applies one agreement to all customers using a specific service, such as a standard reactive maintenance response. A multilevel SLA layers corporate, customer, and service-level terms together. It suits large FM contracts where sites or asset types need different target windows.

Where are SLAs used in facilities maintenance?

SLAs appear wherever one party relies on another to keep buildings and assets working:

• Outsourced FM contracts: a contractor delivers hard and soft services to a customer against agreed targets
• Specialist subcontractor agreements: a main contractor holds a lift or fire specialist to the response windows in its own contract, which a subcontractor portal can track against the contract SLAs
• Internal FM teams: an in-house team agrees service standards with the departments it supports
• Multi-site estates: retail, education, or housing portfolios apply tiered targets by site type
  
  

Service level agreement examples for hard and soft services

Hard services cover building systems and fabric, such as electrical, mechanical, and structural work. Soft services cover cleaning, catering, and security.

Hard services SLA examples

These examples show how hard services targets read in a contract:

• Reactive repairs: attend within the priority window and complete repairs within two working days
• Air conditioning: service every unit quarterly, with each visit completed within its scheduled month
• Fire systems: service the fire alarm system at least every six months, in line with the BS 5839-1 recommendation, and issue the inspection and servicing certificate within five working days of each visit

Soft services SLA examples

Soft services targets focus on frequency and standard of finish:

• Cleaning: clean communal areas daily during operating hours, attending reported spills within 30 minutes
• Washrooms: check and restock washrooms every two hours during opening times

Minimum performance thresholds and breach consequences

A minimum performance threshold tells both parties when missed targets become a contract problem. This example table pairs each threshold with a consequence:

SLA contract example for field service and FM

Adapt this example contract wording to your own terms.

What is the difference between an SLA and a KPI?

An SLA sets the minimum standard both parties agree, such as completing reactive repairs within two working days. A key performance indicator (KPI) measures how often you meet it, such as 93% of reactive repairs completed within two working days this month. The SLA is the promise in the contract, and the KPI is your evidence at every review. Tracking KPIs in field services shows you which targets are slipping before a breach pattern forms.

How do you write an SLA step by step?

Work through these steps in order when drafting an SLA for a new or renewing contract:

• Define the scope: list the sites, assets, and services covered, and name anything excluded
• Set priority definitions: describe emergency, urgent, and routine jobs with real examples
• Agree response and resolution windows: assign both to each priority level using historical job data
• Write the clock rules: state when the clock starts, pauses, and stops
• Decide how you will measure: confirm which timestamps count, such as job logged and engineer on site
• Agree reporting: set the format and frequency of compliance reports
• Set service credits: define the threshold, credit value, and rolling period
• Schedule reviews: book quarterly reviews to adjust targets as data builds up
• Define termination terms: state how many consecutive months of missed thresholds allow either party to end the contract

What happens when an SLA is breached?

Remedies escalate with repeated failure, typically through service credits, a corrective action plan, increased monitoring, and finally termination. The table above shows how different metrics start at different points on that ladder.

Service credits and corrective action

In the example table above, a single missed month on emergency response costs a service credit, while a missed month on reactive attendance triggers a corrective action plan setting out the cause, the fix, and a recovery date. Weekly reporting follows repeated misses, making avoiding service credits an operational priority.

How do missed SLAs affect contract renewals?

Your SLA compliance record is the first evidence a customer reviews at renewal. A run of breaches weakens your position on price and scope, and can push the customer to retender. A clean record with clear reports supports a case for extending the contract or adding sites.

Joblogic's contract management monitors SLA adherence per contract, so the record you take into a renewal meeting comes from the job data rather than a spreadsheet rebuilt the week before.

How do asset failures affect SLA compliance and penalties?

One failing asset can generate several reactive callouts, each with its own SLA clock. If a boiler fails because a PPM visit was missed, the customer will hold you responsible for every breach that follows. Agree exclusions for assets past their working life or awaiting customer-approved replacement, and record asset condition at every visit.

Joblogic's asset register holds each asset's condition and service history, so you can show whether a run of callouts traces back to a worn asset or a missed visit.

What are the best practices for agreed SLAs?

Targets set above your team's real capacity generate breach records before the contract has properly started. Mobilisation errors, such as incorrect PPM visit frequencies or unvalidated asset lists, make targets harder to hit from day one. These habits help SLAs hold up across the full contract period:

• Set targets your team can meet: base windows on workforce availability, travel time, and parts stock before negotiation starts
• Define when the SLA clock runs: confirm business hours, out-of-hours cover, and site-specific exceptions in writing
• Build in a review cycle: a quarterly cadence gives both parties enough data to adjust targets
• Separate SLA policies by contract: your contract management system should apply the right rules per contract automatically
• Track performance in one place: SLA data captured during the job lifecycle is more reliable than a spreadsheet rebuilt before a customer meeting

How do you manage SLA tracking across PPM and reactive work?

Manual SLA tracking breaks down across dozens of contracts. A job logged at 07:45 on a Friday against a four-hour urgent target needs action before 11:45. A shared calendar won't show that window. If a reactive callout is raised without the correct asset or SLA, the clock may start against the wrong priority. Engineers arrive unprepared, and the breach is recorded before anyone spots the setup error.

How does SLA management software prevent breaches?

SLA management software connects targets to the job lifecycle. In Joblogic, when a job is logged, the system assigns a priority level and starts the SLA countdown automatically. For PPM contracts, visits are raised automatically at the agreed frequency with SLA targets attached. PPM contracts are available on the Premium and Enterprise plans; the plan comparison shows what each plan includes.

Engineers see job details and asset history on the mobile engineer app, which works offline on sites with no signal. The drag-and-drop scheduling board lets you reallocate jobs before a breach occurs. Contract management monitors SLA adherence, automates compliance reporting, and alerts you to approaching deadlines, while Dashboard Reporting tracks SLA compliance and job completion rates by contract.

What should you do before your next contract renewal?

Start with the contract closest to renewal. Pull its last 12 months of SLA performance and compare each target with what your engineers delivered. Where the gap is wide, fix the cause, such as visit frequencies or engineer coverage, or renegotiate the target with evidence.

Then check every live contract for clear priority definitions, clock rules, and exclusions, because gaps there become disputes the first time a breach is contested.

If you manage SLAs across multi-trade, multi-site contracts, our playbook on closing the SLA gap covers repeat visits, first-time fix, and cash flow.

Joblogic works with 7,000+ UK service businesses managing contracts like these. If you'd like to see how SLA countdowns and alerts would work on your own contracts, book a demo with one of our specialists.

Frequently asked questions

What is the difference between an SLA response time and a resolution time?

Response time measures how quickly you attend or acknowledge a job after it is logged. Resolution time measures how quickly you complete the work to the customer's satisfaction. Both sit in the same SLA.

How often should SLA targets be reviewed after a contract starts?

Review SLA targets quarterly. That cycle gives both parties enough data to check targets against actual delivery. It also leaves time to update exclusions or service credits before disputes build up.

What makes an SLA breach different from an exclusion?

A breach occurs when a target is missed and no valid exclusion applies. An exclusion is a pre-agreed circumstance that pauses or stops the SLA clock, such as a customer-caused access delay. Precise exclusions at the drafting stage prevent disagreements over responsibility.

Can you change SLA targets during a contract?

Yes, if the contract allows amendments. Agree changes at a scheduled review, record them in writing, and apply the new targets from a set date so your compliance reports compare like with like.