Barranca Signal-Timing Request Was Closed Without a Verified Corridor Outcome
Human Experience ReformShare
Human Experience Reform public Evaluation
Stable Evaluation ID: UXR-EVAL-0010
Barranca Avenue I-10 to I-210: North-South Signal Progression and Travel Continuity
Administrative referral and closure are not the same as a verified traffic-engineering outcome.
Current status
Evidence posture
Needs More Evidence. One City request record and one contributor's later corridor experience currently support the question.
Administrative record
The City documented Engineering attribution, referral to Bear Electric, closure, and dates.
Operational outcome
Downstream receipt, analysis, action, and measurable travel improvement remain unverified.
Reform
No verified signal-timing or closed-loop response reform is currently recorded.
In plain English
A City of Covina record says a traffic-calming and congestion request was assigned to Engineering, reported to Bear Electric on March 12, 2025, and later marked Closed with a March 24 resolution date. In August 2026, the contributor reported that north-south travel on Barranca still involved stopping at many red lights and did not know whether Bear Electric received or acted on the referral.
Related Incident: Barranca Traffic Signal Timing Request With City-Reported Bear Electric Referral.
Why this matters
A resident-facing request system should preserve more than “we sent it somewhere” and “closed.” For signal timing, the meaningful result is whether the responsible entity received the request, evaluated the corridor under relevant conditions, acted or explained why not, communicated the disposition, and left a correction path if the reported condition remained.
Evidence and limits
Supported now
- The City-authored record identifies Traffic Calming/congestion and Department Engineering.
- It says the request was reported to Bear Electric on March 12, 2025.
- It later shows Closed status and a March 24, 2025 resolution date.
- The contributor reports that a repeated-stop north-south pattern remained apparent in August 2026.
Not established
- Whether Bear Electric received, analyzed, or acted on the referral.
- Which organization controlled each relevant signal.
- What timing plan, safety constraints, pedestrian phases, demand patterns, or time-of-day conditions applied.
- A controlled before/after measure, population prevalence, or a finding that every signal was mistimed.
Current findings
Positive finding
The City preserved an organization-authored administrative history with category, department, referral, closure, and dates.
Negative finding
The current record does not close the loop from referral to downstream receipt, analysis, action, or measurable corridor result before the request was marked Closed.
Reform requested
Use a closed-loop signal-timing request pathway. Record the responsible signal owner or contractor, downstream receipt, analysis performed, action taken or supported no-action reason, and resident-facing disposition. Distinguish administrative referral from verified outcome. For corridor questions, define the directional and time-of-day objective, collect appropriate travel-time or progression data, document legitimate constraints, communicate the result, and provide a correction or reopening path.
What would count as a real fix?
What could change HXR's view?
- Downstream receipt, work order, analysis, or disposition from Bear Electric or the responsible signal owner.
- Authoritative signal ownership and jurisdiction records.
- Comparable northbound and southbound travel or progression data across defined time windows.
- A supported explanation showing why no timing change was appropriate.
- A current correction/reopen pathway or verified corridor improvement.
Supported corrections, legitimate constraints, positive outcomes, and verified reforms are appended and credited.
Responsible organizations: respond or add evidence
The City of Covina, Bear Electric, or another authority-verified signal owner may correct attribution, provide downstream evidence, explain constraints, document a current process, propose reform, or request verification. Responding does not require an admission.
Start a private organization responseHave you encountered this corridor pattern?
Useful context includes direction, approximate date and time window, number or pattern of stops, unusual traffic, construction, pedestrian or emergency conditions, any request/response record, and whether conditions changed over time. Do not expose license plates, precise private routines, or unnecessary identifying trip details.
Privacy: the public corridor and organization-authored request facts may be discussed without identifying the contributor.