Skip to content
AssetLink

Roads · $125 per month

Your roads, without building a road layer.

Roads starts from Census road data that we load for your county, already cut into blocks between intersections. Draw where the crew worked and the record names the streets and blocks it touched. Say which roads are yours and rate them in your own scale, on the same map. Nothing to digitise first.

The extent belongs to the work order

A pothole is a point. Patching Elm from Main to Oak is a line. Crack-sealing four streets in one shift is four stretches on one work order. A parking lot or an intersection is an area. You draw what happened; the record holds that shape, and the blocks it ran along are attached to the work order, so a block’s history lists every job done on it.

Asset-first platforms cannot do this. They make you attach work to pre-cut segments that never line up with where the crew actually stopped, so the record is always approximately wrong.

Street names attach themselves

When the extent is saved, the streets it runs along are resolved against Census road data that we load for your county and maintain. You never edit that data and never import it.

This matters more than it sounds. A name someone typed is N Main St on Monday and North Main Street on Thursday, and no report can group them. A resolved name is the same name every time.

The crew went further than planned. Push the line down the block.

A saved extent can be extended afterwards. The drawing reopens with the last stretch back under the cursor, so a few more clicks lengthen it rather than starting over — and the street names are resolved again from scratch, because a longer job may have run onto another street.

Say which roads are yours

Mark a block, a whole street, or every block inside an area you draw as ours or not ours. A block nobody has answered for stays unanswered, which is different from no. Add the surface, width, lanes and the date it was last resurfaced, in surface words your town chooses.

Rate them in your own scale

A condition survey is an inspection: one survey rates many blocks, each with its own rating and the distresses the rater saw. The scale is yours — its range, its decimals, its bands and their names. PASER is where it starts, not a rule. The map colours every block by your bands, and each rating keeps the scale it was made in, so changing the scale later rewrites nothing.

Sections, and the inventory you already keep.

If you manage roads by section, name your sections and put blocks in them. A section is rated as one thing, and each of its blocks shows the newer of its own rating and the section’s.

Already keep a road inventory? Upload it as a zipped shapefile, GeoJSON, or a CSV with the geometry in a column. It is matched onto the blocks and shown to you before anything is written. A feature that matches nothing is listed, never guessed at, and importing the same file twice changes nothing.

What Roads does not do

Worth stating plainly, because it is the usual next question.

No PCI, no deterioration curves

Roads keeps the ratings your raters give. It does not compute a PCI, predict how a road will age, pick treatments or plan a budget. That is pavement management, a different discipline, and pretending otherwise would be selling you a number you could not defend.

No quantities from geometry

The shape you draw is a visual record of where, never a source for how much. Drawn extents run long — crews extend and rarely trim — so tonnage comes off a measuring wheel, not off the map.

No county we have not loaded

The Census road data is loaded one county at a time. Until yours is, the Roads map has no streets for your town, so tell us your county when you start and we load it.

Draw a week of work and see.

Seven days, no card. Tell us your county first, so your streets are there.