Quiet by default
Routine progress remains available without competing for attention.
FleetOS · Canadian transportation operations
See the load.See what needs adecision.
FleetOS keeps routine loads quiet and brings forward the exceptions dispatch needs to verify, correct, or send.
- No driver app
- Runs beside the current TMS
- Dispatcher-approved sends
Operations Centre · Live product
One place for the work that changed.
Most loads do not need another dashboard. FleetOS focuses the operating surface on what moved off plan, why it matters, and who has the next decision.
One-load walkthrough · Ontario corridor
From tender to invoice, keep the story together.
The route changes, people make calls, and new evidence arrives. FleetOS keeps those moments on one operating record instead of scattering them across the inbox, TMS notes, and billing files.
Four operational moments. One record.
Field Note · Demonstration load
- Load ID
- BL-2048
- Route
- Mississauga → Montréal
- On site
- —
- Exception
- None
- Dispatcher decision
- Verify tender
Inbox to operating record
The load starts where the work already arrives.
FleetOS reads the tender from dispatch Gmail or EDI and prepares a load record for review. No duplicate entry and no new driver workflow.
- Signal
- Tender received
- Evidence
- Original email and extracted fields remain attached
- Human judgment
- Dispatch verifies the customer, stops, and rate before acceptance.
Tender receivedPlan the movement
Build the trip around the actual freight day.
Loads move onto the dispatch board, where trips, legs, drivers, and appointment windows stay connected to the same record.
- Signal
- Trip ready to assign
- Evidence
- Stops, appointments, and driver assignment
- Human judgment
- Dispatch chooses the driver and resolves conflicts before release.
Trip ready to assignBring forward the decision
Routine loads stay quiet. Exceptions earn attention.
FleetOS watches for the conditions that change the plan, then surfaces the load with the reason, context, and next decision in one place.
- Signal
- Free time exceeded
- Evidence
- Confirmed arrival, current dwell, and detention terms
- Human judgment
- Dispatch corrects the time or approves the prepared notice.
Free time exceededClose the operating record
The invoice inherits the story of the load.
Departure, notice history, source events, and supporting files remain connected so billing does not have to reconstruct the day later.
- Signal
- Invoice support ready
- Evidence
- Timestamped event trail and customer notices
- Human judgment
- A person confirms the final charge before it enters billing.
Invoice support readyDetention recovery · Evidence chain
Detention is easier to bill when the evidence starts at the dock.
FleetOS builds the record as the load moves. Billing gets confirmed events and notice history—not a reconstruction assembled days later.
“Every claim has a source.”
Demonstration record · BL-2048Ready for review
Dock events begin with a named source.
Arrival and departure are recorded from dispatch-confirmed driver updates. Corrections remain visible instead of silently replacing the record.
- Arrival
- 09:14 · Driver call
- Free time ended
- 11:14 · Detention terms
- Departure
- 12:47 · Dispatch confirmed
Human approval remains part of the record.
Every outbound notice shows who approved it.
FleetOS can prepare the customer message, but the latest operational time is checked and the send is explicitly approved by dispatch.
- Prepared
- 11:16 · FleetOS
- Approved
- 11:19 · M. Chen
- Delivered
- 11:20 · Customer email
Human approval remains part of the record.
Billing receives the evidence, not a summary.
The charge, timestamps, notice trail, POD, and original load record remain linked for invoice support and any later dispute.
- Billable time
- 1 h 33 min
- Charge basis
- Customer tariff
- Record status
- Ready for billing
Human approval remains part of the record.
The operating surface
Different views. The same load underneath.
FleetOS is not a collection of dashboards. Each tool works on the same operating record and returns the decision to the people running the freight.
Dispatch board
The day’s plan, without losing the load record.
Build trips, split legs, assign drivers, and keep appointment conflicts visible. The dispatch board shows the plan; the Operations Centre carries the decisions behind it.
- Imported loads stay traceable to the tender
- Exceptions follow the load across trip changes
- No driver app required
SpotTrack
See whether the freight fits before the truck moves.
Dimensions, stackability, and trailer position become a loading decision dispatch can inspect. It is a working view, not a decorative dashboard.
- Trailer-aware placement
- Clear capacity conflicts
- Human-confirmed loading plan
Tender intakeLoads can begin from dispatch Gmail or EDI.
ArrivalTrackCustomer updates follow confirmed operating events.
PODCaptureDelivery documents stay with the load record.
DisputeShieldSource events support the response, not generated claims.
Detention opportunity · Your inputs
What is detention costing the operation now?
Use your own load volume, detention frequency, and average billable amount. The result is an estimate, not a promise, and no contact details are required.
Estimated detention opportunity
$4,410 / month
Estimate based only on your inputs. It is not a guarantee of recovery or savings.
30-day pilot · No card
Start beside the current operation.
Connect one dispatch inbox, follow real loads for 30 days, and decide from evidence. FleetOS does not require a forced migration or driver rollout.
Apply for the pilotDirect onboarding with the Boreal Lab product team.
Starter
$149
CAD / month after pilotFor small carriers replacing spreadsheets and inbox chasing.
Gmail import · Dispatch · Detention · PODGrowth
$299
CAD / month after pilotFor growing carriers adding EDI and more operating modules.
Everything in Starter · EDI · ArrivalTrack · SpotTrackEnterprise
Custom
Staged rolloutFor carriers that need a connector plan, reporting, and support agreement.
TMS connectors · Custom reporting · SLA · Priority supportFleetOS · Built in Ontario
Keep the routine quiet. Make the next decision clear.
Run FleetOS beside the current operation for 30 days. We will look at exception timing, evidence quality, dispatcher effort, and recovered charges together.