Large addresses often need more than one pass in a night, and the usual way to plan that is two routes that both include the address: one crew early, another later. Sending both routes on the same dispatch does what you would want, and the wording for it is one stop, two visits.
What the office sees
The address appears once on the dispatch. It is one stop, in one place, with one set of notes, photos and complaints, and it becomes one invoice line, not two.
Beside it is a badge counting the passes: 1/2 means the address is planned for two visits and one of them is done. Hover it for the explanation, and under it one line per route: where that pass stands and when it ran. The stop itself keeps showing as in progress until the count is full.
Open the stop and the usual Check In and Check Out pickers are not there; a note says the address has several passes and points you to Time at the address, where each pass is listed with its route, its driver and its times, and each open pass has its own pickers and a Complete pass button. Passes are closed one at a time from the web, and the stop follows from them; the steps are in complete, mark unable, remove or restore a stop.
What each driver sees
Each crew sees the address on their own route, and it stays open work for them until they have registered it. The first crew finishing does not tick the address off for the second one, and a driver who runs both routes registers twice, once per pass.
Everything the driver does (start work, check in, check out, confirm, mark unable) lands on their own pass. That holds for anyone the app lets register work there, not only drivers with an accepted place on the crew: an administrator driving the run, for one, lands on the pass of the route they are on, and somebody on none of the routes takes the earliest pass still open. A registration never closes the stop while leaving its pass open, so a finished run does not linger on the phone's Home as started. Photos, notes and the stop's history stay shared, because they belong to the address rather than to one visit.
When the stop is done
The stop is completed once every planned pass is registered:
- All passes completed: the stop is completed and bills normally.
- One crew cleared it, another could not: the stop is completed. An address that got done is done, whoever managed it.
- No pass managed it: the stop is unable, and it does not bill.
The stop's check-in is the earliest arrival of any pass and its check-out the latest departure, so the times you see on the stop cover the whole night's work on that address. While a planned pass is still open the stop shows In progress and no check-out of its own, whether the other pass was closed by its crew or by the office.
What it bills
One line, whatever the address is priced by. For an hourly address the quantity is the sum of the passes, not the stretch between them: two visits of 45 and 30 minutes, four hours apart, bill 1.25 hours, not 5.5. See what makes an invoice line appear.
If the second crew never comes
Nothing bills while a pass is open, so an address waiting on a crew that will not arrive holds up its line. Close it from the web: open the stop and, under Time at the address, give the open pass a check-out and press Complete pass. When that was the last open pass the stop completes on its own. If nobody is going to do that pass at all and the first crew's work is not enough, Mark Unable on the stop settles every open pass with it, and completing the whole dispatch does the same. See completing and correcting a stop.
Two runs, not two routes
This is about one dispatch. Sending the same address twice in two separate dispatches is a different thing: two runs, two stops, two invoice lines, which is the right answer when a second storm arrives in the evening. Why your dispatch was merged explains which of the two you are about to get.
Older dispatches
Addresses dispatched before this was built have a single pass and behave the way they always did: one registration closes the stop. The badge only appears where more than one pass was planned.