Home / Dashboard – Functional Specification v0.9

The old SM has two separate landing artefacts: a Home page of coloured launcher tiles (one per section) and a Dashboard page of eight KPI tiles plus two Highcharts time-series graphs (Service Agreement Activity; Stock Items Expiring Within a Month). In the SSL Service Manager these collapse into a single operational landing view (G-001):

Design principle. This is a shift-operations view for supervisors and ARC/dispatch staff – "what is happening right now and what needs my attention", not management reporting. Every number is live, every number is a drill-through into the list it counts. No charts.

• Default route. Opening the app, or clicking Home in the left menu, lands on the dashboard (#dashboard). There is no intermediate tile page (D-008).
• Greeting + context line. "Good morning, Petra" with the weekday + date and live clock (shell convention), and an "as of" timestamp showing data freshness next to the refresh control (§6).
• Audience & permissions. Content is scoped to what the signed-in user may see (Authority / CC / Region / System, SSL-15.4). A supervisor sees their teams by default; a region manager can widen the scope (§6). Operators themselves (responders/installers) primarily use the field app – the dashboard is the office/ARC view.
• Layout. Full-viewport width (4K-friendly); the stat band reflows to fewer columns ≤1100px and to a single column ≤640px; the work-queue preview scrolls horizontally on small screens (SSL-15.2).

A band of compact stat tiles – Mark's stat-tile component, Tunstall palette, status-pill colour language (01 §4). Each tile is a single number with a label and a drill action; SLA-bearing tiles carry a RAG accent (X-001). No "More info" footer link (the whole tile is the control); no graphs inside tiles.

Change (Ivan, 10 Jul 2026): every tile now navigates for real in the wireframe - Requests due/overdue and Active jobs open the Work queue (03 #queue; the Due+Overdue / In-progress presets are applied in the build, not reachable by hash), Avg. time to accept opens the Request Report (24 #request), Tasks this shift opens the Roster (18 #roster), Unscheduled tasks opens Daily Planning (18 #planning). The two responder cards keep their in-page #respdetail behaviour. The "What's due next" rows open the request detail (14 #request).

Clicking the On-shift responders or Agents available tile opens a side panel (interaction grammar: quick context = side panel, 01 §4). This is the agreed replacement for Mark's rejected "staff online" widget (D-004) – the information is reachable on demand, not occupying the landing permanently.

A compact, read-mostly slice of the cross-client Work queue (SSL-14) – "what's due next" – so the supervisor can triage without leaving Home. It is a preview: the full queue with all filters lives in the Requests module.

• Columns: Service user, Type, Status pill, Next action by (SLA-RAG), Assigned to, Priority. Rows sorted by SLA urgency (overdue first).
• Scope toggle Team work / My work mirrors the Work queue's scopes (SSL-14.1).
• Row → request detail; the service-user cell → Service User Profile (S-001).
• "View all in Requests" opens the full console; "Open in Scheduling" opens the planner for unscheduled items.
• Urgent (incident) rows show the ARC mini-timeline state inline (sent → accepted → en route → arrived), consistent with the profile (S-013, SSL-7.2).

The operationally useful half of the old KPI grid is retained as a compact drill list (counts, no graphs). Each row is a saved filter into another module – these answer "what's stacking up".

Explicitly carried so coverage is complete and the rejections are traceable. Greyed equivalents in the wireframe name the decision.

Every screen group in the old SM 1 Home and 2 Dashboard folders, accounted for. Counts verified against the screenshot files.

• "Calls this shift" (D-007) – confirm the exact definition against the roster model (tasks assigned to agents on shift vs. calls handled).
• Vehicle location (D-005) – which vehicle-tracking system feeds responder location, and how is it obtained?
• Default scope per role – should a supervisor default to "My teams" and a region manager to their region, or always "My teams"? (H-6.1)
• Stat band membership – confirm the eight tiles are the right operational set; is "Services expiring" a tile or only a pending-by-type row?
• Shift boundaries – how is "this shift" delimited for the average-time-to-accept and calls-this-shift KPIs (rolling 8h, roster shift, calendar day)?
• Weather (D-004) – confirm it stays out, or returns as an opt-in tile later.