Recurring trips and driver roster

How does a recurring trip work?

You describe the duty once: where it starts and ends, the default driver and vehicle, which weekdays it runs, the start time, and the first and optional last date. Odobase then creates the individual trips for the days ahead, up to your chosen horizon of 7 to 60 days, and keeps extending it as time passes. It suits any contract work that repeats every week, from a daily staff shuttle to a standing school run or executive pickup. For staff shuttle contracts, read our guide to running an employee transport roster.

Every occurrence is an ordinary trip. It blocks its driver and vehicle, the driver starts and completes it from the driver app, and it can be invoiced with the customer’s other trips. Nothing downstream needs to know it came from a series.

What does the roster show?

The roster is a week grid: one row per standing duty, one column per day. Each cell is that day’s trip, with its driver and vehicle. It is where a dispatcher answers “who is doing the 8:00 office run on Thursday?” at a glance, and changes it. A day whose default driver or vehicle was already booked elsewhere shows as a gap to fill.

How do you change a driver for part of a series?

From any day you can reassign just this day or this and following. For “this and following”, Odobase moves every future scheduled occurrence where the new driver and vehicle are free, skips the dates that clash, and reports those dates so you can sort them out. Started and completed days are never rewritten.

How are holidays and contract breaks handled?

• Skip a single date, such as a public holiday.
• Pause the series while a client’s office is closed, and resume it later.
• End the series, or shorten its dates or its weekdays.

Each of these cancels the affected trips and detaches them from the series, so resuming or un-skipping creates those days again cleanly, and a trip you cancelled deliberately is never brought back by accident.