Skip to main content

Admin Delivery Plan

This is the ordered admin-app build queue.

Use it together with docs/planning/master-roadmap.md.

Stage 0: Admin Foundations​

  • confirm admin V1 route map
  • define lead statuses and operator workflow states
  • define recommendation review requirements inside admin
  • define installer tier and status model
  • define region and postcode ownership model
  • define routing assignment states
  • define follow-up statuses and outcomes

Stage 1: Dashboard And Lead Foundations​

  • define lead and recommendation backend boundaries
  • define dashboard metric definitions
  • replace placeholder dashboard metrics with real data
  • build leads list route
  • build lead detail route
  • show assessment answers in lead detail
  • show recommendation output in lead detail

Stage 2: Installer And Region Operations​

  • define installer backend boundary
  • define region backend boundary
  • build installers list
  • build installer detail
  • build regions list
  • build region detail

Stage 3: Routing Workflow​

  • define routing backend boundary
  • build routing controls in lead detail
  • build compare-quotes assignment flow
  • build recommended-installer assignment flow
  • show assignment history and internal notes

Stage 4: Follow-Ups​

  • define follow-up backend boundary
  • build follow-up list
  • build follow-up detail/actions
  • capture satisfaction outcomes and issues

Stage 5: Reporting And Settings​

  • build basic analytics/reporting screens
  • harden settings area
  • tighten operator permissions assumptions

Dependency Rule​

Do not build admin CRUD screens before the underlying status model and route map are defined.

Working Rule​

Do not invent admin routes casually.

New admin routes should come from real operational modules:

  • /leads
  • /installers
  • /regions
  • /follow-ups
  • /analytics
  • /settings