Escalation Trigger Attribution(3.6.7)

A high escalation score can be driven by many different combinations of underlying signals. One project might be escalating primarily because of SLA breaches. Another might be driven by reopen surges. A third might have both. Understanding which signal is contributing most to the score tells you where to direct remediation effort.

What you can conclude

• If SLA breach rate dominates the score, capacity or prioritization is the problem — the team can't deliver within its commitments.
• If reopen surge dominates, quality is the problem — work is being closed prematurely and coming back.
• If stuck-issue growth dominates, workflow blockages are the issue — something is preventing issues from progressing.

How this chart works

Stacked bar chart showing weekly escalation score broken down by contributing signal per project: SLA breach rate, reopen surge, and stuck-issue growth. Each segment's size represents its proportional contribution to the total score. Select a project to see its weekly timeline; leave unfiltered to compare latest values across all projects.

Measured, zero, and not measured

The three contributions are measured independently, and any one of them can be unmeasurable in a week whose own signal fell below the volume floor for that signal. A segment reading 0.0 pts is a measurement: the signal was present and contributed nothing to the score that week. A contribution that could not be measured is not drawn at all, and its tooltip entry reads not measured this week — on a stacked bar an absent segment and a zero-height one are the same pixels, so the tooltip is where the two are told apart. A project for which none of the three signals could be measured is left off the axis entirely and named in a line beneath the chart, rather than drawn as a zero-height stack: a stack of no height under a project name reads as a project that contributed nothing, which is the opposite of what an unmeasured week means.

This chart reads each project's latest complete week and does not count the week in progress. Projects report in different weeks, so the chart names no single week.