Ask a public works crew where work orders really come from and the honest answer is everywhere. A resident calls about a pothole. Someone emails a photo of a broken sign. A councilmember texts the director. A supervisor writes it on a whiteboard. By the time any of it reaches a system, half of it is already lost.
That is the actual problem with public works work order management, and it is why buying work-order software so often disappoints. The software is rarely the weak link. The intake is. This guide covers what work order management needs to do for a public works department, why intake decides whether any tool succeeds, and how a department can run the whole loop on tools it likely already owns.
What is public works work order management?
Public works work order management is the process of capturing, assigning, tracking and closing maintenance and service requests across a public works department, from a citizen report or an internal inspection through to a completed job with a record of what was done, by whom, and at what cost.
A working system does five things in order:
- Captures every request through one intake, whatever the source
- Routes each request to the right division and crew
- Schedules and assigns the work
- Records completion, labour, materials and cost
- Reports on backlog, response time and spend
Intake decides whether any system works
The reason work-order projects fail is almost never the assignment or reporting features. It is that the requests never make it into the system cleanly in the first place.
When a pothole report can arrive by phone, email, a paper form, a text to a supervisor and a comment at a council meeting, no software can manage what it never received. Crews end up working from five informal lists, the official system shows a fraction of the real backlog, and the reports that go to the council are quietly wrong. Buying a better work-order tool does not fix this. It just gives the fraction that gets entered a nicer home.
The fix is one intake and one queue. Every request, no matter how it arrives, lands in the same place and becomes a tracked item. That is a process decision first and a software decision second, and it is the single highest-value change most departments can make. It is the same pattern behind consolidating asset data across divisions, which we covered in our guide to asset management software for public works.
Where work orders sit relative to the asset register
Work orders and the asset register are two halves of one system, and it helps to be clear on which is which.
The register is what you own and its condition. Work orders are what needs doing to it and what got done. A work order that is not tied to an asset is just a task list, and an asset register with no work history is just an inventory. The value shows up when the two connect, so that a pump’s whole maintenance history sits on the pump’s record and feeds the decision about when to replace it.
This is why buying a standalone work-order app can be a dead end. If it does not share data with the asset register, you have built another island, which is the problem you were trying to solve.
Running the whole loop on tools you already own
A public works department running Microsoft 365 already has the pieces for the entire work-order loop, and most directors do not realise it.
Power Apps can be a mobile app a crew uses to receive, update and close jobs from the field, including offline at a site with no signal. A public form or a Power Automate flow can be the single intake that turns a citizen report into a tracked request and routes it to the right division. SharePoint or Dataverse holds the queue and the history. Power BI shows the council the backlog and the response times.
On licensing, to be exact: E1, E3 and E5 include seeded rights to build Power Apps and Power Automate over Microsoft 365 data such as SharePoint, and E5 includes Power BI (Microsoft Power Platform Licensing Guide, August 2026). A larger build using Dataverse adds a Power Apps Premium cost, still well below a per-seat municipal work-order subscription across every division. The point is not that you must build. It is that the whole loop is within reach of tools you already pay for, which changes what you should expect to spend.
Here is how the work-order loop tends to compare across the two routes:
| Part of the loop | Dedicated work-order platform | Built on Microsoft 365 you own |
|---|---|---|
| Citizen request intake | Often a polished public app | Web form or Power Automate flow, more setup |
| Field mobile app | Included | Power Apps, including offline |
| Routing and assignment | Built in | Power Automate, strong for standard rules |
| Link to the asset register | Varies, sometimes a separate module | Direct, same tenant |
| Backlog and response reporting | Vendor reporting | Power BI, included with E5 |
| Ongoing cost | Per-user or per-crew subscription | Build cost, then support on owned licences |
The row to weigh first is citizen intake. If a branded public reporting app matters now, that is the clearest reason to buy. The rest of the loop tends to favour building for a department already on Microsoft 365.
UNIFIED UTILITY MANAGEMENT
Want one intake and one queue for every division?
Nexinite builds mobile work orders, citizen-request intake and backlog reporting into the Microsoft 365 your department already runs, tied to your asset register. No new subscription per crew, and no forever licensing.
When a dedicated work-order platform is worth it
Some departments should buy, and it is worth being honest about when.
You want a public citizen-request app out of the box. If a branded resident reporting app with maps and status updates is a priority now, several vendors ship one, and building the equivalent takes real effort.
You need heavy fleet or specialized maintenance depth. Fleet maintenance in particular is often better on a dedicated tool that then feeds the shared queue.
You have no internal capacity to own a build. A supported product is the safer choice for a small department with no IT function.
If none of those apply, the reason to buy is usually the demo, not the need.
How this looks when it is done right
Silicon Valley Clean Water is the clearest proof of the connected approach, on the utility side where the reporting stakes are highest. Its work and asset data were split across financial systems, project tools and SCADA. Nexinite built the work and asset management on the Microsoft stack SVCW already licensed, tying maintenance activity to each asset and into capital planning.
According to Nexinite’s published case study, the result was a 40% reduction in unplanned maintenance and an estimated 20% saving in operational costs. The detail is in the SVCW case study. A public works department is the same shape with more divisions feeding one queue.
Frequently asked questions
What is public works work order management?
It is how a public works department captures, assigns, tracks and closes maintenance and service requests across every division, from a citizen report or inspection through to a completed job with a record of the work, the crew and the cost. Done well, it gives the department one backlog and honest response-time reporting instead of several informal lists.
Why do work order systems fail in public works?
Usually because intake is broken, not because of the software. When requests arrive by phone, email, paper and text, no system captures the full backlog. Fixing intake to one queue matters more than the tool.
Can we run public works work orders on Microsoft 365?
Yes. Power Apps gives crews a mobile app to receive and close jobs, a form or Power Automate flow becomes the single intake, SharePoint holds the queue, and Power BI reports the backlog. Seeded rights over SharePoint come with E1, E3 and E5 (Microsoft Power Platform Licensing Guide, August 2026), so much of it uses licences you already hold, with Dataverse the main paid add-on for a larger build.
How do work orders relate to the asset register?
They are two halves of one system. The register is what you own and its condition; work orders are what needs doing and what got done. The value comes from tying each work order to an asset so the maintenance history informs when to repair or replace it. A standalone work-order tool that does not share data with the register just creates another island.
Where to start
Fix intake before you shop. Getting every request into one queue is the change that makes any work-order system work, and it costs process discipline more than money. Once the queue is real, decide what software, if any, you still need, and check what your Microsoft licences already cover first.