Skip to main content
Logistics & Transportation

Every Load Tracked, Every Hour Compliant, Every Mile Earned

We build dispatch and TMS platforms, ELD and Hours-of-Service compliance, telematics, and shipper portals for Canadian carriers, fleets, brokers, and 3PLs. Software that works twenty kilometres past the last cell tower, keeps you onside with the National Safety Code, and turns deadhead miles back into margin. Calgary roots, working with fleets from the Lower Mainland to the 401.

Dispatch & TMSELD / Hours of ServiceFleet TelematicsFreight VisibilityCross-Border Ready

The Canadian Reality

Canadian Trucking Runs on Margins Measured in Cents per Mile - and Most of the Software Was Built for the Lower 48

The dispatch is run on a whiteboard, phone, and text. The logbooks are paper or a half-implemented ELD nobody trusts. The TMS, the ELD, and the accounting system have never spoken to each other. We build the operation, not just the platform.

Walk into a typical Canadian carrier and the pattern is the same whether they run twelve trucks or two hundred. Dispatch is a whiteboard, a cell phone, and a string of texts - the dispatcher knows where the trucks are because they called the drivers, and the customer knows where the freight is because they called the dispatcher. Hours of Service live on paper logs or a bargain-bin ELD that throws false violations nobody trusts, so the safety manager keeps a parallel spreadsheet just in case an audit shows up. The TMS, the ELD, and the accounting system are three vendors that have never exchanged a single record, so somebody re-keys every load three times. None of this is anyone's fault - it is what happens when the tools were bought one fire at a time.

Off-the-shelf software does not fix it, partly because the strongest products were built for the US market and stop at the 49th parallel. Canadian carriers run under the National Safety Code, not the US FMCSA rules - 13 hours of driving, 14 on-duty, mandatory off-duty, and a 70-hour-7-day or 120-hour-14-day cycle that a US-tuned ELD models incorrectly. They cross the border under CBSA eManifest northbound and US ACE southbound, with CARM now reshaping how duties and the importer of record are handled. They haul dangerous goods under the TDG Act with placarding and documentation rules that differ from the US 49 CFR. And they do all of it across distances and winters - a Calgary to Thunder Bay run, a January closure on the Coquihalla - that a platform designed for dense regional freight never accounted for.

We build custom software for Canadian logistics because the operation is the product. A dispatch and TMS platform where a planner assigns a load and the system checks the driver's remaining Hours of Service before the truck is committed - and offers a relay or a swap when the math does not work, instead of finding out at a roadside inspection. A driver app that captures the log, the pre-trip inspection, and the proof of delivery offline in a dead zone and syncs the second it finds signal. A telematics and routing layer that turns the empty backhaul into a booked load. A shipper portal that answers where is my freight without a phone call. We have built variants of these for carriers, brokers, and private fleets, and the cents-per-mile they recover keeps justifying the build.

Headquartered in Calgary puts us inside one of the country's most important freight hubs - CPKC (Canadian Pacific Kansas City) is headquartered here, the city sits at the crossroads of the Trans-Canada and the QEII corridor, and the inland port and intermodal terminals in Rocky View and the Calgary Logistics Park move freight in every direction. Our engineers understand the difference between a long-haul, an LTL, and a drayage move, why a dispatcher will not adopt a tool that takes three extra clicks per load, and what a CVSA inspection or an NSC facility audit actually asks for. That context shows up in every screen, and it is the part a transportation platform sold from a booth at a US trade show never had.

~70%
Of Canadian goods, by value, are moved by trucking - the backbone of domestic and cross-border trade
Canadian Trucking Alliance (directional)
Thousands
Of unfilled truck-driver positions in Canada, a persistent shortage that makes every booked mile count
Trucking HR Canada / industry estimates
15-25%
Typical share of kilometres run empty (deadhead) in the industry - revenue-free miles routing can recover
Industry averages
Mandatory
Certified ELDs are now required for federally-regulated carriers under the Canadian ELD mandate
Transport Canada / NSC

What's Broken Today

The patterns we keep seeing

ISSUE 01

Dispatch run on a whiteboard, phone, and text

The dispatcher knows where the trucks are because they called the drivers, and the customer knows where the freight is because they called dispatch. There is no real-time visibility, no single board, and the institutional knowledge lives in one person's head and phone.

ISSUE 02

Hours-of-Service compliance risk and audit exposure

Paper logs or an ELD nobody trusts, a parallel spreadsheet kept just in case, and a constant low-grade risk that a violation surfaces at a roadside inspection or an NSC facility audit - where the cost is fines, a downgraded safety rating, and lost contracts, not just a ticket.

ISSUE 03

Deadhead and empty miles eroding thin margins

Trucks running empty on the backhaul burn fuel and hours for zero revenue. Without routing and load-matching tied into dispatch, a meaningful share of every mile earns nothing - on margins already measured in cents.

ISSUE 04

TMS, ELD, and accounting that do not talk to each other

The dispatch system, the ELD, the telematics, and the accounting package are separate vendors that never exchange a record, so a single load gets re-keyed three times and a clean billing or compliance picture takes a manual stitching exercise every week.

What We Build

Solutions tailored to logistics & transportation

Not a generic platform with industry skins. Architecture, workflows, and integrations chosen for logistics & transportation operations specifically.

A single live board for planners and dispatchers that replaces the whiteboard and the phone tree - load assignment, driver and asset status, and customer commitments in one place, with Hours-of-Service checked before a load is ever committed.

Real-time dispatch board with drag-and-drop load assignment
Hours-of-Service feasibility check before a load is committed
Relay, swap, and team-driver suggestions when a single driver cannot make it legally
Order entry, rating, and automated billing tied to delivery events
Driver, broker, and asset management in one source of truth

Logging built to the National Safety Code, not borrowed from US rules - with the cycle math, off-duty enforcement, and audit trail that keep a carrier onside and ready for an inspection or an NSC facility audit.

Certified-ELD integration and NSC Standard 9 cycle tracking (70h-7day / 120h-14day)
Electronic driver logs, pre-trip inspections, and DVIRs
Audit-ready record-keeping with violation detection and edit trails
Driver safety scoring and CVSA inspection readiness
TDG documentation and dangerous-goods workflow support

A telematics and routing layer that turns vehicle data into fewer empty miles and fewer breakdowns - Canadian-distance and winter-aware routing, with maintenance driven by actual engine and odometer data.

Geotab / Samsara telematics integration for location, engine, and fuel data
Route optimization and deadhead reduction with load matching
Preventive maintenance scheduled on real engine hours and mileage
Fuel-tax (IFTA) mileage capture by jurisdiction
Cold-weather and corridor-aware routing with closure handling

A self-serve portal that answers where is my freight without a phone call - live ETAs on a Canadian route map, proof of delivery, and document access for shippers, brokers, and consignees.

Live load tracking and predictive ETAs on a route map
Self-serve shipper and broker portal with status and documents
Electronic proof of delivery with photos and signatures
Automated status and exception notifications (delay, detention, arrival)
EDI and API integration with shipper and broker systems

Dispatch to Delivery

Assign a Load Without Booking a Compliance Violation

A live mock of the dispatch and fleet console we build for Canadian carriers. Assign a freight load to a truck and watch the board check the driver's remaining Hours of Service, flag the run before it breaks the National Safety Code, and offer a relay or swap to fix it. Track the ETA on a Canadian route map, then flip to the driver view for a live HOS clock and proof of delivery.

Auto-playing: assign a long haul to a near-limit driver, hit the HOS block, relay it legal, roll the truck, then deliver from the cab.

dispatch.chinookfreight.ca/board
Chinook Freightlines
Dispatch board

Dispatch freight, legally

Assign loads on Canadian lanes with an Hours-of-Service check on every dispatch

ELD / HOS guardrails on

On-time

94.2%

Utilization

81%

Deadhead

12.4%

HOS compliance

99.1%

Live route map

Dispatch a load to light its lane and roll the truck across the corridor.

Load board

3 open
  • L-4471YYCYWG13 h

    Dry van - retail freight22tThu 14:00 - 18:00

    Open
  • L-4473YYCYVR11 h

    Reefer - produce18tWed 08:00 - 12:00

    Open
  • L-4475YEGYXE5 h

    Flatbed - steel24tWed 16:00 - 20:00

    Open
  • L-4468YYCYEG3 h

    Dry van - parcel9tTue 13:00 - 15:00

    T-07Sukhdeep GillETA Tue 14:10

    Dispatched

Pick a driver from the roster to dispatch the next open load. Every assignment runs an HOS check first.

Fleet & drivers

3 ready
  • T-14Dwayne Cardinal

    Calgary, AB

    Available
    Drive11.5 hOn-duty12.0 hCycle48.0 h
  • T-22Renee Beaulieu

    Calgary, AB

    Available
    Drive2.0 hOn-duty2.0 hCycle12.0 hLow hours
  • T-07Sukhdeep Gill

    Edmonton, AB

    On a load
    Drive13.0 hOn-duty13.5 hCycle61.0 h

Dispatch log

  • Sukhdeep Gill on YYC - YEG, ETA Tue 14:10

    just now

  • Shift board synced - 3 open loads, ELD hours current across the fleet

    earlier today

Every assignment, HOS check, relay, and delivery is logged with the ELD hours - a full, auditable trail.

Illustrative mock of the dispatch and fleet console we build for Canadian carriers and logistics operators. The carrier, drivers, trucks, loads, lanes, Hours-of-Service figures, ETAs, and KPIs shown are entirely fictitious. The real product runs on Canadian data residency with ELD / HOS-aware dispatch enforcing NSC Standard 9 limits, telematics and route integration, and proof-of-delivery synced back to the board - built to WCAG 2.2 AA.

The Regulatory Map

The rules we design around

Compliance is architectural for us, not a checkbox added at the end.

ELD Mandate

Canadian ELD Mandate

Federally-regulated carriers must use a third-party-certified electronic logging device to record Hours of Service. We integrate with certified ELDs and build our logging to the certification requirements, rather than rolling an uncertified logger that an inspector will reject.

Applies to: Federally-regulated carriers and their drivers

NSC HOS

National Safety Code Standard 9 - Hours of Service

The Canadian Hours-of-Service rules - 13 hours driving, 14 on-duty, mandatory off-duty, and 70-hour-7-day or 120-hour-14-day cycles. We build the cycle math and off-duty enforcement to the NSC, not to US FMCSA rules, so the system flags real violations and not phantom ones.

Applies to: Commercial carriers operating across NSC jurisdictions

TDG

Transportation of Dangerous Goods Act & Regulations

Federal rules for classifying, documenting, placarding, and handling dangerous goods - distinct from the US 49 CFR. We design shipment and document workflows so the right TDG paperwork, training records, and placarding details travel with the load.

Applies to: Carriers and shippers moving dangerous goods

Customs / CARM

CBSA eManifest / US ACE / CARM

Cross-border freight requires advance commercial information - CBSA ACI/eManifest northbound and US CBP ACE southbound - while CARM reshapes how duties and the importer of record are handled. We build the data capture and integrations so the border crossing is not a manual scramble at the bridge.

Applies to: Carriers and brokers running cross-border lanes

PIPEDA

PIPEDA

Canada's federal private-sector privacy law governs driver and customer personal information, including telematics and location data - which is personal data when it tracks an identifiable driver. We design consent, retention, and access into how location and ELD data are stored and shared.

Applies to: Any carrier handling driver or customer personal data

IFTA / IRP

IFTA / IRP - Fuel Tax & Registration

The International Fuel Tax Agreement and International Registration Plan govern how interjurisdictional fuel tax and plate registration are reported by distance travelled in each jurisdiction. We capture mileage by jurisdiction from telematics so quarterly IFTA filings come out of the data instead of a logbook reconstruction.

Applies to: Carriers operating across provincial and state lines

Proof Points

Patterns we have shipped

The scenario

Regional carrier moving 60 trucks off paper logs to certified ELD

Replaced paper logs and a distrusted logger with certified-ELD integration and NSC-correct cycle tracking - phantom violations disappeared, the parallel safety spreadsheet went away, and the fleet walked into its NSC facility audit with a clean, defensible record.

Audit-ready logs, zero parallel spreadsheets

The scenario

Freight broker / 3PL with no real-time visibility into loads

Built a dispatch platform with live tracking and a self-serve shipper portal - the check-call volume collapsed, shippers answered their own where-is-my-freight questions, and the brokerage took on more loads per coordinator without adding headcount.

Check calls down sharply, loads per coordinator up

The scenario

Private fleet bleeding margin on empty backhaul miles

Wired routing and load matching into dispatch so the planner sees the legal, loaded option first - cut deadhead kilometres, recovered revenue on previously-empty return trips, and gave dispatch a Hours-of-Service-aware board instead of a whiteboard.

Deadhead kilometres cut, backhaul revenue recovered

Tools Chosen for the Job

Why we use what we use

React Native + Expo

One codebase for the driver app on iOS and Android that captures logs, inspections, and proof of delivery offline in a dead zone and syncs on reconnect - with over-the-air updates so a fix reaches the cab without an app-store wait.

PostgreSQL + PostGIS

A relational core with geospatial indexing for routing, geofencing, ETA calculation, and mileage-by-jurisdiction - the spatial queries a dispatch and routing engine lives on, without bolting on a separate GIS.

Geotab / Samsara / certified-ELD integrations

Direct integration with the telematics and ELD hardware fleets already run, so location, engine, fuel, and Hours-of-Service data flow into dispatch instead of being re-keyed - and the ELD stays certified.

Event-driven tracking pipeline

A streaming pipeline for GPS pings, status changes, and exception events so the board, the ETAs, and the shipper portal update in real time and notifications fire on delay, detention, or arrival.

Next.js + TypeScript

Server-rendered dispatch dashboards and a shipper/broker portal that load fast on a warehouse tablet or a phone in the yard - type-safe end to end from the portal to the API.

AWS Canada

Reproducible, Canadian-resident infrastructure in the Calgary and Montreal regions, keeping driver, customer, and location data in Canada by default and aligned with PIPEDA.

FAQ

Questions buyers ask first

Common questions about logistics & transportation software development in Canada

Ready to talk logistics & transportation software?

Book a 30-minute scoping call. We will walk through your operation, talk through what's worked for similar Canadian logistics & transportation operations, and tell you honestly whether we are the right team.