Cross-border fleets running 5–200 trucks on Alberta and Saskatchewan ↔ USA lanes need a matcher that ranks leased owner-operators and company drivers on their own ledgers and shoots the load to the right cab in minutes. LoadBridge AI scores every cross-border posting against the whole fleet in parallel — Coutts-Sweetgrass and North Portal both covered, the empty-leg back across the border closed before the miles start.
Built by someone who drove it — 30 years, 49 US states, 90% of Canada, including the same Alberta / Saskatchewan corridors.
One southbound empty leg burns miles. A fleet of twenty southbound empty legs burns the month — every unloaded mile across the fleet adds up, and the back-office is not built to surface the per-truck, per-leg exposure in real time. Closing the backhaul before the drop is what turns fleet-wide empty miles back into load miles, before the dispatcher starts the 20-minute phone tag that defines the cross-border back-office.
Concept framing informed by cross-border fleet dispatch practice; specific per-truck economics vary by lane, broker, currency hedge, and quarter.
A carrier's next leg is not a straight line back to origin — it is a four-directional decision the matcher scores continuously, against every truck on the fleet in parallel. South to Texas, east to Chicago, west to the Pacific Northwest, north via North Portal — each leg has its own backhaul cycle and its own load-board density.
Edmonton and Calgary southbound to Dallas / Houston / San Antonio carry the deepest empty-leg exposure on the prairies. A multi-truck carrier running five trucks south every Monday needs a load booked at every Texas drop, or those trucks burn 1,650–2,150 empty miles repositioning to wherever the next pickup is — north across the border, east to a new market, or further south — across leased owner-op trucks and company-driver trucks alike. LoadBridge scores each truck independently so the desk can reassign the load that closed first to the driver sitting 20 minutes closer.
Calgary → Chicago is the densest eastbound cross-border lane; Edmonton → Ontario / Quebec is the same triangle on a slower freight cycle. For a fleet of 10–25 trucks, the eastbound return is where the matcher earns its keep — Chicago / Detroit / Sarnia drops land in minutes and the desk needs to instantly see which truck can clear the border on current HOS without burning a reset. Each score surfaces the document set the truck is filed under so the dispatcher does not commit a truck without a PARS barcode attached.
Edmonton and Calgary westbound to Seattle / Portland are typically booked on import freight. Returns into AB often run light, but the cross-border premium is lower than south or east because the BC corridor is mostly intra-Canada. For a fleet, that leg is a filler — useful for one well-rested truck, not a primary backhaul — and the matcher tags it as such so the dispatch desk knows which lane to spend a phone call on.
Saskatoon and Regina northbound are intra-Canada; the more interesting direction is south-via-SK to North Portal, then I-29 down to Texas. SK carriers reach the southern US faster than they would through Alberta, and the North Portal queue is shorter than Coutts-Sweetgrass at peak. For a Saskatchewan-anchored fleet, North Portal is the primary gate; for an Alberta-anchored fleet it is the alternate when Coutts is stalled at the rail bridge backup.
These four lanes recur every quarter in Alberta / Saskatchewan cross-border fleet dispatch data. Each row tracks how much empty-leg exposure the fleet carries over weekly round-trips — the fraction of the haul that returns across the border without revenue.
| Corridor | Loaded (one RT) | Empty-leg exposure | Empty-leg impact |
|---|---|---|---|
🇨🇦 CA ↔🇺🇸US Edmonton, AB ↔ Dallas, TX | ~2,150 mi RT | Southern return ~50% of fleet miles if unbooked | High |
🇨🇦 CA ↔🇺🇸US Calgary, AB ↔ Chicago, IL | ~1,650 mi RT | Eastern return ~40% of fleet miles if unbooked | High |
🇨🇦 CA ↔🇺🇸US Calgary, AB ↔ Houston, TX | ~2,000 mi RT | Southern return ~45% of fleet miles if unbooked | High |
🇨🇦 CA ↔🇺🇸US Saskatoon, SK ↔ Houston, TX (via North Portal) | ~2,000 mi RT | Southern return (via North Portal) ~45% of fleet miles | High |
Empty-leg impact is a directional label (High across the four fleet-ops corridors on the prairies), not a recoverable dollar estimate — actual backhaul economics vary by rate per mile, fuel stops, currency hedge, HOS windows at each border, and the leased vs company-driver split on the fleet. The label reflects direction, not dollar split.
The bottleneck on a fleet is not the per-driver pick — it is the per-desk queue. Two concerns dominate: keeping leased owner-op and company-driver trucks on separate ledgers so the per-truck P&L stays honest, and pushing the right truck the right load without the 20-minute phone tag that defines the cross-border back-office.
A leased owner-operator is paid off the net of the load, not the gross; a company driver is paid off the gross plus per-mile, with hours-of-service paid on top. The matcher keeps them on separate ledgers because folding them into one score hides the real margin — a leased truck running a high gross but thin net looks identical to a company truck running net-positive miles, and the desk assigns the wrong driver to the wrong load. LoadBridge AI parses each truck as either leased or company before the queue score is calculated, and the dispatcher sees the per-truck P&L impact before they hit assign.
A solo O/O closes the empty leg with one phone call. A fleet desk closes 20 empty legs at once, with the same person on the phone — so what matters is not how fast a driver picks the load, it is how fast the desk can shoot the load to the right truck. The matcher renders one ranked list across the fleet for every posting, scores both leased and company trucks against the same load simultaneously, and the picker assignment sends the load detail (PARS, ACE eManifest, broker contact) to the assigned driver in a single push — so the desk spends minutes, not the customary 20-minute phone tag, per load.
For a fleet, a posted spot quote is rarely the number the carrier should accept — and treating the rate as a free-form question at the desk burns the call. The LoadBridge AI rate-negotiation step counters inside the policy window the dispatcher configures: three-band bracket (minimum-accept → target → walk-away), per-load rationale visible before accept, no counter above the window without surfacing a manual-approval request to the desk.
Per-truck windows for leased owner-operators (because each lease has its own split that moves the minimum-accept floor). Fleet-wide windows for company drivers paid off the same per-mile floor across the fleet (so the AI counters consistently). On every cross-border posting, the matcher produces a counter inside the window — every counter is paired with the same four-input rationale as the solo-O/O flow (currency, fuel-surcharge basis, customs detention, broker spread), and the dispatcher sees the full counter history plus the per-counter rationale before they hit accept. The never-counters-outside-the-window guarantee is the part that matters most to a fleet manager: the AI will not freelance on a number the desk has not authorized.
Informational copy — describes the matcher's decision logic; this static page does not invoke the AI endpoint.
Settlement is where a fleet sees the cross-border margin land — and where a single bad reconciliation across twenty trucks can eat a week. The LoadBridge AI Stripe flow consolidates payouts across the whole fleet: one weekly settlement, multi-truck reconciliation built in, and the carrier Pro subscription owned end-to-end on the /pricing page.
A solo O/O carries the working capital for one truck; a fleet carries it for twenty. The difference is one weekly settlement against one day-truck, not forty — so the payout cadence is the cash-flow lever, not the per-load fee. The /pricing page owns the carrier Pro subscription end-to-end, including the seat rate per dispatcher, the per-truck surcharge above the base fleet size, and the consolidated Stripe payout that closes the week without a follow-up spread.
Informational copy — points to /pricing for the actual Pro subscription, plan, and hosted checkout; this page does not embed Stripe Elements.
Fleet onboarding is per-truck, not per-company — every tractor on the fleet needs its own CARRIER PROFILE on record with CBSA (PRO/CRS number), its own PARS barcode flow tied to the US Customs broker on that truck, and its own ACE eManifest filing. The good news is that the rest is templated: once one Alberta-anchored truck is fully papered for Coutts / Sweetgrass, the same documentation footprint copies to trucks 2–N with only the per-tractor US DOT update. Most fleet managers spend the first week on trucks 1–3 as short-lane cross-border (Calgary → Great Falls, Edmonton → Billings) because the documentation loop closes inside the same week, and then scale trucks 4+ as the desk gets the queue-pattern for the multi-truck load flow.
Each truck in the fleet has a profile flag — `leased` or `company` — that the matcher reads before the score is computed. Two parallel scores are produced: the leased-truck score is discounted by the per-load flat / revenue-share split you pay the O/O (so the desk sees net-effective margin, not gross revenue); the company-truck score is gross-margin plus HOS cost, with hours-of-service clocked separately per driver. The dispatch desk sees one ranked list across the fleet but the leased and company trucks come back tagged, so assigning the wrong driver to the wrong load does not happen. Per-truck P&L is also visible before the assign is pushed, so the dispatcher knows the cost of every match before committing the cab.
A policy window is the bracket you set per truck (or per fleet, for company drivers paid off a uniform floor) inside which the AI is allowed to counter a broker quote. The window has three bands: the minimum-accept (below this number the AI walks away and the desk gets the call), the target (the number the AI tries to land on the first counter), and the walk-away (above this number the AI accepts without a counter at all). Everything between minimum-accept and target is the negotiation corridor — the AI counts down with rationale on every counter. The window is set once per truck (or once per fleet, for fleet-wide floors), and the dispatcher sees the full counter history plus the per-counter rationale before they accept. The AI never counters outside the window without surfacing a manual-approval request to the desk first.
The matcher scores every posting against every active truck in the fleet in parallel — south, east, west, and north returns are all evaluated simultaneously per drop. The dispatch desk sees one ranked queue per drop, with leased and company trucks tagged and the rationale visible. Instead of one driver working one phone call, the desk works the queue: when a Chicago return posts, the matcher has 10–25 trucks pre-scored against it, the desk assigns the closest, the driver gets the load detail (PARS, ACE eManifest, broker contact) in one push, and the queue moves on to the next posting. The reduction in empty legs scales with the fleet size because the desk now treats the empty-leg problem as a queue, not a one-by-one phone tag.
Pro for fleets gives unlimited trucks per account (the per-truck rate is the same regardless of fleet size), multi-driver PIN login per truck for HOS compliance, fleet-wide policy-window rate configuration (with per-truck overrides when needed), priority lane coverage for the four-direction matcher, and consolidated Stripe payout + reconciliation across the whole fleet (so the desk sees one settlement per week, not one per truck). Pricing scales off the fleet size and the load volume — the per-truck and per-seat rate is set on the /pricing page, and the Pro subscription is the only checkout flow that grants multi-truck sponsorship.
Watch the live demo queue your trucks against a real Edmonton → Dallas or Calgary → Chicago load — deterministic multi-truck scoring, AI-priced rationale inside the policy window, and the load detail pushed to the right cab. Compare Pro for fleets on /pricing.
No commitment required. Respond within 1 business day.
Watch the live matcher queue your trucks in real time against every fresh cross-border posting — leased and company-driver trucks scored on their own ledgers, the load pushed to the right cab in minutes. See the live demo.
Sister route for the owner-operator running the same Alberta and Saskatchewan corridors one truck at a time — same four-direction matcher, same AB / SK corridor set, single-truck framing. See the Alberta cross-border landing page.
The Pro-for-fleets subscription — unlimited trucks per account, fleet-wide policy-window rate configuration, consolidated weekly Stripe payout — is set end-to-end on the pricing page. See the multi-truck Pro plan and per-seat rate.