Production variance

Actual against expected production, worst first. Sites that cannot be scored appear at the top, not the bottom. Data source: MOCK (shape of public.pulse_monitoring_variance(), docs/sql/002_public_monitoring_bridge.sql — unapplied).

Site-months
13
Needs attention
10

4 critical · 3 under · 3 unscored

Named by project
46%

7 sites with production and no project

Scoreable
77%

3 with no usable expectation

7 of 13 site-months cannot be attributed to a project. Those sites have production readings but no scoop_id mapping, so nothing here can name the customer, dealer or investor group behind them. That is a source-data gap, not a filter — see docs/handoff/warehouse-facts-verified-2026-07-31.md §4.

Production variance for 2026-07, worst first
SiteProjectActualExpectedOf expectedStatus
FLIP-2005(no project mapped)405 kWh0 kWhNot computable
FLIP-2006(no project mapped)289 kWhNot computable
FLIP-2007(no project mapped)764 kWhNot computable
FLIP-1006PLS-00160 kWh910 kWh0%Critical
FLIP-2001(no project mapped)46 kWh855 kWh5%Critical
FLIP-1001PLS-0001118 kWh980 kWh12%Critical
FLIP-2004(no project mapped)332 kWh812 kWh41%Critical
FLIP-1005PLS-0014780 kWh1,238 kWh63%Underproducing
FLIP-1002PLS-0004513 kWh723 kWh71%Underproducing
FLIP-1003PLS-0006869 kWh1,034 kWh84%Underproducing
FLIP-2002(no project mapped)612 kWh700 kWh87%On track
FLIP-2003(no project mapped)902 kWh889 kWh101%On track
FLIP-1004PLS-00101,143 kWh1,120 kWh102%On track

Band thresholds are a proposal, not a decided convention: critical below 50% of expected, underproducing below 85%. Nobody has said what counts as needing attention — they live in one place (src/lib/variance.ts) so the answer is a one-line change.