Docs
Routes
Order, notes, copies for a shutdown week, and what a normal reading looks like on the stop.
A route is an ordered list of assets and the checks you do at each one. The order is the order of the walk, including the annoying parts. If you pass the gate before the intake, the gate is stop one even when the intake is the point of the trip.
Notes
Each stop can carry a note: access, a hazard, a tool, a neighbor. Notes are for the person who does not do this route every week. Write them as instructions, not atmosphere. “Shoulder-height conduit, hinge side” is a note. “Be careful” is not.
What normal looks like
A limit belongs on the check. For a number, set the bound. For a condition, write the passing sentence and let a failure open a deficiency. Do not hide the limit in a PDF somewhere else. The person on the embankment will not fetch it.
Where a qualitative reading is all you have, pick words you can compare next week. “Drip, about one per second” can be compared. “Looks worse” cannot. The journal note on readings is the longer argument.
Copies
Shutdown week, a drill, or a flood day is not a reason to edit the Tuesday route into something you will forget to undo. Duplicate the route. The copy keeps the notes. Changes to the copy stay on the copy. That is release 2.8, and it is the difference between a special week and a route that quietly rots.
Done
A route is finished for the day when each stop has a record or an explicit skip with a reason. A skip without a reason is an unfinished stop. The pack will say so.