PaveKeep Book a walkthrough

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. Each step opens: the page under it is the tutorial a council is taught from, which is a longer and more honest answer to how much of my week is this than a list of titles.

Not sure any of this is the right job at all? Why choosing which roads to fix is hard takes the question on its own, including what councils do instead and when each of those is the better answer.

1. Get in

You are in, and the product says which council and what you may do.

4. Load condition

A survey run is filed; segments carry a score; the unsurveyed length falls.

These pages are a rendering of tutorial version f9a7ff6fe082. The repository is the source; this is an export of it, and the version moves when the tutorial does rather than when the repository does.

See also: what PaveKeep cannot do yet.

Nothing above needs a consultant in the middle of it

And nothing above is a screen that exists only in marketing.

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

See the steps runningSign in