Klacks plans routes and drivers — keeping the absolute 60-hour weekly limit, the 48-hour average over the reference period, and correctly recorded Period of Availability (POA) under S.I. No. 2/2005 all in view. Routes are optimised automatically.
S.I. No. 2/2005 sets an absolute maximum of 60 hours in any single calendar week for mobile road transport workers — on top of the 48-hour average limit.
The reference period for the 48-hour average limit is 4 months by default; an extension to 6 months is only possible through a collective or workforce agreement, not automatically as in other sectors.
Waiting time at borders or during ferry crossings counts as POA rather than towards the 48-hour working time, but must still be recorded and made known to the worker in advance — a frequent source of error by hand.
From optimised routes to correctly recorded POA — it all fits together.
Klacks sequences stops in the most sensible order — short journeys, time windows kept, fewer empty runs.
Klacks checks both the absolute 60-hour weekly limit and the 48-hour average limit over the 4-month reference period in real time, in line with S.I. No. 2/2005.
Klacks records Periods of Availability (POA) separately from working time and makes sure they are known to the worker in advance.
Klacks only assigns routes to drivers with the matching licence — and warns before certificates expire.
Klacks runs on your own infrastructure — route and driver data never leave your organisation, not even for the AI.
"Plan tomorrow's routes, driver Murphy is off sick" is enough — Klacksy recalculates everything, POA included.
From your service addresses, Klacks works out the most sensible order and shows the finished route on the map. All you choose is the mode of transport.
Stylized example: Klacks connects the service locations into the shortest route.
Try the Playground to see how Klacks handles routes, driving hours and POA — or install it directly on your own infrastructure. Free and without registration.
