Monitoring KPIs for outsourced services means measuring what leads to a correction, a penalty or an improvement agreement. Not every number in a report is a KPI: a steering KPI has a contractual standard and a consequence when it is missed, while a noise KPI merely fills a dashboard. Organisations that make this distinction and link the right KPIs to the contract and the invoice save an average of 8% per year.
Four supplier reports sit on your desk. The cleaning provider sends a DKS score, the security firm an incident list, the caterer nothing at all, and the technical maintenance provider a printout with fourteen numbers. You read them, you file them, and in the supplier review you talk about trends. But proving that a supplier is performing below the agreed standard is impossible. This is how it works at most organisations that monitor outsourced services: you measure a lot and steer on nothing.
Why most KPI reports help nobody
Availability of 99.2% sounds good. But that figure means nothing until you know what the agreed standard was and what it costs when that standard is missed. Was 99.5% the requirement? Then your supplier is performing below contract, and you are probably paying the full price without any correction.
This is the heart of the problem in monitoring outsourced services. Reports are collected, not used. They do not lead to a conversation, a correction or a saving. Time goes into pulling figures together from four different formats, not into steering. And when a complaint comes in, you have to search back manually for what was actually agreed.
What is the difference between a steering KPI and noise?
A steering KPI leads to action. When the standard is missed, you step in: you escalate, apply a penalty or make an improvement agreement. A noise KPI fills a chart and is read by nobody. The distinction is simple, yet it is almost never made.
Take cleaning. The number of hours deployed is noise: interesting for the supplier, irrelevant to you as long as the quality holds up. The DKS or VSR score against the contract standard is a steering KPI, because a consequence hangs on it. For security, the number of patrols completed is noise. The response time to incidents against the agreed standard is the KPI that counts.
The rule: only measure what you will use to steer. Choose one or two KPIs per service that genuinely matter. A monthly report with twelve numbers that nobody acts on costs more than a report with two numbers that trigger action.
The five questions every KPI must answer
Before you add a KPI to your report, it must answer five questions. If it cannot, it is noise.
- Definition: what exactly are you measuring, and is that definition the same for both parties?
- Data source: where does the figure come from and is it objectively verifiable?
- Owner: who is responsible for the measurement and the follow-up?
- Standard: what value is set in the contract as the line between good and unacceptable?
- Escalation path: what happens in concrete terms when the standard is missed?
The fifth question is the most important. Without an escalation path, a KPI is non-committal. In performance measurements in GRIP, you set the standard and the consequence per KPI, so a deviation does not disappear into an email.
Which steering KPI belongs to which service?
Monitoring outsourced services only works if you choose the right KPI per type of service. Four verticals, each with one or two steering KPIs:
- Cleaning: DKS or VSR score against the contract standard (for example an average of at least 7.5). The data source is an objective measurement in line with NEN 2075, not the impression of a site manager.
- Security: response time to incidents against the standard (for example on site within 8 minutes). The number of cameras or patrols says nothing about the performance you bought.
- Catering: the outcome of the hygiene audit plus registered complaints per period. If the caterer reports nothing, you measure yourself: no data is a signal too.
- Technical maintenance: fault resolution time and uptime of critical installations against the SLA. At a hospital with 15 sites, a cooling failure is not noise but an immediate risk.
Note that each service involves different data and different owners, but the same model: standard in the contract, measurement against that standard, consequence when it is missed. In healthcare, the continuity of technical installations carries more weight, while for a school building the emphasis lies on cleaning and experience. The model stays the same; the weighting differs per sector.
The KPI that counts: performance linked to the invoice
This is where Excel fails completely. You note a missed standard on a tab, but that deviation ends up nowhere. There is no link to the contract, no automatic alert and no audit trail. If you want to apply a penalty three months later, you cannot show when the standard was missed and by how much.
A steering KPI only becomes valuable when a deviation automatically triggers a consequence. A cleaning score below 7.5 leads to a penalty under the contract agreement. A response time above the standard in security leads to a credit. A missed indexation condition leads to a correction on the invoice. Performance and money sit side by side, with a recorded justification.
Making it demonstrable is the point. Without a justification, you dare not apply the penalty, and you pay the full price for substandard performance. With an audit trail per measurement, the conversation with the supplier is factual rather than a back-and-forth about trends.
From a standalone dashboard to steering on the right KPIs
KPIs too often live on an island. They only mean something when they sit alongside the contract agreements and the invoice. A score of 7.2 means nothing without the standard of 7.5 beside it and the penalty scheme beneath it. Once those three come together, your monthly report changes from a collection of numbers into a steering instrument.
That is exactly what the Contract Dashboard is built for: contract, KPIs, deviations and invoices in one place, across all types of service. Organisations that steer on the right KPIs this way instead of on noise save an average of 8% per year and free up 30% of the time spent on contract administration. Not by measuring more, but by measuring what counts and acting on it.
Frequently asked questions
What is the difference between a KPI and an SLA?
An SLA (service level agreement) sets the agreed standard, for example a response time of no more than 8 minutes. A KPI is the measurement that shows whether that standard is being met. The KPI becomes useful once you set it against the SLA standard and link a consequence to any deviation.
How many KPIs should I monitor per outsourced service?
One or two steering KPIs per service is usually enough. Choose the indicators that carry a contractual consequence and leave the rest out. A report with two numbers you act on is more valuable than a dashboard with twelve numbers nobody reads.
Which KPI belongs to a cleaning contract?
The DKS or VSR score against the contract standard, measured in line with NEN 2075. The number of hours deployed is noise: it says something about the supplier, not about the quality you bought. Measure the score objectively and link a penalty agreement to it if the standard is structurally missed.
How do I link a KPI to a penalty on the invoice?
Set out in the contract which standard applies and what financial consequence a deviation carries. Measure the KPI per period and record every deviation with date and scale. Without an audit trail per measurement, you cannot justify a penalty, and in practice you will not dare to apply it.
Why is Excel not enough for KPI monitoring?
In Excel, a missed standard stands apart from the contract and the invoice. There is no automatic alert, no link to the agreement and no audit trail. If you want to apply a correction months later, you cannot prove when the standard was missed and by how much.
What is a steering KPI for security services?
The response time to incidents against the agreed standard. The number of cameras, patrols or staff deployed is noise. Measure how quickly the supplier is on site during an incident and set that against the SLA standard you bought.
Want to see how to link steering KPIs to the contract and the invoice for all your outsourced services? See how GRIP solves this and book a demo.