How each stop records its planned window, arrival and departure, what Orbit Cockpit shows the driver at a stop, on the tour map and about the shared location, and the proof of delivery captured at the stop.
Was this article helpful?
Did not find your answer?
Ask Luna, or write to our support team.
Note
A Stop is a single pickup or dropoff on a Tour. Each stop carries its planned arrival and departure times, the actual times recorded in Orbit Cockpit, and any proof of delivery captured at the stop.
A Tour is an ordered list of places a driver visits, and each place on that list is a Stop. A stop is either a pickup, where cargo is collected, or a dropoff, where it is delivered. Only a Tour has stops: an Order or a Shipment on its own does not. When you route a Shipment onto a Tour, its pickup and its dropoff take their places in that tour's sequence of stops.
Every stop tells you when the driver was meant to be there and what happened during the visit. As the driver works through the Tour in Orbit Cockpit, each stop fills in with its arrival, departure, and any proof of delivery required at that location. In Orbit MissionControl you can read the plan, the actual times, and the proof.
Key highlights:
Stop is one pickup or dropoff in the Tour's ordered sequence of visits.Tour on a map, with the route still to drive.Think of a Tour as a route with a running order of places to visit. Each place in that order is a Stop. A pickup stop is where the driver collects the Load; a dropoff stop is where they hand it over. A simple tour that moves one Shipment from Berlin to Lisbon has two stops, the Berlin pickup and the Lisbon dropoff, in that order.
When more than one Shipment collects from or delivers to the same address, Orbit combines them into a single stop, so the driver makes one visit rather than several to the same place. Each shipment keeps its own contact, company, and documents under that shared stop, so nothing is lost by grouping them.
When the driver opens a stop in Orbit Cockpit, the top of the stop screen shows who and where: the company or the name of the combined stop, the loading point if there is one, the address and the stop's time window.
The stop screen shows one stop at a time, and a swipe moves to the stop before or after it. Below the top, the stop's sections follow on a grey page, each with its title and its content on white cards: the stop's Comment, the loads that stay on board or were carried back, Unload, Load, the stop's Tasks, Stop Documents and Proofs of delivery. A section with nothing to show is left out.
At the bottom, above the tab bar, a bar holds the button for the stop: Arrived on the way to it, Continue once the driver is there, and Complete Tour at the end of the tour. A stop further down the route reads Stop Is in the Future. At a stop the driver has reached, the red × beside the button opens Why Did This Stop Fail?. Where the driver records a status for each load, a stop with loads has no ×: a load that could not be handled is recorded in the load status panel instead.
The country appears after the city only when the stop lies in another country than the carrier's, so a stop abroad stands out at a glance.
Below the time window, one line shows the site's opening hours for the day of the stop. When a stop has a loading point with its own hours, those hours apply. The line reads:
If the plan expects the driver to wait at the stop, the same line adds the waiting time, for example "approx. 15 min waiting time". A stop without opening hours and without waiting time has no such line. See Opening Hours for Locations for how opening hours are set.
Below the contacts, a box collects the arrival hints of the stop's shipments, such as which gate to use. The same hint given on several shipments appears once.
Four round buttons sit under the address:
| Button | What it does |
|---|---|
| Navigate | Opens the stop in the navigation app the driver chose. Without a chosen app, Orbit Cockpit lists the navigation apps on the phone, with Copy Address or Coordinates as the last option. |
| Call | Calls the stop's contact. With more than one phone number at the stop, the button shows how many and opens Who do you want to call? |
| Copy | Opens What would you like to copy? with Copy Address and Copy Coordinates, for a navigation app the driver types into by hand. |
| Map | Opens the tour map on this stop. See The tour map. |
Call appears only when the stop has a contact with a phone number. In Who do you want to call?, each row shows the contact's name, the company or Site, and the number. A tap on a row starts the call; Cancel closes the list.
The first navigation app the driver picks from the list is remembered for the next stops. The driver changes it, or sets Always ask, under More > Navigation app. A long press on the address opens the same choice as Copy.
Under the buttons, Orbit Cockpit shows whom the driver can reach at the stop:
The driver calls with Call. A contact with only a name is shown but cannot be called.
Unload and Load list the loads of the stop, one card for each company the loads come from or go to. The head of the card names the company, such as From ACME Ltd or To Orion Industries, and adds up its loads, for example 6 units · 1,450 kg.
At a stop with several shipments, each Shipment in the card starts with its own head: Shipment 1 of 2, its references and units, and at a dropoff the sender, for example From Orion Industries. The sender is the company the shipment's goods were picked up from, as the Tour records it. The head leaves the sender out when the head of the card already names it, and when the tour names no sender for the shipment.
Each Load takes one row:
Badges under the row point out what needs attention: Dangerous goods · UN 1203 (or Dangerous goods without a UN number) and Waste or Hazardous waste with the waste code. Where your organisation records a status for each load, a completed stop shows a green check or a red cross after each row, with the failure reason, the deviation noted on a successful load, or Note where only a comment was left. A load that could not be loaded at its pickup reads Not Loaded in red at its delivery stop. A speech bubble on a badge means a comment sits behind it.
A tap on a load opens its details: the status with the reason or deviation and the full comment, the notes at loading, Load with Dimensions per unit, Weight, Stackable and Reference, and Route with the Pickup and the Delivery. At a stop with several shipments, Route also names the shipment the load belongs to. A load with dangerous goods or waste adds a group with their details. The details only show the load and change nothing.
Two more sections can come first. Stays On Board lists the loads of a cancelled shipment that ride along past this stop and must not be delivered there. Carried Back Loads lists loads that were refused at a later stop and are unloaded here, one card for each stop they came back from, each load marked Carried back · Refused with the reason.
The tour map shows all stops of a Tour on a map, together with the route between them.
The tour details in Orbit Cockpit show a small map of the route at the top of the Route section, with Open Map in the corner. It appears in every tour status. Without a connection, Map not available offline covers the preview, but a tap still opens the map. When no stop has coordinates, the grey box still opens the map.
A tap on the preview opens the map on the next stop of the Tour, or on stop 1 when no stop is next, such as on a finished tour. Map on a stop opens it on that stop.
Every stop has a numbered marker:
Stops at the same place share one marker. A depot at the start and at the end of a seven-stop tour shows as "1 · 7".
The route still to drive is drawn in your highlight colour, the part already driven in grey. Where the roads cannot be loaded, the map draws straight dashed lines between the stops. Without a connection, it also shows Offline: straight lines instead of roads at the top, and loads the roads once the phone is back online. A stop without coordinates gets no marker, the line runs from the stop before it to the stop after it, and a hint such as 1 stop without coordinates says how many are missing. Its card stays in the list below. The highlight colour is set in the whitelabel settings.
Below the map, one card per stop shows its number, the company, the address and the time window. While the tour runs, each card shows its distance from the stop before. While the tour is not running, each card says instead whether the stop is a Pickup, a Delivery or both. Cards of stops already done are grey.
A swipe moves to the next card and the map to its stop. A tap on a marker brings its card to the front. Each card has two buttons:
When the tour has drive times, a line at the bottom sums up the tour like the tour details. While the tour runs, it shows how many stops are left, with their distance and driving time.
Tour is Running and only when Orbit Cockpit is already allowed to use the location. The map never asks for location access itself.The map shows the tour and does not change it. The stop order is not changed on the map. Where the driver may change the order of the stops, they use the skip button at the top right of the stop screen, which asks Where Should This Stop Go?
Every stop holds two kinds of time, and it helps to keep them apart.
The two are read together to judge how a Tour is running: an arrival later than the planned window tells you a stop ran behind, while a stop with no arrival yet has not been reached. A planned window is never an arrival time; it is the intention, not the event.
When automatic stop detection is enabled and Orbit Cockpit has background location permission, it records arrival when the driver reaches a stop. The arrival appears in the stop view, with an Undo option for one minute. The driver can still use the stop controls in Orbit Cockpit.
Orbit Cockpit records departure automatically when the driver leaves a stop and all required loads and proofs are complete. If something is missing, Orbit Cockpit sends a notification and shows what remains on the stop. After the driver completes the missing work, they can select Ready to depart to record the departure.
If background location is not allowed, the tour can still start, but automatic stop detection is unavailable. Orbit Cockpit shows Automatic stop detection off: background location not allowed under Start Tour. The driver can continue using the stop controls to record arrival and departure.
Orbit Cockpit shares the driver's location while a Tour the driver started on this phone is Running, so that dispatch and the customer see where the tour is. It stops on its own after the tour. The page under More > Location opens with a card that names the state and its reason:
| Card title | When | What the driver can do |
|---|---|---|
| Your Location Is Being Shared | A Tour runs on this phone. The card shows the driver's own position on a small map, since when the location is shared and the Tour itself. | Pause GPS pauses the sharing for 1 hour, 4 hours, 8 hours or until Monday 06:00. |
| GPS Paused Until … | The driver paused GPS. The Tour keeps running, but no location is shared until the end of the pause. | Resume Now ends the pause early. |
| Location Only While the App Is Open | The access allows the location only while Orbit Cockpit is open, and the location is still being shared while the app is open. When the driver locks the phone, it stops. | Open Settings leads to the access. Pause GPS sits in a row of its own below the card. |
| Location Is Not Being Shared | No Tour runs on this phone, Orbit Cockpit may not read the location at all, the access allows the location only while the app is open and the sharing never started, or Orbit Cockpit cannot read whether GPS is paused, so it sends nothing. | With a running Tour: Open Settings when the access is missing, and with "While Using the App" there is no Pause GPS row. When the GPS pause cannot be read, the card offers no action. Without a running Tour, Pause GPS sits in a row of its own below the card. |
A tap on the Tour opens the tour. The Location row under More names the same state on a second line: Sharing, Paused Until …, Only While the App Is Open or Not Being Shared. Without a running Tour it has a second line only while GPS is paused.
Below the card, the Permission block shows whether Orbit Cockpit may read the location always and whether the location is precise. A row that is not in order has an arrow: a tap on it asks for the access or opens the system settings.
There is also a third, forward-looking time while a Tour is on the road: the Expected Arrival, a live estimate of when the driver will reach an upcoming stop. That estimate is covered in its own article, Live Tracking & Expected Arrival, because it behaves differently from the planned window and the logged fact. In short: the planned window is the intention, the Expected Arrival is the live estimate, and the logged Arrival is what actually happened.
Proof of delivery is captured at the stop, at the moment of the visit, by the driver in Orbit Cockpit. It is the evidence that a pickup or dropoff really took place: a photograph of the goods in position, a recipient's signature, a signature with the signer's name, or a scanned document.
A stop can carry proof requirements, for example one signature and one photo before the delivery counts as complete. The Proofs of delivery section of the stop in Orbit Cockpit lists the kinds of proof, always in the same order: Photo, Document, Signature, Signature with Name, Documented Signature and Scan. Documented Signature appears where the stop requires one or your organisation has set up documented signatures, Scan only where the stop requires one.
A kind the stop requires carries Required, and the counter next to the section title, such as 1 of 3 done, counts every requirement. Below a required kind, a line says what is still open: Proof is requested but not yet uploaded, or one line for each recipient where every recipient owes their own proof, such as ACME Ltd · open. At a stop with several shipments, each recipient's line names the sender below it, such as From Orion Industries: where that shipment's freight was loaded, so two shipments for the same recipient read apart. Once every requirement of the kind is met, the line reads Done. A required scan is captured while marking the loads, so its line reads Captured in the scan panel when unloading or Captured in the scan panel when loading.
A tap on a kind captures one: Take Photo or Choose from Library for a photo, the same or Choose Document for a document, the signature pad for a signature, and the handover for a documented signature. Each proof is listed under its kind, numbered and stamped with the time it was taken, such as Photo 1 · 14:41. At a stop with several shipments, a proof that belongs to one Shipment adds its recipient, such as Photo 1 · 14:41 · ACME Ltd, and below it the sender, such as From Orion Industries. Where Orbit does not know the sender, the line names the recipient only. A tap on a proof opens it. A documented signature whose delivery receipt is not ready yet reads Receipt Still Being Created and opens once the receipt is there.
A proof counts as done the moment it is captured, also while it is still uploading. Its line shows the progress, such as Uploading · 40 %, and the × stops the upload. A failed or stopped upload reads Upload Failed or Upload Stopped, its requirement is open again, and the retry button sends the same file once more, so the driver does not capture it again.
Before the driver has arrived, the section reads You can capture once you are at the stop. and its kinds cannot be tapped. Proofs already captured still open.
If a required proof is still missing when the driver taps Continue, Orbit Cockpit shows Proofs Are Missing and lists the outstanding proofs above the button; Record Proofs Now closes the message. From then on, the open required proofs in the section are shown in red, as they are when the driver leaves the stop with a proof missing.
At a stop with several shipments, each outstanding proof that one recipient owes shows the recipient's name and, below it, the sender: where that shipment's freight was loaded, its pickup stop on the Tour. When two shipments go to the same recipient, the driver opens the right handover by the sender. Where Orbit does not know the sender, the proof shows the recipient's name only.
At a stop with several shipments, Orbit Cockpit first asks which Shipment a proof belongs to, for example Photo for which shipment? It asks for a photo or a document, for a signature or a signature with name that the stop requires from each recipient, and for a documented signature, which always belongs to one shipment. Each row shows Shipment 1 of 2, Required where that shipment owes the proof, its sender at a dropoff, the references and units, and a tick once the shipment has a proof of that kind, or open while it still owes one. For a photo or a document, the last row is Whole stop (all shipments). A required signature lists only the shipments that owe it. A documented signature lists every shipment, with Required on those that owe one. A tap on a row captures at once, and Cancel captures nothing.
Where a photo or document appears depends on that choice:
Shipment and on its Order only.Shipment at the stop and on their orders.Orbit Cockpit asks for every outstanding proof before the driver can complete the stop. Where nobody can sign a documented signature, the driver records why instead (see Documented Signatures & Delivery Receipts). Orbit Connect asks too: a carrier who completes the stop there uploads the missing photos, documents and signatures first, and may continue only without the proofs Orbit Connect cannot capture, such as a documented signature or a proof for one company at a stop with several shipments. The server does not refuse a departure without its proofs: a stop completed without them keeps the gap on record. An operator sees the missing proofs on the stop in Orbit MissionControl as soon as the driver has left it, and again when reviewing the tour.
Back in Orbit MissionControl, the proofs captured at a stop appear against that stop, grouped by kind: Photo Proofs, Signature Proofs, Signature with Name Proofs, and Document Proofs, each showing when it was taken. This is where an operator confirms that a delivery was completed and reviews the evidence behind it.
In the tour details in Orbit MissionControl, a stop the driver has left without all its required proofs shows an orange warning icon right after its proof icons. Point at the icon, or move to it with the keyboard, to open Mandatory Proofs Missing. It explains that the stop has been departed and lists each missing proof on its own line: the proof type, such as Photo, or at a stop with several recipients the proof type and the recipient, such as Signature for Orion Industries.
The icon follows the tour as it runs, without reloading the page. It appears when the driver leaves the stop and disappears once the missing proofs have arrived. It counts the proofs the way the review does: per recipient at a delivery to several recipients, once per proof type at a pickup. A proof that is still uploading counts as missing until its upload has finished. See Reviewing a Tour for how proofs are counted.
A stop the driver has not left shows no warning icon, and neither does a stop with all its proofs or without required proofs. While the tour's documents are still loading, no stop shows the icon.
An empty proof list on a stop the driver has not reached yet is completely normal. It is not a missing document or a gap to chase. Proofs appear only after the visit happens, so a stop still ahead on the route simply has nothing to show yet.
The proof captured at a stop is also stored as a file you can view, download, and share, alongside other paperwork such as delivery notes and invoices. That file side (how documents are versioned, linked across an Order, Shipment, and Tour, and who is allowed to see each one) is covered in the Documents article.
A driver, Mohammad, is running a Tour for Spaceport Shipping Co. with a delivery to ACME Ltd in Lisbon. Before he sets off, he opens the map from the tour details and sees the depot marked "1 · 6", because the tour starts and ends there. The Lisbon stop was planned for a window between 13:00 and 15:00, and its stop screen reads Open today 08:00 – 17:00. On the way he taps Call, picks the warehouse supervisor in Who do you want to call? and announces his arrival. Mohammad arrives at 14:41. Under Proofs of delivery, Photo and Signature both carry Required, and the counter reads 0 of 2 done. He taps Photo, chooses Take Photo for the pallets on the loading bay, then taps Signature and hands the phone to the warehouse supervisor. The counter reads 2 of 2 done. Later, Julia, an operator watching the run in Orbit MissionControl, opens the Lisbon stop and sees a logged Arrival of 14:41 against a Planned Arrival window that opened at 13:00, together with the photo and signature timestamped to the visit. She confirms the delivery is complete without having entered a single value herself.
Stops, their planned and logged times, and the proofs captured at them are all available programmatically through the Tour they belong to. For endpoints and schema details, see the API Reference.
Because the driver hasn't reached it. A logged Arrival appears only once the visit happens. Until then the stop shows just its planned window, which is the plan, not a missing time.
The planned window (Planned Arrival and Planned Departure) is the schedule worked out before the tour moves. The Expected Arrival is a live estimate that updates while the Tour is running. The logged Arrival is what actually happened. See Live Tracking & Expected Arrival for how the estimate is calculated.
Not if the driver hasn't been there yet. An empty proof list on an unvisited stop is normal; proofs are captured at the moment of the visit. Once the driver reaches the stop in Orbit Cockpit and records the required proofs, they appear against the stop in Orbit MissionControl.
Not in Orbit Cockpit: the driver captures the outstanding proofs before completing the stop, or records why nobody signed a documented signature. Orbit Connect asks for the missing proofs as well, and lets the carrier continue only without those it cannot capture. A stop completed without its proofs is not refused, and an operator sees the missing proofs on the stop in the tour details and when reviewing the tour.
The driver has left the stop, and some of its required proofs are not there. Point at the icon to see which proofs are missing and, at a stop with several recipients, for which recipient. The icon disappears by itself once the proofs arrive, or once you add them when reviewing the tour.
Yes. At a stop with several shipments, Orbit Cockpit asks Photo for which shipment? before capturing it, and the same for a document. A proof for one shipment appears on that Shipment and its Order only. Whole stop (all shipments) puts the proof on every Shipment at the stop and on their orders.
The proof stays under its kind with Upload Failed, and its requirement is open again. The retry button next to it sends the same file again, so the driver does not have to capture it a second time.
Proofs are captured at the stop. Until the driver has arrived, the section reads You can capture once you are at the stop. Once the driver taps Arrived, or Orbit Cockpit records the arrival by itself, the kinds can be tapped.
A tap on the load on the stop screen opens its details: status, dimensions per unit, weight, reference, the route and, where they apply, its dangerous goods and waste. Nothing changes when the driver opens them.
When more than one Shipment collects from or delivers to the same address, Orbit combines them into a single stop so the driver makes one visit. Each shipment keeps its own contact, company, and documents under that shared stop.
Yes. When automatic stop detection and background location are available, Orbit Cockpit records arrival and records departure when all required loads and proofs are complete. If work is missing, it notifies the driver and shows what remains. Without background location permission, the driver can still start the Tour and use the stop controls to record arrival and departure.
Call appears only when one of the stop's contacts has a phone number. A contact with only a name is shown under the buttons but cannot be called.
The country is shown only for a stop outside the carrier's country. A carrier without a country of its own counts as based in Germany.
Orbit Cockpit could not load the roads, usually because the phone has no connection. Then the hint Offline: straight lines instead of roads says so, and the roads load once the phone is back online. Once the roads have loaded, the map keeps them while the app stays open, also without a connection.
The own position appears only while the Tour is Running and only when Orbit Cockpit is already allowed to use the location. The map never asks for the access. The driver checks it under More > Location.
Yes. Under More > Location, Pause GPS pauses the sharing for a chosen time while the Tour keeps running. The card then says until when nothing is shared, and Resume Now ends the pause early. After the pause, the location is shared again on its own.
No. The map only shows the tour. Where the driver may change the order, they use the skip button at the top right of the stop screen.
Yes, while you review the finished Tour. In the review, Edit Times corrects a stop's arrival and departure, and Upload Proof adds a proof the driver could not capture. Corrected times are saved when you complete the review. See Reviewing a Tour.
Each proof is also stored as a file, alongside delivery notes, invoices, and other paperwork. How those files are versioned, linked across the Order, Shipment, and Tour, and made visible to different parties is covered in the Documents article.