Where we are, and what to build next

Six packages are now delivered: the global shell, the Service User Profile (Phase 1), the Home / Dashboard (Phase 2), the Requests console (Phase 3), Referrals (Phase 4) and Scheduling (Phase 5). The remaining grid now also folds in the rest of Mark's design – Inventory & stock, Live Service (team location & vehicle tracking), the Responder / field app, and team creation (installers, assessors) inside Administration. Team shift scheduling already shipped with Phase 5 (Roster). Each remaining module is scored on four axes so we can pick the next package deliberately – not just by appetite. Higher build effort means more work; higher decision-readiness, dependency pull and customer value all argue for doing it sooner.

Build effort Decision-readiness Dependency pull Customer value

Order modules by

Delivered Phases 0–7 complete

▤ Global shell & foundations

Done

Phase 0 – left menu, top bar, theming, status-pill tokens, ticker, favicons.

Covers: 7-section nav, dark/light/system theme, search, toasts, live ticker, doc cross-linking.

01-global-shell00-decisions-register

👤 Service User Profile

Done

Phase 1 – Service Agreements → profile landing view (rounds 11–14).

Covers: identity, services, equipment, assessments, requests tab, activity/audit timeline, reactivate / terminate / cancel flows, edit details.

02-spec03-wireframes04-build

🏠 Home / Dashboard

Done

Phase 2 – operational landing dashboard (D-001…D-009).

Covers: stats-only KPIs (on-shift responders, requests open/due, average time to accept, active jobs), work-queue preview, pending-by-type drill, refresh control. No graphs / weather / alerts (D-004/D-006).

11-spec12-wireframes

🗒 Requests console

Done

Phase 3 – create / triage / assign / close service requests (G-001, Q-001…Q-011).

Covers: data-driven cross-client list (count-tile filters, scope, search highlight, pagination, sortable columns), 2-step create with dynamic task sets, SLA-derived dates, assign / on-hold / cancel, urgent ARC timeline.

13-spec14-wireframes

📥 Referrals

Done

Phase 4 – intake → conversion to an agreement (R-001…R-007, G-006, P-004).

Covers: referral console, lifecycle detail (received → in review → accepted → converted / rejected / on hold), duplicate detection at creation, templates & public surveys, convert / reject / hold / assign flows.

15-spec16-wireframes

📅 Scheduling

Done

Phase 5 – getting tasks onto the right person's day (C-001…C-004, Q-015).

Covers: Bookings queue (task-type filter C-003, recurring tasks, names & addresses), Daily Planning dispatcher board (responder lanes + route map + auto-schedule by priority & travel), Roster (shift patterns + sick/holiday/training, roster-change re-home C-002), day-aware schedule/reassign/reschedule flows, and the outfield accept/reject app.

17-spec18-wireframes

📦 Inventory & stock

Done

Inventory phase – stock & custody across all stores; Goods In → transfer → install → return → refurb / scrap (I-001…I-011).

Covers: Stock by location (store types incl. vans, custody lifecycle), Device catalogue (all products regardless of level, multi part-number), Goods In (scan-to-populate, multiple primary stores, bulk), Transfers + receipt confirmation, Returns & quarantine (clean / check / reprogram, decommissioned-until-serviced), Scrap store (purge + 6/12-month value), Stock take (matched / missing / overstock), and the barcode/QR scan seam.

22-spec22-wireframes

📊 Reports

Done

Reports phase – 21 old operational reports consolidated into 5 merged reports + 1 planning view on a shared viewer platform (P-001…P-008).

Covers: Report catalogue (grouped predefined searches + custom reports), shared viewer (P-001 scoping, date ranges, “as of” search, column show/hide with per-user memory, CSV export), Request / Referral / Service-agreements / Stock / Audit reports, Assessment next-review (RAG + review-task search), battery-replacement request generation from the Stock report, and Scheduled reports (emailed link, never content).

24-spec24-wireframes

Remaining modules Scored on complexity

⚙ Administration

Foundation

Teams (installers, assessors), user groups, task types, SLAs, assessment templates, roles.

Complexity: High

Build effort4

Decision-ready3

Dependency pull5

Customer value3

Why early: Requests, Scheduling and the field app all pull teams (installers / assessors / responders), task types, SLAs and user-group → assignee lists from here (Q-003/Q-005/Q-006). The current admin stub (file 17) covers only keywords, referral sources and ticker messages – this is the full module. Building it out first unblocks everything downstream.

Teams: installers / assessorsUser groupsTask typesSLA matrixAssessment templatesRoles & permissions

🛰 Live Service & team location

Remaining

Live map / wallboard – staff & vehicle positions, availability, en route.

Complexity: Medium-High

Build effort4

Decision-ready2

Dependency pull2

Customer value4

Where vehicle tracking & team location live. Mark's Live Service / Tech-Ops pages plot staff, response and tech-ops units on a Leaflet map with online / available / not-answered counts and en-route state – a control-room wallboard. Best once field devices emit the live GPS / availability it visualises; thin without them.

Live mapTeam locationVehicle trackingAvailabilityEn routeWallboard

Recommended sequence

#	Module	Complexity	Rationale for the slot
1	Administration	High	Foundational. Requests, Scheduling and the field app all draw teams (installers / assessors / responders), task types, SLAs and user-group lists from here; building it out next hardens the config the live modules already consume.
2	Live Service & team location	Med-High	The control-room wallboard – team location and vehicle tracking on a live map. Reads best once field devices feed it live positions and availability.

Scores are 1–5 planning estimates from the project record (meeting decisions, SaaS4 scores, the build spec, Mark's design and the round 11–14 corrections), not measured values – adjust as we learn. "Decision-readiness" = how much is already agreed vs. needs a fresh decisions round. Team shift scheduling from Mark's design already shipped in Phase 5 (Scheduling → Roster: shift / off / sick / holiday / training, Teams & 365 sync, roster-change re-home), so it sits under Delivered, not here. The SM v1 (TSP) → ILOS SM v2 database migration is tracked separately (see Data Migration Plan) and is deliberately out of this build-sequence view.

SSL Service Manager · planning sitemap · updated 3 July 2026 · Phases 0–7 delivered (shell, Service User Profile, Home/Dashboard, Requests, Referrals, Scheduling, Inventory & stock, Reports) · remaining grid = the rest of Mark's design (Live Service & team location, Administration, Reports) · pairs with 00–24 and PROJECT-INSTRUCTIONS §10 roadmap.