Docs
Start
The first route, the people on it, and what to ignore until Tuesday has happened once.
Start with one route that already happens. Give it the name the crew uses, including the day if the day is part of the name. “North Basin · Tuesday” is a better name than “Route A.”
Put the people on it before you put the assets on it. An inspector records. A supervisor can assign and close. An administrator can edit the route and the limits. On a first week, one administrator is enough, and it should be someone who walks, not only someone who buys software.
Add stops in walking order. Each stop needs an asset name the crew already says, a place in ordinary words, and at least one check. A check is either a reading with a limit or a condition written as a sentence. “Ok” is not a condition. “No visible drip at the gland” is a condition.
Write the access note while the person who knows it is in the room. Gate codes go in the note only if your own rules allow it. If they do not, the note should say where the code lives, not the code.
Load the route to the device on the office network, before the yard. Walk it once with the notebook still in the truck. Mark what the route got wrong. Edit the route before you add a second one.
Ignore, for now, the assets you do not walk, the desire for a map, and any report other than the pack for this route. The pack is how you know the first Tuesday worked. Routes is the next page if the stops are the part you are unsure about.