Driver-related settings

Permissions: update_product

In the Driver-related settings section of the tenant settings of a product, you can configure the following settings for the product’s drivers.

Drivers may deactivate matching into their vehicle

When enabled, this setting allows drivers to deactivate matching to the vehicle they are connected to through the vehicle occupation. Drivers do this in ioki Vehicle App during an active vehicle planning—see manage vehicle availability for the driver-side steps. When it is off, drivers cannot deactivate their vehicle from matching. It is disabled by default.

Driver client automatically accepts ride requests

When activated, the driver client automatically accepts ride requests on the driver’s behalf. Drivers are notified of new tasks but do not need to actively accept them. The setting does not change the acceptance deadline itself (see Waiting for driver acceptance until the system cancels); if a ride is still not accepted when that deadline passes, it is only the recorded cancellation reason that differs (driver client did not accept in time instead of driver did not accept in time). It is disabled by default.

This setting applies only when a connected driver would otherwise accept the ride in the app. It is separate from the engine-level automatic driver acceptance that always happens in certain situations, such as when no driver is connected to the matched vehicle, when a ride is prebooked well in advance, or when the ride is matched into a task list that is not currently active or is paused.

Driver can reject tasks

If this option is activated, connected drivers can reject tasks before they are added to their vehicle planning. For example, drivers can decline requested rides. The capability is exposed to the driver client as a product feature, so the reject action only appears in the app when this setting is on. It is disabled by default.

Waiting for driver acceptance until the system cancels

This setting defines how long the system waits for a driver to accept a ride request before canceling it. The time can be set between 5 seconds and 5 minutes, in 5-second increments; the default is 2 minutes.

When a booking is created, the ride is marked as valid for the driver only until now plus this duration. Once a passenger has accepted and this deadline passes without driver acceptance, the ride is automatically canceled. This is the driver-side counterpart to the passenger-side Waiting for passenger acceptance until the system cancels setting.

The following four pairs of settings all work the same way, each for a different task type: start of shift, end of shift, start of pause, and end of pause. In each pair, the require timely completion checkbox switches the guard on, and the completion threshold defines how far in advance of the task’s planned time it may be completed.

When require timely completion is on, the earliest a driver may complete the task is the task’s planned (negotiation) time minus the completion threshold. Attempting to complete it earlier is rejected as too early. When the checkbox is off, there is no early limit and the threshold has no effect. Each threshold can be set between 1 and 60 minutes, in 1-minute steps.

Start of shift tasks require timely completion

When this option is enabled, a driver cannot start their shift before the earliest allowed time (the planned start minus the Start of shift tasks completion threshold). This is disabled by default.

Start of shift tasks completion threshold

This defines how much time in advance a driver is allowed to start a shift, applied only when Start of shift tasks require timely completion is enabled. The default is 30 minutes.

A driver can act on a task only while its task list is current, and a task list becomes current 15 minutes before its planned start. Because the start of shift task is the first task in the task list, a driver never sees it more than 15 minutes before the planned shift start. As a result, setting this threshold above 15 minutes has no practical effect for start of shift: the earliest a shift can start is still bounded by this 15-minute window. This 15-minute bound is specific to start of shift. The other guards act on tasks in the middle of a task list, so their full 1 to 60 minute range applies.

End of shift tasks require timely completion

When this option is enabled, a driver cannot end their shift before the earliest allowed time (the planned end minus the End of shift tasks completion threshold). This is enabled by default.

End of shift tasks completion threshold

This defines how much time in advance a driver is allowed to end a shift, applied only when End of shift tasks require timely completion is enabled. The default is 30 minutes.

Start of pause tasks require timely completion

When this option is enabled, a driver cannot start a pause before the earliest allowed time (the planned start minus the Start of pause tasks completion threshold). This is disabled by default.

Start of pause tasks completion threshold

This defines how much time in advance a driver is allowed to start a pause, applied only when Start of pause tasks require timely completion is enabled. The default is 10 minutes.

End of pause tasks require timely completion

When this option is enabled, a driver cannot end a pause before the earliest allowed time (the planned end minus the End of pause tasks completion threshold). This is disabled by default.

End of pause tasks completion threshold

This defines how much time in advance a driver is allowed to end a pause, applied only when End of pause tasks require timely completion is enabled. The default is 10 minutes.

Repositioning tasks require timely completion

When this option is enabled, repositioning tasks cannot be completed before the earliest allowed time (the planned time minus the Repositioning tasks completion threshold), in the same way as the shift and pause guards above. This is disabled by default.

Repositioning tasks completion threshold

This defines how early a repositioning task may be completed, measured back from the task’s planned time, and applies only when Repositioning tasks require timely completion is enabled. The default is 10 minutes; it can be set between 1 and 60 minutes.

Repositioning tasks can be canceled

Although this setting appears in Driver-related settings, it is not limited to drivers. When enabled, connected drivers and Operators who can manage tasks can cancel repositioning tasks by using the existing task actions. This setting is disabled by default.

This setting only affects manual cancellation. Automatic dismissal of dismissable repositioning tasks still follows the existing repositioning rules and the Dismissal threshold of vehicle repositioning setting.

Line stop tasks require timely completion

When this option is enabled, line stop tasks cannot be completed before the earliest allowed time (the planned time minus the Line stop tasks completion threshold), in the same way as the shift, pause, and repositioning guards above. This is disabled by default.

Line stop tasks completion threshold

This defines how early a line stop task may be completed, measured back from the task’s planned time, and applies only when Line stop tasks require timely completion is enabled. The default is 10 minutes; it can be set between 1 and 60 minutes.

Line stop tasks can be cancelled

Although this setting appears in Driver-related settings, it is not limited to drivers. When enabled, connected drivers and Operators who can manage tasks can cancel line stop tasks by using the existing task actions. This setting is disabled by default.

Line stop tasks are automatically completed once reached

When enabled, a line stop task is completed automatically as soon as the vehicle reaches its stop, without waiting for the driver to confirm it manually. When it is off, the driver completes each line stop task in the app. This setting is disabled by default.

Reposition vehicle on idle time threshold

This setting belongs to the product feature vehicle repositioning. It defines the default vehicle idle-time threshold. If a driver does not receive a new trip order within the configured number of minutes after the previous one has ended, the app navigates to a waiting position depending on the automated repositioning strategy applied to the vehicle planning. This is a default value and can be overridden on the vehicle; the value on the vehicle takes precedence when present. The default is 20 minutes and can be set between 1 and 60 minutes.

The soft auto-repositioning logic uses this threshold in two ways: a repositioning task is only spawned when there is at least this much idle time before the next task, and it is scheduled to start roughly halfway (threshold / 2) into that idle gap.

Dismissal threshold of vehicle repositioning

This setting belongs to the product feature vehicle repositioning. It defines the threshold for delays after which dismissable vehicle repositioning tasks are dismissed. When a repositioning task’s delay (the difference between its calculated time and its negotiation time) exceeds this threshold, the task is automatically dismissed during planning recalculation, rather than kept in the plan. The default is 20 minutes and can be set between 1 and 60 minutes.

Threshold for slightly delayed tasks

The slightly delayed and heavily delayed thresholds together classify a task’s driver-facing delay state as ok, slightly delayed, or heavily delayed. The delay is measured as the difference between the task’s current planned time and its latest acceptable time (the negotiation time max). The equivalent passenger-facing thresholds are configured separately under passenger-related settings.

The classification is: ok when the delay is at or below the slightly delayed threshold; slightly delayed when it is above the slightly delayed threshold but at or below the heavily delayed threshold; and heavily delayed when it exceeds the heavily delayed threshold. If either threshold is unset the state is treated as ok.

This threshold defines the point at which a task’s delay state is considered slightly delayed—the first band above on time.

A task is classified as slightly delayed if its planned time occurs later than the negotiation time max by more than the slightly delayed threshold, but not by more than the heavily delayed threshold. The delay state is evaluated per task, so different tasks in the same vehicle planning can carry different states. A task whose delay has not yet passed this threshold stays on time; if its delay later grows beyond the heavily delayed threshold, it escalates to heavily delayed. If either delay threshold is left unset, the state is always on time.

This represents a minor schedule deviation that is noticeable but not critical. The default is 5 minutes and it can be set between 1 and 60 minutes.

Threshold for heavily delayed tasks

This threshold defines the point at which a task’s delay state is considered heavily delayed.

A task is classified as heavily delayed if its planned time occurs later than the negotiation time max by more than the heavily delayed threshold.

This represents a significant delay that may require urgent attention. Heavily delayed tasks are often highlighted in client applications to draw attention. The default is 10 minutes and it can be set between 1 and 60 minutes.