Site Revenue Growth — Quality & Safety Trigger Monitor
% growth
Trigger Detail by Site
Site
Setting
Change $
Change %
Trigger 1
Investigated
Row shaded = Trigger 1 firedTick Investigated once the Quality team has reviewed the site — that opens the Trigger 2 watch.Click a row to open that site on the Revenue Trend tab.
Trigger 2 — Escalation Watch
After a Trigger 1 investigation is marked complete, the site stays on watch for a
fixed number of months. If any single month inside that watch grows more than the month-over-month
threshold, Trigger 2 fires and the site escalates.
months
% month over month
Site
Trigger 1 Month
3-Mo Growth
Investigated
Watch Window
Month-over-Month Inside Watch
Trigger 2
Month above the threshold — Trigger 2Month inside watch, below thresholdWatch month not yet posted
Paste this into engine/investigations.json under
"log" and re-run the build so the marks survive the next refresh.
Trigger History — Repeat Sites
Every evaluated month since the first month with two complete 3-month blocks.
Consecutive triggers matter more than a single spike.
Trigger firedNo triggerNo / insufficient revenue
Revenue Trend
Monthly and Rolling 3-Month Revenue
Month
Monthly Revenue
Change vs Prior Month
3-Month Window
3-Month Revenue
Prior 3-Month Window
Prior 3-Month Revenue
Change
Change %
Trigger
3-Month Revenue = that month plus the prior 2 months.Prior 3-Month Window = the 3 months immediately before it — back-to-back blocks, no overlap.
