Skip to content

CleanCore · Bus & fleet

Bus depot cleaning software, built around the vehicle

Spot cleans, deep cleans, steam and detail scheduled per bus per night, on a board that shows what is scheduled, started, completed and verified.

Book a demo See pricing

The problem this solves

Depot cleaning does not fit a site-based cleaning system. The unit of work is a vehicle, it moves, it goes out of service, and the cycle is nightly across a fleet in the hundreds — so the thing you need on screen at 21:00 is not a site scope, it is tonight’s buses.

CleanCore was built against a bus-depot tender, so the fleet is a register in its own right rather than an asset type bolted onto a building. Every bus carries its type, its depot and its last clean, and the nightly board is organised the way a shift is actually run.

The two arguments a depot contract always produces — a bus that was not available, and graffiti that has to be gone by morning — are handled as records rather than as phone calls.

Worked example

Tonight’s board on a 198-bus depot. Two things go wrong.

  1. 1

    A bus is off the road

    It is excluded from the cycle by the customer or by operations, with charge or no-charge recorded at the moment of the decision rather than argued at invoice time.

  2. 2

    Offensive graffiti is found

    It is flagged, a removal SLA starts, and the NSW Police report pack is generated from the record instead of retyped into a form.

  3. 3

    The rest of the night proceeds

    Each task moves scheduled, started, completed, verified — per bus — so the morning board shows what happened rather than what was planned.

  4. 4

    The customer’s ad-hoc requests sit in the same queue

    Accepted or declined on screen, each with its own charge decision.

At shift end the board is the record: no separate reconciliation, and nothing to reconstruct from memory.

Capabilities

What bus & fleet gives you

All 4 of these are in the product today. Each one names what it is built on.

Fleet register

Live

Every bus, its type, its depot and its last clean — the register a depot manager opens first.

First included in the Starter tier

Per-bus cleaning board

Live

Spot cleans, deep cleans, steam and detail scheduled per bus per night, with the board showing scheduled, started, completed and verified.

First included in the Starter tier

Exclusions with a charge decision

Live

A bus out of service is excluded from the cycle by the customer or by ops, with charge or no-charge recorded rather than argued later.

First included in the Pro tier

Graffiti to a police report

Live

Offensive graffiti flagged, a removal SLA started, and the NSW Police report pack generated from the record.

First included in the Pro tier
What backs these claims

Each capability names the decision record, module, route or table it is built on. Ask us for any of them in an evaluation and we will walk you through the code.

Fleet register
imss_depot_buses · /imss/depot-buses · client-portal/bus-register
Per-bus cleaning board
ADR 0025 · imss_bus_cleaning_tasks · /imss/bus-cleaning
Exclusions with a charge decision
ADR 0026 · imss_bus_cleaning_exclusions
Graffiti to a police report
ADR 0024 · src/server/imss-graffiti.ts · /api/imss/graffiti-reports

Where this sits

Back to

CleanCore — every capability in one place

The whole module: what is live, what is committed, what is only on the roadmap.

Read next

Prove the cleaning was done — and who did it

Every clean, verification, exclusion and defect is written once, in the same transaction as the act itself, so the record cannot be edited into a different past.

Twenty minutes on a real contract.

Real data, four logins, nothing typed on the day — including the parts we have not built, which we will point out ourselves.

Book a demo See pricing