How it works

From citizen request
to closed work order.

A job in public works passes through five stages: intake, triage, dispatch, field work, and reporting. Most software handles one or two of them well. WorkmanIQ handles all five in the same system, with AI helping at the triage and reporting stages.

Start to finish

The five stages of a job.

01

Intake

Requests come in from the public portal, SeeClickFix, or a webhook from another system. Technicians can create them from the field and office staff can log them from a desk. All of them go into the same queue.

  • Public portal with no login, photo upload, address lookup, and reCAPTCHA
  • SeeClickFix v2, Samsara, Geotab, and ESRI integrations included
  • Tracking codes (SR-XXXXXXXX) so residents can check status without an account
02

Triage

When a request arrives, WorkmanIQ reads it and suggests a division, category, and priority. It checks for open work orders and assets within 200 meters. If the classification has a high confidence score, the request becomes a work order right away. Otherwise it waits for a supervisor to review it.

  • Division, category, and priority suggested on arrival
  • Flags duplicates and repeat problems at the same location
  • A confidence score and a one sentence explanation with each result
03

Dispatch

The work order shows up in the division's queue with its priority and SLA already set. A supervisor assigns it from a phone or a desktop. If it sits too long, the system warns and then escalates.

  • SLAs by priority: Emergency 2 hours, High 8 hours, Medium 3 days, Low 7 days
  • Workflow rules such as "assign emergency hydrant work orders to the on call crew"
  • A warning at 75% of the SLA clock and escalation when it is missed
04

Field work

The technician opens the app on their phone, with or without a signal. They scan the asset's QR code, photograph the work, record a voice note, log labor and materials, and mark the job complete.

  • Installs to the home screen on iOS, Android, Windows, and Mac
  • Works offline and syncs when the connection comes back
  • Voice clips, photos, QR scans, mileage, and materials all on the work order
05

Reporting

The director types "Which assets cost us the most this quarter?" into the AI Assistant and gets back a chart, a table, and a short written summary. Scheduled reports go out by email at 6 a.m. The resident who reported the problem sees it marked complete.

  • Questions in plain English return a chart, a table, and a summary
  • Standard reports for cost by division, technician productivity, asset risk, and Michigan Act 51
  • Scheduled email digests and CSV or Excel export from any list
Sample workflow #1

A pothole report, start to finish.

It is 7:02 a.m. on a Tuesday. A resident on Lakeshore Drive sends in a photo of a pothole through the public portal.

7:02 AM

campaign Resident submits

"Big pothole on Lakeshore between 4th and 5th. Hit it twice this week." A photo is attached and the address is located on the map.

7:02 AM

auto_awesome Request is triaged

Division: Streets · Category: Pothole · Priority: Medium, with 94% confidence. One earlier request 38 meters away was closed last week. The request becomes WO-2026-000412.

7:14 AM

assignment_ind Supervisor assigns

The Streets supervisor opens the queue on their phone and assigns WO-412 to the Truck 7 crew. The resident gets a notice that the request is in progress.

9:48 AM

build Crew arrives

The foreman scans the location marker, takes a "before" photo, and taps Start. The crew uses 0.3 tons of cold patch, which comes out of inventory.

10:11 AM

task_alt Job closed

The foreman adds an "after" photo and a voice note ("patched and tamped, will need a hot mix overlay in spring"), logs 23 minutes of labor, and taps Complete. The resident is told the request is closed.

5:00 PM

insights Daily report

The director's evening digest shows Streets closed 18 work orders today with an average close time of 2.6 hours. The voice note stays in the location's history for when the spring overlay schedule is planned.

Sample workflow #2

A failing lift station pump.

Lift Station #3 has been moving up the asset risk list for two weeks. Then the SCADA alarm goes off.

14 days before

timeline Risk score rises

Lift Station #3 moves from Medium to High. The explanation: three repairs in the last six months, 72% of its expected lifespan used, and a declining condition trend.

7 days before

history Supervisor reviews history

The utility supervisor opens the asset record: 14 work orders in 24 months and an impeller replacement 18 months ago. The AI Assistant shows how repair costs have trended.

5 days before

menu_book SOP drafted

The supervisor uploads the manufacturer's PDF manual for the pump. WorkmanIQ drafts an SOP with 12 numbered steps, safety notes for each step, a parts list, an estimated time, and a service interval. The supervisor reviews it and publishes it.

Day of

notifications_active Alarm goes off

The SCADA system sends the alarm to WorkmanIQ by webhook. It is marked Emergency in the Sewer division, linked to Lift Station #3, and routed to the on call crew as a work order.

Day of

engineering Repair

The technician opens the work order and finds the SOP already attached. They follow the 12 steps with no signal in the wet well, then upload photos and a voice summary on the way out.

Next day

trending_down Score is recalculated

The closed work order is added to the asset's repair history. The risk score drops from High back to Medium and the PM schedule is adjusted.

See it with your own setup.

We will walk through the citizen portal, the technician app, and the AI Assistant using your divisions and your assets.

Request a demo arrow_forward