iDARMS UAT & User Guidelines

Integrated Digital Addressing and Revenue Management System
Phase 3 – Segment 1

This controlled documentation supports business-led User Acceptance Testing for the iDARMS release candidate across infrastructure, web portals, mobile apps, partner workflows, and end-to-end revenue-management journeys.

Document status

Version: 1.0
Status: Ready for UAT execution
Classification: Controlled UAT Copy
Credentials: Not included

Coverage

Area	Test series	Cases
System Infrastructure Setup	INF	12
Frontend Admin Panel	ADM	20
Ratepayer Portal	RPP	16
Ratepayer Apps — iOS and Android	RPM	16
Agent Apps	AGT	18
LVD Portal	LVD	12
End-to-End Journeys	E2E	10
Back Office menu destinations	BO	90
Back Office sidebar/access controls	BO-NAV	8
Ratepayer Portal Authentication	RPP-AUTH	16
iDARMS Website	WEB	24
Total		242

How to use this site

1. Review the UAT scope, roles, entry criteria, environment, and evidence rules.
2. Validate the Back Office sidebar, routes, and permission visibility.
3. Validate the iDARMS Website menu pages, visual baselines, and Lighthouse rings.
4. Assign acceptance-test pages to the appropriate business testers.
5. Execute each test against the recorded release/build and controlled data.
6. Record result, actual outcome, evidence, and defect reference.
7. Retest fixes and execute affected regression cases.
8. Complete the final acceptance decision and sign-off.

Result values

Result	Meaning
PASS	Expected business outcome achieved with acceptable evidence.
FAIL	Actual outcome materially differs from the expected result.
BLOCKED	Execution cannot continue because a prerequisite or dependency is unavailable.
PASS	Case has not yet been executed.
N/A	Case is not applicable and includes an approved justification.