{"id":32977,"date":"2026-01-28T15:26:08","date_gmt":"2026-01-28T14:26:08","guid":{"rendered":"https:\/\/sii.pl\/blog\/?p=32977"},"modified":"2026-05-07T12:56:00","modified_gmt":"2026-05-07T10:56:00","slug":"servicenow-and-sla","status":"publish","type":"post","link":"https:\/\/sii.pl\/blog\/en\/servicenow-and-sla\/","title":{"rendered":"ServiceNow and SLA"},"content":{"rendered":"\n
The practice of establishing SLA (Service Level Agreement) is almost as old as the entire IT industry. According to ITIL4, an SLA is a documented agreement between a service provider and a customer that defines both the services required and the expected level of the service. The provider and the customer may be separate entities (in which case the agreement is commercial), or they may be part of the same organization (in which case the agreement is non-commercial).<\/p>\n\n\n\n
In addition to SLAs, we also distinguish:<\/p>\n\n\n\n
\n
OLA \u2013 Operational Level Agreement: an agreement on the guaranteed level of internal support.<\/li>\n\n\n\n
UC \u2013 Underpinning Contract: a contract with an external supplier.<\/li>\n<\/ul>\n\n\n\n
The relationships between SLA, OLA, and UC are as follows:<\/p>\n\n\n\n
\n
SLA represents the main agreement regarding the services provided by the provider to the customer.<\/li>\n\n\n\n
OLA and UC concern supporting services provided either:\n
\n
OLA \u2013 internally (departments, teams within the service provider’s organization),<\/li>\n\n\n\n
UC \u2013 externally (third-party service providers).<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
Example:<\/p>\n\n\n\n
\n
SLA \u2013 agreement for service provision: maintaining a website,<\/li>\n\n\n\n
OLA \u2013 internal agreement covering network, infrastructure maintenance, or user support,<\/li>\n\n\n\n
UC \u2013 agreements with external entities for supporting services necessary to deliver the leading service, such as internet connectivity, power supply, physical security, etc.<\/li>\n<\/ol>\n\n\n\n
The practice of using Service Level Agreements<\/strong><\/strong><\/h2>\n\n\n\n
In many organizations, these three types of agreements are not always clearly distinguished. Instead, the term SLA is used in all cases, often with an additional qualifier indicating the parties involved (e.g., “SLA with the client” or “SLA with the ISP”). This is not a significant issue since each of these agreements typically contains the same elements:<\/p>\n\n\n\n
\n
Scope of the agreement (which services are provided).<\/li>\n\n\n\n
Required service levels.<\/li>\n\n\n\n
Service measurement and verification methods.<\/li>\n\n\n\n
Payment terms and penalties (in internal agreements, these may differ from commercial ones).<\/li>\n<\/ul>\n\n\n\n
Mapping the terms of SLA\/OLA\/UC agreements into the ServiceNow system can be a significant challenge, especially when contract terms are imprecise or do not account for the realities of ITSM tools. Moreover, SLA reports generated by ServiceNow can serve as the basis for evaluating service quality and, consequently, for settling accounts between parties. This makes the topic extremely important.<\/p>\n\n\n\n
Features of services covered by SLAs<\/strong><\/strong><\/h2>\n\n\n\n
Parameters or service characteristics that are (or should be) included in SLAs usually cover:<\/p>\n\n\n\n
\n
Volume\/Traffic:<\/strong> Can the service handle the required volume of requests or data? (e.g., up to 100,000 HTTP requests per month)<\/li>\n\n\n\n
Availability:<\/strong> Is the service available to users\/customers when they need it? (e.g., 99% availability, 24×7)<\/li>\n\n\n\n
Latency:<\/strong> Is the service response delivered within an acceptable time frame? (e.g., HTTP service response within 300 ms.)<\/li>\n\n\n\n
Errors:<\/strong> Does the service provide the required functionality? (e.g., HTTP requests do not return 4xx or 5xx errors)<\/li>\n\n\n\n
Ticket Handling:<\/strong> Is support effective and efficient? Are tickets (incidents, requests, changes) resolved within the agreed timeframe?<\/li>\n<\/ul>\n\n\n\n
It is worth noting that the parameters listed above are generally well understood by users, customers, and the business; however, assessing the quality of their delivery using the SLA mechanisms available in ServiceNow may prove challenging.<\/p>\n\n\n\n
Due to space limitations, the examples provided here focus on ticket handling (such as incidents or service requests) and typical scenarios (not covering all possible cases).<\/p>\n\n\n\n
Parameters for ticket handling<\/strong><\/strong><\/h3>\n\n\n\n
Common SLA parameters for ticket handling include:<\/p>\n\n\n\n
\n
Scope of services provided (e.g., issues with the website will be handled, but a user’s workstation failure will not).<\/li>\n\n\n\n
Communication channels through which issues or requests can be reported (phone, e-mail, portal, chat)?<\/li>\n\n\n\n
Who is authorized to submit requests\/report issues?<\/li>\n\n\n\n
Defined ticket volume (e.g., the customer is entitled to 100 tickets per month under the agreement, with additional tickets billed separately).<\/li>\n\n\n\n
Response time (how soon after ticket submission or creation actions will be taken).<\/li>\n\n\n\n
Resolution time (how soon the issue will be resolved or the request fulfilled).<\/li>\n<\/ol>\n\n\n\n
A well-written (precise) SLA is a prerequisite for a good implementation in ServiceNow.<\/strong><\/p>\n\n\n\n
In the above example, precision concerns points:<\/p>\n\n\n\n
\n
1, 2, 3, and 4: On what basis do we determine whether a ticket is valid\/properly submitted? Should invalid tickets also be logged, and if so, do they count toward the customer’s quota?<\/li>\n\n\n\n
5 and 6: How do we measure time? When do we start, pause, or stop the timer? Are response and resolution times cumulative or separate (do they start simultaneously, or does resolution time start after the response time ends)?<\/li>\n<\/ul>\n\n\n\n
The complexity increases when SLAs are established in large organizations operating across different time zones<\/strong> (different working hours), cultures (different calendars of working days and holidays, communication languages), and when services vary by location.<\/p>\n\n\n\n
SLA Definitions in ServiceNow<\/strong><\/strong><\/h2>\n\n\n\n
The first element you may need to configure is the SLA Definition<\/strong>. The form for a new record looks as follows:<\/p>\n\n\n\n
Fig. 1 The form for a new record<\/figcaption><\/figure>\n\n\n\n
Field descriptions<\/strong><\/strong><\/h2>\n\n\n\n
Name:<\/strong> The name of the record \u2013 it’s best to define a naming convention before configuration to keep names meaningful and organized. The more records in the contract_sla<\/em> table, the more important this becomes. A consistent naming convention helps with list navigation and significantly improves name-based filtering.<\/p>\n\n\n\n
Type:<\/strong> While you can differentiate types of SLAs in ServiceNow, this only affects reporting and does not influence the SLA Definition’s functionality. In relation to CSDM, SLAs are usually linked to a BSO (Business Service Offering), whereas OLAs or UCs relate to a TSO (Technical Service Offering).<\/p>\n\n\n\n
Target:<\/strong> Distinguishes between Resolution and Response. This property is relevant only for reporting purposes and does not affect the behaviour of the SLA Definition itself. However, it is important to configure the remaining record parameters consistently if one of the above values is used.Note:<\/em><\/strong> The configuration of this property should reflect the content of the agreement. It is essential to ensure that both parties share a common understanding of what constitutes a response and a resolution, particularly regarding when each action begins and ends.<\/p>\n\n\n\n
Table:<\/strong> Important setting that determines the table the SLA Definition applies to. Common examples include tables like: incident, sc_req_item, sc_task,<\/em> and problem<\/em>. The table selection determines which process the SLA definition is associated with.<\/p>\n\n\n\n
Flow:<\/strong> Enables triggering specific actions during SLA execution, such as sending notifications or initiating escalations.<\/p>\n\n\n\n
Vendor:<\/strong> References the core_company<\/em> table to indicate the vendor responsible for fulfilling the agreement (especially relevant for UC).<\/p>\n\n\n\n
Service Commitment:<\/strong> Check this option if the SLA Definition is linked to a Service Commitment (and, consequently, to a Service Offering).<\/p>\n\n\n\n
Enable logging:<\/strong> Enables detailed logs for the SLA definition, which are helpful for diagnosing SLA-related issues.<\/p>\n\n\n\n
Active:<\/strong> Marks the SLA definition as active and ready for use.<\/p>\n\n\n\n
Duration type:<\/strong> Specifies how SLA time is calculated and changes the behaviour of the definition and form. Choices include:<\/p>\n\n\n\n
\n
User-specified duration:<\/strong> Requires specifying a duration in the Duration<\/em> field.<\/li>\n\n\n\n
Other options:<\/strong> Specify a relative time, e.g., “End of next business day.<\/em>” This requires selecting the record type for relative time calculation under “Relative duration works on.”<\/li>\n<\/ul>\n\n\n\n
Duration:<\/strong> Appears when “User specified duration<\/em>” is selected. Defines the time after which the SLA is breached. Note: Time measurement may not be continuous \u2013 it depends on other SLA Definition parameters, such as Schedule<\/strong> and Start\/Pause\/Stop Condition<\/strong>.<\/p>\n\n\n\n
Relative duration works on:<\/strong> Appears when a relative duration type is selected. Options: Task record<\/strong> or SLA record<\/strong>.<\/p>\n\n\n\n
Schedule source:<\/strong> Determines the schedule used to measure SLA time. Choices include:<\/p>\n\n\n\n
\n
No schedule:<\/strong> 24×7 schedule without exceptions.<\/li>\n\n\n\n
SLA Definition:<\/strong> Requires selecting a schedule in the next field.<\/li>\n\n\n\n
Task field:<\/strong> Depends on the selected table (e.g., Incident field, catalog task field) and requires specifying an object with a schedule (e.g., Configuration Item \u2192 Schedule).<\/li>\n<\/ul>\n\n\n\n
Schedule source field:<\/strong> Specifies the object containing the schedule (e.g., Configuration Item Schedule or Caller Schedule).<\/p>\n\n\n\n
Schedule:<\/strong> Select a specific schedule from the cmn_schedule<\/em> table (typically defining working days and hours).<\/p>\n\n\n\n
Timezone source:<\/strong> Determines the time zone used when creating the SLA task:<\/p>\n\n\n\n
\n
Caller’s time zone<\/li>\n\n\n\n
SLA definition’s time zone (specified in the Timezone field)<\/li>\n\n\n\n
CI’s location’s time zone<\/li>\n\n\n\n
Task’s location’s time zone<\/li>\n\n\n\n
Caller’s location’s time zone<\/li>\n<\/ul>\n\n\n\n
Note:<\/strong> Time zone settings are particularly important in international organizations where support operates in different time zones from the users (e.g., a European service desk supporting users in the U.S.).<\/p>\n\n\n\n
These conditions define when SLA time tracking should be started (start<\/strong>), paused (pause)<\/strong>, completed (stop)<\/strong>, or reset<\/strong> (restarted under specific circumstances).<\/p>\n\n\n\n
The configuration of Start\/Pause\/Stop\/Reset conditions offers a wide range of possibilities. It typically uses<\/strong> simple to highly complex conditions (filters) that must be met to trigger a specific time-tracking action.<\/p>\n\n\n\n
Start condition:<\/strong> An example configuration form is shown in the figure below. A set of filters defining when the time measurement should begin.<\/p>\n\n\n\n
Fig. 2 An example configuration form<\/figcaption><\/figure>\n\n\n\n
Retroactive start:<\/strong> Selecting this option enables two additional parameters \u2013 Retroactive pause<\/em> and Set start to<\/em>. When enabled, it changes the way time is measured: instead of starting when the condition defined in the Start condition<\/em> filter is met, time measurement begins at the point specified in the Set start to<\/em> field. This option is required when there is a possibility that one SLA definition may be cancelled and another triggered in its place. Example of use: A change in a ticket’s priority during its handling.<\/p>\n\n\n\n
Retroactive pause:<\/strong> Previously recorded pause periods are included in the time calculation.<\/p>\n\n\n\n
Set start to:<\/strong> Specifies which point in the entry history is considered the start of time tracking when Retroactive Start<\/em> is enabled.<\/p>\n\n\n\n
When to cancel:<\/strong> Defines when time measurement should stop. Three options are available:<\/p>\n\n\n\n
\n
Cancel conditions are met<\/strong> \u2013 selecting this option enables an additional Cancel conditions setting and requires specifying the conditions that must be met to cancel the operation of the given SLA definition.<\/li>\n\n\n\n
Start conditions are not met<\/strong> \u2013 time measurement stops when the conditions specified in the Start condition are no longer met.<\/li>\n\n\n\n
Never<\/strong> \u2013 Time measurement is never cancelled; no additional configuration is required.<\/li>\n<\/ul>\n\n\n\n
Pause condition:<\/strong> Contains conditions (filter) that must be met to pause time measurement.<\/p>\n\n\n\n
When to resume:<\/strong> Defines when time measurement should resume (either when pause conditions are no longer met or when specific resume conditions are met).<\/p>\n\n\n\n
\n
Pause conditions are not met:<\/strong> as soon as the conditions specified in the Pause condition option are no longer true, time measurement is resumed.<\/li>\n\n\n\n
Resume conditions are met:<\/strong> specifies the conditions that must be met to resume time measurement. Requires the addition of a Resume conditions option, which is a set of conditions (filters).<\/li>\n<\/ul>\n\n\n\n
Stop conditions<\/strong>: it only contains conditions (filters) that, when met, stop time measurement.<\/p>\n\n\n\n
Reset condition<\/strong>: Allows you to define additional conditions that, when met, result in the immediate termination or cancellation of the current SLA definition and the initiation of a new one. This option is practical when a significant parameter changes during task execution and requires the SLA to be updated. For example, assigning a task to a different Assignment group that operates under conditions different from those defined in the currently active SLA. If the new SLA definition meets the Start condition, it will be launched automatically.<\/p>\n\n\n\n
Note: <\/strong>SLA conditions (Start<\/strong> \/ Pause<\/strong> \/ Stop<\/strong>) are evaluated in the following order:<\/p>\n\n\n\n\n
Stop condition<\/li>\n\n\n\n
Pause condition<\/li>\n\n\n\n
Start condition<\/li>\n<\/ol>\n\n\n\n
If a matching condition is found during processing, subsequent conditions are NOT evaluated!<\/strong><\/p>\n\n\n\n
Case Study<\/strong><\/strong><\/h2>\n\n\n\n
As a detailed description of all SLA Definition<\/strong> record configuration options would be extensive enough to warrant a separate article, this article is limited to illustrating the most common use cases.<\/p>\n\n\n\n
Before beginning the configuration, it is advisable to review key recommendations for approaching this task. In addition to thoroughly understanding the content of the SLA agreement(s), it is beneficial to map out (or visualize) the process by which the SLA definitions are being created. All potential use cases for the process should be carefully considered and appropriately reflected in the configuration.<\/p>\n\n\n\n
Defining SLAs for incident management<\/strong><\/strong><\/h3>\n\n\n\n
Suppose SLA definitions need to be configured for incident management with four priorities, as shown below:<\/p>\n\n\n\n
Next to the priorities, schedules, and execution times (Duration<\/em>) are given.<\/p>\n\n\n\n
Three support teams are involved (represented in sys_user_group<\/em> in ServiceNow):<\/p>\n\n\n\n
\n
Service Desk<\/li>\n\n\n\n
Level 2<\/li>\n\n\n\n
Level 3<\/li>\n<\/ul>\n\n\n\n
A task defined in this way presents specific challenges during implementation:<\/strong><\/p>\n\n\n\n\n
How should time be measured for tickets handled by multiple teams \u2013 separately or as a whole?<\/li>\n\n\n\n
Who owns the ticket from creation to closure?<\/li>\n\n\n\n
How should response time versus resolution time be measured?<\/li>\n\n\n\n
Under what conditions should time measurement be paused?<\/li>\n\n\n\n
Under what conditions should ticket processing be cancelled?<\/li>\n\n\n\n
Do schedules account for holidays?<\/li>\n<\/ol>\n\n\n\n
When assigned a similar task, the individual responsible for configuring ServiceNow SLA Definitions must obtain answers to the questions outlined above. These answers may already be specified in the SLA document; if not, clarification should be sought from the person responsible for drafting the agreement.<\/p>\n\n\n\n
For this example, let us assume that the following answers have been obtained:<\/p>\n\n\n\n
\n
Time is measured holistically from the customer’s perspective.<\/li>\n\n\n\n
Service Desk is always the owner.<\/li>\n\n\n\n
Response and resolution time measurement start simultaneously. Response time stops when the Assigned to<\/strong> field is populated.<\/li>\n\n\n\n
Waiting for user communication allows time measurement to be paused.<\/li>\n\n\n\n
All tickets must be resolved (no cancel conditions).<\/li>\n\n\n\n
Schedules do not account for holidays.<\/li>\n<\/ol>\n\n\n\n
Even in this relatively simple scenario, at least eight SLA definitions<\/strong> are required (four priorities \u00d7 two definitions: response and resolution).<\/p>\n\n\n\n
A little practice<\/strong><\/strong><\/h3>\n\n\n\n
Consider the following case:<\/strong> According to the example above, P2 incidents must be resolved within 12 hours of being logged. Processing occurs 24 hours a day on business days. In summary, every P2 incident must be resolved within the specified timeframe, implying a 100% resolution rate. The same principle applies to incidents of other priorities in the example provided.<\/p>\n\n\n\n
In SLA management practice, achieving a 100% resolution rate is rare<\/strong>, often impractical, or prohibitively expensive (for instance, maintaining 99.999% system availability) and is therefore reserved for exceptional cases. Can similar principles apply to ticket resolution? The answer is Yes \u2013 SLAs should define expected resolution levels, for example:<\/p>\n\n\n\n
SLA definition records themselves do not include a field for this. However, SLA performance can be measured and reported in SLA reports. Another option is to use Service Commitment<\/strong>, which includes the SLA Percentage<\/strong> property.<\/p>\n\n\n\n
During the given billing period, 95.03%<\/strong> of Priority 3 (P3) incidents were resolved within the parameters specified in the SLA definition for this priority. 4.97%<\/strong> of incidents were not resolved within the required timeframe.<\/p>\n\n\n\n
According to the table above, the required fulfillment rate for P3 incidents is 98%<\/strong>. Therefore, in this example, the SLA was violated, as the achieved fulfilment rate was just over 95%<\/strong>.<\/p>\n\n\n
![\"The](\"https:\/\/sii.pl\/blog\/wp-content\/uploads\/2026\/01\/image1-1-1024x505.png\")
![\"An](\"https:\/\/sii.pl\/blog\/wp-content\/uploads\/2026\/01\/image2-1-1024x407.png\")
![\"Sample](\"https:\/\/sii.pl\/blog\/wp-content\/uploads\/2026\/01\/image3-1.png\")
![\"\"](\"https:\/\/sii.pl\/blog\/wp-content\/uploads\/2026\/04\/Blog-ServiceNow-Desktop_.jpg\")
\n <\/picture>\n \n