How it runs
Verified carriers in. Certified shipper paths through. Controlled execution out.
48BY40.io verifies carrier truth. Freight establishes shipper certification. Packet truth and approvals determine quoting and execution access — separately. Movement runs under verified conditions. Proof and review feed downstream settlement-readiness.
The universal application
This workflow runs on every load. Not a tier. Not an SLA upgrade. The operating standard. Pricing differentiates scale and depth; pricing does not differentiate whether the system fully works. Same workflow on load one. Same workflow on load ten thousand.
Six gates. One governed loop.
Most freight platforms compress this loop into one step. We don't. The whole point is that the gates are real.
Stage 1 · Verify carrier truth
48BY40.io continuously verifies carrier identity, authority, insurance, documents, safety, and equipment. The standing layer is upstream of every Freight decision.
Stage 2 · Establish shipper relationship
Standard relationship path or structured-capacity path. We learn the shipper's lanes, equipment, operating posture, and commercial structure before quoting touches the relationship.
Stage 3 · Quote-ready approval
The four document packets — Legal, Commercial, Treasury-Billing, Operations — are reviewed. When packet truth and operating reality are sufficient, the relationship is cleared into governed quoting.
Stage 4 · Execution-ready approval
A separate gate. Quote-ready does not mean execution-ready. Execution access turns on once execution-readiness is documented.
Stage 5 · Routed and executed
Loads cascade through Contract → Preferred → Open Auction tiers, gated on verified carrier standing at every tier. Once routed, the operational stack runs end to end. Every load. Same workflow.
Dispatch. The load is confirmed to the carrier in standing. Documented expectations attach at dispatch.
Driver assignment and license verification at pickup. The driver who will move the load is identified before pickup; the license and identity are matched against the verified-standing record.
In-platform document staging. The bill of lading and load-specific documents are staged in the platform — not assembled at the gate.
Two-party sign-off at pickup. Carrier and shipper-side (or shipper-designated facility) each sign the load into the carrier's possession. The event chain opens with documented proof, not a paraphrased version.
Live en-route visibility. Telematics inputs from Samsara, SkyBitz/AMETEK, and Geotab surface continuous position. No "where's my driver" calls.
Direct messaging. Dispatcher, driver, and shipper communicate on the platform — not on side-channels that break the audit trail.
Shareable customer-facing track-and-trace. The carrier can share a customer-facing URL with their shipper directly — the shipper sees position continuously without needing to call.
Delivery sign-off. Two-party sign-off at delivery closes the event chain with documented proof.
Immediate claim flagging. Exceptions surface in real time at delivery — not in a retrospective claim cycle weeks later.
Movement runs against documented expectations the platform tracks, not against improvised phone-and-spreadsheet workflow. The event chain produced through these steps becomes the captured operating proof matched in flight against the canonical proof chain.
Stage 6 · Proof and review
Captured operating proof matches in flight against the canonical proof chain. The platform carries the artifacts and the matching:
Doc-and-bill match. The canonical document runs against the captured event chain. Settlement closes against matched proof — not against month-end reconstruction.
Payment per agreed terms. Settlement runs per the Treasury-Billing packet the shipper signed — on the terms documented, against captured proof. Not phone chase. Not month-end argument.
HOS-aware re-dispatch. Hours-of-service status surfaces against scheduled re-dispatch — the next load lands within hours-of-service visibility, not against an unknown clock.
Re-dispatch. The carrier moves from this load to the next without rebuilding the relationship or re-onboarding. Verified standing is portable across every shipper relationship the carrier holds in the network.
Backhaul matching. Return-load candidates surface against the carrier's verified standing and the network's open inventory.
Settlement-readiness follows from the captured proof — not from end-of-month reconstruction. The 48BY40-controlled match is the artifact that decides whether settlement opens or argues.
Commercial primitives underneath
The financial certainty layer.
Underneath the six-stage operating loop, Freight runs five commercial primitives that produce predictable lane economics. These primitives are universal across certified plans — pricing differentiates scale and depth, not whether these run.
Bidding (RFP/RFQ). Shippers run annual or quarterly bid events for lane portfolios; the platform supports the bid and the award.
Routing guide enforcement. The platform enforces routing-guide order at every tender — Contract → Preferred → Open Auction. Lanes awarded in the bid go to contracted carriers first.
Standardized fuel surcharge. Platform-set fuel-surcharge rules apply across loads — no per-load fuel disputes.
Standardized accessorial framework. Platform-set accessorial rates and dispute-resolution rules — detention, layover, redelivery, and exception handling all run on a documented schedule.
Standardized contract template. Platform-issued master commercial framework — trade terms, payment terms, indemnity, and dispute resolution land at the relationship layer, not per lane.
The operating loop runs against verified counterparties. The financial certainty layer runs against the operating loop. Together they are the universal operating standard — every load, every shipment, every verified counterparty.
Why we don't compress
Better execution starts with better truth on both sides of the move.
Generic brokerages collapse onboarding, quoting, and execution into one transaction. We separate them because they're different decisions with different truth requirements. A shipper can be in a relationship without being quote-ready. A shipper can be quote-ready without being execution-ready. A carrier can be eligible without being a fit for a specific load. Each gate exists because confusing them is how wrong-carrier risk gets through.
Move from reading to starting
You've read how it runs. The relationship intake is how you enter.
The six-stage operating loop runs against verified counterparties from intake to settlement. The relationship intake is gate two of that loop. Start there.