Compare customer SLA deadlines with internal handoff targets

Keep the customer obligation visible while reviewing internal team milestones. An internal target can help explain where delivery time went, but it does not replace the customer deadline. A team may meet its own acceptance target after an earlier handoff has already consumed the customer's remaining buffer.

ServiceNow's SLA API documentation distinguishes customer SLAs from OLAs between internal teams. That distinction supports separate reporting; the actual definitions and clock behavior still come from the organization's approved configuration and agreements.

Model separate obligations and milestones

Use one customer-obligation row per ticket and applicable cycle. Link internal milestone rows through the ticket and reviewed process version. Each milestone needs its own named owner, intended trigger, target duration or due time, calendar, actual completion event and evidence source.

Record the extraction cutoff and time zone. Inputs can include receipt, triage completion, specialist acceptance, investigation completion, fulfillment acceptance and resolution. Only include milestones the process actually records. An agent assignment is not evidence of acceptance unless that is the documented source meaning.

Use SLA attainment per account for the customer measurement and ticket handoff analysis for reconstructed queue intervals. This page concerns how those layers are compared in one operational review.

Check the intended sequence and clocks

Document which milestones are sequential, parallel or optional. An internal acceptance target measured from transfer differs from a customer resolution target measured from receipt. It is possible for the former to be met while the latter is missed.

Keep elapsed wall-clock intervals separately labeled from qualifying SLA or OLA business time. Apply the business-hours calculation rules when clocks use calendars or approved pauses. A transfer to another team is not itself permission to stop the customer clock.

If no approved internal target exists, report elapsed milestone timing descriptively. Do not invent an OLA or label a team noncompliant because its observed interval exceeds a convenient threshold.

DEMO: a handoff consumes the buffer

This synthetic case uses a shared continuous clock on October 6, 2026. The customer resolution target is four hours from 9:00 a.m., giving a 1:00 p.m. deadline. The internal milestones below are illustrative process targets, not recommended standards.

At investigation completion, the customer had 50 minutes remaining. Resolution took another 60 minutes. Triage and investigation met their internal targets, while acceptance did not and the customer deadline was passed.

The decision is to review the acceptance handoff and the fulfillment stage together. The table shows timing under the stated rules; it does not prove that the acceptance delay alone caused the missed customer target. A different path might still have exceeded four hours.

Review buffers as design assumptions

For a known customer deadline, display remaining customer time at each actual milestone. Compare that with a documented internal planning allowance, if one exists. Label the allowance as a process assumption rather than a contractual entitlement or a forecast.

Parallel work needs special care. Summing two simultaneous 60-minute activities produces 120 minutes of effort but may consume only 60 minutes of elapsed time. Preserve their overlapping intervals so the report does not fabricate a serial critical path.

Record exceptions and accountable next steps

Unknown acceptance dates, changed priorities, optional milestones and missing process versions should be visible. Route each evidence exception to a reviewer and retain the resolution. Excluding unresolved cases silently can make the handoff design appear better than its source records support.

For operational follow-through, record what the lead chose to review: trigger clarity, acceptance responsibility, process sequencing or available handling capacity. Separate that decision from any contractual interpretation or remedy calculation.

Scope the first comparison

Start with one request type and one documented process version. Check a small sample of event chains with both teams before aggregating percentages. Report the customer and internal results side by side, with their respective clocks.

Contact Covirage to discuss a bounded comparison using the existing event history. A useful output makes the customer deadline, internal evidence and unresolved handoffs understandable in the same review.