ServiceNow SLAs Explained: Definitions, Task SLAs & Timers

ServiceNow SLAs Explained

A Service Level Agreement (SLA) is a time-based commitment on a piece of work — for example, "respond to a priority-1 incident within 15 minutes and resolve it within 4 hours." ServiceNow tracks these commitments automatically and warns you before they are breached.

The building blocks

• SLA Definition — the rule. It specifies what the SLA applies to and its timing through three sets of conditions: Start (when the clock begins), Pause (when it stops temporarily), and Stop (when it ends). It also references a Schedule and a Duration.
• Task SLA — the instance. When a record matches an SLA definition's start condition, a Task SLA record is attached to it and begins tracking. One task can have several Task SLAs (response, resolution, and more).
• SLA timer / breach time — the running countdown shown on the record.

Schedules and elapsed time

SLAs usually measure business elapsed time against a schedule (for example, 9-to-5, Monday to Friday), not raw wall-clock time — so an incident opened Friday evening does not burn its SLA over the weekend. When an incident goes On Hold, a pause condition can stop the SLA clock so reporting stays fair.

Breach warnings

SLA workflows typically trigger warning and breach notifications based on percentage of time elapsed (say, 50% and 75%) rather than fixed times. Using percentages lets a single generic SLA workflow work across many different durations.

Where SLAs are used

• Incident — response and resolution targets by priority.
• Change and Request — fulfilment and approval targets.
• Catalog items — SLAs can target the requested item table and apply to specific catalog items via the start condition.

OLAs and underpinning contracts

Two related agreements support an SLA:

• OLA (Operational Level Agreement) — an internal commitment between teams (e.g. the network team responds to the service desk within 30 minutes).
• Underpinning Contract — a commitment from an external vendor.

Together, SLAs (to the customer), OLAs (between internal teams), and underpinning contracts (from suppliers) form the chain that makes an end-to-end service target achievable.

Frequently Asked Questions

What is an SLA in ServiceNow? A time-based commitment on a record — for example, resolve a P1 incident within 4 hours. ServiceNow tracks it automatically and warns before a breach.

What is the difference between an SLA Definition and a Task SLA? The SLA Definition is the rule (conditions, schedule, duration). A Task SLA is the running instance attached to a specific record when it matches the definition's start condition.

What are the three SLA conditions? Start, Pause, and Stop — they control when the timer begins, temporarily halts, and ends.

Why do SLAs use a schedule? So they measure business elapsed time (e.g. 9-to-5) rather than wall-clock time — an incident opened Friday night should not burn its SLA over the weekend.

What is the difference between an SLA, an OLA, and an underpinning contract? An SLA is a commitment to the customer, an OLA is between internal teams, and an underpinning contract is with an external vendor.

Key Takeaways

• SLA Definition = the rule (start/pause/stop + schedule + duration); Task SLA = the instance on a record.
• SLAs measure business elapsed time against a schedule; going On Hold can pause the clock.
• Breach warnings fire on percentage of time elapsed, so one workflow fits many durations.
• End-to-end targets rely on SLA + OLA + underpinning contract together.

Where to go next

• See where SLAs attach: Incident Management
• The automation that drives them: Flow Designer
• Practise: free practice test