Stop service credits with AI and live SLA dashboards
Last updated: 5 November 2026
Written by: Joblogic

Facilities management (FM) and field service teams stop service credits with AI (artificial intelligence) by flagging at-risk jobs early. AI compares live job and engineer data against each service level agreement (SLA) clock. Your dispatcher then acts on the jobs closest to breach while there's still time to save them.

The pressure on those clocks keeps rising. HFMA reports that NHS England's maintenance backlog for 2025/26 reached £17.3bn. That's a 9.1% increase from £15.9bn in 2024/25.

Hiring more engineers is hard as well. A 2025 analysis by DART Tool Group looked at engineering and manufacturing apprenticeships across Great Britain. It found 145 job vacancies for every live apprenticeship opening, a gap of nearly 46,000 unfilled positions.

With fewer people covering more sites, breaches start in small moments on an ordinary day:

  • An engineer runs late between sites

  • A subcontractor accepts a job and never updates the status

  • A reactive call waits on access, parts, or approval until the SLA time runs out

Each one looks minor on the day. Together they become failed response and fix times, then service credits on your invoice.

How do service levels, KPIs, and service credits connect?

A service level is the promise you make on a contract, such as attending emergencies within four hours. A key performance indicator (KPI) measures how often you keep it, for example 95% of emergencies attended on time. Miss the KPI often enough and service credits apply as deductions from your invoice.

Picture the monthly report on a reactive and planned maintenance contract. It boils down to four questions:

  • Did engineers hit agreed response times?

  • Did jobs close inside agreed fix times?

  • Did planned preventative maintenance (PPM) and statutory work stay compliant?

  • Did complaints and callbacks stay under control?

Keep the measured list short. RICS and IFMA strategic FM guidance warns that collecting and reporting non-essential measures can waste much effort. FM consultancy Landmark & Associates also warns against KPI overload. It recommends service credits only where failure carries significant operational or reputational risk.

Your customer judges you on a few critical service levels. If a KPI can trigger a credit, it belongs on a live view of engineers, sites, and subcontractors.

Why should service credits be proportionate?

Service credits should match the value and risk of the contract, according to GOV.UK guidance on risk allocation and pricing. The note covers central government contracts on a comply or explain basis. For a provider, a proportionate regime ties each credit to a service level that matters, so monitoring effort goes there first.



What can missed SLAs cost beyond the service credit?

Repeated SLA failures on central government contracts put both the contract and future bids at risk. The same GOV.UK guidance note lists critical performance failure as a possible termination trigger event. Failure to implement an agreed rectification plan appears on that list too.

The note also says poor KPI performance could risk exclusion from future procurements. Private sector contracts set their own terms, so check the termination clauses in each one.



Why do multi-site contracts breach SLAs?

Multi-site contracts breach SLAs when the office loses sight of jobs, engineers, and subcontractors between updates. Here's where that visibility breaks down:

  • An engineer gets held up between sites, and nobody adjusts the route before the attendance clock runs out.

  • The office sends a job to the wrong trade, so the engineer needs a follow-up visit.

  • A job sits on hold for access, permits, parts, quotes, or customer approval, with nobody owning the next step.

  • A subcontractor finishes the work but returns completion evidence late, so the job still looks open.

  • Half the board carries priority 1 or 2 (P1 or P2), so engineers go to the loudest job first.

  • Requests arrive by email, phone, or WhatsApp, and the breach only appears when someone builds the report.



How do live status and engineer tracking rescue at-risk jobs?

Live status and engineer tracking show which jobs are near their limit and who can reach them. A real-time SLA dashboard for field service should answer these questions at a glance:

  • Which jobs are closest to their response or fix limit?

  • Which engineers are on site, travelling, or about to finish?

  • Which subcontractor jobs have gone quiet?

Joblogic facilities management software gives you real-time visibility of jobs, assets, engineers, and contracts through a single dashboard. You can filter that view by site, trade, or contract, so each manager sees their own sites.

Joblogic engineer tracking shows where engineers are on a live map that updates every five minutes. It runs from the engineer's phone and comes included in the Premium plan.

Joblogic contract management tracks SLA adherence and alerts you to approaching deadlines. Customisable dashboards then track SLA performance by contract.

Joblogic's subcontractor portal tracks each subcontractor job from report to completion. Subcontractors using their own version of the software can update job information themselves.

With that picture, a dispatcher can change the outcome:

  • Move a job close to breach to the top of the queue

  • Hand work from an overloaded engineer to someone nearer

  • Escalate a slow subcontractor with clear facts, or send an in-house engineer



How can you stop service credits with AI before a breach?

AI stops service credits by watching every open job and flagging the ones heading for a breach. Your dispatcher still decides what happens next.

JLL's Global State of FM 2026 report surveyed 1,321 organisations across 15 countries. It found 45% of occupiers already scaling or optimising AI within FM operations.

A busy dashboard holds more jobs than one dispatcher can watch all day. AI scans the board in the background and raises the jobs most likely to breach. Here's what to watch and what an alert should flag:

What to watch What an alert should flag
Response and fix clocks Jobs close to breach, based on live status and job history
Jobs on hold Holds for parts, access, or approval running longer than normal
Sites, assets, and trades Repeat appearances in breaches or near misses
Subcontractor jobs Late attendance or slow status updates

How do predictive alerts differ from fixed threshold alerts?

A fixed threshold alert fires when a job reaches a set point in its SLA window. A predictive alert reads patterns in your job history and warns you earlier when a job looks set to miss.

Take two emergency jobs with the same time left. One sits with an engineer 10 minutes away. The other sits with a subcontractor who updates late at that site. A fixed threshold treats both jobs the same. A predictive alert raises the second job first, because the history points to a breach.

Keep a few fixed thresholds as a backstop, so your team trusts each alert.

Who should act on an SLA alert?

Every SLA alert needs a named owner and a time by which they act. Without an owner, AI alerts for SLA monitoring become another line on a busy screen. Agree owners for each alert type before you switch alerts on:

  • Dispatcher: reassigns or reroutes jobs close to breach

  • Service manager: escalates stalled subcontractor jobs and long holds

  • Contract manager: updates the customer when a breach looks unavoidable

Review the alert list each week and remove any rule nobody acts on.

Joblogic Dynamic Scheduler is a separate AI product that evaluates every engineer against the job. It checks skills, location, current workload, shift patterns, and SLA deadlines. Dispatchers can review and override each suggestion.

Our guide to compliance-first FM operations shows how an SLA planner sets response, attendance, and fix windows from the contract. Jobs in the risk window rise to the top with early alerts. AI also nudges the team when updates are late.



What does a daily SLA risk routine look like?

A daily SLA risk routine uses short, owned checks at set points in the day. For public sector estates, GOV.UK's Facilities Management Standard 001 requires central government organisations with property responsibilities to have an FM management system that includes performance evaluation.

Follow these steps each day:

  1. Open the dashboard each morning for a 10 to 15 minute risk check with the service manager and dispatcher.

  2. List the jobs closest to breach, jobs on hold, and subcontractor jobs with no recent update.

  3. Agree three to five actions, each with an owner: reassign, escalate, chase, or update the customer.

  4. Rescan the dashboard at midday for five minutes and check the morning actions have moved.

  5. Close the day with a 10-minute review of breaches and near misses, noting the main cause of each.

  6. Capture one improvement for tomorrow, such as a rule to change.

After a few weeks, the cause notes show which sites and subcontractors keep appearing in near misses. Those names give you a fact-based agenda for the next contract review.



Start with the service levels that carry credits

List the service levels that trigger a credit on each contract. Then check whether your team can see those clocks live today.

Any clock your team can't see live is your first fix. Next, give every alert an owner before you add more alerts. A short rule list with clear owners is easier to act on during a busy shift.

Each prevented breach keeps one more deduction off your invoice. To see how live SLA tracking would work across your contracts, book a demo with our team.





FAQs

What software flags jobs falling behind schedule before they miss an SLA?

Software with live job status and SLA tracking flags late jobs before they miss. Joblogic contract management tracks SLA adherence and alerts you to approaching deadlines. Engineer tracking shows each engineer on a live map that updates every five minutes. A dispatcher can then reassign a late job while time remains.

Can software monitor SLA risk in real time across all contracts?

Yes. FM software can show SLA risk across every contract in one live view. Joblogic gives real-time visibility of jobs, assets, engineers, and contracts through a single dashboard. You can filter it by site, trade, or contract, so each manager sees their own work. Customisable dashboards then track SLA performance contract by contract.

How does visibility software reduce SLA penalty costs?

Visibility software reduces SLA penalty costs by showing at-risk jobs while you can still save them. Live job status, engineer locations, and subcontractor updates sit in one view. The dispatcher can move a job up the queue or send a closer engineer. Each job saved inside its window is a service credit that never reaches your invoice.

How does a lack of visibility cause SLA breaches in FM?

A lack of visibility causes SLA breaches because nobody sees a job slipping until the clock runs out. Jobs wait on hold with no owner. Subcontractors finish work but update late. Requests arriving by email or phone sit outside the system. Each problem surfaces when someone builds the monthly report, after the credit already applies.

How do missed SLAs affect contract renewals?

On central government contracts, missed SLAs can affect the current contract and future work. GOV.UK guidance lists critical performance failure as a possible termination trigger event. It also says poor KPI performance could risk exclusion from future procurements. Private sector contracts set their own terms, so check the renewal and termination clauses in each one.