Experience
Role-specific views for residents, staff, reviewers, executives, privacy, procurement, and delivery partners.

Prepared as an interactive experience model for the Housing Authority of the City of Alameda. This package translates the sample AI Use and Governance Policy into people, workflows, controls, evidence, and an implementation path.
The proposed experience connects public service delivery with governance. It starts with resident dignity, keeps trained staff in control, gives reviewers the evidence they need, and gives leadership a defensible operating record.
Role-specific views for residents, staff, reviewers, executives, privacy, procurement, and delivery partners.
Purpose, risk, privacy, accessibility, security, human authority, monitoring, and expiration built into the flow.
Source documents, reviewer actions, corrections, approvals, incidents, vendor changes, and reports remain connected.
Residents interact through accessible mobile and assisted channels. Approved services organize evidence. Staff resolve exceptions. Governance teams apply controls. Executives see outcomes. Every step writes to the same traceable operating record.


A clear, accessible way to submit evidence, correct mistakes, and understand what happens next.
Scenario: Submits income evidence and receives a human-reviewed request for one missing item.
A complete evidence package, policy references, exceptions, and authority to correct the record.
Scenario: Reviews extracted values, resolves a date mismatch, and records the final action.
Portfolio risk, service performance, adoption, cost, and unresolved exposure in one view.
Scenario: Drills from a monthly metric into its department, use case, vendor, and evidence.
Data boundaries, retention, purpose limitation, incident history, and defensible controls.
Scenario: Pauses a workflow after protected information appears in an unauthorized tool.
Vendor evidence, contract commitments, accessibility, subprocessors, and exit terms.
Scenario: Triggers reassessment when a vendor changes a material subprocessor.
Clear acceptance criteria, control ownership, implementation tasks, and proof of completion.
Scenario: Connects system delivery milestones to governance approval and staff readiness.
ResidentJordan RiveraA clear, accessible way to submit evidence, correct mistakes, and understand what happens next.
Scenario: Submits income evidence and receives a human-reviewed request for one missing item.
CaseworkerOmar DavisA complete evidence package, policy references, exceptions, and authority to correct the record.
Scenario: Reviews extracted values, resolves a date mismatch, and records the final action.
Executive sponsorElena RuizPortfolio risk, service performance, adoption, cost, and unresolved exposure in one view.
Scenario: Drills from a monthly metric into its department, use case, vendor, and evidence.
Privacy officerRavi PatelData boundaries, retention, purpose limitation, incident history, and defensible controls.
Scenario: Pauses a workflow after protected information appears in an unauthorized tool.
Procurement leadClaire WilsonVendor evidence, contract commitments, accessibility, subprocessors, and exit terms.
Scenario: Triggers reassessment when a vendor changes a material subprocessor.
Delivery partnerLuke FarrellClear acceptance criteria, control ownership, implementation tasks, and proof of completion.
Scenario: Connects system delivery milestones to governance approval and staff readiness.Use-case intake records purpose, owner, users, benefits, data, integrations, measures, and pilot dates.
Rules show every classification factor and route the correct human reviewers.
Records data type, retention, training terms, consent, boundaries, and incident response.
No autonomous eligibility action; corrections, approvals, pauses, and escalation stay with trained staff.
Every material action adds the actor, time, previous value, new value, reason, and source record.
Due diligence covers security, privacy, bias, accessibility, subprocessors, deletion, and exit terms.
Role-based completion, attestations, operational measures, exceptions, and annual review dates.
Use-case intake records purpose, owner, users, benefits, data, integrations, measures, and pilot dates.
Rules show every classification factor and route the correct human reviewers.
Records data type, retention, training terms, consent, boundaries, and incident response.
No autonomous eligibility action; corrections, approvals, pauses, and escalation stay with trained staff.
Every material action adds the actor, time, previous value, new value, reason, and source record.
Due diligence covers security, privacy, bias, accessibility, subprocessors, deletion, and exit terms.
Role-based completion, attestations, operational measures, exceptions, and annual review dates.
Confirm stakeholders, policies, systems, data boundaries, service measures, and accessibility needs.
Prototype resident, staff, review, and executive journeys using fictional scenarios and acceptance criteria.
Complete risk, privacy, security, records, procurement, and civil-rights reviews before connection.
Run a limited workflow with trained staff, monitored exceptions, correction procedures, and stop conditions.
Measure quality, burden, access, cost, disparity signals, incidents, and staff or resident feedback.
Document the human decision to expand, revise, pause, replace, or retire the use case.
Confirm stakeholders, policies, systems, data boundaries, service measures, and accessibility needs.
Prototype resident, staff, review, and executive journeys using fictional scenarios and acceptance criteria.
Complete risk, privacy, security, records, procurement, and civil-rights reviews before connection.
Run a limited workflow with trained staff, monitored exceptions, correction procedures, and stop conditions.
Measure quality, burden, access, cost, disparity signals, incidents, and staff or resident feedback.
Document the human decision to expand, revise, pause, replace, or retire the use case.
The California Control Center uses fictional connected records and resets after every session.