Time windows in simple terms

A time window says: “arrive between tw_start and tw_end.” Example: tw_start=09:30, tw_end=11:30. If you reach early, you may wait; if late, it’s a failed SLA or a fee.

Step 1 — Clean your stops (with a template)

Use a standard CSV with names, addresses or GPS, service times, and time windows. We included contacts and notes for dock rules.

 Time windows are 24h format (HH:MM) in local time.

Step 2 — Set vehicle shifts and limits

Drivers can’t run more drops than their shift allows. Add shift_start/shift_end, capacity_units, and max_stops per vehicle.

Include vehicle_class for restricted sites.

Step 3 — Sequence with buffers

Step 4 — Re‑optimize during the day

If a stop runs long or traffic spikes, re-run the optimizer for the remaining drops. Drivers get updated ETAs in the app.

Prove it with numbers

Metric Before After Delta
On‑time % 82 95 +13
Avg km/route 220 195 -25
Driver OT hrs/wk 14 6 -8
Detention fees (AED/mo) 3200 900 -2300

💬 FAQs

They are the earliest and latest minutes you may start service at a stop (local time). Planning must schedule arrival so service begins inside the window.
Either wait until the window opens or move to another nearby stop and return later—your optimizer should simulate both.
Tag stops with vehicle_class and assign “small” vehicles to low‑clearance or gated sites.
Add a soft time window (e.g., 12:30–13:00) with a 30‑minute service_time_min.
Yes: set priority=1 for must‑deliver stops. The optimizer should fill lower priority stops after meeting all priority‑1 windows.

Glossary