Logistics

Depots that never stop, rotas that hold.

Driver hours are a ceiling with law behind them. Build the week against it, keep licences current, and see the peak coming while you can still staff it.

The daily reality

The problems you know too well

  • Hours creeping past a legal ceiling
  • An agency driver whose licence nobody checked
  • Peak season staffed in October instead of August
With Formclock

How Formclock handles it

  • Positions seeded for logistics: Driver, Loader, Warehouse Operative, Transport Planner
  • Coverage the agent fills and explains
  • Compliance enforced before every publish
  • Fair rotation everyone can see
Coverage

Gaps show up before the shift does.

Coverage requirements per day and position mean a hole in Friday shows up on Monday, and the agent can offer it to the right people before it becomes an emergency.

How gaps get filled
1 gap · Fri 4–10pFill gap

Driver hours are a ceiling with law behind them

Most scheduling constraints are preferences with consequences. Driver hours are a limit with an enforcement regime, and crossing it is not an operational inefficiency, it is an infringement attached to a named driver and an operator licence.

That changes what a rota is for. It is not primarily a plan for getting the work done, it is a plan for getting the work done inside a ceiling, and a tool that shows the ceiling only after the week has been worked is describing history rather than helping. The useful moment is while a shift can still be moved, which is also the moment a planner is least likely to be thinking about a ceiling.

A planner is rarely thinking about the ceiling while building a route, which is precisely why the check belongs in the tool rather than in the planner. The warning that matters arrives while the shift can still be moved. A report showing that a driver exceeded their hours last week is an incident record, and by then the only remaining question is what to do about it.

The depot does not stop, so the rota cannot have a seam

Continuous operations have no natural boundary where one week ends and the next begins, which is exactly where scheduling tools put one. Shifts that cross midnight, patterns that cross the week, and hours that belong to a night rather than a date all sit on that seam.

Storing shifts in UTC against the site timezone keeps a night whole and lands it on the night it started. This sounds technical and behaves operationally, because the alternative is a report showing two half-staffed nights where one fully staffed night happened. A night that crosses midnight belongs to the shift, not to the calendar, and every total downstream of that is either right or quietly wrong.

Continuous operations expose every assumption a scheduling tool makes about days. Whether a night belongs to the day it starts or the day it ends decides how hours total, which week they land in, and whether a rest gap is measured correctly. It has to be one answer applied everywhere, because two answers is how a depot ends up with totals that nobody can reconcile.

Agency drivers and the licence nobody checked

Agency covers the gap, and the gap is usually urgent, which is precisely when checking a licence category or a qualification card gets skipped. The risk is not that somebody cannot drive, it is that they cannot drive that vehicle.

Making the requirement live on the position rather than in a process means the check happens whether or not anybody is thinking about it, including when cover is arranged at short notice. A control that only works when people are calm is not a control. The moment an agency driver is booked is the moment the check is worth something, because after the vehicle has left the yard the question has stopped being preventive.

The reason this gets missed is that agency bookings happen under pressure, often by somebody who is not the person who normally builds the rota. A control that depends on the calm, informed version of a process will not survive the morning it is most needed. Putting the check at the point of assignment makes it independent of who is doing the assigning.

Peak season is a staffing decision made months earlier

By the time peak is visible in the volumes it is too late to staff it well, and the options narrow to overtime and agency at the rate the market sets in the busiest month of the year.

Copying a published week forward and adjusting headcount against known cover requirements is a planning exercise that can be done in August with the same information. What changes is the cost of the answer, not the quality of it. A peak planned in September is a recruitment decision, and the same peak planned in November is an agency invoice for the same hours.

What is hard about peak is not the peak, it is the ramp either side of it. Bringing people on too early is paid capacity with nothing to do, and too late is a fortnight of agency cover at the worst rate of the year. Both are visible if you plan the weeks around the peak rather than the peak itself.

Loading bay cover and the shift that starts before the shift

Drivers cannot leave until the vehicle is loaded, so a depot that rosters drivers precisely and loaders approximately is a depot with vehicles waiting. The dependency runs one way and the rota often does not show it at all.

Setting cover by part of the day makes the pre-shift window its own requirement rather than an assumption. It also makes the trade explicit: an hour of loader cover against a fleet standing idle is a comparison worth being able to see. Bay cover starts before the first vehicle and ends after the last, which is a shape the driving rota does not have and cannot be derived from.

Bay work also has its own qualification picture. Counterbalance and reach truck are not the same ticket, and a bay staffed with the wrong one is staffed only on paper. Holding the certification against the person and checking it when the shift is assigned keeps the distinction where it belongs, which is in the plan rather than in a supervisor's memory.

We see the hours before payroll does, which is the only time it helps.
Transport manager, regional distribution

Illustrative scenario, not a customer quote.

Questions

Logistics scheduling, answered.

Does Formclock enforce driver hours?+
It checks the weekly threshold your organisation sets, plus rest gaps and consecutive-day limits from your region's rule pack, before a schedule publishes. Treat it as a scheduling safeguard rather than a tachograph system: it plans against the ceiling, it does not read the vehicle. It warns before publication, against your region's rules pack, and the warning cites the instrument it reads from and the date it was last reviewed. It is a planning control rather than a tachograph, so it works on the shift while the shift can still be moved.
Can we stop an uncertified driver being scheduled?+
Yes. A position can require a licence or certification, and somebody without a current one is not offered it, including when the agent is filling a gap. The check reads the expiry date rather than whether it was ever issued. Yes, and the check runs at the point of assignment, which is what makes it independent of who is doing the assigning. Agency bookings happen under pressure and often not by the person who normally builds the rota, which is exactly when a manual check fails.
How do we plan for peak?+
Copy a published week forward and adjust headcount against it rather than rebuilding from empty. Cover requirements per day and position then show which shifts are still short, which is the work worth doing in August rather than October. By planning the weeks either side of it rather than the peak itself. Ramping up too early is paid capacity with nothing to do and too late is a fortnight of agency cover at the worst rate of the year, and both are visible in advance.
The depot runs continuously. Does that break anything?+
No. Shifts crossing midnight are stored in UTC against the site timezone, so a night that runs to seven in the morning belongs to the night it started rather than being split across two days in reports. No, but the answer has to be consistent. A shift belongs to the day it starts, and hours, rest gaps and week boundaries all follow the shift rather than the calendar, which is what stops a continuous operation producing totals nobody can reconcile.
Do hours across depots count together?+
Yes. Hours total against the person rather than the site, so a driver covering two depots in a week accumulates one set of hours and the ceiling is calculated on the total for rest and overtime purposes. Counting per depot understates it for exactly the people who move around most, splitting them into two records that each look reasonable on their own.

See it with your own schedule

Set up a workspace, add your team, and build a week. It takes about ten minutes and costs nothing.

Start free