Stops and sequencing

A stop is one place the driver visits inside a trip: an address, a position in the route, and the work to be done when they get there. Stops are what the driver app walks through and where proof of delivery is captured.

This page covers the route as a whole — how its order is stored, how you change it, and what each stop holds. Building one from scratch is covered in the trip wizard.

On screen, stops are numbered 1, 2, 3 and so on. That number is a position: the stop’s rank within the route, recalculated whenever the order changes. It is what the driver app shows, what an error message quotes, and what you should use when talking to a driver on the phone.

Underneath, each stop stores a sequence_number that goes up in tens — 10, 20, 30 — so a stop can be slotted between two others without rewriting every row after it. Those two numbers are not the same, and the gap-based one is never shown to a user.

Locking a stop pins it to its place. Use it for the fixed points a route is built around — the 09:00 hospital delivery, the depot return that has to be last — so everything else can be rearranged around them. A lock also protects the stop’s contents: saving a route leaves a locked stop’s own fields exactly as they were.

Everything below a stop’s name and address is optional. A type is not: a hand-added stop starts with none, and linking a destination fills the name, address and coordinates but deliberately not the type — a pickup silently saved as a delivery is worse than a card that says the type is missing.

A route is saved as a whole, not stop by stop. Cooriroo takes the list on screen as the complete intended route: removed stops are deleted, kept stops updated, new ones created, and every position rewritten — in one operation. If any part fails, none of it is applied, so you can never end up with the new stops added and the removed ones still there.

The save is also checked against the version of the trip your page loaded. If someone else changed the trip meanwhile, it is refused and you are asked to refresh rather than silently overwriting their work.

Once a trip is en route its stops advance on their own. Each starts pending and moves through en route, approaching, arrived and servicing to departed. Approaching and arrived are usually set by the geofence rather than by hand.

Three endings close a stop early:

• Skipped — deliberately not done, always with a reason. A required stop can only be skipped by an admin.
• Failed — attempted and unsuccessful, with a reason. A failed stop can be retried, which appends a fresh copy of it to the end of the route linked back to the original, so both attempts stay on the record.
• Cancelled — called off before the driver set out.

Departing a stop is gated on its work. Optional tasks left undone are skipped automatically; required ones are not, and the driver is told which are outstanding. When a stop departs, the next pending stop moves to en route by itself — the driver never has to say they are on their way.