Spike Alert Log

The charts show patterns. This table shows the events. Every statistically significant spike is logged here with its date, project, volume, baseline at the time, and severity classification — so you have a complete audit trail of when your backlog experienced abnormal pressure.

For compliance purposes, this log provides evidence of when demand anomalies occurred and how they were classified — useful for post-incident reviews and capacity planning retrospectives.

What you can conclude

• Critical alerts (spikes exceeding 3× the baseline) represent the most significant demand events — each warrants a post-incident review.
• High alerts (2–3× baseline) are significant but recoverable — useful for pattern analysis over time.
• A log with no entries in a period indicates stable, predictable backlog inflow — a positive governance signal.

How this chart works

Timestamped audit table of all statistically significant spike events. Columns: spike date, project, inflow volume, baseline mean, spike ratio, alert tier (High = 2–3σ, Critical = >3σ).