Breach Acceleration Trend(3.5.9)

The direction of change matters as much as the current state. A project with a 40% breach rate that improved from 60% last week is in a very different situation from a project with the same 40% rate that deteriorated from 20%. This visual shows the week-over-week change in the delivered-only breach rate for each project (each ticket measured against its resolved SLA policy target, or a MetaFrazo default until one is configured), so you can immediately distinguish improving teams from deteriorating ones. A week whose closures were all abandoned carries no rate and produces no direction signal; its abandoned count rides in the row.

What you can conclude

• Projects with a positive delta (rising breach rate) missed their targets on a larger share of delivered tickets than the week before.
• Projects with a negative delta (falling breach rate) missed their targets on a smaller share than the week before; the chart does not show why.
• Projects with near-zero delta are stable — whether that stability is at an acceptable level is a separate question.

How this chart works

Bar chart showing week-over-week change in breach rate per project. Positive bars (rising breach rate) are shown in red; negative bars (improving) in green. A reference line at zero separates improvement from deterioration. Each project's bar is its most recent week with a calculable change: a week needs at least five delivered tickets, and the week before it its own rate. A project with no such week in the range has no bar, and when no project qualifies the panel says so instead of drawing an empty axis.

The week in progress carries no change and is never drawn.