::section hero # Show your working on road renewal Choosing which roads to fix is choosing which roads to let get worse. PaveKeep turns a council’s road list, survey results and budget into a ranked, costed works programme — and keeps the trail that shows why each road is where it is. Built for small and regional councils: the ones with a real road network, a reporting obligation, and no asset-management department. ::cta /see-it See it on a real network ::cta.ghost /about Book a walkthrough ![The demonstration network’s condition map: every segment coloured by its rating, with the unsurveyed road drawn in grey rather than scored.](/media/map-condition.webp) :: ::section stats - **11** things it does, read from the product’s own registry — not from a brochure - **3** of them unfinished, and listed as unfinished - **8** claims that can be shown working, each with the screen or document behind it - **94** segments in the demonstration network, including 8 nobody surveyed :: ::section cards ## Three rules it is built on ### Every number is traceable Any figure PaveKeep produces can be followed back to the survey it came from, the setting that shaped it and the arithmetic that produced it. The software explains itself rather than asking to be trusted. ### Unknown stays unknown A road nobody has surveyed is reported as unknown. It is never scored as zero, and never quietly dropped out of an average that is then presented as the network. This is the one councils test us on. ### It works beside your systems The whole network exports in a standard mapping format that opens in the council’s own GIS. Nothing is locked in, and nothing has to be replaced first. :: ::section split ## *Where did this number come from?* That is the question an auditor asks, a funding body asks, and a councillor asks about their own street. A spreadsheet cannot answer it and most software answers it with a support ticket. Every figure in PaveKeep carries a method statement: the inputs, the settings in force on the day, and the steps between them. It is the same document whether the number is on a screen, in a committee paper or in a grant application. ![A method statement: the inputs to one segment’s score, the settings in force, and each step of the arithmetic between them.](/media/method-statement.webp) :: ::section cards ## What it does These are the 8 capabilities the registry calls finished, in its own order. 3 more are built and incomplete; they are on a page of their own with the limit on each. ### 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. ::cta /what-it-does Every capability, in plain words ::cta.ghost /what-it-cannot-do-yet What it cannot do yet :: ::section note ## The honest state of it **No council uses PaveKeep yet.** It runs on a full demonstration network — 9 roads, 94 segments, real geometry, real surveys, including 8 segments nobody surveyed that still report as unknown. Anything here that reads like a customer reference is a mistake; there are none to make. There is also a page listing every feature that is unfinished and every commitment that is an intention rather than a fact. It exists because a limit a buyer discovers in week three of a pilot costs more than one they read on the way in — and because every other claim here is easier to believe once it exists. ::cta.ghost /what-it-cannot-do-yet Read what it cannot do yet :: ::section split ## From a road list to a programme you can defend Thirteen steps from an empty account to a ranked, costed works programme, each one with something you can point at afterwards. The page that lists them is generated from the same spine the in-product tutorial is built on, so it cannot describe a screen that no longer exists. ![The works programme: segments ranked by the treatment chosen for them, with cost, funder and the year each falls in.](/media/works-programme.webp) ::cta /how-it-works How it actually works ::cta.ghost /proof What can be shown, not just said :: ::section cards ## Writing about road renewal Plain-language articles for council engineers, asset managers and finance officers. Every figure carries its source and year, and figures from US research are labelled as US evidence. ### [Showing a council what a budget buys, and what the next one down costs](/knowledge/what-a-budget-buys) Condition charts do not win the budget argument. A scenario pair, with the roads named, is what changes it. ### [How road deterioration is modelled, and what a model cannot tell you](/knowledge/how-deterioration-is-modelled) Projecting a network ten years forward is arithmetic, not prophecy — and most councils hold two of the five inputs. ### [Putting road condition on a map](/knowledge/road-condition-on-a-map) A spreadsheet of segment scores answers a question nobody in the room is asking. The question is which roads. ::cta.ghost /knowledge The whole knowledge base :: ::section cta ## Have a look at the demonstration network 9 roads, 94 segments, real geometry and real surveys. A walkthrough of it 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. Email [sales@pavekeep.com.au](mailto:sales@pavekeep.com.au), or read the argument first. ::cta /about Book a 20-minute walkthrough ::cta.ghost /trust Hosting, backups, insurance and the rest Accounts are by invitation — self-service sign-up is switched off in the product’s own configuration, so a council gets one by asking. :: --- Source: https://pavekeep.com.au/ · PaveKeep · bound content