Independent public-interest evaluations of how systems respect dignity and support agency.
HXR Evaluation
Covina at Your Service: Reporting and Tracking Resident Problems
In one documented request, Covina at Your Service preserved the report, department, status, resolution date, and City response. More cases are needed to determine how reliably the app works.
- Evaluation ID
- UXR-EVAL-0003
- Status
- Open — gathering evidence
- Evidence
- 1 supporting incident
- Last updated
- August 13, 2026
Technical record details
- Canonical analytical title
- Covina at your Service: Resident Issue Reporting and Tracking
- Evaluation type
- Product or Application
- Benchmark posture
- Developing Evidence
- Blue Score readiness
- Developmental Data Only
- Reform / positive practice
- Positive Practice Observed
- Public revision
- 5
What changed in Public Revision 5
Public Revision 5 synchronizes the Evaluation article to the structured evidence record. The City-authored request directly shows persistent request state, Department: Streets, Closed status, an August 11 resolution date, and the City's remediation statement. Physical after-state and durability remain separate propositions.
What this evaluation covers
These canonical Entity references identify the products, systems, organizations, units, and other durable subjects covered by this Evaluation. Inclusion does not by itself establish responsibility or credit.
Public-eligible organizations, products, services, departments, and workflows in this Evaluation's scope. Inclusion identifies subject and provider context only; it does not by itself establish responsibility, internal ownership, fault, motive, or prevalence.
- Subject entities
- Covina at your Service Mobile App— Civic Reporting Application
GOGov Citizen Requests / 311 Platform— Citizen Request Management Platform
GOGov— Software Company / Platform Provider
City of Covina— Municipal Government
Evaluation scope
Resident-facing municipal issue discovery, documentation, submission, tracking, status, and routing through Covina at your Service.
Question being evaluated
How well does the app let residents report and track municipal issues while minimizing internal-organizational knowledge and repeated follow-up?
Current findings
What works well or deserves recognition
In this incident, the application visibly preserved a request record, department attribution, status, resolution date, and organization-authored closure message. These observed behaviors can reduce navigation, vigilance, and repeat-contact burden.
Mixed or conditional findings
One request demonstrates these behaviors in one deployment but does not establish repeated-use reliability, accessibility, edge-case handling, correction quality, or platform-wide performance. The screenshot's photo is not labeled as an intake or after-work image and is not used as outcome proof.
Evidence coverage and limits
One unique public Incident Case currently supports this Evaluation. Its City-authored screenshot directly demonstrates persistent request display, Department: Streets attribution, Closed status, an August 11 resolution date, and a City remediation statement. Official City documentation independently supports the app-routing and status-update model. The same incident also supports UXR-EVAL-0004 and UXR-EVAL-0005; this remains one occurrence analyzed through three lenses.
How the evidence connects
Request #13706 is the shared supporting incident for the Covina app, City, and Public Works Evaluations. Each Evaluation asks a different question of the same occurrence. The shared dependency is explicit so three analytical records cannot be mistaken for three independent incidents.
Supporting incidents
- UXR-2026-0812-0003: Sidewalk Trip Hazard Request #13706 Through Covina at your Service
Related Evaluations
- UXR-EVAL-0004: City of Covina Service Requests: Routing, Updates, and Completion
- UXR-EVAL-0005: City of Covina Public Works: Street and Sidewalk Request Response
Agency dimensions
Acceptance / benchmark test
Test repeated real requests from issue discovery through submission, persistent retrieval, meaningful status, notification, correction, responsible routing, and fallback.
Next observation or verification
Add other Covina requests as separate Incident Cases to test reliability, accessibility, correction paths, and repeat-use performance. Use request #13706 as direct organization-authored evidence for the administrative behaviors it displays, while keeping physical outcome and durability separate.