1. Overview

A recurring booking is a template that the system uses to automatically generate a cycle of one-off bookings in the Dispatch Panel.

Once active, the system uses your recurrence settings to create future bookings without manual duplication. These generated bookings include the same:

  • Route
  • Time
  • Passenger information
  • Vehicle type
  • Price

They appear in your system as regular bookings and can be managed like any other job.

 


 

2. Create a New Recurring Booking

To create a recurring booking:

  1. Open the Recurring screen
    • Go to Bookings ➜ Recurring in the Dispatch Panel.
    • Click Add to start a new recurring template.
  2. Enter booking details
    • Fill in the booking form as you would for a regular job.
    • Include route, vehicle, passengers, and price.
    • Enter the pickup date and time—this becomes the Start date for the recurring cycle.
  3. Set recurrence
    • Click Set Recurrence to define when and how often the booking should repeat (see Section 3).
  4. Activate the template
    • Tick the Active checkbox.
    • Click Save to activate the recurring series. The system will now generate future bookings based on your rules.

 


 

3. Set Recurrence

When you select Set Recurrence, you'll configure three fields:

  • Repeat every
    • Select the interval: Day, Week, Month, or Year.
    • nter the frequency (e.g. “every 2 weeks”).
    • If you select Week, choose one or more weekdays (e.g. Mon, Wed, Fri).
  • Start date
    • The first day an individual booking should occur.
    • This is based on the pickup date/time set in the template.
  • Ends
    • Choose how the recurring cycle ends:
      • On date – Ends on a specific calendar date.
      • After N occurrences – Ends after a defined number of repeats.
      • Never – Runs indefinitely until stopped manually.

Tip: If you choose Never, you can pause or stop the cycle at any time by deactivating or deleting the template (see Section 5).

 


 

4. How the Date Logic Works (Important)

  1. No retrospective bookings
    • Bookings are only generated from "today" onward.
    • Example: If today is 15 Aug 2025 and your Start date was 01 Aug 2025, the system will not generate bookings for 1–14 Aug.
  2. Future Start dates are respected
    • If the Start date is in the future (e.g. 01 Sep 2025), the system waits until that day and time to create the first booking.
  3. Editing and regenerating a cycle
    • To apply updated settings:
      • Deactivate the template or use Remove Bookings to delete future instances.
      • Adjust recurrence fields or Start date.
      • Reactivate the template.
    • This starts a new cycle based on your updated settings from "today" (or from the future Start date).


 

5. Managing Existing Recurring Bookings

To manage a recurring booking:

  • Go to Bookings ➜ Recurring.
  • Use the search bar or filters to locate templates.

Available actions:

  • Edit
    • Update route, price, passengers, or recurrence settings.
    • Changes only apply to bookings generated after the update.
  • Remove Bookings
    • Deletes all future bookings created by the template.
    • The template itself remains active.
  • Deactivate
    • Pauses booking generation without deleting the template or its existing jobs.
    • Can be reactivated later.
  • Delete
    • Completely removes the template and all future scheduled bookings.
    • Past generated bookings remain in the system for reporting and record‑keeping.

 


 

6. FAQs

Q: I changed the price—why do past bookings still show the old price?
A: Each booking is created as a snapshot at the time it’s generated. Updating the template affects only future jobs. Past ones retain the original values.

Q: Can I generate bookings for past dates?
A: No. The system does not backfill bookings. Add past jobs manually as one-off bookings if needed.

Q: How far in advance are bookings generated?
A: The system checks daily and always ensures the next occurrence is created.
Example: For a “Every Monday” recurrence, the next Monday’s job appears when the daily task runs—typically one day before the pickup.