How it actually works
From an empty account to a defensible works programme is 13 steps. This is all of them, in order, with what you can see at the end of each — not what the software does, but what you can point at and say that happened.
It is read from the same spine the in-product tutorial is built on, so it cannot describe a screen that has been renamed or a step that has been removed.
1. Get in
You are in, and the product says which council and what you may do.
2. Find out what you are allowed to do
The abilities your role carries.
3. Load the road network
Roads, lines and segments appear; the import is listed in the ledger.
4. Load condition
A survey run is filed; segments carry a score; the unsurveyed length falls.
5. Look at what you have
The network on a map, coloured by condition.
6. Find out what it could not see
The unsurveyed length, stated rather than averaged away.
7. Set the rules, or accept the defaults
The setting changes, and the change is on the record with who made it.
8. Run a programme against a budget
A ranked list of works within the budget, and what it could not see.
9. Ask what a different budget would buy
A saved scenario, and the condition the network ends at under it.
10. Produce the documents you have to file
A booklet, stamped with the data and configuration it was made from.
11. Record work that actually happened
The work is on the ledger with its cost and who funded it.
12. Come back next year
The new survey becomes current; last year stays on the record.
Infinity. Undo a survey you should not have filed
The run is retracted and stays on the record; condition falls back.
Nothing above needs a consultant in the middle of it, and nothing above is a screen that exists only in marketing.
See also: what PaveKeep cannot do yet.
Accounts are by invitation — self-service sign-up is switched off in the product’s own configuration, so a council gets one by asking.