A dark intersection is one of the most dangerous things a city can put in front of a driver — crash rates jump nearly 300 percent in the first hour after a signal goes fully dark, and most agencies still find out about that failure from a phone call rather than a monitoring system. A modern signalized intersection carries 15 to 30 individual components working in constant coordination, from conflict monitors to pedestrian pushbuttons, and under the Manual on Uniform Traffic Control Devices (MUTCD), every one of them carries a maintenance and inspection obligation that becomes a liability question the moment a crash happens at a non-compliant intersection. OxMaint's signal maintenance workflow gives public works departments the preventive maintenance schedule, fault tracking, and compliance record that keeps a signal network out of both the news and the courtroom.
A Signal That Goes Dark Is a 297% Spike in Crash Risk, Not a Maintenance Ticket
Preventive schedules, fault dispatch, and MUTCD-ready compliance records for every signalized intersection your department maintains.
Six Systems, One Intersection, Zero Room for a Missed Inspection
Each signal component fails differently, on a different schedule, with a different consequence. A maintenance program that treats them all the same either over-inspects the low-risk parts or misses the ones that actually cause a dark intersection.
How One Failed Component Becomes a City-Wide Problem
A signal failure rarely stays contained to one intersection. The cascade below is why traffic engineers treat signal maintenance as a network safety function, not a facilities task.
Preventive Maintenance Calendar for a Standard Signalized Intersection
| Task | Frequency | Compliance Purpose |
|---|---|---|
| Visual signal head inspection | Quarterly | Lamp function, alignment, visibility |
| Conflict monitor test | Quarterly | Safety-critical, MUTCD-required |
| Detector operation check | Monthly | Vehicle actuation accuracy |
| Pedestrian pushbutton test | Quarterly | ADA crossing time compliance |
| Communication link verification | Monthly | Central coordination and timing |
| Full intersection audit | Annually | Capital planning, condition scoring |
Stop Finding Out About a Dark Signal From a 911 Call
OxMaint schedules every PM task automatically, dispatches fault repairs to the nearest technician, and keeps the photo and timestamp record your department needs for MUTCD compliance.
Reactive Firefighting vs. a Documented PM Program
Agencies that run a structured, documented preventive maintenance program consistently report far fewer emergency callouts than agencies still working reactively. The bars below reflect that typical gap.
One signal technician typically maintains 30 to 40 intersections. A documented PM program is what makes that staffing ratio sustainable — every task is scheduled, assigned, and tracked instead of relying on a technician's memory of which cabinet was inspected last.
Expert Review — A Traffic Signal Operations Supervisor's Perspective
I supervise signal operations for a city with just under 400 intersections and a crew that has never grown past six technicians. For a long time our PM schedule lived in a technician's head and a wall calendar, and conflict monitor testing — the single most important safety check we perform — sometimes slipped by a quarter when someone was out sick. The turning point came after a crash at a flashing intersection where opposing counsel asked for our maintenance records and we could not produce a clean one. Since moving PM scheduling and fault dispatch into a connected system, every test has a date, a technician, and a result attached to the intersection record. When we go into a claims review now, we hand over documentation instead of an explanation.
Every Untested Conflict Monitor Is a Liability Question Waiting to Happen
PM scheduling, fault dispatch, mobile completion, and MUTCD-ready compliance records — for every signal in your network, on autopilot.
Frequently Asked Questions
How does OxMaint schedule preventive maintenance across hundreds of intersections?
Each intersection is set up once with its component inventory and inspection intervals, and the system generates and assigns PM work orders automatically on schedule, with mobile completion and photo documentation. Start free in OxMaint to see the PM scheduling engine.
Can we track and dispatch emergency signal outages separately from scheduled maintenance?
Yes. Reported outages create a priority work order routed to the nearest available technician, tracked separately from routine PM tasks so response time on active dark or flashing signals is visible in real time. Book a demo to see the emergency dispatch workflow.
What records does the system keep for MUTCD compliance and legal discovery?
Every inspection and repair is logged with a date, technician, result, and photo, tied to the specific intersection and component, producing a complete maintenance history exportable for audit or litigation requests. Start free in OxMaint to see a sample compliance export.
Can the platform manage a mix of old electromechanical controllers and newer ATC cabinets?
Yes. Each signal asset is tracked individually regardless of controller generation, so aging and modern equipment share the same PM schedule, parts inventory, and fault history in one system. Book a demo to see mixed-fleet signal tracking.
How much staffing does a preventive signal maintenance program actually require?
Industry practice puts one technician at roughly 30 to 40 signals when the PM schedule is documented and automated; without a system, agencies typically need more staff to cover the same network reactively. Start free in OxMaint to model your staffing ratio.
Your Signal Network Runs 24 Hours a Day. Your Maintenance Program Should Too.
Automated PM scheduling, fault dispatch, spare parts tracking, and compliance-ready records for every intersection in your city.
