Automatic Tour Completion

A Tour that reaches the review phase without findings can be completed by Orbit itself, so your team only reviews the tours that actually need a person.

Every Tour ends in a review. When the driver finishes the last stop the tour reads Review Required, and an operator opens it in Orbit MissionControl, checks how the work went, and closes it. On most tours there is nothing to find: every load was handled, every stop is timed, and every required proof is in place.

Automatic completion lets Orbit close exactly those tours. Your organisation decides what counts as a finding, and any tour that shows one stays in Review Required for your team. Automatic completion is off until someone in your organisation turns it on, and while it is off every tour waits for a manual review.

Key highlights

Set once for the whole organisation. Configured in Orbit MissionControl under Settings > Review, and applied to every tour.
You choose the exceptions. Four rules decide what keeps a tour with your team. All of them are active by default, so only a completely clean tour is closed automatically.
Proof uploads are waited for. Proof documents often arrive a little after the tour ends, so the decision waits for as long as you choose.
Always visible on the tour. A tour closed by Orbit says so, and a tour held back names the reasons.
Nothing is skipped. A tour with a finding follows the ordinary review exactly as a tour does when automatic completion is off.

Turning automatic completion on

In Orbit MissionControl, open Settings and select Review. The Automatic Completion card holds one master switch and the exceptions beneath it.

Switch on Auto-Complete Clean Tours.
Under Keep in Review When, leave every exception you want your team to see switched on.
Choose how long Orbit should wait for proof uploads in Wait for Proofs.
Save.

The setting applies to every tour that reaches the review phase from then on. Tours already sitting in Review Required are not revisited, so switching the feature on never closes a tour your team is already looking at.

The exceptions

Each exception is one kind of finding. When an exception is switched on and that finding appears on a tour, the tour stays in Review Required for a person. Switching an exception off lets those cases pass, and a tour showing only that finding is completed automatically.

Exception	What it catches
Loads Were Not Delivered	A `Load` the driver reported as not loaded or not unloaded, whatever the reason: a refusal, missing goods, or a collection that never happened. Damage is covered by its own rule.
Loads Were Damaged	A `Load` reported as damaged. Keeping this one on means damage is always seen by a person, even where other failed loads are allowed to pass.
Stop Times Are Missing	A `Stop` with no recorded arrival or departure. This is typical of a tour closed without the driver app, where the stops were never logged.
Proofs Are Missing	A `Stop` requires a proof that no uploaded document covers.

All four are active unless you switch them off, so the cautious setting is the one you get by simply enabling automatic completion.

Waiting for proof documents

Proof of delivery is captured at the stop and uploaded from the driver's device, so a document can still be on its way when the tour reaches the review phase. Rather than treat that as a missing proof, Orbit waits.

Wait for Proofs sets how long. You can choose not to wait at all, or to wait 15 minutes, 30 minutes, 1 hour, 2 hours, 4 hours or 6 hours. Two hours is used when no choice has been made. When the wait ends, a required proof that no document covers keeps the tour in review, and so does an upload that is still pending or cannot be displayed.

Changing the value also applies to tours that are already waiting. Shortening the wait settles them sooner; lengthening it gives the outstanding uploads more time.

What you see on the tour

The decision is always visible on the tour's review in Orbit MissionControl.

A tour Orbit completed reads Completed automatically because this tour had no findings, and the review is recorded on the tour like any other.
A tour held back reads Automatic completion is on. This tour is waiting for a manual review because: followed by every exception that applied. Your team reviews and closes it in the usual way.

Because the review is recorded either way, the tour history shows who or what closed each tour.

Who can change the settings

The Review settings page follows your organisation's roles. A role without read access to the review settings does not see the page, and a role that can read but not change them sees the settings with every control switched off from editing. See the Roles and Permissions article for how access is granted.

Example

A courier operator in Lisbon runs about forty tours a day, and almost all of them finish cleanly. The team switches on Auto-Complete Clean Tours, leaves all four exceptions active, and sets Wait for Proofs to 30 minutes, because their drivers upload signatures over mobile data. That evening Julia opens the tour list: thirty-six tours are already Completed, each marked as completed automatically. Four are still in Review Required: two because a receiver refused a pallet, one because a Load came back damaged, and one where a stop has no recorded arrival time because the driver finished it by phone. Julia reviews those four and closes them herself.

Frequently asked questions

Does turning this on change anything for tours already waiting for review?
No. Only tours that reach the review phase after the change are considered.

Can I let damaged loads pass but still catch everything else?
Yes. Each exception is independent, so switch Loads Were Damaged off and leave the others on.

What happens if a proof arrives after the tour was completed?
The document is stored against the records it belongs to as usual. Completion does not stop documents from arriving.

Why is a tour still in review when everything looks fine?
Open the tour's review: when automatic completion is on and a tour is held back, the reasons are listed there. A proof that is still uploading at the end of the wait is the most common one.

Can a tour be completed automatically while the driver is still running it?
No. The check happens only once a tour reaches the review phase, which is after its last stop.

Can I still review a tour that was completed automatically?
The tour is closed, and its review is recorded and readable. Where something needs correcting afterwards, handle it on the records themselves, the shipments, loads and documents, as you would on any completed tour.