Configuration

Settings

These thresholds drive travel-time estimates, warning triggers, and the coverage gauge across the whole app (see README "Reliability scoring" / "Travel-time approximation" for how each one is used). Changes apply immediately to the next check or auto-assignment run — use "Re-run auto-assignment" on the job list to see the effect on the current schedule.

Thresholds

Auto-assignment autonomy

How much judgement the system may use by itself.
Careful leaves every warning for a planner.
Balanced may auto-assign warnings that are mainly up to the interpreter, such as long commute home.
Flexible may auto-assign any warning-level match.
God-Mode additionally lets a planner manually override validation blocks, except overlapping bookings.

Average travel speed (km/h)

Used to convert straight-line distance into an estimated travel time.

Fixed overhead per trip (min)

Added to every travel estimate for parking/walking in, or dialling into a call.

Tight-travel warning buffer (min)

Extra gap beyond the bare minimum required that still gets flagged as a warning instead of accepted cleanly.

Long-distance warning threshold (km)

One-way home-to-job distance beyond which a warning is raised.

Workload imbalance threshold (min)

How far an interpreter's total booked time can exceed the least-loaded qualified alternative before a warning is raised.

Coverage radius (km)

Straight-line radius used to count nearby qualified interpreters for the Coverage indicator.

Coverage gauge cap (count)

Number of nearby interpreters that reads as "full" on the Coverage gauge.

Urgent unassigned threshold (days)

Unassigned jobs due within this many Amsterdam calendar days are highlighted in red on the overview.