What PaveKeep does

There are 11 things PaveKeep does. This page is generated from the product’s own capability registry, so it is a list of what is built rather than a list of what somebody decided to say. Anything unfinished carries its limit in the same sentence as the feature, which is the only arrangement that survives being quoted.

Read from the product on the day this page was built. The registry behind it last changed 2026-09-12.

Finished

Budget planning. Put in a budget and a number of years, and see what it buys: which roads get done, what condition the network ends up in, and what a different budget would have bought instead.

The works programme. A ranked list of what to fix, in what order, at what cost — with the reason each road is on the list, and how much it would take to reach a condition target.

Statutory and funding packs. The documents a council has to produce: what the network is worth, what work happened and who paid for it, and the state of the network as it stood on a chosen date.

Getting data out. The whole network in a standard mapping format, so it opens in the council's own GIS. Nothing is locked in.

Work actually done. A record of completed work with its cost, who funded it, and the agreement or disaster declaration it happened under — which is what an acquittal or an audit asks for.

Condition over time. How the network has actually changed between surveys, rather than a single snapshot.

Council-ready documents. Three finished documents from the same data — a committee paper, a short brief for a councillor or general manager, and a grant submission — each written for the person who reads it.

Looking ahead. What the network will look like in five or ten years under different spending levels, so a council can show the cost of doing nothing.

Not finished

3 capabilities are built but incomplete. They are listed here with the same wording they carry everywhere else.

Gravel and unsealed roads. Unsealed roads are scored on their own terms rather than borrowing a sealed-road method. They are handled as one group. We cannot yet report gravel, formed and unformed lengths separately, which some state returns ask for.

Lane-by-lane condition. Where a council surveys lanes separately, each lane keeps its own condition and its own recommended treatment. We can show a lane needs different work; we cannot yet price it, because nothing records how wide a single lane is.

Learning what treatments achieve. Comparing condition before and after work to estimate what a treatment actually delivered. Modelled from a small number of observations rather than measured, off unless a council turns it on, and not a basis for a spending decision yet.

What it can be shown doing

Eight things can be demonstrated on a working network rather than described.

P1. Every number can be traced back: which survey, which setting, which piece of arithmetic. The software explains itself rather than asking to be trusted.
P2. A sealed road, a sprayed-seal road and a gravel road are scored by different methods, because they fail in different ways.
P3. A road nobody has surveyed is reported as unknown, never as zero and never quietly averaged away. This is the one councils test us on.
P4. Heavy vehicle traffic changes how fast a road is expected to wear out, and the change is visible rather than buried in a model.
P5. The network as it stood on any past date — what an auditor or a funding body asks for when they reopen a claim.
P6. A chain from the survey, to the work done, to who paid for it, to the declaration it happened under.
P7. It sits beside the systems a council already has rather than demanding they be replaced.
P8. From a spreadsheet of roads to a defensible works programme, measured, without a consultant in between.