Skip to main content

SLA First-Response Breach Rate

Share of PSOM tickets that missed the time-to-first-response SLA.

The proportion of PSOM tickets that missed the “Time to first response” SLA, based on the latest snapshot.

This metric is useful for monitoring whether the team is meeting initial response commitments. Only tickets where the SLA clock started are included; tickets with no clock (e.g., non-service-request issue types or tickets created before the SLA scheme was configured) are excluded.

Calculation

From jira.psom_sla, filter to the most recent date partition, to sla = 'first_response', and to rows where breached is not null (i.e., the clock started). Divide the count of rows where breached is true by the total count of those rows.

SELECT
    COUNT(*) AS total_sla_tickets,
    SUM(CASE WHEN breached THEN 1 ELSE 0 END) AS breached_count,
    CAST(SUM(CASE WHEN breached THEN 1 ELSE 0 END) AS DOUBLE)
        / NULLIF(COUNT(*), 0) AS breach_rate
FROM jira.psom_sla
WHERE date = (SELECT MAX(date) FROM jira.psom_sla)
  AND sla = 'first_response'
  AND breached IS NOT NULL;
psom_sla <- tbl(con, in_schema("jira", "psom_sla"))
latest_date <- psom_sla |> summarise(d = max(date, na.rm = TRUE)) |> pull(d)

psom_sla |>
  filter(
    as.Date(date) == as.Date(latest_date),
    sla == "first_response",
    !is.na(breached)
  ) |>
  summarise(
    total_sla_tickets = n(),
    breached_count    = sum(as.integer(breached), na.rm = TRUE),
    breach_rate       = sum(as.integer(breached), na.rm = TRUE) / as.double(n())
  )

Interpretation notes

The rate is a proportion between 0 and 1. Tickets whose clock never started (null breached) are excluded from both numerator and denominator. Check total_sla_tickets to understand the sample size underlying the rate.

A breach means the ticket missed its own goal, which is set per ticket and counted in working hours (09:00 to 17:00). A ticket that is still waiting for a first response and is inside its goal is recorded as not breached (false), the same as a ticket that met the SLA. The rate on a live snapshot is therefore a lower bound: some of those open tickets may still breach before they are answered. It is most meaningful once the snapshot’s tickets are largely resolved.

Alternative names

  • first response SLA breach rate
  • time to first response SLA compliance
  • first-response SLA failure rate