SSL Service Manager — Build Specification

Conventions & data context

IDs: requirements are numbered SSL-§.n per section; stable for backlog breakdown (one requirement ≈ one or a few dev tasks).
Terminology (G-001…): Incidents/tickets → Requests (urgent request = old incident); Service Agreement summary → Service User Profile; Allocated → Reserved; Task history → Tasks; tags → Keywords.
Data platform: SSL SM and the ILOS ARC share one database/service layer (M2). PNC sync rules from the manual remain until PNC migration completes; "PNC" below = the legacy control-centre platform. ARC = ILOS ARC.
Scope model (UM p.7 glossary): users, organisations, referrals, requests, stores, contacts carry a scope = Authority · Control Centre · Region · PNC/System. All queries/pages respect the logged-in user's scope (P-001). Roles/teams per G-009: every team belongs to a category (Responder / Administrative / Engineering …).
Statuses: Agreement = Pending · Active · Terminating · Terminated · (Redacted). ~~Suspended~~ removed (S-004). Request = Pending (in progress) · On hold · Closed · Cancelled (UM p.69) + priority Normal/Urgent. Task = Unscheduled · Scheduled · Accepted · In progress · Complete · Cancelled · On hold.

1 · Application shell wireframe ↗

ID	Requirement	Status	Source
SSL-1.1	Fixed top bar (48px, white, subtle shadow): ILOS logo left, global search centre-right, current time (HH:MM, live), user chip (name · organisation). Left menu (232px, white, 1px border): 7 sections with icons — Home, Requests, Referrals, Scheduling, Inventory, Reports, Administration — active item solid dark slate #334a54; collapsible to an icon rail via button and Ctrl/Cmd+\ ; "Powered by Tunstall" pinned at the bottom, never overlapped by the ticker.	CHANGED	Mark; G-004; X-002; reviews 10–11 Jun
SSL-1.2	Visual language: Tunstall palette (Guardian Navy text #001923, Assure Blue links/highlights #007689, dark slate primary buttons/active states #334a54, Safe Blue background, Steady Slate secondary, borders #c6ccd0), Roboto; cards rounded-10 with 1px border; pill badges; segmented icon tabs. Must read as "a better iteration of Mark's style".	CHANGED	Brand PDF; Mark; review 11 Jun
SSL-1.3	Breadcrumbs on every page; browser back never required (SaaS4 complaint).	NEW	X-002
SSL-1.4	Live ops ticker along the bottom (urgent requests, SLA breaches, stock events, roster gaps); infinite scroll, pause on hover, hide (✕) and restore ("Live feed" pill).	NEW	Mark; reviews
SSL-1.5	Keyboard: Ctrl/Cmd+K toggles search focus (second press / Escape closes); Ctrl/Cmd+\ toggles the menu; Escape closes popups; SaaS4 asks for shortcuts on key functions — extend per module.	NEW	Reviews 10–11 Jun; SaaS4
SSL-1.6	Non-obtrusive success toasts for create/save/complete actions; destructive or irreversible actions always confirm with reason where audited (do-not-redact, cancellations).	NEW	Review 11 Jun; Q-010, S-008
SSL-1.7	Authentication: SSO + MFA. Session timeout with auto-save of in-progress forms (drafts restored on return).	NEW	G-011 (SaaS4 top ask)
SSL-1.8b	Colour theme: System / Light / Dark selector in the top bar; "System" follows the OS preference live; choice persisted per user; all components (incl. logos, pills, focus states) theme-aware with AA contrast maintained in both themes.	NEW	Review 11 Jun
SSL-1.8	Notifications: in-app + push to the field app for assignment, SLA approaching/breach (RAG), incomplete-step prompts before leaving a flow.	NEW	X-001; SaaS4

2 · Global & advanced search wireframe ↗

ID	Requirement	Status	Source
SSL-2.1	Global search bar on every page; tokenised free text (multiple criteria separated by space, as the manual's contact search); matches: name, agreement no., customer reference, address/postcode, telephone, NHS/NI/SS-Ref/Social-Care numbers, PNC equipment id, serial. Typeahead results show name, DOB, agreement no., address, status; Enter → results page; click → profile.	CHANGED	G-005; UM p.50, 65
SSL-2.2	Advanced search page: default criteria = Service, Status (multi), Funder, Name, Agreement No., Address, Telephone, NHS, SS Ref, NI, Social Care no., PNC Equipment Id, Customer Reference (the old SM set) + a field picker over (almost) every agreement field incl. activated/terminated dates. Results: Agreement No., Customer Ref., Full Name, Address, Status, Open Requests; show/hide columns persisted per user.	CHANGED	UM p.50; G-005; P-002
SSL-2.3	Terminated agreements excluded from all live search unless dual-occupancy-linked to a live agreement (flagged "Terminated — linked"); they live in the archive (§13).	CHANGED	S-008
SSL-2.4	Old Status History / Service Level History pages are not rebuilt — status and status-change dates are searchable fields; "as of" queries ride on the audit layer.	REMOVED	S-014; P-002

3 · Service User Profile — identity & data model wireframe ↗

3.1 Information panel

ID	Requirement	Status	Source
SSL-3.1	Panel shows: service user (name, DOB, age), organisation + its logo (replaces client photograph and the manual's profile-image feature — image upload/task-photo carousel not built), agreement number, customer reference, source (referral link), scope, address, telephone, MOSA flag (mobile solution user), email, primary equipment (type + PNC equipment id + telephone), first contact, funder, dwelling colour + risk colour (labelled), keywords, linked agreements, active schedules.	CHANGED	UM p.61–63; S-002, S-003
SSL-3.2	Edit Service User form (pencil next to name/DOB), five groups exactly per the manual: Service User (Title, Forename, Middle Name, Surname, Known As, Telephone, Second Telephone, Mobile Solution User, Email, DOB, Date of Death); Additional Information (NHS, NI, Account, SS Ref, EPRN, SOS ID, Social Care Reference numbers); Keywords (1–10, from synced list); Service User Characteristics (Service Level, Commissioning, Person Type); Demographics (Gender, Religion, Birthplace, Language, Sexual Orientation, Ethnicity). Profile-image fields dropped (S-002).	BASE	UM p.55–56
SSL-3.3	Edit Address/Dwelling form, shared by all users at the dwelling: Address (Name/Number, Address, Town, Postcode + postcode lookup & what3words), Key Safe (Number, Location), Dwelling Characteristics ([Scope] 1–3, [Global] 1–3).	CHANGED	UM p.56–57; M4 (w3w)
SSL-3.4	Sync: user details synchronise with PNC/ARC (demographics excluded) once a PNC equipment ID exists; keyword/characteristic/demographic picklists are managed centrally and synced. One person store shared with the ARC.	BASE	UM p.56; S-011
SSL-3.5	Keyword colour model: PNC allows any colour, ILOS three — mapping rule on migration to be confirmed with Tunstall; coloured borders ideally kept.	TBD	G-008; M3

4 · Profile actions wireframe ↗

ID	Requirement	Status	Source
SSL-4.1	New request — see §7.2.	CHANGED	§7
SSL-4.2	Add user to agreement (manual "Quick Add"): dialog with Title, Forename, Middle Name, Surname, Known As, Telephone, Second Telephone ( mandatory). No validation — agreement already valid. Creates a linked agreement at the dwelling (pending if parent pending); activation date = today; dwelling equipment inherited, service-user equipment not; syncs to PNC once primary equipment configured.	BASE	UM p.57–58; S-007
SSL-4.3	Move service user (temporary move): search target agreement → move; original agreement stays live for return; details + contacts migrate; blocked across control centres or into dwellings with a pending request.	BASE	UM p.58
SSL-4.4	Print to PDF: prettified, print-dialog based (no server PDF licence); contains the profile summary; used for archives/coroner files.	CHANGED	S-020; M4
SSL-4.5	Log internal call: colleague picker (own organisation), Teams/Zoom, notes editable during the call, outcome (Completed / No answer / Declined / Failed); logged to Call History tagged Internal only on explicit "Log call"; discardable.	NEW	S-009; review 10 Jun
SSL-4.6	Decommission — see §13.1. Reactivate — §13.2.	CHANGED	S-005, S-006
SSL-4.7	Suspend / Resume: not built. (Manual p.61: present but unused; no billing effect.) If ever reintroduced it must drive billing.	REMOVED	S-004; M3
SSL-4.8	Action availability follows state (manual pattern: invalid actions greyed/disabled, e.g. Reactivate only ≤3 months post-decommission; Change requests only after completed installation).	BASE	UM p.61; Q-001

5 · Services wireframe ↗

ID	Requirement	Status	Source
SSL-5.1	Services grid on Summary: type, start, end, cost, payee/funder, status. Add Service: VAT applicable?, service type, start/end dates, account holder, service characteristics (capture amount/frequency; reportable). Multiple funders per agreement supported (e.g. one pays installation, another monitoring) — main account holder flagged.	BASE	UM p.62–63; S-021
SSL-5.2	End service = set end date; services auto-cancel at end date; agreements expiring within 7 days surfaced (report + profile badge).	CHANGED	UM p.63; S-021
SSL-5.3	Service Level editable on the agreement; can be calculated by a Service Support Plan / Connect assessment outcome (§10).	BASE	UM p.63
SSL-5.4	Service/funder data populates a finance data extract (consumable by finance systems for AR ledger/invoicing) — no invoice generation in SM.	BASE	UM p.62; SaaS4

6 · Contacts wireframe ↗

ID	Requirement	Status	Source
SSL-6.1	Grid: Order (call priority 1..n, re-orderable via "Change Priority"), Full Name, Telephone(s), Contact Type (relationship), categories. Categories: Primary, Emergency, Keyholder, Next of Kin (max one per service user), Power of Attorney (multiple) — checkboxes.	CHANGED	UM p.64–65; S-011; M4
SSL-6.2	Single create entry point: "＋ New contact" opens a dialog whose lookup field live-suggests existing people within the user's organisation (email match; manual allows ≤4 space-separated criteria); link existing (relation defined per service user; one person may serve many users with different relations) or create new. Mandatory: forename, surname, telephone, contact type; address mandatory only if "Address Known" ticked or contact is a funder. Phones added one-by-one with type (mobile/home/work) + icon.	CHANGED	UM p.65–66; S-011; reviews
SSL-6.3	Editing a shared contact updates them for all linked service users (warn). Removing a contact with no remaining relationships deletes the person record (no orphans — SaaS4 complaint).	BASE	UM p.66; SaaS4
SSL-6.4	Availability: per weekday up to two available windows (from–to), all-day-unavailable toggle, per-day "copy to remainder of week"; plus short-term unavailability (date range + operator-visible reason). Unavailable contacts grey out at call time; syncs to ARC.	NEW	S-011; M4 (PNC behaviour)
SSL-6.5	Contact Groups (created in PNC, migrated): read-only display; max one group per dwelling.	BASE	UM p.66–67
SSL-6.6	Contact email doubles as the future Friends & Family app login; app self-service edits are audited.	NEW	X-003; M4

7 · Requests wireframe ↗

7.1 Model & list

ID	Requirement	Status	Source
SSL-7.1	Types: Installation (created by referral validation; only via referral except reinstating after reactivation), Change (only after a completed installation), Decommission, Custom (new — covers what incidents/ad-hoc work needed). Urgent priority = old incident: responder notified via app, ARC colour-coded status timeline applies.	CHANGED	UM p.69–72; Q-001; S-013
SSL-7.2	Multiple open requests allowed per agreement and across linked agreements — the manual's single-pending-request lock (incl. across linked agreements, p.71) is removed; conflicting combinations left to user judgement, no system validation. Within one visit, multiple tasks batch into one request (M4 pattern).	CHANGED	Q-001; S-012; M4
SSL-7.3	Requests tab grid: request no., title, type, status, assigned/responsible, next-action-by; tasks nested under each request row; filter pills All / Live (default) / Closed; closed rows show their tasks + spawned follow-ons.	CHANGED	UM p.70; S-012; reviews
SSL-7.4	Follow-on request: any request can save an associated follow-on at creation/completion; parent may close while the follow-on stays open, auto-scheduled for its date.	NEW	S-012; M4
SSL-7.5	Request history: who was Assigned/Responsible and for how long, plus state changes — accessible from the request (folds into the audit layer).	BASE	UM p.71; S-014

7.2 Creation form (dynamic per type)

ID	Requirement	Status	Source
SSL-7.6	Shared fields: Title + Details (top), Priority (Normal/Urgent), Channel (Phone/WhatsApp/Form/Internal) TBD, Requester + phone TBD, Location (defaults to customer address; postcode lookup + what3words) TBD, follow-on selector, notes-at-creation (saved to request notes, manual behaviour).	CHANGED	UM p.72–73; Mark; reviews
SSL-7.7	Type-specific: Change → equipment affected (installed list), change kind (exchange/add/remove/battery), technical requirement TBD; Custom → task type (admin list) + description; Decommission → reason category + recovery date, hands off to §13.1; Installation → prescribed equipment + linked assessment.	CHANGED	Mark; Q-001/3; reviews
SSL-7.8	Default task set displayed and auto-added per type (admin-configured with SLA each); per-task "N/A — close immediately" tick; custom tasks addable. The manual's user-picked Next Action Date (date+time picker, min today) is replaced: next-action-by derives from task SLAs, read-only. "Cause" field dropped.	CHANGED	UM p.72–74; Q-003, Q-006
SSL-7.9	Assignment: select Responsible's user group first → Assigned person filtered to that group ∩ task-type role; Responsible = real manager (no ghost users); responsible's group stored. Save / Save&Edit / Cancel per manual.	CHANGED	UM p.72; Q-005; review

7.3 Detail, hold, links, completion, cancellation

ID	Requirement	Status	Source
SSL-7.10	Detail page: details panel (type, priority, channel, requester, assigned, responsible+group, next-action-by, resolution), Tasks, Stock items, Links, Notes (on tasks), creator/modifier metadata (read-only), cancel/complete controls.	CHANGED	UM p.74; wireframe
SSL-7.11	On hold: any request/task (manual: change requests only) — reason from admin list, who + when recorded; held items rendered amber; queryable system-wide (work queue filter).	CHANGED	UM p.73; Q-008
SSL-7.12	Links: URL or network path + display name attached to request (and per task); add/edit/remove (pencil/trash); no version control — link store only.	BASE	UM p.73; Q-009
SSL-7.13	Completion: request completes only when all tasks complete/cancelled and all task forms complete. On last-task completion the completing user is prompted "All tasks complete — close this request?" with optional free-form resolution; explicit "keep open" choice required otherwise. Per type: Installation → set commencement date (default today), activate agreement, populate allocated stock to linked agreements (blocked while picked-not-allocated stock outstanding); Change → apply stock changes to all linked agreements, de-allocated stock to chosen store; Decommission → set terminated-on + termination reason, status Terminated, de-allocate non-shared stock (see §13.1).	CHANGED	UM p.76–77; Q-002, Q-010
SSL-7.14	Cancellation: mandatory reason from admin-scoped list mapped to standard categories. Installation cancel → agreement terminated, service user + dwelling removed/archived in PNC (dwelling only if last resident). Change/Decommission cancel → all changes reversed to pre-request state. Stock auto-released to spare (partial release supported). Completed requests cannot be cancelled → raise a change request. End-to-end UX flow TBD with Tunstall.	CHANGED	UM p.77; Q-010/11

8 · Tasks wireframe ↗

ID	Requirement	Status	Source
SSL-8.1	Tasks are the work units of a request; a request cannot complete until every task is complete/cancelled; a task cannot complete until all its forms are complete. Form answers mapped to agreement fields update the domain on completion.	BASE	UM p.82
SSL-8.2	Task types + default sets + SLAs configured in Administration; each type maps to a role filtering assignees; SLA drives next-action windows and RAG colouring.	CHANGED	UM p.82; Q-003/5/6
SSL-8.3	Task grid under request: name, type, follow-on-visit flag, state, assigned, start/end; task detail: status, assignee, SLA, reserved stock, links, multiple notes (author + timestamp; reassignments append notes); actions Complete / Hold / Reassign. Add-task dialog: type (admin list, SLA shown read-only), description, responsible group → assignee, notify (app/app+SMS/none), optional note. Tasks creatable on linked agreements at creation.	CHANGED	UM p.82–87; Q-007; reviews
SSL-8.4	Task schedules (recurring: type, name, frequency, start/end, duration) remain — surfaced under Active Schedules; management moves to the Scheduling module. Editing locked once complete/cancelled.	BASE	UM p.99–104; C-001

9 · Stock on requests wireframe ↗

ID	Requirement	Status	Source
SSL-9.1	Pick stock (not on decommissions): search/select from stock available to the agreement's scope incl. pre-configured bundles; quantity by assessed risk; picked items shown on the request. SSL ordering: stock picked first → reserved; installer chosen after; if the installer's van (secondary store) lacks the item a stock transfer auto-raises. Unpick allowed except primary stock; allocated stock must be de-allocated first. Reservation prevents allocation conflicts.	CHANGED	UM p.77–79; Q-004
SSL-9.2	Status wording: picked stock = Reserved (replaces "Allocated" in the list); on request completion → Assigned to client. De-allocation selects a receiving store; if stock isn't in-store the user is told a transfer is required.	CHANGED	UM p.79; Q-007
SSL-9.3	Primary stock: one item flagged as the unit communicating with the control centre; requires generated PNC equipment ID (unique comms ID); shown in the information panel; cannot be unpicked.	BASE	UM p.77–78
SSL-9.4	Speech modules / hard-wired devices are not managed in SM (not picked). Shared dwelling equipment propagates to linked agreements on completion.	BASE	UM p.78, 76

10 · Assessments (Connect) wireframe ↗

ID	Requirement	Status	Source
SSL-10.1	Grid: name, assessed on/by, review on, status (Draft/Published). Templates admin-managed (Form Design); "New" offers template choice; "Copy" pre-populates from the latest assessment without altering it.	CHANGED	UM p.67–68; S-016
SSL-10.2	Draft → Publish lifecycle replaces sign-off: editable while draft; locked permanently on publish; later changes = new version. A linked request cannot complete until its assessment is published (manual: forms must be complete to complete tasks — same gate, stronger wording). Where assessments gate stock (configurable), a published assessment with future review date is required before allocation.	CHANGED	S-016; UM p.67, 76
SSL-10.3	Content = Connect assessment form: General info (name, date, assessor, identifier type + number); Wellbeing (9 Q), Supported Self-Management (12 Q), Connectedness (8 Q) — scored options exactly per the form workbook; initial subset (Q1–3, 10–12, 22–24) pre-populates the full form; per-group progress; free-text supplementary questions accept "not applicable".	CHANGED	Connect xlsm; review 11 Jun
SSL-10.4	Output: intensity score → Level 1 (1 call/quarter) · 2 (1 call/month) · 3 (1 call/week) · 4 (Refer to CRT) per the Intensity Logic (abuse/suicide/social/health scores); priorities as % of risk (Home, Falls, Connectedness, Digital Inclusion, SSM); live while editing; printable output per the workbook's printable sheet; can set Service Level (§5.3).	CHANGED	Connect xlsm
SSL-10.5	On publish: auto-create review request (+12 months default, TSA standard, configurable), linked to and viewable with the assessment; replaces the manual's mandatory review-date field. Auto-cancelled on decommission. Answers mapped to record fields update the domain through the audit trail.	CHANGED	S-016; UM p.67; M4

11 · Equipment tab wireframe ↗

ID	Requirement	Status	Source
SSL-11.1	List of main unit + peripherals assigned to user/agreement: item, serial, location, installed date, battery due; live by default, toggle to include decommissioned.	CHANGED	UM p.68; S-017
SSL-11.2	Device details view: model + number, serial, PNC equipment id, firmware, SIM/line, location, installed + installer, battery due, warranty, last test call, paired peripherals; raise-change-request action (equipment changes only via requests).	NEW	S-017; review 11 Jun
SSL-11.3	DMP integration: per-device click-through to status/performance (connectivity, mains, battery health, periodic-call success, firmware, SIM status, recent events); SIM suspend on scrap/loss is an Inventory-module action.	NEW	S-017; X-004

12 · Call History · Notes · Messages · Audit wireframe ↗

ID	Requirement	Status	Source
SSL-12.1	Call History: ARC call records via the service layer (most recent also packaged to the field app); internal Teams/Zoom entries tagged Internal with outcome + notes.	CHANGED	UM p.92; S-015, S-009
SSL-12.2	Notes: permanent + temporary (expiry); creator + timestamp + origin (PNC migration / ARC sync) displayed; create dialog shows expiry only for temporary; task notes excluded (live on tasks). No size limit (SaaS4); printable for FoI requests via §4.4.	CHANGED	S-019; SaaS4; review
SSL-12.3	Messages: profile-filtered view of the messages console; send to person or admin-defined team; channels app (free) / SMS; bulk-SMS limits & charging TBD (cost risk, M4).	CHANGED	S-019; M4
SSL-12.4	Audit: when · who · source (SM/ARC) · entity · action · from → to; filters entity/source/date-from; covers field changes, request/task lifecycle, assessment status, system events, internal calls, app self-service edits; replaces the History tab; powers "as of" reporting.	CHANGED	UM p.90–92; S-014; P-002

13 · Lifecycle: decommission, reactivate, archive, redaction wireframe ↗

ID	Requirement	Status	Source
SSL-13.1	Decommission (guided, 3 steps): (1) dual-occupancy guard — only the resident's own equipment recovered; shared equipment stays or partial-recovers, confirmed by the processor; (2) schedule recovery task + choose receiving store (→ quarantine flow, Inventory module); warn that all live requests incl. follow-ons auto-cancel; (3) reason (standard category) + do-not-redact flag. On completion: terminated-on + reason set, status Terminated, data archived, ARC/PNC record archived (date-of-death records remain in PNC struck through; last resident archives the dwelling; scheme dwellings void to an empty agreement ready for re-referral).	CHANGED	UM p.51–54, 76–77; S-005
SSL-13.2	Reactivate ≤ 3 months: restores data (ARC records re-created) and equipment if already removed — pending recovery tasks simply cancel (equipment never left); removed equipment auto-creates a restore/reinstall request (pick-stock flow). Redaction schedule cleared; status → Active.	CHANGED	S-006; notes; review
SSL-13.3	Terminated archive: separate page (never mixed with live); search by agreement no. (works post-redaction — the number survives, personal data shows redacted: the data-removal verification for subject access requests), name, status (All/Redacted/Do-not-redact), terminated from/to.	NEW	S-008; M4
SSL-13.4	Redaction: automatic nightly job after the admin-configured retention period (e.g. 36 months; typically 3–7 years), per agreement; one rule set across SM/ARC/migrated PNC. Do-not-redact flag stops it; changing the flag = confirmation dialog + mandatory reason, permission-controlled, audited; clearing after the due date redacts on the next nightly run (irreversible — warned).	CHANGED	UM (1am job, M4); S-008

14 · Work queue (replaces Workspace) wireframe ↗

ID	Requirement	Status	Source
SSL-14.1	Cross-client queue of open requests/tasks (manual Workspace grid: Agreement No., Customer Ref., Full Name, Address, Type, Status, Requested, Next Action, Assigned To, Priority + old filters Assigned, Responsible, Type, Status, Hold Reason, Address, Name, PNC Equipment Id, Agreement No., Customer Ref.). SSL: scopes Work list (org) / My work (mine); filters type/status (incl. On hold)/priority/SLA-RAG + field picker; row → request detail; service-user column → profile. Final home: Requests module; roster-reassignment workflows start here (Scheduling).	CHANGED	UM p.59–61; G-007; Q-008; C-002

15 · Non-functional requirements

ID	Requirement	Status	Source
SSL-15.1	Accessibility — WCAG 2.1 AA: programmatic label–control association on all forms; visible focus indicators (incl. custom tab/pill controls); 4.5:1 text contrast (incl. placeholders, pills per the brand contrast grid); landmarks (one main, nav, header); icon-only controls carry accessible names; toasts/status messages announced via aria-live; animations respect prefers-reduced-motion (ticker pauses); full keyboard operability incl. modals (focus trap, Escape).	NEW	Review 11 Jun; Brand PDF p.11
SSL-15.2	Responsive: full-width layouts (4K), icon-rail menu ≤900px, single-column forms ≤640px, horizontally scrollable tables on small screens; field-app parity handled by the mobile app, not responsive SM.	NEW	Review 10 Jun
SSL-15.3	Every entity change carries change-date + author (enables audit + "as of"); soft deletes only where redaction rules apply; agreement number immutable and survives redaction.	CHANGED	P-002; S-008/14
SSL-15.4	Permissions: scope-based visibility (Authority/CC/Region/System) on all queries; role-gated actions (flag changes, decommission, reactivate); per-user UI preferences (column choices) persisted.	BASE	UM p.7; P-001/2
SSL-15.5	Performance: SaaS complaint "slow, often fails" — target interactive <2s on lists ≤10k rows (server paging), search typeahead <300ms; offline tolerance is the field app's concern.	NEW	SaaS4

Round 11 — review changes (12 Jun 2026)

Build-affecting items from the 12 Jun review and critiques 05/06. Detailed change log lives in 02 §Round 11; wireframed in 03.

Req	Behaviour	Tag	Source
SSL-4.4	Cancel request: mandatory reason from the Administration cancellation-category list; reserved stock auto-released to spare (partial release supported); audited; completed requests cannot be cancelled.	NEW	Q-010/11; S-014
SSL-5.2	Service.type is a stored field (configured in Administration) alongside name/start/end/cost/payee; Add service and Extend service actions; expiring services (<7 days) surface here and feed the Reports expiry list with extend / let-lapse / call-funder actions.	CHANGED	S-021; P-008
SSL-3.1	Identity edit (audited) and added fields: Source→referral, Scope, MOSA flag, Email, First contact (name+number).	CHANGED	S-014
SSL-7.2	Requests grid: per-row quick actions (hold/history); urgent requests show the ARC colour-coded timeline (sent→accepted→en route+ETA→arrived→completed) on the profile.	CHANGED	S-013; Q-008
SSL-6.1	Contacts: call-order (priority 1..n) column + Change-priority control; phones are `tel:` links.	CHANGED	S-011
SSL-7.4	Terminated read-only view: non-redacted terminated agreements open read-only; redacted records open only to verify; Reactivate gated to the 3-month window.	CHANGED	S-008; S-006
SSL-10.1	Assessment editor is a full page (route), not a modal: group nav, per-group completion, autosave/resume; Publish stays a confirmation step.	CHANGED	S-016
SSL-12.x	UX system: interaction grammar (entities=pages, quick-context=side panels, confirmations=modals); 7-state pill tokens (01 §4); required-field marks + inline validation + error summary; typeahead keyboard model; New Request 2-step; scroll-lock behind popups; audit pagination.	NEW	06; AA 3.3.x

16 · Out of scope (other modules) & open questions

Referrals module: referral creation/validation, simplified referral (ex-Quick Agreement incl. its stock-reallocation semantics, UM p.54–55), duplicate-address matching (R-005), survey templates/public URLs.
Requests module: full request console, urgent-request (incident) console + SLA timeline, incident automation rules.
Scheduling module: planner, rosters, task scheduling/reassignment workflows, nearest-staff ranking (removed from request creation by review 10 Jun).
Inventory module: stores/types, transfers + receipt confirmation, stock take, quarantine/scrap flows, goods in, barcode mapping.
Reports module: consolidated reports (P-003…P-008) incl. finance extract surfacing.
Administration module: form design (assessment templates), task types + default sets + SLAs, cancellation/hold reasons, roles/teams/categories, retention periods.
Open questions (carried from 02): keyword colours (G-008); bulk-SMS policy; request-cancellation UX (Q-011); Mark-derived fields to confirm (channel, requester, location, title/details split, technical requirement); assessment draft window; review-period configurability; day-one audit scope; Health Events tab.

Backlog guidance. Each SSL-x.y row is sized to decompose into 1–5 development tasks (UI, API, data, sync, tests). Suggested epics: Shell & auth (§1) · Search (§2) · Profile data + PNC sync (§3) · Actions & lifecycle (§4, §13) · Services & finance extract (§5) · Contacts (§6) · Requests & tasks engine (§7–8) · Stock-on-requests (§9, with Inventory dependency) · Connect assessments (§10, with Form Design dependency) · Equipment + DMP (§11) · Cross-cutting tabs (§12) · Work queue (§14) · NFR hardening (§15).