ServiceNow SLA Elapsed Time Practice: Actual vs Business

Free ServiceNow SLA practice: from the schedule, the SLA duration, the start, any pause and the time now, work out the actual and business elapsed time and percentage. Check my answer names the slip, such as counting the weekend or forgetting the pause.

   
   
   
   
   
   

Check your answer to see the working.

Actual time counts 24x7. Business time counts only the hours inside the schedule. Both leave out the time the SLA was paused, and the percentage is the elapsed time over the SLA duration.

Every case is invented: one time zone, no holidays, and any pause falls inside the schedule hours.

ServiceNow exam prep

The CIS-ITSM exam blueprint gives Incident Management 25% of the exam. Start with the free real exam questions, then get the full pack.

ServiceNow CIS-ITSM
242 real exam questionsUS$39
Free: 60 questionsGet the full pack

For access rules, try the ServiceNow ACL practice.

SLA elapsed time FAQ

The rules in short
  • Actual elapsed time: from the start to now, 24x7, minus the pause.
  • Business elapsed time: only the hours inside the schedule, minus the pause.
  • No schedule: business elapsed time is the same as actual elapsed time.
  • Elapsed percentage: elapsed time ÷ SLA duration × 100, for actual and business time alike.
What is the difference between actual and business elapsed time in ServiceNow?

The ServiceNow documentation says actual elapsed values are calculated on a 24x7 basis, and business elapsed values are calculated based on the schedule specified in the task SLA, which is taken from the SLA definition by default. So actual time counts every hour from the start to now, and business time counts only the hours inside the schedule.

What are the worked examples in the ServiceNow docs?

With a schedule of 9 am to 5 pm on weekdays, a task SLA that starts at 2 pm on a weekday shows 3 business hours and 19 actual hours by 9 am the next weekday. In the second example an incident is opened on Friday at 9 pm, outside a schedule of 8 am to 5 pm on weekdays, and the time now is the following Monday at 9:30 am: business elapsed time is 1 hour 30 minutes and actual elapsed time is 60 hours 30 minutes. The first case in the drill is this second example.

How is the elapsed percentage worked out?

The Task SLA table defines the Actual Elapsed Percentage as the percentage of total SLA that has elapsed, and the Business Elapsed Percentage as the percentage of total SLA that has elapsed within the specified schedule, both minus pause duration. So divide the elapsed time by the SLA duration and multiply by 100. In the docs example on an 8 hour SLA that is 60.5 ÷ 8 × 100 = 756.25% actual, which the docs call over 750%, and 1.5 ÷ 8 × 100 = 18.75% business, which they give as 19%. The drill asks for 1 decimal place.

Why can the actual elapsed percentage be over 100%?

Actual time keeps running at night and at the weekend, while business time stops outside the schedule. In the docs example, 60 hours 30 minutes of actual time is over 750% of the 8 hour SLA, while the business elapsed percentage is 19%.

How does a pause change the elapsed time?

In the Task SLA table, the actual elapsed time is the time between start time and now, and the business elapsed time is the time within the schedule between start time and now, both minus pause duration. In this drill every pause falls inside the schedule hours, so the same pause comes off both.

What if the SLA has no schedule?

Then the business elapsed time is the same as the actual elapsed time, as the ServiceNow docs say. The docs add that a system property can turn this off, which leaves the business fields 0 or empty. The drill uses the default.

How do I type my answer?

Type a time as hours and minutes: 60 h 30 min, 60h30m and 60:30 all work, and so do decimal hours such as 60.5. Type a percentage to 1 decimal place, such as 18.8.

What does the drill leave out?

Time zones, holidays, a retroactive start and pauses outside the schedule hours. Every case is invented and runs in one time zone, with the SLA in progress at the time now.

Sources
  • ServiceNow documentation (Brazil release, updated 10 September 2026), Elapsed time counting: actual elapsed values on a 24x7 basis, business elapsed values from the schedule in the task SLA, no schedule meaning business equals actual, and the two worked examples (3 business and 19 actual hours; 1 hour 30 minutes business and 60 hours 30 minutes actual, over 750% and 19% on an 8 hour SLA).
  • ServiceNow documentation (Brazil release, updated 10 September 2026), Task SLA table: Actual and Business Elapsed Time and Percentage, each minus pause duration, and the Stage values.
  • ServiceNow University, CIS-ITSM exam blueprint: the exam domains and their weights (Incident Management 25%).
  • Checked 21 November 2026. The tool's own approach: every case is invented, in one time zone with no holidays; a pause always falls inside the schedule hours; Now is 1 to 6 days after the start; percentages are asked to 1 decimal place. The drill reproduces both worked examples in the documentation, and an independent re-solver (calendar dates, counted in 15 minute steps) agreed with it on 38,004 generated problems.

Checked 21 November 2026 against the ServiceNow documentation (Brazil release) and the CIS-ITSM exam blueprint.

More free tools

All free tools