Overview & worklist

The Overview (the app’s home page) is the daily command center. It answers, in one screen: how many files are open, whose court each one is in, and which ones are overdue.

Header stats

A row of stat cards summarizes the whole portfolio, computed from GET /api/metrics:

Stat	Meaning
Open estimates	Count of estimates not yet done, with total RCV in flight.
Our court	Estimates where the ball is with us — files that need an estimator’s action.
Carrier court	Estimates we’re waiting on the carrier for.
Overdue	Estimates past their window, plus overdue follow-ups (warning-highlighted).
Avg rounds / Settled	Average revision rounds per completed file, and how many settled this cycle.

Triage table — “who owes the next move”

The left panel lists every estimate, sorted by urgency: overdue → due → warm → fresh → done, and within a state by percentage of budget consumed. Each row shows the estimate, carrier, status pill, ball pill, the active SLA/desk-audit clock (a state pill + progress meter + label), and RCV. Click any row to open its deal detail page.

The first page renders server-side (zero flash); the rest paginate client-side at 25 rows per page.

Revision lifecycle flow

Below the triage table, a six-step diagram walks the loop — Draft → Submitted → Desk audit → Revision → Respond → Settled — showing the state, the action, and which way the ball moves at each step. It’s the picture of the ball-in-court model.

Carrier turnaround

The right panel lists each carrier’s desk-audit facts — portal, O&P cap, typical audit days, and open/total counts — so you can gauge which carriers are running slow.

Navigation

The left sidebar groups the app into:

• Operations — Overview, Estimates, Follow-ups, Inbox, Audit log.
• Reference — Carriers, Estimators.
• Configuration — Overview, App registrations, Email & domains, SLA & phases, AI & prompts.

The top bar carries a breadcrumb, a global search box (semantic — see Search), and the Follow-ups link shows an overdue count pill when any are past due.