Home › Resources › Glossary › SLA

Resources · Glossary

What is an SLA? Service level agreements in audit work

In shortAn SLA, or service level agreement, is an agreed and measurable target for a service, such as how quickly a request is answered or how available a system is. In audit and compliance work, SLAs set the expected time to respond to a finding, supply evidence, review a submission or approve a stage.

What does an SLA mean in audit work?

The term comes from service contracts, where a supplier commits to a level of service. Inside an organisation the same idea sets expectations between teams.

For audits, the useful SLAs are about time: how long an owner has to respond to a finding of a given severity, and how long a reviewer has to accept or return evidence.

What does a usable SLA define?

WhatThe target

The event being timed and the limit, such as a response within two working days.

HowThe measurement

When the clock starts and stops, and what counts as meeting the target.

Then whatThe consequence

Who is told and what happens when the target is missed.

What do audit SLAs look like?

Example targets an organisation might set. The numbers are illustrative; choose your own.

EventExample target
Owner responds to a critical finding2 working days
Evidence supplied after a request5 working days
Reviewer accepts or returns evidence3 working days
Critical corrective action completed30 days, with escalation at day 20

This is an illustration written for this page, not a customer record.

Where do frameworks refer to service levels?

FrameworkWhereWhat it asks for
ISO 20000-1Clause 8.3.3Service level management: agreed service levels, monitoring and review against targets.
ISO 27001Annex A 5.22Supplier services are monitored, reviewed and evaluated, including against agreed levels.
SOC 2Availability criteriaCommitments made to customers about availability are met and monitored.
ISO 27001Clause 9.1The organisation decides what is monitored and measured, and when.

References are to the current editions listed under Sources. Check the edition your auditor is using.

What goes wrong with SLAs?

01

Targets nobody measures

The policy says five days, but nothing records the start time.

Instead: time it from the system, automatically.

02

One target for everything

A low-risk observation has the same deadline as a critical finding.

Instead: set targets by severity.

03

No consequence

Missed targets are noted and nothing follows.

Instead: tie each SLA to an escalation path.

How does QULDEX handle this?

Auditor Command Center

Every audit, finding and deadline in one view, with overdue items surfaced first.

See the module

SLA: common questions

What does SLA stand for?

Service level agreement.

What is the difference between an SLA and a KPI?

An SLA is a commitment to a target. A KPI is a measure of performance. Whether an SLA was met is often reported as a KPI.

Are internal SLAs binding?

They are not contracts, but they can be set in policy and reported to management, which gives them weight.

Deadlines that are timed and escalated automatically

Controls, evidence, findings and corrective actions in one audit workspace.

Schedule
Book a Demo