A refrigerated carrier based in Memphis was about to lose a steady customer. The shipper, a consumer goods company moving palletized freight between Dallas and San Antonio five days a week, had gotten a rate offer from a competitor that seemed impossible to match: lower per-mile rate, same service window, no hidden charges. The Memphis carrier's operations director pulled up the competitor's authority lookup out of curiosity, and what he found stopped him cold. The competitor was not running human drivers on that lane. They had booked Aurora autonomous capacity through their McLeod TMS (transportation management system) and were passing the driver-cost savings through to the shipper as a rate advantage. The Memphis carrier was losing freight not to a bigger fleet, but to a procurement mechanic they had not yet learned to use. By the end of that week, the operations director had made his first call to his McLeod account manager to understand how to get the same integration turned on.

How Autonomous Capacity Actually Reaches the TMS

The 2026 wave of bookable autonomous capacity works through a fundamentally different model than the AV (autonomous vehicle) demonstrations of the early 2020s. Aurora and other SAE (Society of Automotive Engineers) Level 4 autonomous operators have built commercial freight networks that connect directly to the TMS platforms carriers already use, rather than requiring carriers to adopt new dispatch software, learn a new interface, or join a separate marketplace. For Aurora specifically, the integration with McLeod Software means that a dispatcher with an existing McLeod account can see and book Aurora capacity the same way they would book capacity from a human-driven carrier in a freight brokerage arrangement: load goes into the TMS, the system queries available capacity, Aurora autonomous slots appear in the results alongside other options, the dispatcher selects and confirms, and the load is tendered.

That architectural choice, embedding autonomous capacity in existing TMS workflows rather than building a standalone AV booking platform, is what makes the 2026 market different from the pilot programs of earlier years. Aurora's 250,000-plus driverless commercial miles were not logged on a test track or in a controlled pilot with a single partner. They were commercial loads moved on freight contracts, billed to shippers, and tracked through the same operational infrastructure that human-driven freight uses. More than 1,200 fleets now have access to the McLeod-Aurora integration, and the number is growing as Aurora expands its ODD (operational design domain), the certified geographic and environmental envelope within which its vehicles can operate without human backup.

The market context matters for procurement decisions. The autonomous long-haul market was $2.7 billion in 2024 and is projected to reach $42.6 billion by 2034 at approximately 32 percent CAGR (compound annual growth rate). The carriers that have figured out how to incorporate autonomous capacity into their procurement mix in 2026 are not chasing a trend; they are building operational capability in a market that will be structurally different within five years. The Memphis competitor who beat the Memphis carrier on that Dallas-to-San Antonio lane understood this. The Memphis carrier, once it caught up, understood it too.

The Procurement Mechanics of Booking Through McLeod

Understanding how to actually book autonomous capacity requires working through the procurement mechanics at each stage of the process, because several steps differ from conventional capacity booking in ways that create operational risk if the dispatcher handles them the same way as a human-driver load.

Step One: Enabling the Integration

Access to Aurora autonomous capacity through McLeod begins with enabling the integration at the carrier or fleet level. McLeod customers who have not yet enabled the Aurora integration will not see AV capacity in their load board results. The enablement process involves a commercial agreement between the carrier and Aurora (covering rates, terms, liability allocation, and ODD parameters), followed by an integration configuration step in the McLeod platform that links the carrier's account to Aurora's capacity feed. This is not a self-service setup for most carriers; it requires involvement from the carrier's McLeod account manager and Aurora's fleet onboarding team. The configuration typically takes one to three weeks from the commercial agreement to live integration, and carriers should budget time for their TMS administrator to test the integration on a small number of loads before relying on it for high-value freight.

The commercial agreement is where the rate structure, the liability split, and the service-level commitments are documented. Unlike a spot market transaction with a human carrier, where rates are often negotiated load by load, the Aurora arrangement in 2026 operates more like a contract carrier relationship: the carrier agrees to route certain eligible loads through Aurora's network at agreed-upon rates, and Aurora commits to capacity availability and service performance within its ODD. Carriers should read the ODD schedule in the commercial agreement carefully, because it defines which lanes the autonomous capacity covers and what happens when weather or infrastructure conditions push a load outside the certified corridor.

Step Two: Load Eligibility Screening

Not every load in a carrier's book is eligible for autonomous deployment. The eligibility screen happens at the load level, and it involves checking the load against several criteria simultaneously.

The ODD corridor check is the most fundamental. The load's origin and destination must both fall within Aurora's certified network, and the routing must stay within the ODD for the entire movement (or, for hub-and-spoke lanes, the autonomous segment must be fully within the ODD with a defined relay point for the human-driven segments). A load that originates in Austin and terminates at a warehouse dock inside the Dallas city limits may have its autonomous-eligible segment end at a relay hub on the outskirts of Dallas, with the final urban delivery handled by a human driver. The TMS configuration built during integration setup should flag this automatically, but the dispatcher confirming the assignment needs to understand what "AV eligible" means in practice for each specific load.

The equipment check is the second criterion. Aurora's vehicles are Class 8 tractors operating in specific configurations. A load requiring a flatbed, a tanker, a specialized trailer type, or temperature-controlled equipment may not be compatible with the current AV fleet configuration. As autonomous operators expand their equipment type coverage, this constraint will loosen, but in 2026 the majority of autonomous capacity is configured for dry-van trailers, with reefer and other configurations in earlier stages of deployment.

The customer consent check is the third criterion. Some carriers have contracts with shippers that pre-date the autonomous wave and contain language about the type of equipment or driver that will be used. Before assigning autonomous capacity to a customer's freight, the carrier should confirm that the customer's contract and preferences are compatible with AV delivery. This check should be part of the TMS's customer profile configuration, not a dispatcher's personal knowledge, so it is applied consistently and documented.

The hazmat and cargo-type check is the fourth. Certain hazardous materials designations and cargo types may have regulatory or insurance restrictions on autonomous transport in 2026. The carrier's compliance team should maintain a definitive list of cargo types that are cleared for autonomous transport and those that are excluded, and that list should be embedded in the TMS eligibility logic.

Step Three: Rate Comparison and Assignment Logic

One of the genuine operational questions for a carrier integrating autonomous capacity is how to price and assign loads when both AV and human-driver capacity are available for the same lane. The cost structure of autonomous capacity differs from human-driven capacity in ways that are not uniformly favorable. On long, open interstate corridors, AV capacity often comes in at a lower per-mile cost than human-driven capacity because there is no driver wage, no driver per diem, and no HOS (hours-of-service) constraint limiting how long the truck can run without a break. On shorter loads, loads with complex pickup or delivery requirements, or lanes that require hub-relay handling, the calculus may be different because the relay infrastructure and the human-segment costs need to be factored in.

The rate comparison should be done at the fully-loaded cost level, not the per-mile rate. A carrier that adopts autonomous capacity based on the per-mile quote without accounting for relay fees, hub facility costs, and the occasional human-driver insertion cost for exception handling may find that the net economics are less attractive than the headline rate suggested. The TMS configuration should, ideally, surface the total estimated cost for the autonomous slot alongside the total estimated cost for available human-driver options so the dispatcher or the load-planning algorithm can make an informed comparison.

Assignment logic for carriers operating high volumes of autonomous-eligible loads is increasingly being managed by the TMS's optimization layer rather than by dispatcher judgment on individual loads. The optimization logic can be configured to automatically prefer autonomous capacity for eligible loads when the total cost is below a defined threshold relative to human-driver options, subject to the eligibility checks described above and the human confirmation gate. Carriers with higher load volumes will want to invest in this configuration work because manual load-by-load comparison is unsustainable at scale.

Step Four: Tendering and Confirmation

The tender process for an autonomous load through McLeod follows the same EDI (electronic data interchange) framework as a conventional tender to a contract carrier, with some additional data fields specific to autonomous operations. The load tender confirms the origin, destination, equipment type, freight details, and pickup and delivery windows. It also triggers Aurora's capacity allocation process, which assigns a specific vehicle to the load from Aurora's available fleet and begins the pre-route planning process that includes weather modeling, ODD validation for the planned route, and transfer hub scheduling if the load requires a relay.

The carrier receives a confirmation that includes the vehicle identifier, the planned route, the relay hub assignments if applicable, and the estimated delivery window. That confirmation is not simply a "we have a truck for this load" response; it is the carrier's agreement to the specific operational parameters that Aurora's system has planned. The carrier should review the relay hub assignments in particular, because they define where the human-driver segments begin and end, which determines which of the carrier's drivers (or third-party local carriers) need to be positioned for pickup at the hub.

The tender confirmation also starts the clock on the carrier's responsibility for hub coordination. If the load requires a relay, the carrier needs to confirm that a human driver will be available at the designated hub at the projected arrival time. That coordination is the carrier's operational responsibility, not Aurora's, and it is one of the most common failure points in early mixed-fleet deployments. A carrier that tenders the autonomous load without confirming hub capacity is booking a load it may not be able to complete on the delivery window it committed to.

Monitoring and Exception Management During Transit

Once an autonomous load is rolling, the carrier's operational role shifts from dispatch management to exception monitoring. Aurora's operations center provides the primary real-time monitoring of the vehicle's system state, route compliance, and ODD status. The carrier's responsibility is to maintain awareness of the load's status through the TMS integration and to manage the business-level exceptions that Aurora's operations center cannot resolve: a shipper calling to change a delivery window, a consignee requesting early access, a customer service escalation that requires a human with carrier authority to act.

The TMS integration surfaces Aurora's real-time load status in the carrier's tracking interface alongside the status of human-driven loads. Dispatchers should treat autonomous loads in the tracking queue the same way they treat human-driven loads: checking status at regular intervals, noting any planned delivery window deviations, and flagging exceptions for escalation. The specific exceptions that require carrier action include: a delivery window deviation of more than one hour (requiring proactive shipper or consignee notification), a hub arrival time shift that affects human-driver availability at the relay point (requiring immediate driver coordination), or a load suspension triggered by an Aurora system safety event (requiring the carrier's emergency protocol to engage either a human-driver rescue or a shipper delay notification).

The load suspension scenario deserves specific attention because it is the exception that most carriers are least prepared for. Aurora's system is designed to detect when route conditions exceed ODD parameters and to bring the vehicle safely to a designated stop point rather than continuing under conditions it is not certified to handle. When that happens, the carrier has a truck on the side of the road, a load that is not moving, and a delivery window that is at risk. The carrier's protocol for this scenario should specify, in advance: who the carrier's point of contact is for Aurora's operations center to notify, what authority that person has to authorize a human-driver rescue (dispatching a local carrier or a company driver to pick up the trailer and complete the delivery), and what the customer notification process is. The carrier that has never thought through this scenario will spend valuable time figuring out the protocol while the shipper's delivery window closes.

The Financial Model: Costing and Billing Autonomous Loads

The financial model for autonomous capacity has some structural differences from human-driven operations that affect how carriers cost and bill loads to customers. Understanding these differences is important both for maintaining healthy margins on autonomous loads and for pricing accurately to shippers who are comparing autonomous and human-driven rates.

On the cost side, the absence of driver wages and benefits is the most significant difference, and it is the source of the per-mile cost advantage on long corridor runs. However, autonomous loads carry costs that human-driven loads do not: relay hub access fees (charged by Aurora or by the hub facility operator for staging and handoff), technology access fees built into the per-mile rate that the carrier pays Aurora, and the additional TMS configuration and compliance overhead of managing a dual-capacity system. The carrier's cost model for autonomous loads should explicitly break out these categories so that the comparison between autonomous and human-driven fully-loaded cost is based on accurate numbers, not just the headline per-mile rate.

On the billing side, the question of whether to present autonomous capacity as a line-item service to shippers or to blend it into the carrier's standard rate structure depends on the carrier's commercial strategy. Carriers who want to use autonomous capacity as a competitive differentiator on price should disclose it to shippers and pass through some of the savings as a rate incentive, which is the strategy the Memphis competitor used to win the Dallas-to-San Antonio lane. Carriers who want to maintain rate discipline and use autonomous capacity to improve their own margins rather than compete on price can treat the autonomous slot as an internal procurement decision, not visible to the shipper as a separate service category. Both strategies are commercially valid, but they require different disclosure practices and different customer communication protocols.

From a billing documentation standpoint, loads moved on autonomous vehicles require the same POD (proof of delivery) documentation as human-driven loads, including a delivery timestamp, consignee signature (where required), and notation of any exception. The ELD (electronic logging device) mandate that governs human-driven operations does not apply to vehicles without a human driver, but the carrier still needs to maintain a digital record of the load's movement that can serve the same evidentiary function in a freight dispute or regulatory inquiry. Aurora's route log serves this function for the autonomous segment; the hub handoff record and the human driver's ELD serve it for any relay segments.

Building Autonomous Procurement Into the Carrier Strategy

The carriers who will extract the most value from the 2026 autonomous wave are those who treat AV capacity as a procurement category to be managed strategically rather than a novelty to be evaluated one load at a time. Strategic management of autonomous procurement means thinking about lane commitment, network capacity mix, and investment in the operational infrastructure that makes AV capacity reliable rather than experimental.

Lane commitment is the starting point. Rather than booking autonomous loads opportunistically as they appear eligible, a strategic carrier identifies the three to five lanes in its network where autonomous capacity offers the clearest advantage (long interstate corridors, consistent freight patterns, ODD-compatible end points) and negotiates contract capacity with Aurora on those lanes. Contract capacity gives the carrier priority access and more predictable rates; it also gives the carrier's operations team a defined set of lanes to build protocols around, which accelerates the learning curve.

Network capacity mix planning is the next level. A carrier running a 90-truck fleet does not need to decide whether to become an autonomous fleet or stay human-driven. The strategic question is: on which lanes and at what percentage of volume does autonomous capacity serve the network better than human-driven capacity? For a carrier whose core network has three or four long-haul interstate corridors surrounded by urban distribution operations, the answer might be to target autonomous capacity for 30 to 40 percent of the corridor volume while keeping all urban distribution in human hands. That mix decision should be revisited quarterly as ODD coverage expands and as the carrier's performance data on autonomous loads accumulates.

Investment in operational infrastructure is what separates the carriers who make autonomous capacity work from those who get frustrated by exception handling and abandon the program. The operational infrastructure includes: TMS configuration (eligibility rules, rate comparison logic, confirmation workflows, exception escalation paths), hub relationship management (contracts or standing agreements with the relay hub facilities the carrier's lanes require), driver communication (ensuring that drivers who work relay segments understand the handoff protocol and the DVIR requirements), and customer communication (disclosure processes and exception notification templates). None of this infrastructure is complex, but it all requires deliberate investment before the first load, not retroactive construction after the problems surface.

The FMCSA (Federal Motor Carrier Safety Administration) regulatory updates on driverless operations are moving on a parallel track to the commercial expansion of autonomous capacity. Carriers building their procurement protocols in 2026 should designate a point of responsibility for tracking FMCSA regulatory developments related to autonomous operations, because rule changes on inspection requirements, electronic logging for AV loads, and liability documentation could require protocol adjustments with relatively short notice. The carrier that has someone watching the regulatory track is in a far better position than the carrier that discovers a new FMCSA requirement at the roadside inspection.

Key Takeaways

• Autonomous capacity is procurable today through existing TMS platforms: the McLeod-Aurora integration, serving 1,200-plus fleets, allows dispatchers to book driverless capacity through the same load board interface used for human-driver loads, making the autonomous procurement mechanic available to any McLeod customer who enables the integration.
• The autonomous market context is commercially significant: the autonomous long-haul market grew from an early-stage segment to $2.7 billion in 2024 and is projected at $42.6 billion by 2034 at roughly 32 percent CAGR. Carriers building procurement capability now are positioning ahead of a structural market shift, not chasing novelty.
• Aurora's 250,000-plus driverless commercial miles were moved on real freight contracts, not test tracks. The booking, billing, and operational model is proven at commercial scale. What distinguishes carriers who benefit from those who struggle is operating protocol quality, not access to the technology.
• Load eligibility screening requires four checks before autonomous assignment: ODD corridor (complete route within certified network), equipment compatibility (dry-van configurations are most widely available in 2026), customer consent (contract and preference review), and cargo type (hazmat and specialty exclusions). All four checks should be embedded in TMS configuration, not dispatcher memory.
• Rate comparison for autonomous loads must be done at fully-loaded cost, not per-mile rate. Relay hub fees, technology access charges, and occasional human-insertion exception costs can significantly affect the net economics on loads with complex routing or relay requirements.
• The tender confirmation for an autonomous load includes relay hub assignments and vehicle-level route planning. The carrier's responsibility for hub coordination, positioning a human driver at the relay point at the projected arrival time, is the most common early failure point and must be treated as a dispatching task, not an afterthought.
• Exception management during transit requires a carrier-side protocol for three scenarios: delivery window deviation (proactive customer notification), hub arrival time shift (immediate driver coordination), and AV load suspension (human-driver rescue or delay notification authority). Carriers without written exception protocols will improvise badly when the first suspension occurs.
• Strategic autonomous procurement means committing to specific lanes, managing a deliberate network capacity mix (human-driven and autonomous by lane type), and investing in TMS configuration and hub infrastructure before the first load, not as a reactive response to the problems that emerge without it.