CBS
Get in touch

Contingency Bus System

Their spec in. Your invoice out.

CBS reads the TfNSW timetable and specification, builds your vehicle blocks and driver shifts under your own rules, counts every hour and kilometre depot to depot, and produces the GTFS, the TODIS file and the invoice.

What happens when the work arrives

The Excel lands Wednesday. You are rostered by Wednesday afternoon.

Today that is two days of someone rekeying a timetable into a roster, and every typo becomes an operational problem on Saturday night. CBS does the mechanical part and leaves you the decisions.

Load the spec

Drop in the Excel timetable and the Word specification. CBS reads them into routes, trips, stands and standby requirements, shows you every line it found, and commits nothing until you confirm it.

Build the blocks

Trips are chained into vehicle blocks from your depot, with repositioning where the work is one-directional. You see how many buses it needs before you commit a single driver.

Cut the shifts

Blocks become driver shifts under your shift rules — maximum span, breaks, sign-on and sign-off, minimum engagement. Shifts that would breach are refused, not flagged after the fact.

Brief the crew

Each driver gets their shift on a phone: sign-on time, which bus, stands, departure times, the stop list, and who to ring at 4am.

Record the day

Sign-on, pre-departure check, trip by trip. Breakdowns, standby call-ins and incidents captured as they happen with time and place attached.

Send and claim

GTFS and TODIS files out to TfNSW, invoice built from what actually ran, with the supporting documentation attached.

Depot to depot

Every hour and kilometre counted from the depot gate

You are paid by the hour and the kilometre, and the run to the first stand and back from the last is part of it. CBS measures that on every shift instead of estimating it at the end of the month.

Driver shift SH-04 · Saturday 14 MarchHornsby depot · Bus 2841
03:45Sign on, pre-departure check
04:00Depot to Sutherland — empty12.4 km
04:30Block R4-05  Sutherland – Cronulla  11 trips78.2 km
09:12Break — paid30 min
09:42Block R4-11  Engadine – Heathcote  9 trips93.8 km
13:05Sutherland to depot — empty12.4 km
13:24Sign off, fuel and wash
Paid span 9h 54m Total 196.8 km Empty running 24.8 km Within shift rules ✓

An example shift. Your own rules and rates produce your own numbers.

Your shift rules, not an award we picked

  • Maximum shift span and driving time
  • Break length, and whether it is paid
  • Sign-on and sign-off allowances
  • Minimum engagement
  • Split shift rules and penalties

Your depots

  • Several depots, each with its own fleet
  • Running time to each stand
  • Empty kilometres measured, not guessed
  • Work allocated to the depot that can reach it

Your fleet

  • Seating and standing capacity
  • Wheelchair accessible, where the spec demands it
  • Home depot and availability
  • Subcontracted vehicles marked as such

What comes out

The files they ask for, without anyone rebuilding them by hand

Every output is generated from the same record, so the timetable you publish, the data you send and the invoice you issue cannot disagree with each other.

GTFSA valid feed of the service as you will run it, ready to send.
TODISIn the format TfNSW require, generated from the same trips.
Driver shiftsPrinted running sheets, or on the driver's phone.
Vehicle blocksWhich bus does what, and from which depot.
Tax invoiceHours and kilometres at the rate in force on the day.
Supporting packTrip records, incidents and currency evidence attached.

Rates

Indexation applied, including the fuel component

Rates are held with their history, never overwritten. Each component escalates on its own index and its own cycle, and because the published figures arrive late, CBS holds the escalation and recalculates the affected service dates when they land.

Built the way the contract is written

  • Labour, fuel and remaining components, each with its weight
  • A separate index and review cycle for each
  • Fuel against the diesel index, with any deadband
  • Hourly and kilometre rates escalating independently
  • The calculation shown, so you can check the arithmetic

Back-adjustments you would not chase by hand

When a quarter's index is published, CBS recalculates every service date it covers and produces the adjustment as its own claim line. Reconstructing that across a quarter of possessions is a day's work nobody does, so it usually goes unclaimed.

Every invoice is checked against the rate that applied on the service date, not the rate in force today.

Before the invoice goes

Three numbers that have to agree

What the specification committed you to, what your drivers actually ran, and what your invoice claims. When they disagree, CBS says so while you can still do something about it.

Example: a weekend possession, reconciled before invoicing.
BlockSpecifiedOperatedClaimedStatus
R4-02 · Sutherland – Waterfall181818Agrees
R4-05 · Sutherland – Cronulla222121Agrees
Trip 14 not run — vehicle defect recorded 04:12, standby deployed 04:40.
R4-07 · Loftus shuttle141416Over-claim
Two trips claimed that no driver recorded. Caught before the invoice was sent.
R4-11 · Engadine – Heathcote161614Under-claim
Two trips run and never billed. Added back.

Figures shown are an example, not a customer's data.

While it is running

Know how the weekend went before they tell you

Performance against the contract measures

Trips operated against trips specified, departures against the published time, first and last services, by route and by day. Measured from your own trip records, so it stands up whether or not a live feed covers the work.

Readiness, because contingency pays for it

  • Buses declared available, and their condition
  • Drivers on standby with authority current on the day
  • When the call came, when you accepted, when the first bus moved
  • Work you had to decline, and why

In production

A narrated walkthrough of the whole system

Rather than a sales call, there will be a full recorded walkthrough: the spec going in, the blocks and shifts being built, the files going out and the invoice coming back. Watch it in your own time, as many times as you like, and send it to whoever else needs to see it.

Published here once the system is complete

  • Loading a real timetable and specification
  • Blocks and driver shifts built under an operator's own rules
  • Hours and kilometres counted depot to depot
  • GTFS and TODIS generated and sent
  • The day recorded, then reconciled and invoiced

Price

One subscription, scaled to how much work you run

$900 / month

+ $17 per bus-day

Excluding GST

A bus-day is one bus working one service day. An 18-bus Saturday and a 16-bus Sunday is 34 bus-days. Quiet months cost you less; nothing is charged per trip, per driver or per user.

No setup fee, no lock-in.

ScaleBus-days / monthMonthly
Occasional work40$1,580
Most weekends120$2,940
Multiple corridors350$6,850

Against one planner's time, or one deduction dispute you can finally answer.