How to Manage Streetlight Work Orders

A work order that isn't linked to a fixture location is an instruction with no address — and an instruction with no address is harder to act on than it should be.

Streetlight work order management in most public works departments involves some combination of a work order system that doesn't have a map, a map that doesn't connect to the work order system, and a dispatcher who bridges the gap by looking things up in both and passing information by phone. The result is work orders that lack the location precision crews need to navigate, fixture maintenance histories that exist in one system while work order records exist in another, and managers who can't answer "what's the status of that repair on Elm Street?" without checking two systems and calling a crew supervisor.

Atlas links every work order to the specific fixture it addresses, giving dispatchers, crews, and managers a single place where location, work order status, and maintenance history are the same record.

Here's how to set up work order management that actually connects to your streetlight inventory.

Why Location-Linked Work Orders Improve Maintenance Operations

A work order attached to a map point is qualitatively different from a work order with an address in a text field.

Work order management that lives in the same platform as the fixture inventory removes every step that currently requires looking something up in one system and entering it in another.

Step 1: Create Work Orders Directly from Fixture Records

The most efficient work order creation flow starts at the fixture:

Open the fixture record in Atlas by clicking the fixture on the map — this is the starting point for any work order associated with that fixture
Create a new work order from within the fixture record, which automatically links the work order to the fixture's GPS coordinates, fixture ID, and current attribute data without any manual entry
Select the work order type from a standardized list — lamp replacement, ballast repair, pole inspection, damage repair, scheduled preventive maintenance, new installation — so work order type is consistent across the full maintenance history
Set priority level — emergency, urgent, routine — based on the outage type, fixture location, and your department's priority classification rules
Add work order description with specific instructions, parts required, and any special access notes that aren't already in the fixture record — the work order description is what the crew reads at the site

Work orders created from fixture records inherit all the location data automatically, eliminating the address entry step and the geocoding uncertainty that address-based work orders carry.

Step 2: Configure Your Work Order Workflow Stages

Every work order moves through defined stages, and each transition should be tracked:

Draft — work order created but not yet reviewed or assigned; useful for work orders generated automatically from 311 reports that need dispatcher review before dispatch
Open — work order reviewed, priority confirmed, ready for crew assignment; visible on the dispatch queue and the outage map
Assigned — specific crew assigned, work order visible on the crew's mobile queue with expected completion date
In Progress — crew has arrived and started work; status updated by crew in Atlas mobile when they arrive at the fixture
Pending Parts — work started but paused waiting for parts that weren't available on the truck; fixture status updated to reflect the repair is in progress but not complete
Completed — work finished, fixture status updated, maintenance record closed; work order moves to fixture's closed history
Deferred — work order cannot be completed for a defined reason (utility coordination required, safety concern, access denied) and needs rescheduling

Each status transition creates a timestamp in the work order record, enabling response time calculation for every stage of the maintenance process.

Step 3: Assign Work Orders to Crews with Equipment Context

Assignment is where route planning and work order management intersect:

View all open work orders on the fixture map before assigning any — assignment decisions made with geographic context produce more efficient dispatch than assignment decisions made from a work order list
Filter open work orders by priority so emergency and urgent work orders are assigned before routine maintenance
Check crew availability and location before assigning — a crew finishing a job nearby is a better assignment than a crew on the other side of the district, regardless of which crew is technically next in the queue
Verify equipment match between the work order requirements and the assigned crew's truck — bucket truck work assigned to a pickup crew, or work in a low-clearance alley assigned to a full-size bucket, creates avoidable assignment failures
Set expected completion targets when assigning — the target date for each priority level should reflect your department's service level commitments, creating accountability without the overhead of formal SLA administration

Also read: Plan Streetlight Maintenance Routes

Step 4: Enable Field Crews to Manage Work Orders from Mobile

The work order workflow only works if crews can interact with it in the field:

Crew opens assigned work orders on Atlas mobile at the start of each shift, seeing their queue sorted by route sequence rather than work order number
Navigate to each fixture directly from the work order record using precise GPS coordinates in the crew's preferred navigation app
Review fixture context from the work order — fixture type, previous work orders, access notes — before arriving so the crew arrives prepared
Update status to "In Progress" when arriving at the fixture, creating the on-site timestamp that records actual response time against the target
Log completion details in the field — parts used, findings, photos — immediately at the fixture rather than at end of shift when details are less precise
Submit work order completion from the mobile device, updating the fixture status on the live map in real time without requiring office staff to process the closure

Step 5: Use Work Order Data for Parts Inventory Management

Work order completion data is parts demand data:

Aggregate parts usage from closed work orders by fixture type — a fixture type that generates frequent lamp replacements is consuming lamps at a predictable rate that should inform stockroom inventory targets
Track parts usage by district to identify whether certain districts have higher consumption rates for specific parts — a district with older HPS fixtures will consume more ballasts than a district with recently retrofitted LED fixtures
Flag fixtures with repeated same-part replacements — a fixture that has had the same component replaced three times in eighteen months is failing systematically, not randomly, and is a candidate for a more comprehensive repair or replacement
Calculate average material cost per work order type from actual parts consumption records — lamp replacement work orders that consistently use parts costing $45 should be budgeted at that level, not estimated at the beginning-of-year unit cost
Export parts demand projections for procurement planning based on open work order volume and historical parts usage rate by work order type

Step 6: Analyze Work Order Performance for Program Improvement

Closed work order records are a performance management dataset:

Calculate average resolution time by priority level — time from work order creation to completion for emergency, urgent, and routine work orders — and compare against target resolution times to identify where the program meets commitments and where it doesn't
Track work order volume trends by month and district to identify seasonal patterns, infrastructure aging effects, and whether maintenance program investments are reducing or increasing work order generation rates
Identify repeat-problem fixtures with three or more work orders in a rolling 12-month period — these fixtures are spending maintenance budget disproportionately and are candidates for replacement
Measure crew productivity by comparing work orders completed per crew per shift across comparable districts and work order types, identifying best practices that other crews can adopt
Report program performance to management and council with actual resolution time data, work order volume trends, and cost per fixture — demonstrating program value and justifying budget requests with documented outcomes

Use Cases

Managing streetlight work orders matters for:

Municipal public works departments where dispatchers currently bridge a work order system that has no map and a GIS system that has no work orders, and where connecting those two creates operational efficiency immediately
Utility companies with streetlight maintenance agreements who need to document response times, parts used, and completion dates against contractual service level requirements for every work order
Maintenance contractors billing municipalities for labor and materials by work order who need detailed per-work-order records as the basis for invoicing and client reporting
Transportation departments managing highway lighting work orders that require documentation for FHWA reimbursement, state reporting, and traffic incident coordination
Emergency management coordinators tracking work orders generated during large outage events — storm damage, accidents — who need to manage dozens of simultaneous work orders across multiple crews and districts

It matters for any organization where the gap between the work order and the fixture location creates operational friction that slows every maintenance response and degrades every maintenance record.

Tips

Create work orders from fixture records, not from addresses — the fixture is the asset you're maintaining; the address is incidental, and an address-linked work order loses its connection to the asset's history when the address changes
Close work orders in the field, not at the end of the shift — field-closed work orders have more accurate completion timestamps, better parts detail, and fewer corrections needed than shift-end batch closures
Never delete a work order, even if it was a duplicate — mark it as a duplicate and link it to the primary work order, preserving the full record of reports received for each fixture
Track "deferred" work orders as carefully as "completed" ones — a work order that was deferred three times and then finally closed after four weeks represents a fixture reliability problem that a simple completion report doesn't reveal
Review "pending parts" work orders weekly — a work order sitting in "pending parts" status for more than a week either needs an expedited parts order or a fixture-level escalation decision

Location-linked work order management in Atlas gives every streetlight maintenance work order the context that makes it efficient to dispatch, efficient to complete, and valuable as a historical record.

Streetlight Work Order Management with Atlas

Effective streetlight work order management requires a platform where the work order and the fixture record are the same object — not two records in two systems that someone has to keep synchronized. Atlas provides that connection, giving dispatchers, crews, and managers a unified view of every work order and the fixture it addresses.

From Creation to Close on One Platform

With Atlas you can:

Create work orders from fixture map records that inherit GPS coordinates, fixture attributes, and maintenance history automatically — no address lookup, no separate system entry
Assign and dispatch work orders from the live fixture map where all open work orders are visible alongside fixture status and crew locations
Close work orders from the Atlas mobile app in the field, updating fixture status on the live map in real time without requiring office processing

Also read: How to Track Streetlight Outages and Repairs in Real Time

Accountability at Every Stage

Atlas lets you:

Calculate response time from work order creation through completion for every priority level, comparing actual performance against target resolution times without manual data assembly
Identify repeat-problem fixtures with multiple work orders in a rolling period, surfacing early replacement candidates before cumulative repair costs exceed replacement value
Export complete work order history for audit, contract compliance, FHWA reporting, and budget justification using actual data rather than estimates

That means less time chasing work order status — and more time using work order data to improve the maintenance program.

Work Order Management at Any Scale

Whether you're managing 50 streetlight work orders per month or 5,000, Atlas handles the volume without requiring a separate CMMS subscription or a GIS integration project.

It's streetlight work order management built for public works operations — linked to your fixture inventory from the first click.

Start Managing Work Orders from the Map Today

Efficient work order management starts with connecting the work order to the fixture it addresses. Atlas gives you that connection — from outage report through crew dispatch, field completion, and maintenance history — on a single browser-based platform.

In this article, we covered how to manage streetlight work orders — from creating location-linked work orders and configuring workflow stages to assigning crews, enabling field management, tracking parts, and analyzing performance.

From the first work order created through the maintenance history that grows with every closed record, Atlas supports complete streetlight work order management without separate system integration.

So whether you're replacing a disconnected work order system or building your first formal maintenance tracking workflow, Atlas gives you the map-linked work order management that streetlight maintenance requires.