stormwater asset management
6 min read

Stormwater Asset & Work Order Management

Track stormwater assets and the inspections, cleaning, and repairs against them in one system, so MS4 permit reporting is a query, not a scramble.

See a 10-minute demo

For US Utilities serving 3,000-100,000 meters and for operations team, billing team and utility managers. For Heads of Billing who own collections accuracy and revenue leakage.

Written by
Sewanti Lahiri
Published on
August 29, 2026
Updated on
September 4, 2026

Stormwater asset and work order management is the practice of tracking every piece of stormwater infrastructure (catch basins, pipes, culverts, detention ponds, and outfalls) as an asset record, then driving the inspections, cleaning, and repairs against each asset as work orders in the same system. Doing both in one platform is what makes an MS4 permit auditable: the asset holds the record, and the work order holds the proof of maintenance. When assets sit in a spreadsheet or GIS and work orders live in a separate system, inspection history is scattered and compliance reporting becomes a manual reconstruction every audit cycle.

Stormwater utilities and public works departments carry thousands of assets that rarely get attention until one fails during a storm. A single mid-sized system can hold tens of thousands of catch basins, hundreds of miles of storm pipe, and dozens of detention ponds and outfalls, each with its own inspection schedule and regulatory obligation. Managing them well means treating the asset and the work against it as one connected record.

This guide covers why stormwater is hard to manage, what a stormwater asset record should hold, how to set up asset and work order management together, and how the MS4 permit shapes the whole process. Utilities evaluating a platform that keeps assets and work orders in one place should look at SMART360 for water utility management, built for the 3,000 to 100,000 connection range.

Why stormwater is hard to manage

Stormwater sits in a hard spot operationally. Unlike water and sewer, it usually generates no meter and no bill, so it competes for budget against services that produce revenue. Yet it carries a federal compliance obligation and fails visibly, through flooding, when neglected.

The management problem is fragmentation. Assets are commonly mapped in GIS, inspection records kept in spreadsheets, and repairs tracked in a separate work order tool or on paper. When a storm drain floods, staff cannot quickly see when the connected catch basin was last cleaned, what the last inspection found, or whether a work order is already open. The same fragmentation that plagues water asset programs applies here, and the fundamentals in the water utility asset management guide apply directly to stormwater infrastructure.

Are your stormwater assets and work orders in the same system?

If an inspector logs a finding in one system and the repair crew works from another, the asset record and the maintenance history drift apart. The first casualty is the audit: proving a catch basin was inspected and cleaned on schedule means stitching together a GIS export, a spreadsheet, and a stack of paper work orders. When the asset and its work orders share one record, that proof is one click.

Common stormwater assets and the work they generate

Every stormwater asset type has a characteristic maintenance pattern. Knowing the pattern is how you set inspection frequencies and forecast crew workload.

Asset typeWhat it doesTypical work generated
Catch basin / inletCaptures street runoff and traps sedimentRoutine inspection, sediment and debris cleaning (often vac truck)
Storm sewer pipeConveys runoff to outfallCCTV inspection, root and blockage removal, repair or lining
CulvertCarries flow under roads and embankmentsInspection, debris clearing, structural repair
Detention / retention pondStores and slows runoffInspection, mowing, sediment removal, outlet structure repair
OutfallDischarges to receiving waterInspection, erosion control, illicit-discharge screening

Most of the recurring labor is inspection and cleaning of catch basins and pipes, because sediment and debris accumulate every season. Detention ponds and outfalls generate less frequent but higher-cost work. Planning inspection cycles by asset type keeps a small crew ahead of the failures instead of reacting to them.

What a stormwater asset record should hold

An asset record is only useful if it carries enough to drive maintenance and satisfy an audit. Each stormwater asset should hold:

  • Location and identity. GIS coordinates, asset ID, type, material, size, and install date.
  • Condition and inspection history. Every inspection date, the finding, condition rating, and photos, kept on the asset itself.
  • Maintenance history. Every work order ever run against the asset, with date, crew, and outcome.
  • Schedule and next-due date. The inspection or cleaning frequency and the next date it comes due.
  • Regulatory linkage. Which permit requirement or reporting obligation the asset falls under.

The point of holding all of this on the asset is that the record answers the two questions that matter: what condition is this asset in, and can I prove we maintained it. A record that holds only location without condition and maintenance history is a map, not an asset management system.

How to set up stormwater asset and work order management

Setting up stormwater asset and work order management follows a consistent sequence whether you start from spreadsheets or from GIS.

  1. Build the asset inventory. Import or field-collect every stormwater asset with location, type, and attributes. Start with the assets that carry the highest failure or compliance risk if inventory is incomplete.
  2. Set condition baselines. Run an initial inspection pass to record a starting condition rating for each asset, so future change is measurable.
  3. Define inspection and maintenance schedules. Assign an inspection and cleaning frequency by asset type, then let the system generate the due dates.
  4. Turn schedules into work orders automatically. Each due date generates a work order assigned to a crew, with the asset, location, and task attached. The linkage between the schedule and the field work is what the work order management workflow is built to handle.
  5. Capture work in the field. Crews complete inspections and cleaning on a mobile device, recording findings and photos against the asset, so the record updates as work happens.
  6. Report against the asset history. Pull inspection and maintenance history by asset, area, or permit requirement for internal review and regulatory reporting.

The step utilities underestimate is the first one. A stormwater inventory is rarely complete, and the assets missing from it are the ones no one is inspecting. Field-verifying the inventory before building schedules prevents a compliance program that looks complete on paper but misses assets in the ground.

Stormwater compliance and the MS4 permit

For most US stormwater operators, the reason this becomes a program rather than an afterthought is the MS4 permit. A Municipal Separate Storm Sewer System permit, issued under the federal NPDES program, requires operators to inspect and maintain their stormwater infrastructure and to keep records that prove it. Failing to produce those records is itself a violation, even if the maintenance happened.

This is where connected asset and work order management pays for itself. When every inspection and cleaning is captured as a work order tied to the asset, the annual permit report is a query, not a scramble. Utilities managing stormwater alongside broader regulatory obligations should review the overview of water utility regulations and compliance software to see how maintenance records feed compliance reporting.

Can you produce an inspection history for any catch basin on demand?

That is the question an MS4 auditor effectively asks. If the answer requires pulling three systems together, the program is carrying audit risk it does not need to. A single asset record with its full work order history attached turns the audit from a reconstruction into a lookup.

How SMART360 manages stormwater assets and work orders

SMART360 keeps asset management and work order management in one platform, so a stormwater asset carries its condition, inspection history, and every work order in one record. Inspection and cleaning schedules generate work orders automatically, crews complete them on mobile with photos and findings attached to the asset, and reporting pulls maintenance history by asset, area, or permit requirement.

Island Water Authority deployed SMART360 including its Asset Management and Service Orders modules and reached go-live in 10 weeks, contributing to a 47% operational cost reduction. For a stormwater program run by a small crew, keeping assets and the work against them in one system is what makes preventive maintenance and permit reporting sustainable. Utilities comparing tools specifically for the work order side should read the work order software comparison for water utilities.

Frequently Asked Questions

What is stormwater asset and work order management?

It is the practice of tracking stormwater infrastructure (catch basins, pipes, culverts, detention ponds, and outfalls) as asset records, then managing the inspections, cleaning, and repairs against each asset as work orders in the same system. The asset holds the condition and history; the work order holds the proof of maintenance. Keeping both connected is what makes stormwater maintenance plannable and MS4 permit reporting auditable.

Why should stormwater assets and work orders be in one system?

When assets live in GIS or a spreadsheet and work orders live in a separate tool, inspection history and maintenance records drift apart. Proving that an asset was maintained on schedule then requires stitching multiple systems together. One connected record lets staff see an asset's condition, its last inspection, and any open work order at once, and turns permit reporting into a query instead of a manual reconstruction.

How does the MS4 permit affect stormwater management?

A Municipal Separate Storm Sewer System permit, issued under the federal NPDES program, requires operators to inspect and maintain stormwater infrastructure and to keep records proving it. Failing to produce those records is a violation even when the maintenance was done. Capturing every inspection and cleaning as a work order tied to the asset makes the required records available on demand.

What should a stormwater asset record include?

A stormwater asset record should include location and identity (GIS coordinates, asset ID, type, material, size, install date), condition and inspection history with photos, full maintenance history of every work order run against it, the inspection or cleaning schedule with the next due date, and the regulatory requirement the asset falls under. Together these answer the two questions that matter: what condition the asset is in, and whether you can prove it was maintained.

About Two Cta Image

Ready to see how SMART360 fits your utility?

Book a personalized demo with the SMART360 team and see how SMART360 fits your utility?

Related Post From This Category