Contractor performance audit: how to check what the SLA can’t

A contractor performance audit checks whether fixes hold, not just response times. What to check before, during and after each job, step by step.

Infraspeak Team
•Nov 19, 2026•9 min read

A contractor performance audit checks whether a contractor’s work solved the problem they were paid to solve, not only whether they turned up on time. It collects evidence at three points: before the job starts, when it closes, and across the life of the contract.

“Closed within SLA.” It’s on every monthly report, usually in green, and it says nothing about the air handling unit on the third floor that’s been “fixed” three times since spring. That gap is what a contractor performance audit is for. The SLA measures the speed of the visit. The audit measures what the visit left behind.

This guide covers what to check, when to check it and how to run the audit so the results hold up in a renewal conversation. For the wider job of vetting, briefing and tracking contractors, our guide on how to manage contractors without spending your week chasing them covers the full cycle.

What is a contractor performance audit?

A contractor performance audit is a structured review of the work an external contractor delivered, checked against the contract and against what happened to the assets afterwards. It looks at evidence (job reports, photos, checklists, failure history) rather than the contractor’s own summary of the month.

It sits between two reviews you probably already run. A maintenance audit looks at your own maintenance operation as a whole, and a contract review looks at cost and terms. A contractor performance audit focuses on one relationship and asks a narrower question: is this contractor making the operation better, or just keeping the tickets moving?

Why isn’t SLA compliance enough to judge a contractor?

Most SLAs measure activity: response time, attendance, tickets closed. A contractor can hit every one of those and still leave you with an asset that fails again within a fortnight, a part that stays “on order” for most of the quarter, or a fix that lasts until the next heatwave.

The SLA report can’t tell these apart, because it was never built to. When the same chiller comes back on the work order list, you need to know why before you decide who’s at fault. The usual causes are these:

  • Recurring failure: the root cause was never found, so each visit treats the symptom.

  • Poor execution: the job was done badly, or closed without being done.

  • Contract scope: the contractor did exactly what the contract asks, and the contract asks for the wrong thing.

  • Missing parts or skills: the right technician or the right part wasn’t available when it mattered.

Only one of those is entirely the contractor’s problem. An audit that separates them gives you something to act on, whether that’s a corrective plan, a contract change or a different contractor. Without it, renewals default to price, and the contractor who’s best for your operation can lose to the one who’s cheapest on paper.

What should a contractor performance audit check?

Check the outcomes on the assets alongside the activity on the tickets. These are the checks that tell you the most, and the evidence each one needs:

Check

What it tells you

Evidence you need

Repeat failures on the same asset

Whether fixes are holding

Work order history per asset, with failure codes

First-time fix

Whether the right technician and parts turn up

Revisits linked to the original work order

Time to resolve, not only to respond

Whether the clock stops when the problem does

Open, start and close timestamps

Proof of work

Whether the job was done as reported

Photos, timestamps and signatures on the job report

Safety and access conditions

Whether site rules were followed before work began

Completed pre-work checklists

Quality on site

Whether standards hold across locations

Scored inspections tied to locations or assets

You won’t need every check for every contractor. A lift contractor and a cleaning contractor fail in different ways (and leave very different complaints behind), so weight the checks by the risk each contract carries.

When should you audit contractor performance?

At three points: before the job starts, when it closes, and across the contract. Each one catches problems the others miss, and the evidence from the first two is what makes the third one fair.

Before the job starts

The cheapest problem to fix is the one that never reaches the site. Before a technician starts work, they should confirm the site’s risk assessment, the safety conditions and that they hold the certifications the job needs. If that check lives in a binder at reception, nobody can prove it happened. If it’s a required step before the job can start, it becomes evidence.

When the job closes

Close-out is where most audit evidence is won or lost. A job report that says “done” is a claim. A report with photos, timestamps and a signature is proof. Make that proof a condition of closing the job, so you’re never chasing it after something has gone wrong.

Across the contract

This is the audit most people picture: a periodic review of how the contractor performed against what was agreed. It works when it’s built on the evidence above. Compare the contract with what happened (SLA performance, repeat failures, inspection scores per site) and bring the results to every quarterly review and renewal.

Look for trends over single bad weeks. One missed deadline during a heatwave tells you little. The same asset failing after every visit for a whole quarter tells you a lot, and that pattern only shows up when the evidence from every job sits in one place.

How do you run a contractor performance audit, step by step?

A contractor performance audit works best as a routine you run all year. These six steps take you from the contract to a result you can act on:

  1. Define what good looks like for each contract. Agree the outcomes that matter for that service, such as repeat failures on critical assets or site inspection scores, alongside the SLAs already in the contract.

  2. Make evidence a condition of the work. Pre-work checklists before the job starts, photos and signatures before it closes. Evidence collected at the time beats any report written at the end of the month.

  3. Get contractors working in the same system as you. When their data lives in their own software and reaches you as a monthly spreadsheet, you’re auditing their summary. When they work inside your operation, you’re auditing the work.

  4. Inspect with the same questionnaire everywhere. Score the same points at every site, so a good score in Lisbon means the same as a good score in Leeds.

  5. Separate the causes before you score the contractor. Check whether a failure came from execution, scope, parts or a root cause nobody has found yet.

  6. Act on the results. Turn each failed check into a corrective plan with an owner, a deadline and the evidence that will prove it’s fixed, then check it at the next audit.

The last step is where most audits stall: the findings go into a slide deck and stay there. Tie each failed check to a follow-up action, and the next audit has something real to check.

How does Infraspeak help you audit contractor performance?

Infraspeak, the collaborative FM platform, brings contractors inside your operation through Infraspeak Network, our supplier relationship management workspace. You and your contractors work from the same live data, so the audit starts from what happened on the job, not from what someone typed up afterwards. Here’s how it covers each audit point:

  • SLAs on shared work: configure and track SLAs on Work orders and Planned jobs shared with contractors, and get notified when a contractor breaches a deadline or doesn’t carry out a job as the contract sets out.

  • Gatekeeper before the job starts: require contractors to acknowledge site risk assessments, safety conditions and required certifications before they can start a Work order or Planned job order.

  • Proof of work at close-out: require photos, timestamps and digital signatures on the job report before a job can be closed.

  • Audits for scored inspections: build score-based questionnaires tied to locations or assets, schedule them periodically, and set rules that raise a work order automatically when a measurement isn’t met.

  • Analytics across the contract: compare each contractor’s performance with the KPIs and objectives you agreed, contract against reality, in reports you can bring to every review.

What you get is a record of evidence you didn’t have to build by hand, and contract conversations that start from what the contractor delivered. If you’re still comparing tools, our shortlist of supplier relationship management software sets out the options. Or go straight to the source: see how Infraspeak Network works.

Frequently asked questions about contractor performance audits

How often should you audit a contractor?

Collect evidence on every job, and run the scored review in time for each quarterly contract review. Add spot inspections more often on critical assets and high-risk sites.

Who should carry out a contractor performance audit?

The person who owns the contract should own the audit, with input from the site teams who see the work every day. Where you can, have scored inspections done by someone who doesn’t sign off that contractor’s invoices, so the scores stay credible.

What should you do when a contractor fails an audit?

Share the findings with the evidence, agree a corrective plan with deadlines, and re-check the failed points at the next audit. If the same points keep failing, you have the record you need to change the contract or the contractor.

Should contractors see their own audit results?

Yes. Contractors can only fix what they can see, and a contractor looking at the same evidence you are has far less to dispute.