// 00CARRIER · Load Planning Runtime for Freight Operators

CARRIER·

Fewer Trips · Tighter Loads · Audit-Ready Dockets

Stop guessing what goes on which trailer, in what order, on which trip. CARRIER decides — the dispatcher signs.

CARRIER is a load planning runtime for freight operators. Box pools ingest from the dock, an operator queue, or a CSV. The runtime produces a complete plan for every trip — which box on which truck, where in the trailer, in what order, on which axle — and the dispatcher reviews and signs each docket before it commits. The outcomes show up on the first dispatch: fewer trips per pool, tighter trailer utilisation, multi-stop loads packed in delivery order, DOT-bound by default, and a paper trail that holds up to audit.

// 01What Changes

Outcomes you can measure on the first dispatch.

The dispatcher's daily question — "what goes on which trailer, in what order, on which trip?" — becomes a queue of dockets to review rather than a spreadsheet to wrangle. What that means concretely, on day one:

// OUTCOME 01

Fewer trips per pool

Same freight, fewer trucks dispatched. CARRIER compresses a pool against your specific fleet and constraints and consistently produces fewer trips than a hand-planned schedule or a single-heuristic planner.

Lower Dispatch Cost
// OUTCOME 02

Tighter trailer utilisation

Every cubic foot the trailer can legally carry, the runtime fills — while staying inside DOT axle limits and respecting your class rules. Utilisation often pushed into the high 90s on bulky freight.

Less Wasted Space
// OUTCOME 03

Multi-stop loads in delivery order

The trailer is divided into stop zones. Load order matches the delivery sequence — first-off goes in last. No more re-stacking at stop three because the boxes are in the wrong order at the back.

Drivers Stop Arguing
// OUTCOME 04

DOT compliance by default

Axle weight limits, kingpin-to-rear-axle distance, payload caps, trailer dimensions — all bind before the plan is generated. A plan that violates a constraint never reaches the dispatcher. Signing means signing into the envelope.

No Surprise Violations
// OUTCOME 05

Fragile stays fragile

Every box carries a class — heavy, medium, light, fragile, plus operator-defined classes for hazmat, temp-controlled, oversize. Class is a hard constraint: fragile never under heavy, hazmat segregated, temp-controlled near the reefer.

Class-Aware Packing
// OUTCOME 06

Audit-ready dockets

Every trip generates a printable, signable manifest — box-by-box placement, stop sequence, axle load, constraint envelope, signed timestamp. Auditors get the paper trail. Drivers get the load chart. Operators get the receipts.

Printable · Signed · Replayable
// 02Why It Wins Consistently

Six algorithms compete to optimize every load.

Most load planners run a single packing heuristic and accept whatever it produces. The problem: no single heuristic is right for every load. A pool of bulky low-weight freight wants one strategy. A pool hitting axle limits wants another. A pool with mixed fragility wants a third. CARRIER's advantage is mathematical — a bank of engineered optimisation strategies, raced in parallel, ranked on what matters operationally. The specifics of the bank stay inside the engagement.

// PROPERTY 01

Multiple strategies, raced in parallel

CARRIER solves every pool several ways at once. Each strategy is engineered for a different binding constraint — space, weight distribution, class mix, route geometry, fuel economy. The strategy that wins is the one that fits the pool on the dock today, not the one that won last week.

Multi-Strategy · Constraint-Bound
// PROPERTY 02

Ranked on what matters operationally

The candidate plans are scored on trips required and load efficiency — the two numbers your CFO actually cares about. The winner is surfaced alongside the runners-up so the trade-off is visible. The dispatcher can switch strategies or override a placement without leaving the runtime.

Trips × Efficiency
// PROPERTY 03

Every decision replayable

The inputs, the strategy applied, the dispatcher who signed, the time — all written to the run log. Any docket can be replayed against any historical state and reach the same answer. The math is auditable end-to-end. Reproducibility is engineered in, not bolted on.

Replayable · Auditable
// 03How a Dispatch Works

Scan. Solve. Sign.

01

Scan

A box enters the pool — scanner at the dock, dispatcher queue, or CSV import. CARRIER records its id, dimensions, weight, class, and stop assignment. The pool keeps growing through the morning; the runtime is ready whenever the dispatcher is.

02

Solve

When the dispatcher hits go, the runtime solves the pool against your fleet — several strategies in parallel, ranked on trips and load efficiency. The output is a complete trip plan: which box on which trip, where in the trailer, in what order.

03

Sign

The dispatcher opens each trip docket, reviews the placement, accepts the recommendation (or switches strategies, or overrides a box), and signs. Only a signed docket commits. The signature, the strategy, the inputs are written to the run log.

// 04Who CARRIER Is For

Built for operators who dispatch every day.

CARRIER pays off most where load planning is a real daily decision rather than a once-a-week scheduling task. Three operator profiles are the clearest fit — the math compounds fastest at this kind of dispatch volume and complexity.

// PROFILE 01

Fleet operators & private fleets

Trucking companies and manufacturers running their own trucks, where dispatch volume is high enough that load planning is a real cost center. Every percentage point of utilisation matters across hundreds of dispatches a week. CARRIER compresses trips, raises utilisation, and gives dispatchers hours back per day.

High Volume · Daily Dispatch
// PROFILE 02

3PLs · LTL · multi-stop

Less-than-truckload carriers, regional 3PLs, food and beverage delivery, retail replenishment — operations where every truck makes multiple drops and unload order matters as much as load efficiency. CARRIER's stop-zone packing makes drivers faster at every stop and removes the re-stacking penalty at the back of the trailer.

Multi-Stop · Route-Aware
// PROFILE 03

Specialised & regulated freight

Hazmat, refrigerated, oversize, food-grade, fragile — operators where class constraints, segregation rules, and audit trails are not optional. CARRIER treats class as a hard constraint and produces a signed, replayable docket for every trip. The compliance paper trail builds itself with every dispatch.

Class-Bound · Audit-Grade
// 05Frequently Asked

Direct answers.

What does CARRIER actually do for a freight operator?
CARRIER decides — for every freight pool you load — how many trips you need, which boxes go on which trip, where in the trailer each box sits, and in what order. The dispatcher gets a complete docket per trip, reviews it, signs, and commits. The result is consistently fewer trips, tighter trailer utilisation, and a paper trail every step of the way.
How is this different from my current TMS or load planner?
Your TMS records what shipped and tells trucks where to go. CARRIER decides what should ship together, in which order, on which trailer — the question the planner used to answer in a spreadsheet. CARRIER sits ahead of the TMS. It does not replace it; it produces the load and trip plan the TMS then executes.
Does CARRIER work for multi-stop loads?
Yes — multi-stop is built in. The trailer is divided into stop zones, and the load order matches the delivery sequence: first-off goes in last. Every box on the docket carries its stop assignment. Drivers stop re-stacking at the back of the truck.
How does CARRIER handle fragile, hazmat, or temperature-controlled freight?
Every box carries a class — heavy, medium, light, fragile, plus operator-defined classes for hazmat, temp-controlled, oversize, or anything else relevant to the fleet. The runtime treats class as a hard constraint: fragile never under heavy, hazmat segregated by your rules, temp-controlled placed near the reefer. The dispatcher does not have to re-check these every load.
Will it keep us inside DOT axle limits?
Yes. DOT axle weight limits, kingpin-to-rear-axle distance, payload caps, and trailer dimensions bind before any plan is generated. A plan that violates a constraint never appears on the docket. The dispatcher signs into the constraint envelope, not against it.
Is CARRIER autonomous?
No. Every docket queues for a dispatcher signature before it commits. The dispatcher can accept the recommendation, switch to a different load plan, or hand-place an individual box. The runtime carries the cognitive load; the dispatcher owns the decision and the signature.
How do I get started?
Send a one-paragraph brief through the engagement form on our Contact page describing the operation, the fleet (size and trailer types), the freight mix, and the timeline. Direct inquiries and introductions are both fine — no referral required. We respond within two business days with next steps.
//Engagement

Move freight every day?
Let's talk about how CARRIER fits.

Send a brief through the form · Response within two business days