The day board: vans, crews and runs

Scheduling a delivery schedules the collection

When you schedule a delivery, Event Managr creates its collection run at the same time, on the booking’s due-back date. This is the single most useful thing on this screen: a due-back date that nobody has turned into a job is the one that gets forgotten, and it gets forgotten in the week that is already busy.

What counts as a clash

Two runs on the same van or the same crew member, on the same day, with nothing separating their times. That last part is the whole rule. A morning delivery and an afternoon collection on one van is an ordinary working day, and an app that called it a conflict would be shouting at you every day until you stopped reading it.

So a clash fires when two runs share a departure time, or when one or both have no time set at all — because then nothing says they do not overlap.

A crew member is also checked against the rest of their day, not just against other runs. Putting somebody on a van when they are already on an event’s crew that day, or when their staff record says they are away, is refused the same way and can be overridden the same way. The refusal names the job or the dates — never the reason somebody is away, which stays on their staff record.

Overriding one

You can schedule anyway, but you have to say why and your name goes on it. Nothing stores a “this clashes” flag — the clash is worked out fresh from the day’s runs every time you look, so it cannot be left stuck on after the schedule changes underneath it. What is stored is the decision you made.

A hired-in truck never clashes

A van you own is scarce: the same one cannot be in two places. A truck you hire in is not — you ring the supplier and get another. So a run carries either one of your vehicles or a transport supplier, and two supplier runs on the same day are never flagged.

Dates and times

The booking owns the dates — when stock leaves and when it is due back. The run owns the time the driver turns the key. Keeping them apart means there is never a booking-level timestamp to reconcile against a run-level one for the same trip.