Day-to-day operating brief
What Routing Scheduler work looks like in practice
A Routing Scheduler sequences stops and assigns work using routing software and operational knowledge. Terms should cover map and customer data, vehicle dimensions, time windows, service duration, road restrictions, mileage, tolls, depot cut-offs and route publication. The scheduler should not make a route appear efficient by removing realistic loading, break or waiting time. Routing data should be maintained as an operational asset, including delivery restrictions, gate locations, vehicle access and realistic service time. The scheduler may test clustering or optimisation settings, but changes should be compared against actual driver and customer outcomes. Employers should define treatment of ferries, tolls, clean-air zones and seasonal traffic. Repeated manual overrides can signal poor source data and should be analysed rather than accepted as normal workarounds. Route notes should be concise enough for safe driver use and avoid copying obsolete customer comments whose age, source or continuing relevance cannot be verified.
Individually written and reviewed against the maintained role record.