PaveKeep Book a walkthrough

See it on a real network

No council uses PaveKeep yet, so everything below runs on a demonstration network: 9 roads, 94 segments, real geometry, real surveys — and 8 segments nobody surveyed, which still report as unknown rather than as zero.

That last detail is the point of showing you a demonstration rather than a brochure. The gaps are in it.

7 cuts, about 4 minutes in all

Silent and caption-led, so they work with the sound off. Every screen in them is a capture of the product running on the demonstration network below — none of it is a mockup, and none of the figures were typed. Start with the overview; the rest go deeper on one part of it.

Road asset management, in one minute — what this is, who it is for, and where it is up to. Start here. 60 seconds.
Decide which roads to fix next, and prove it — the whole argument, end to end. 34 seconds.
See the network — a road register is rows; roads are on the ground. 20 seconds.
What to fix, in what order, at what cost — and each surface scored by the method that fits how it fails. 20 seconds.
Every number explains itself — where a figure comes from, in the product's own words. 41 seconds.
Model the cost of doing nothing — the same network five years on, unfunded. Modelled, and labelled as modelled. 26 seconds.
The documents you file anyway — a committee paper and a brief, carrying the same four figures. 28 seconds.

The network, on a map

Every segment carries its own condition, and the legend has a row for not surveyed. A road nobody has looked at is grey — not red, and not green.

The demonstration network coloured by condition, with a legend that includes "not surveyed"

Open any segment

It says what was seen, when, and by which method — the distresses recorded, the chainage they sit at, and the arithmetic behind the score.

A segment's detail panel: condition, survey date, method and the arithmetic behind the score

What to fix, in what order, at what cost

A ranked, costed list. Each row carries the treatment, what it costs, what the condition becomes afterwards, and what the network average would be if the programme ran to that line.

The works programme: a ranked list with treatment, cost, condition after, and cumulative spend

Or ask it the other way round

Name the condition you want every road to reach and it prices that standard — what it would cost, how many segments and how many kilometres it touches, and where the network average lands afterwards. Including the floors that cost nothing, because the network already meets them.

The cost-to-target table: each PCI floor priced, with the segments, length and resulting network average

Where the numbers come from

Every threshold, rate and rule the software uses, read live from the council's own configuration rather than from a brochure. Including the ones it does not use yet, which are on the same page.

The method statement: thresholds, rates and rules, with the model build they were read from

What a council actually sends

The same data becomes a committee paper, a short brief for a general manager, and a grant submission — each written for the person who reads it.

The real files are on the proof page, not as pictures but as the PDFs themselves.

A page of the committee booklet, generated from the demonstration network

Seeing it on your own network

A walkthrough of the demonstration network takes about twenty minutes and is the fastest way to find out whether any of this is useful to your council. There is nothing to install and nothing to sign.

Accounts are by invitation — self-service sign-up is switched off in the product’s own configuration, so a council gets one by asking.

How to reach a personSign in