Maps, forms, and work orders for highway, water, sewer, and DPW departments

Close out the job. The map updates itself.

Every culvert, hydrant, valve, and sign on one live map your whole crew works from. Assign the work, fill the form on the job, and the record lands on the asset with the date, the crew, and the photos. Nobody retypes anything and nobody hand-colors a map.

See it work Get a price

A price on the first callMonth to monthExport your data any dayNothing to install

sample data

Culverts · Crossings

CV-0142 · Route 31 at Dutch Hollow

Records

Camera inspection

2026-05-14 · Culvert inspection · M. Rivera

Cleaned and inspected

2026-03-11 · Culvert inspection · D. Kowalski

Debris removal after storm

2025-11-18 · Storm response · T. Shaw

Headwall repair

2024-09-09 · Repair log · D. Kowalski

Ditch regrade

2024-05-21 · Roadside maintenance · M. Rivera

Why one system

The field work that keeps a map true and the enforcement work that runs on top of it are the same system.

A crew closes out a culvert and that culvert's file grows. An officer opens a case on a parcel and that parcel's file grows the same way, on the same parcels, the same tiles, and the same selection tools your crews already use. Public works is the half that keeps the map honest, and every other office in the building is downstream of that. So this is where the map, the forms, and the work orders live in full, and the code office is a door off it rather than a separate product with its own login.

Try it right here

Go ahead. Open a culvert.

No video, no form, no rep on the line. Three assets are due on this work order. Pick one, fill out the form the way your crew would, add a photo, and hit submit. Watch the map change.

Show me:

WO #218 · Culvert inspection

Assigned to you · 3 due

Tap an amber culvert

Fill the form

Submit it

0 of 3 done

An interactive model of the real screen, built for this page so you can click it without an account. To see it running on your own system, ask us for a walkthrough.

That is the whole thing. Nobody typed it twice.

The form already knew the asset

ID, size, material, last service, carried over from the record. Your crew only types what is new, which is the only reason they will actually use it.

The map changed with it

The status your crew picked on the form is the status on the map, and the answers you mapped are written onto the asset itself. Nobody opens a laptop to hand-edit a layer.

The visit landed on the asset

Who, when, the readings, and the photos, added to that culvert's own history. It stays on the culvert after the work order is closed and forgotten.

The work lands on the asset, not in a job that gets closed in the spring and forgotten. That is the difference between a map you keep updating and a system that keeps itself current.

You set it up once, per form: which answers should update the asset. After that every submission does it on its own.

What it replaces

One system instead of five almosts.

Paper forms riding shotgun in the truck Filled on the job and submitted from there

The spreadsheet only one person understands Fields the whole crew shares

The wall map from 2011 A map that changes when the work happens

Photos scattered across six phones Photos pinned to the asset they belong to

The binder of inspection sheets in the office History on the asset itself, in one place

Getting started

Three steps, and we do the first one with you.

There is no implementation project, no certification, and nothing to install.

Send us what you have

A shapefile, a spreadsheet, a list from the county, or a photo of the map taped to the wall in the garage. We do the first import with you, and your assets come in with the columns you already keep, including last-inspected dates.

Invite your crew

Invitations go out by email. Admins, office staff, and crews each get the access their job needs, and departments can be scoped to their own maps.

Send the work

Pick the assets, attach the form, assign the crew. They fill it out on the job, and the map and the asset records keep themselves current from there.

The part that pays off later

Every asset carries its own file.

Every inspection, repair, and reading lands on the asset's own timeline, whatever form or program produced it, with the crew, the date, and the photos attached. One click prints it.

A resident calls about the pipe behind their house.

Pull up the pipe and read them the last three dates while they are still on the line.

The board wants to know what got done this quarter.

Open the program and print what closed, by asset, with dates, before you leave the garage.

A new operator starts Monday.

What used to live in one guy's head is on the asset, and he reads it himself.

Sample data

Civimax

Asset history report

CV-0142 · Route 31 at Dutch Hollow · Culverts · Crossings

Date	Work	By
2026-05-14	Camera inspection	M. Rivera
2026-03-11	Cleaned and inspected	D. Kowalski
2025-11-18	Debris removal after storm	T. Shaw
2024-09-09	Headwall repair	D. Kowalski
2024-05-21	Ditch regrade	M. Rivera

Generated on demandPage 1 of 2

The code office

A parcel keeps a file the same way a culvert does.

The code office is the other half of this system, and it works the same parcels, the same tiles, and the same selection tools your crews do. Complaints, site visits, cases, violations cited out of your own chapters, and notices whose compliance dates are counted by rules your office sets, section by section. When an order runs out and the town ends up doing the work itself, the abatement reaches your crew as an ordinary work order, with the same numbering and the same completion form as every other job, and the cost comes back onto the case as a charge against the property. That side has its own page, and it is the front door of this site.

See the code enforcement page

Do the inspecting rather than the managing?

Three inspections. Not three copies of the same job.

If you CCTV the mains, inspect the manholes, and run SL-RAT over the same segments, you already know what cloning the job three times costs you. There is a page for that.

For inspection contractors

Price

Straight answers about price.

We sell to towns, districts, and the contractors who serve them, so we price the way we would want to be priced: simply, in writing, on the first call.

Priced by your system

By the size of what you manage, not by counting logins. Your own crew does not cost extra.

No setup fee, no lock-in

Month to month, cancel any time, no multi-year contract, and no implementation fee. Purchase order, invoice, and a check are all fine.

A number on the first call

You should not need three meetings to learn a price. Tell us roughly what your system looks like and you get the number in writing, before you sit through a single slide.

Everything else you would ask about.

✓Your data, in and out. Import shapefiles, spreadsheets, GeoJSON, KML and KMZ. Export SHP, GeoJSON, CSV, XLSX, KMZ, and PDF reports, any day, from inside the app.

✓Your fields, your forms. A sign inventory and a sewer system do not look alike. Build the fields and the inspection forms to match, with required fields, dropdowns, and choice lists you maintain once and reuse everywhere.

✓Photos and GPS on the record. Crews attach photos as they work, and a location field takes a live GPS fix with the accuracy shown on screen before they commit it.

✓Work orders that mean something. A real object with a form, a target list, and a crew. Several programs can run on the same assets at once, each with its own form and its own count.

✓Full asset history. Every inspection, repair, and reading on the asset's own timeline, and a printable history report for any asset.

✓Code enforcement on the same parcels. Complaints, cases, violations cited from your own chapters, and notices whose compliance dates are counted by rules your office sets. The parcel keeps its own file the way every other asset does.

✓Roles and department scoping. Admins, office, and crews each see what their job needs, and a department can be scoped to its own maps.

✓Style the map yourself. Color assets by any field, pick from a library of municipal icons, and group your layers the way your department thinks about them.

✓Hosted in the United States. On AWS, encrypted in transit. If your IT person has questions, we answer them in plain English.

Built for the departments that own the pipes, the roads, and the trucks.

Highway, DPW, and parks

Culverts, signs, guide rail, catch basins, trees, and plow routes. One map from the superintendent's desk to the truck, without hiring a GIS department to run it.

Water, sewer, and stormwater

Hydrants, valves, mains, manholes, and lift stations. Flushing, camera work, and condition inspections keep the system map current as the work happens, and the service history stays where anybody who asks for it can find it.

The code office down the hall

Complaints, cases, violations cited out of your own chapters, and notices whose dates are counted by rules that office sets. It runs on the parcels your crews already work, so the village buys one system instead of two.

How it works for the code office

Inspection contractors

CCTV, manhole condition, smoke and dye, SL-RAT, root control. Run every inspection type on one set of assets and hand the client a deliverable their system can take.

Rule-based inspection forms

See your system on the map.

Send us a spreadsheet, a shapefile, or whatever your records look like today. We will put your assets on a live map, run one job all the way through to a finished record, and give you a price in writing. Thirty minutes, on your screen.

Send us what you have

Or write to info@civimax.com and tell us what you are working with.