IT CanvassTalk to an advisor
Administration · LessonBy , ServiceNow Architect · Updated

SLAs

Service Level Agreements track whether work is handled inside its promised time. In ServiceNow an SLA is a timer, attached to a task, driven by conditions and a business schedule. Getting the schedule and the start/stop/pause conditions right is what separates accurate SLAs from constant disputes.

Quick answer

Service Level Agreements track whether work is handled inside its promised time. In ServiceNow an SLA is a timer, attached to a task, driven by conditions and a business schedule. Getting the schedule and the start/stop/pause conditions right is what separates accurate SLAs from constant disputes.

Key takeaways
  • Definition vs instance
  • The four conditions
  • Why schedules change everything
  • Warnings and escalation
  • Retroactive start and pause

Definition vs instance

You configure an SLA Definition (the rule). At run time the platform attaches a Task SLA record (the live timer) to each matching task. The Task SLA shows elapsed time, percentage, stage and breach status, it is what reports and dashboards read.

The four conditions

Start
When the clock begins (e.g. incident opened AND priority = 1).
Stop
When it is met (e.g. state = Resolved).
Pause
When time should not count (e.g. state = Awaiting caller).
Reset
Conditions that start a fresh timer.
// A P1 response SLA Start: priority = 1 AND active = true Pause: state = Awaiting Caller Stop: state IN (Resolved, Closed)

Why schedules change everything

An SLA measured against a 9-5, Mon-Fri schedule pauses overnight and at weekends, so "8 business hours" is not 8 wall-clock hours. Time zone matters too, the same SLA can breach or not depending on which schedule and zone it uses. This is the number-one source of SLA arguments.

Warnings and escalation

A flow (or the legacy SLA workflow) attached to the definition can notify the assignee at, say, 50% and 75% elapsed, reassign, or escalate on breach, so teams act before the deadline, not after. This is where SLAs stop being a report and start driving behaviour.

Retroactive start and pause

Two options fine-tune accuracy: retroactive start begins the timer from an earlier timestamp (e.g. when the incident was actually opened, not when the SLA attached), and correct pause conditions stop the clock while you legitimately wait on the customer.

Common mistakes

  • Ignoring the schedule/time zone, so elapsed time looks wrong.
  • Missing a pause condition, so time accrues while waiting on the customer.
  • Overlapping start conditions spinning up duplicate timers on one task.
  • No warning/escalation, so SLAs are noticed only after they breach.

Practice challenge

3 questions
Q1An SLA measures...

Whether work meets a time target

SLAs track time-to-respond and time-to-resolve.

Q2An SLA counts time against a...

Schedule of working hours

Schedules define which hours count.

Q3A breached SLA usually triggers...

Escalation or notification

Breaches drive escalations so teams react.

Frequently asked questions

What does the term SLAs refer to in ServiceNow?
Service Level Agreements track whether work is handled inside its promised time. In ServiceNow an SLA is a timer, attached to a task, driven by conditions and a business schedule. Getting the schedule and the start/stop/pause conditions right is what separates accurate SLAs from constant disputes.
What reporting depends on SLAs?
The Task SLA shows elapsed time, percentage, stage and breach status, it is what reports and dashboards read.
What automates SLAs in Flow Designer?
A flow (or the legacy SLA workflow) attached to the definition can notify the assignee at, say, 50% and 75% elapsed, reassign, or escalate on breach, so teams act before the deadline, not after.
What tends to go wrong with SLAs?
Ignoring the schedule/time zone, so elapsed time looks wrong. Missing a pause condition, so time accrues while waiting on the customer. Overlapping start conditions spinning up duplicate timers on one task.

Want this taught live, with job support?

ServiceNow Training is delivered live by working practitioners, with certification prep and placement support.

See ServiceNow Training →