Streetlight and pole issue report
How do we take a streetlight or pole issue report from a resident with the location and a photo, match it to the asset, and create the work order on the repair standard?
Make the report a tap on a map that matches the asset. Callvu takes the resident's report from the website, the app or a call (the location from the phone or the pole tag, the photo, the issue type), prefills the asset from the streetlight and pole inventory (the fixture, the owner, the municipality's contract, any open order), classifies the issue (a light out, cycling or dim, a day-burner, a knocked-down or leaning pole, exposed wiring or a hazard), creates the work order in the work management system with the repair standard's due date, routes a hazard to dispatch immediately and a municipal-owned light to the municipality, and writes the report to the CIS so the resident can see the status and the repair is reported under the tariff's standard.
In scopeSimpleCallvu moves: prefill, classify, write back
Last updated November 7, 2026.
The problem today
The same dark light was reported eleven times, and the work order said 'near the school'.
Streetlight reports are frequent, low value individually and visible to everyone: a resident calls, describes a location, and a work order is written from the description. The crew cannot find the pole; the light stays dark; the resident reports it again; the municipality, which pays for the light under the tariff, asks why its repair standard is being missed.
The streetlight tariff sets the service (the fixture types, the ownership of the pole and the fixture, the repair standard in days from the report) and the municipality is the customer; the pole inventory holds each asset with a tag and coordinates; the work management system holds the order. A resident's phone knows where it is and can take the photo. The report should match the asset, not describe it.
A report tied to the asset is a repair that happens once.
How it runs
From the requestto the system of record.
A resident reports a streetlight or pole issue on the website, in the app, by call or through a municipal portal. Callvu opens the report.
- Resident
- Reports with the location from their phone or the pole tag and a photo, and sees the status.
- Municipality
- Receives reports on lights it owns and the repair reporting under the tariff.
- Field operations
- Receive the work order with the asset and the hazards first.
- Callvu
- Captures, prefills the asset, classifies, creates the order, routes and writes.
Capture and prefill the asset
The location is taken from the phone's position, the map pin or the pole tag number, with a photo of the light or the pole; the asset is prefilled from the streetlight and pole inventory (the pole and fixture identifiers, the fixture type, the owner, the municipal contract, any open order on the asset); a report on an asset with an open order attaches to it rather than creating a duplicate.
Classify the issue
The issue is classified from the report and the photo: a light out, cycling or dim, a day-burner, a damaged or missing fixture, a leaning or knocked-down pole, exposed wiring or a hazard; a hazard routes to dispatch immediately; a light the municipality owns and maintains routes to the municipality's system; a utility-owned light gets the repair standard's due date from the tariff.
Create the work order
The work order is created in the work management system with the asset, the issue, the photo, the due date and the crew type; the resident receives the reference and the expected repair window.
Write back and report
The report is written to the CIS, the system of record, against the municipal lighting account, the resident sees the status and the completion, and the repair times are reported against the tariff's standard to the municipality and the commission's service quality report.
Where it ends: The report matched the asset from the resident's phone, the hazard went first, one work order was created on the repair standard, and the CIS and the work management system hold the report and the completion for the service quality reporting. The Decision Trace shows the asset match and the classification; the Audit Trace shows the report, the order and the completion with time.
Runtime enforcement
What is enforcedwhile the work runs.
The regulations preloaded in Callvu Studio and the bank's own policies, applied as steps that run, not lines in a binder. A step that breaks a rule does not run, so a completed run was compliant.
The handoff
Between the front doorand the back office.
The front door
The website, the app, a call with a link, or the municipal portal; the resident's phone supplies the location and the photo.
The back office
Field operations receive orders tied to assets with hazards first; the municipality receives its own lights' reports.
The Decision Desk
- A report that cannot be matched to an asset, or an ownership conflict between the utility, the municipality and a joint-use owner, goes to the lighting desk in the Decision Desk with the record and only the allowed outcomes.
Proof
In scope.Proof at scale, not one process at a time.
The kind of process Callvu runs in production for customers in this industry. Ask for a reference on this exact process. The results below are the industry's published proof; each claim code links to its record on agents.callvu.com.
More than 1,000 processes are live across Callvu customers.
Across Callvu customers
PSEG Long Island runs start, stop and move service on Callvu, live in 4 weeks.
Across Callvu customers
Questions
What buyers ask next,answered plainly.
How is the light identified?
From the resident's phone position, a map pin or the pole tag, matched to the streetlight and pole inventory; a report on an asset with an open order attaches to it.
How fast is it repaired?
A hazard is dispatched immediately; a routine outage carries the tariff's repair standard as the order's due date, and the repair time is reported.
What if the municipality owns the light?
The report routes to the municipality's system with the asset record, under the contract's responsibilities.
Related processes
Bring this process, or the one that costs you most.
We build it against your policies and your systems, train your team and stay with you through launch. You are live in weeks.