Escalation Run Duration(3.6.9)

A project that hits the escalation threshold for one week may be experiencing a temporary spike. A project that has been at or above the threshold for six consecutive weeks has a structural problem that has not been addressed. This visual shows how many consecutive weeks each project has spent above the escalation threshold — making a project that sits above it for many weeks running impossible to overlook.

What you can conclude

• Projects with long escalation durations (4+ weeks) require a structured remediation plan, not just a quick fix — the problem is embedded.
• A project that recently entered escalation and has been there for only 1–2 weeks may respond to targeted intervention before it becomes chronic.
• A project with zero escalation weeks in the period had no scored week above the escalation threshold in it.

How this chart works

Horizontal bar chart ranking projects by total consecutive weeks above the escalation threshold. Use the date filter to set the observation period.

Runs still in progress, and what the date range selects

A run whose most recent week is the current, still-filling week has no length yet — a week that is half over cannot be counted as a week the project spent above the threshold — so that run is counted but not plotted, and the number of such runs is stated in a line beneath the chart. Drawing it would put a bar of no length under a project that is escalating right now, in the calmest color the chart uses.

The date range selects the runs that overlap the period rather than the runs that fit inside it, so a run longer than the window is visible in the window. It previously selected only runs that both started and ended within the period, which hid exactly the long runs this panel exists to show: a twelve-week run could not appear in any thirty-day window it spanned.