T TradieBridge Docs Sign in

Docs

The Fleet Office

Assets, GPS history, prestarts, utilisation and timesheets.

Each record is held whole. A resource's columns are what a list filters and sorts by.

Questions

utilisation jobs

How hard the fleet worked between two days: work, idle and total hours and distance by asset or by day, most hours first.

from*
string. First day, e.g. 2026-09-01.
to
string. Last day, inclusive. Default today; at most 400 days.
by
string. Default asset.

Ask with ask_question, or GET …/answers/{question} with the arguments as query parameters.

15 resources

asset_locations Asset locations

Where each asset is now, read every five minutes: fixed_at (the organisation's local time), speed, ignition, odometer, latitude and longitude, keyed by asset_id.

Keyed by source_id

9 columns
  • source_id string
  • modified_at datetime
  • asset_id string
  • fixed_at string
  • speed decimal
  • ignition decimal
  • odometer decimal
  • latitude decimal
  • longitude decimal

asset_types Asset types

The kinds of asset set up in The Fleet Office, with their expected daily run hours.

Keyed by source_id

3 columns
  • source_id string
  • modified_at datetime
  • record_name string

assets Assets

The fleet as The Fleet Office lists it: vehicles, plant and equipment, with unit_id (the fleet number), record_name (the description) and rego.

Keyed by source_id

5 columns
  • source_id string
  • modified_at datetime
  • unit_id string
  • record_name string
  • rego string

divisions Divisions

Divisions, keyed by name, with their manager, assets and users.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • manager string

geofences Geofences

Geofences: record_name, fence_type and the fence's points.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • fence_type string

organisations Organisations

The organisation itself, one document: name, time_zone, ABN, contacts, address, positions, departments and cost codes.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • time_zone string

prestarts Prestarts

Prestart checks as drivers filed them: created (local time), asset_id, unit_id, description, created_by and deleted.

Keyed by source_id

8 columns
  • source_id string
  • modified_at datetime
  • created string
  • asset_id string
  • unit_id string
  • description string
  • created_by string
  • deleted string

projects Projects

Projects, with their managers, users and timesheet supervisors.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • description string

roles Roles

The company's own roles.

Keyed by source_id

4 columns
  • source_id string
  • modified_at datetime
  • record_name string
  • slug string

system_roles System roles

The Fleet Office's built-in access levels.

Keyed by source_id

3 columns
  • source_id string
  • modified_at datetime
  • record_name string

timesheets Timesheets

Timesheets with every field filled in: form_num, user_id, user_name, status, submitted and edited (local time).

Keyed by source_id

8 columns
  • source_id string
  • modified_at datetime
  • form_num string
  • user_id string
  • user_name string
  • status string
  • submitted string
  • edited string

track_days Track days

Every GPS fix an asset reported in one day, as one document per asset per day: asset_id, day (the organisation's calendar) and fixes_count. The fixes are in the document.

Keyed by source_id

5 columns
  • source_id string
  • modified_at datetime
  • asset_id string
  • day string
  • fixes_count integer

users Users

The people set up in The Fleet Office: record_name and address.

Keyed by source_id

3 columns
  • source_id string
  • modified_at datetime
  • record_name string

utilisation_days Utilisation days

Each asset's day as The Fleet Office summarises it: day, asset (its name), asset_type, work_hours, idle_hours, total_hours and total_distance, with an entry per hour in the document. Hours worked: summarize total_hours.

Keyed by source_id

9 columns
  • source_id string
  • modified_at datetime
  • day string
  • asset string
  • asset_type string
  • work_hours decimal
  • idle_hours decimal
  • total_hours decimal
  • total_distance decimal

utilisation_periods Utilisation periods

Each asset's running and idling periods: asset_id, started_at, ended_at and idling.

Keyed by source_id

6 columns
  • source_id string
  • modified_at datetime
  • asset_id string
  • started_at string
  • ended_at string
  • idling boolean