TL;DR

  • Timetables are reusable schedules (plans).

  • They contain template runs (times, buses, capacity).

  • Scheduling a timetable creates real runs for a specific date.

  • Runs are what drivers actually operate.

  • Jobs only exist on runs, never on timetables.

  • Editing a timetable affects future scheduling only.

Think: Timetable → Template Runs → Real Runs

Timetables Page Overview

The Timetables page is where you define recurring courtesy bus schedules.

A timetable represents a reusable schedule — for example, Friday Nights, Saturday Day Service, or Footy Nights — that can automatically generate runs on specific days.

Timetables help you:

  • Avoid re-creating the same runs every week

  • Maintain consistent start and end times

  • Quickly schedule multiple runs at once

  • Reduce manual scheduling errors

What Is a Timetable?

A timetable is a container for one or more template runs.

It does not represent an actual operating run on its own.

Think of a timetable as a plan, and runs as the instances created from that plan.

Timetables vs Runs (Key Concept)

Understanding this distinction is critical:

  • Timetable
    A reusable schedule definition.

  • Template Run
    A run definition inside a timetable (time, bus, capacity).

  • Run
    A real, dated instance created from a template run.

Timetables define what should happen.
Runs are what actually happens on a specific date.

Template Runs

Each timetable contains one or more template runs.

A template run defines:

  • Start time

  • End time

  • Assigned bus

  • Capacity settings

For example:

  • Friday Nights timetable

    • 6:00pm – 9:00pm (Bus 1)

    • 9:00pm – 12:00am (Bus 1)

Each of these is a template run.

How Timetables Are Used

Timetables are used to generate runs for real dates.

When you schedule a timetable:

  • Each template run is copied

  • A real run is created for the selected date

  • The new runs appear on the Runs page

After creation, runs are completely independent of the timetable.

Scheduling Timetables

Timetables can be scheduled in different ways depending on your workflow.

Common approaches include:

  • Scheduling a timetable for a single future date

  • Scheduling the same timetable repeatedly (e.g. every Friday)

  • Scheduling multiple timetables at once for upcoming weeks

This allows venues to plan weeks or months ahead in seconds.

Editing Timetables

Editing a timetable affects future scheduling only.

Changes to a timetable:

  • Do not modify runs that already exist

  • Only apply when the timetable is scheduled again

This prevents historical data from being altered accidentally.

When to Use Multiple Timetables

Most venues use multiple timetables to reflect different operating patterns, such as:

  • Weeknights vs weekends

  • Public holidays

  • Sporting events

  • Seasonal changes

This keeps scheduling predictable while still allowing flexibility.

Why Timetables Don’t Show Jobs

Timetables never contain jobs.

Jobs only exist inside runs, and runs only exist after a timetable is scheduled.

This separation keeps planning clean and avoids mixing future plans with live operational data.

Removing or Disabling Timetables

Timetables can be:

  • Disabled when no longer needed

  • Removed if they were created in error

Removing a timetable:

  • Does not affect existing runs

  • Does not delete historical data

  • Only removes the scheduling template

Best Practices

  • Create timetables for any service that repeats

  • Keep timetable names clear and descriptive

  • Use separate timetables for different service types

  • Avoid editing timetables to “fix” live runs — edit the run instead

Key Things to Remember

  • Timetables are plans, not real runs

  • Template runs live inside timetables

  • Scheduling creates real runs

  • Editing timetables does not affect existing runs

  • Jobs only exist on runs, never on timetables