How do municipalities track work orders?

Most municipalities track work orders in one of three ways: a spreadsheet or paper binder maintained by the supervisor, a municipal asset-management or work-order platform, or dedicated public-works operations software. What matters more than the tool is that a single list is trusted by everyone, that deadlines surface on their own, and that completion evidence is attached to the job rather than kept separately.

What is the difference between a service request and a work order?

A service request records that something was reported to the municipality. A work order authorizes and documents the work the department decides to perform. One service request may generate several work orders, or none.

Can public works software create its own work orders, or does it need another system?

It depends on the software. Some tools are strictly companions to an asset-management platform. PW Command can operate either way: work orders can be created directly in PW Command, or imported from an existing municipal system that remains the system of record.

How long should a municipality keep work-order records?

Retention is set by the municipality's own records-retention by-law and any applicable provincial requirements, not by the software. Because operational records are frequently relied on in claims that arise years later, most departments retain them well beyond the operating year. Confirm your own retention schedule with your clerk.

Public works resource

Municipal Public Works Work Order Management

What is a public works work order, and how do municipalities manage them?

In short

A public works work order is the record a municipality creates to authorize, describe and document a specific piece of operational work — a pothole repair, a catch basin cleanout, a sign replacement, a winter callout — including where it is, who did it, when it was done and what was used. Work order management is the practice of moving that record through its lifecycle: intake, prioritization, assignment, field execution, documentation and closure.

Service request or work order?

The two are often used interchangeably and it causes real confusion. A service request is what someone outside the department reports: a resident calls about a washout, a councillor forwards an email, a bylaw officer flags a sightline. A work order is what the department decides to do about it.

Not every service request becomes a work order. Some are duplicates, some are another department's or another road authority's responsibility, some are inspected and closed. Keeping the two separate lets a municipality answer both questions honestly: what was reported to us, and what did we do.

	Service request	Work order
Created by	Public, council, other departments, staff observation	The department, after triage
Purpose	Records that something was reported	Authorizes and documents work
Closure means	The requester has an answer	The work is done and documented
Typical volume	Higher — includes duplicates	Lower — one per job

The work-order lifecycle

1.Intake. The work arrives from a service request, a patrol finding, an inspection, a preventive-maintenance schedule, or a supervisor's own observation.
2.Triage and classification. Confirm jurisdiction, location, asset and road segment. Attach the class or category the department uses so priority is not a matter of opinion.
3.Prioritization. Rank by risk, statutory or policy timelines, seasonal window and practical grouping.
4.Assignment. Match the job to a crew with the qualifications, equipment and traffic-control capability it needs.
5.Field execution. The crew works from a clear scope with the location, hazards and access notes attached.
6.Documentation. Completion time, quantities and materials, photos, and anything that changed on site.
7.Closure and follow-up. Close the job, close the originating request, and raise a follow-up if the fix was temporary.

Why prioritization is the hard part

Most departments can list their open work. Very few can say, at 6:30 a.m., which ten items matter most today given who showed up, what equipment started, and what the weather is doing.

That is a scheduling problem disguised as a records problem, which is why buying a bigger records system often does not fix it. Priority in public works is a function of four things at once: risk to the travelling public, any timeline the municipality is held to by regulation or its own policy, geography (what can be done in one loop), and resource fit (who is qualified and what is running).

Risk first: anything that endangers road users or workers moves ahead of everything else.
Timelines second: work with an external clock on it should never be discovered late.
Geography third: grouping by area is the cheapest productivity gain a department has.
Resource fit last, but it is a veto — a plan a crew cannot legally or physically execute is not a plan.

Recurring, preventive and emergency work

Three streams compete for the same crews. Recurring and preventive work — sweeping, grading, catch basin cleaning, ditching, sign inspections — is the work that quietly prevents future complaints, and it is the first thing sacrificed. Reactive work arrives daily. Emergency work arrives without warning and takes precedence.

A department that only tracks reactive work will show a busy year and a declining road network. The practical answer is to make recurring work visible in the same list as everything else, so displacing it is a visible decision instead of an accident.

Documenting completion so it holds up later

Operational documentation is written for a reader who was not there, possibly years later, possibly a lawyer. The test is simple: could someone reconstruct what happened from the record alone?

Where: segment or asset identifier, not just a street name.
When: discovery time and completion time, captured when they happen rather than reconstructed.
Who: crew members present, and who supervised.
What: scope actually performed, quantities, materials, equipment used.
Evidence: before-and-after photos, ideally with location and timestamp intact.
Judgment: anything the crew decided on site, and why — including work deferred and the reason.

Small departments and spreadsheets

Spreadsheets and paper work orders are not a failure of professionalism; they are a rational response to systems that cost more to feed than they return. They break in three specific places: nobody knows the current version, nothing warns you that a deadline is approaching, and the evidence lives somewhere else entirely (a phone camera roll, a truck binder).

A small department does not need an enterprise asset-management deployment to fix that. It needs one list everyone trusts, a deadline that surfaces itself, and photos attached to the job rather than to a phone.

Checklist

Work-order health check

Use it as written or adapt it to your own municipal policy. It is a practical aid, not a compliance guarantee.

Every open item has a location precise enough to dispatch to without a phone call.
Every item has an owner — a crew or a named person, not a department.
Items with an external timeline are visibly separated from items without one.
Recurring and preventive work appears in the same view as reactive work.
Completion capture includes time, quantities and photos as a matter of routine.
Closed jobs that were temporary fixes generate a follow-up item automatically or by habit.
Someone can produce the full history of one location in under five minutes.

Common mistakes

Treating the service request as the work order, so the public record and the operational record drift apart.
Prioritizing by report date because it is the only field everyone trusts.
Letting photos live on personal phones, where they are unsearchable and eventually gone.
Closing a temporary repair as complete with no follow-up.
Recording the street but not the segment, which makes history impossible to assemble later.

Frequently asked questions

How do municipalities track work orders?: Most municipalities track work orders in one of three ways: a spreadsheet or paper binder maintained by the supervisor, a municipal asset-management or work-order platform, or dedicated public-works operations software. What matters more than the tool is that a single list is trusted by everyone, that deadlines surface on their own, and that completion evidence is attached to the job rather than kept separately.
What is the difference between a service request and a work order?: A service request records that something was reported to the municipality. A work order authorizes and documents the work the department decides to perform. One service request may generate several work orders, or none.
Can public works software create its own work orders, or does it need another system?: It depends on the software. Some tools are strictly companions to an asset-management platform. PW Command can operate either way: work orders can be created directly in PW Command, or imported from an existing municipal system that remains the system of record.
How long should a municipality keep work-order records?: Retention is set by the municipality's own records-retention by-law and any applicable provincial requirements, not by the software. Because operational records are frequently relied on in claims that arise years later, most departments retain them well beyond the operating year. Confirm your own retention schedule with your clerk.

References and sources

This page is operational guidance for public-works staff. It is not legal advice. Where a regulation is discussed, work from the current consolidated text and your municipality's own policies and legal advice.

Municipal Act, 2001, S.O. 2001, c. 25 (highway maintenance duty, s. 44)
Sets the municipal duty to keep highways in a reasonable state of repair.
O. Reg. 239/02: Minimum Maintenance Standards for Municipal Highways

Last reviewed against its sources: 2026-08-16. Regulatory material changes; confirm current text before relying on it operationally.