In this guide
“The light is broken” can refer to a traffic signal, a pedestrian indication, or a streetlight. It can also conceal whether the observer saw a dark signal, a damaged component, or a timing concern. Phoenix’s public reporting system treats those questions differently. A useful report identifies the visible issue and its location without requiring the observer to diagnose a controller or electrical fault.
Observe only from a safe, lawful position. Do not stand in traffic, approach damaged equipment, open a cabinet, or direct road users. City employment alone does not authorize signal work or traffic control. For immediate danger, use the appropriate emergency process rather than delaying to build a detailed report.
Use the urgent route when the City identifies one
The Phoenix traffic-signal reporting page distinguishes non-emergency online submissions from urgent items. It directs reports of dark or flashing signals and several damaged or nonworking components to its 24-hour line, 602-262-6021. The same page warns that online submissions can take up to seven business days to process. A routine form therefore should not be treated as a live dispatch conversation.
Check the current City page for the full category list. Employees may also have required internal reporting channels. The purpose here is to prevent an urgent visible concern from being silently placed into a slower public workflow, not to create an independent severity-ranking system.
Location needs the side you actually observed
An intersection name can identify several approaches and pedestrian crossings. If known, state the direction of travel or the corner associated with the observed indication. If you cannot establish direction reliably, use a clear public landmark rather than guessing. Include the observation time because a condition may be intermittent or may change before review.
Describe the visible behavior plainly. Do not attribute it to a sensor, power source, software setting, or another department’s work without confirmation. A recurring delay can be reported as a timing concern with relevant context; it does not establish that the signal is broken. Keep photographs optional and subject to safety and employer rules.
An editorial case: two different lights at one corner
Imagine a hypothetical worker hearing that “the lights went out” after a storm. From an authorized location, the worker can establish only that a streetlight is dark; the signal condition has not been observed. Reporting a signal outage based on that phrase would add a fact that is missing.
The worker clarifies what was seen and uses the correct channel. Phoenix’s Street Lights page lists a separate outage route, 602-495-5125. If a signal problem is also observed, it is described separately with its approach and time. The useful contribution is accurate identification, not a theory about a shared electrical cause.
Four fields for the report
- Asset: traffic signal, pedestrian indication, streetlight, or uncertain
- Place: intersection and observed approach or corner, where known
- Condition and time: what was actually seen and when
- Route: the current official reporting channel appropriate to that condition
Do not add driver identities, license plates, or speculative blame to a public maintenance note. For career explorers, this example shows how the visible public interface and the technical work behind it differ. An observer supplies reliable context; qualified staff determine the assessment and response. Read monsoon drainage stewardship for another case in which nearby storm effects require distinct descriptions.
Sources and limits
Public sources checked October 5, 2026. Editorial examples are hypothetical; official instructions and case-specific decisions remain with the responsible City service.
- Phoenix: Report Traffic Signal Issues
Public distinction between urgent signal reporting and non-emergency forms; no technician procedure or live outage data.
- Phoenix Street Lights
Public streetlight reporting route and distinction from traffic signals; no electrical troubleshooting guidance.