01 · Drift queue
Aggregate drift review
Weekly scan flags scopes (jobCategory × specTier × postcodeDistrict) where community ranges have drifted beyond threshold. Approve to promote new baseline, reject to flag bad submissions, or extend watch by 7 days. Every action requires a reviewer note of 10+ characters.
02 · Submission triage
Cost-submission review queue
Per-submission outlier / flagged queue with approve / reject / request-info actions. Each row exposes scope, cost, CCI variance, and the validation flags that put it in the queue. Reviewer note ≥10 chars required on every action.
03 · CCI engagement
Demand-side CCI tile row
How users interact with CCI estimates on the demand side — viewed, expanded, anchored a budget on, or flagged as off. The cockpit's CCI tab was admin-only before Sprint 2; this row closes the loop.
04 · Maintenance cycle
Automated refresh & re-aggregation
The scheduled crons that keep CCI current: ONS inflation indices, community re-aggregation, the weekly drift scan, and the monthly PropertyData refresh. Each card shows the next run, whether the previous run completed its full pass (not just that it fired), and the API calls it made.
05 · Data coverage
Dataset completeness & cache health
Coverage across every CCI statistic — atomic tasks, material costs per tier, era factors, house-type modifiers, trade rates, composite jobs — and the freshness of the computed cost cache. Gaps here are informational: some trade/era and category/house-type pairs legitimately don't exist.
06 · ONS inflation review
Flagged inflation deltas
When an ONS series moves beyond its safety threshold it is held here instead of auto-applied, in case the jump is a data glitch. Approve applies the published value to the CCI baseline (and refreshes cost estimates); reject keeps the current baseline. Both need a reviewer note.