# Load condition *Whose job: the surveyor. You should see a survey run is filed; segments carry a score; the unsurveyed length falls.* ## What you are doing You are telling PaveKeep what condition the roads are in, from a spreadsheet that names a road and a stretch of it — "Cooma Road, 0 to 400 m, 55". This is the door for a council whose condition data came from a drive-around, an inspector's notes, or a consultant's report typed up afterwards. It needs no identifier from PaveKeep at all. It is usually the job of whoever did the looking, or whoever was handed their notes. If a consultant produced the report, somebody at the council still has to decide it is fit to file, because filing it is what makes it the council's statement about its own network. ## What PaveKeep does with it Each row is resolved to a road by its name, and then to the segments that fall inside the chainage range you gave. The score is written onto those segments, and a dated history point is recorded against each one with your name on it — so a figure can always be traced back to the upload that produced it. The whole upload is filed as ONE SURVEY RUN, dated from the file rather than from the day you uploaded it, with your name on it. That is what makes next year's survey a comparison rather than an overwrite — the previous run stays, and the condition trend is the difference between them — and it is what makes this reversible: a filing can be retracted as one thing. The unsurveyed length falls by exactly what you covered, and the part you did not cover goes on being reported as unknown. ## What it will not do - **The method** — A condition index is a summary, not a diagnosis. Two roads scoring 55 can need different work, for reasons a single number cannot carry. The score tells you where to look and roughly how urgently; it does not tell you what is wrong. - **The product** — Road names are matched, and a name that matches two roads is REFUSED rather than guessed — on every row it affects, not just the first one, so one upload tells you everything you need to fix. A name that matches nothing is reported the same way. Neither is written and then corrected later. - **What you have not got yet** — It can only score what your spreadsheet covers. If you drove the sealed network and not the gravel, the gravel stays unsurveyed — and every figure built on this will say so rather than quietly averaging over the gap. - **Your role** — Filing condition needs the condition-entry capability. Retracting a filed survey is a separate capability again, deliberately: entering what you saw and deciding a filing should be withdrawn are different acts, and the surveyor role carries the first and not the second. - **The product** — A score is a number you gave, not a measurement this product derived. There is no distress behind it — no potholes, no cracking, no extent — so the treatment it leads to is coarser than one from a distress survey, and the product cannot tell you WHY a road scored what it did. That is the trade this door makes for costing nothing. ## How you know it worked **Before:** a council with a network loaded, and a spreadsheet of `road_name`, `chainage_from`, `chainage_to`, `pci`. **Do:** Import Data, Street + Chainage (CSV), choose your file. **After:** the screen reports how many segments were updated and lists any row it could not resolve, with the reason. Rows it could not read are skipped and the rest are still applied, so a file with three bad rows leaves you three rows to fix. The map colours. The unsurveyed figure on the dashboard falls. **If it was wrong**, void the run from the Surveys tab. Its segments fall back to whatever the previous survey said, or to "not surveyed" if this was their first — never to a score nobody measured. The run itself stays on the record with who filed it and who retracted it, which is what an auditor asks for and the reason this is a retraction rather than a delete. **Hand to:** the engineer who will run the programme. What they need from you is not the file — it is the date the survey was done and how much of the network it covered. --- **If it went in wrong:** this step can be undone, and the undoing stays on the record rather than erasing what happened. A council reads these same four sections inside PaveKeep, beside the screen that does the work — the same sentences, held to the same source in both languages. [← Load the road network](/how-it-works/network-import) · [Look at what you have →](/how-it-works/network-look) · [All 13 steps](/how-it-works) --- Source: https://pavekeep.com.au/how-it-works/condition-chainage · PaveKeep · derived content