Seven Schedule Fields That Make Logistics TSAs Exit Faster

For a logistics carve-out, the transition services agreement has to be schedule-driven, priced per service with real acceptance tests, and sequenced as staged parallel runs, not one flip-the-switch cutover. The single biggest structural decision is this: build the exit plan and the integration inventory before you sign, not after. A logistics TSA that skips this ends up running long, costing more than anyone budgeted, and putting live freight at risk during the handoff.

TL;DR:

• A detailed exit plan must be built before signing the TSA, focusing on staged parallel runs and full integration rebuilds to prevent delays and cost overruns.
• Service schedules should include specific descriptions, named owners, measurable SLAs, pricing formulas, acceptance tests, dependencies, and migration tasks to avoid scope disputes.
• Effective governance requires a contract manager on each side, regular steering committee meetings, clear change request processes, and escalation tied to SLA breaches to minimize conflicts.
• Logistics cutovers should be executed in phases with validated testing for carrier integrations, operating authority, and warehouse automation, not via a single big bang.
• TSA pricing should incorporate step-down formulas that reward exit progress and escalation provisions to discourage delays, with clear liability caps and franchise rights for subcontractors.

Table of Contents

• What a Logistics Transition Services Agreement Actually Covers
• The Seven Fields Every Service Schedule Must Include
• Governance and Escalation: Running the TSA Without Constant Fights
• Cutover Sequencing: Why Logistics Can’t Do a Big Bang
• Pricing Structures That Push the Exit Forward
• Contract Clauses Logistics Teams Miss (and Regret Later)
• Building the Exit Plan: Acceptance Tests and the 0-30-60-90 Map
• RJR Worldwide’s Notes From Running Linehaul and Supplier Transitions
• Negotiation Priorities: Buyer vs. Seller
• How RJR Worldwide Supports Logistics Transition Planning
• Model Forms and Guidance Worth Saving
• Sources

What a Logistics Transition Services Agreement Actually Covers

A transition services agreement is the contract that keeps a carved-out business running on the seller’s systems and people for a defined period after close, while the buyer stands up its own capability. That is the standard definition, and it holds for logistics the same way it does for any other divestiture. Where logistics diverges is in the sheer number of moving parts that have to keep moving during the transition itself. You cannot pause a dispatch board, and you cannot tell a carrier partner to wait until IT finishes its migration.

Most TSAs, logistics or otherwise, bundle services into recognizable families. A typical service inventory looks like this:

• IT infrastructure: hosting, network access, help desk, and security administration
• Payroll and HR: benefits administration, timekeeping, and compliance filings
• Finance and accounting: AP/AR processing, general ledger access, and financial reporting
• Procurement: purchase order systems and vendor payment processing
• Warehousing and WMS: inventory visibility, slotting logic, and pick/pack workflows
• TMS and dispatch: load planning, routing, and driver assignment
• Carrier and customer integrations: EDI feeds, API connections, and shipment visibility portals

Practitioner guidance from BD Emerson identifies IT as the single largest workstream in almost every TSA, and logistics carve-outs push that further because the network runs continuously. You cannot schedule a maintenance window for a fleet that is on the road right now.

The gating issue is integrations, operating authority, and automation. A back-office finance system can usually be migrated on a weekend. A carrier integration cannot, because the moment it breaks, freight stops moving or a customer loses visibility into their shipment. Warehouse automation adds another layer: if the seller’s DC runs a proprietary conveyor control system or a WMS with custom logic baked in over a decade, replicating that on the buyer’s side is not a lift-and-shift job. It is closer to a rebuild.

By the numbers: Logistics-focused TSA exit guidance frames staged parallel runs and full integration rebuilds as the actual critical path in most carve-outs, not a footnote to the legal work. The network never stops, so the transition plan has to be built around that fact from day one.

Discovery traps are where logistics TSAs go sideways. Deal teams scope the agreement using the seller’s org chart, and then three weeks after close, operations discovers a dependency nobody listed: a regional carrier account tied to the seller’s motor carrier number, a customs bond registered under the parent entity, or a third-party freight audit vendor whose contract only covers the seller’s legal name. Every one of these becomes a change order, and every change order slows the exit. SEC exhibit forms from carve-outs like XPO’s separation of GO and RXO build in mechanisms for exactly this: additional services and project work requests that let both sides price and add scope without renegotiating the whole contract.

The Seven Fields Every Service Schedule Must Include

A TSA is only as good as its schedules. The master agreement sets the legal framework, but the schedules are where the actual work gets defined, priced, and made enforceable. Skip a field here and you get exactly the kind of scope dispute that stretches a nine-month TSA into an eighteen-month one. Based on the structure used in public SEC exhibit forms and the Practical Law model TSA, every schedule needs seven fields, no exceptions.

1. Service description at the work level. Not “IT support,” but “Tier 1 and Tier 2 help desk coverage for warehouse handheld scanners, 6 AM to 10 PM Pacific, including device replacement within four business hours.” Vague labels are where disputes start.
2. Named owners on both sides. List a specific person, not a department, with contact information and the authority to approve changes without escalating to legal every time.
3. SLA and KPI definitions with measurement cadence. State the metric, the target, how often it is measured, and what happens when it is missed. “Best efforts” is not a metric.
4. Pricing formula and billing cadence. Fixed fee, cost-plus, or per-unit, invoiced monthly, with the calculation shown, not just the total.
5. Term, exit date, and extension mechanics. Include the escalator for extensions and the process for adding services that were not in the original scope.
6. Acceptance test language. Define exactly what evidence proves a service is ready to exit, whether that is a report, a system log, or a signed test result.
7. Dependencies and migration tasks with named owners. If Service A cannot exit until Integration B is validated, say so on the schedule itself, not in a side email.

Pro Tip: Draft each schedule as if it will be handed to someone who has never seen the deal. If a new ops manager could not run the service from the schedule alone, the description is too thin.

Most disputes trace back to one of these seven fields being left generic. A schedule that says “finance support as needed” with no named owner and no acceptance test gives the seller no way to prove the service is done and gives the buyer no way to hold anyone accountable. SEC filings from the XPO and RXO separation show how mature carve-outs handle this: schedules with defined additional services provisions and a clear process for pricing project work that surfaces mid-transition. Copy that structure rather than reinventing it.

Governance and Escalation: Running the TSA Without Constant Fights

A TSA without governance is a contract that gets litigated one service at a time. The fix is boring on purpose: name specific people, meet on a fixed schedule, and write down how disagreements get resolved before anyone is actually disagreeing.

Every logistics TSA needs a contract manager on each side. This person owns day-to-day administration, the point of contact for both service delivery questions and billing disputes, someone empowered to approve minor scope changes without convening a call with outside counsel every time. Without this role, small issues sit unresolved for weeks because nobody has clear authority to close them out.

Above that sits a steering committee, typically meeting biweekly during the early months and monthly once things stabilize. Membership should span operations, IT, and finance from both organizations. Skip any of the three and you get blind spots: operations without IT means nobody flags an integration risk early; finance without operations means nobody catches a billing dispute before it compounds across three invoice cycles.

The committee’s real job is running change control. New scope surfaces constantly in logistics TSAs, a regional customer requires a new EDI format, a warehouse needs an extra shift of support during peak season, and the contract needs a fast, priced path to approve it. Effective change control usually looks like this:

• A standard change request form with a two-business-day pricing turnaround
• A pre-agreed rate card for common categories of additional work, so pricing is not negotiated from scratch each time
• A cap on unilateral approval authority (say, changes under $10,000 need only the contract manager’s sign-off)
• Anything above that threshold routes to the steering committee at its next scheduled meeting

Escalation needs the same clarity. Tie it directly to SLA breaches and KPI performance: a single missed SLA gets logged and reviewed at the next committee meeting; three consecutive misses on the same metric trigger a formal remediation plan with a deadline; failure to remediate escalates to a named executive sponsor on each side, outside the day-to-day contract managers. Deloitte’s negotiation guidance points out that buyers who come to the table with realistic, well-governed TSA structures often end up positioned as the preferred bidder in a competitive sale process, because sellers know a poorly governed TSA is a liability for both sides, not just the buyer.

Cutover Sequencing: Why Logistics Can’t Do a Big Bang

A single flip-the-switch cutover works fine for a software company migrating a billing system over a weekend. It does not work for a logistics network, because the freight does not stop moving while you migrate. A load that is on a truck at 11:58 PM on cutover night is still on that truck at 12:02 AM, and every system tracking it, dispatching it, and billing it needs to be live and correct through that moment.

That is why staged parallel runs, not big-bang switches, are the standard approach for logistics carve-outs. You run the old and new systems side by side for a defined window, validating that the new environment produces the same outputs before you retire the old one. 3PL migration guidance frames this parallel-run period as the single highest-leverage risk mitigation available, because it catches discrepancies while the old system is still there as a fallback.

The critical path is almost always the integration inventory, not the physical warehouse work. Every EDI connection, API, carrier account, and customer visibility portal has to be mapped, tested, and cut over individually. Miss one carrier integration and a lane goes dark for a customer who has no idea the ownership changed hands.

Pro Tip: Treat operating authority as a hard gate, not a paperwork formality. If the new entity’s motor carrier number is not registered and active, nothing else on the checklist matters. You cannot legally dispatch, no matter how clean the data migration looks.

Site-level cutovers for distribution centers and fleets need their own checklist: warehouse automation and conveyor logic validated under the new WMS, labeling and slotting rules confirmed against the buyer’s standards, carrier accounts re-pointed at the new billing entity, and dispatch boards tested against a full shift before the old system goes dark. Sequence sites one at a time where volume allows it. A regional network with six DCs should cut over in waves, not all at once, so that a problem at site one gets fixed before it repeats at site six.

Pricing Structures That Push the Exit Forward

Pricing design is where most logistics TSAs quietly go wrong. If the buyer pays the same flat fee in month eleven that it paid in month one, there is no financial incentive to finish migrating anything. Structure the money to reward exit, not to reward delay.

Three pricing models dominate real TSAs:

• Cost-pass, where the seller simply passes through its actual cost with no markup, common for shared IT infrastructure
• Cost-plus, adding a margin (often 5 to 15 percent) to cover the seller’s administrative overhead of running the service for someone else
• Per-seat or per-unit pricing, tying cost to a measurable driver like number of users, shipments processed, or trucks dispatched

Per-unit pricing tends to fit logistics best, because it scales with actual volume and gives both sides a clean number to audit.

The mechanism that actually matters is step-down pricing. As the buyer migrates services off the TSA, the fee should drop, so the buyer captures real savings as separation progresses rather than paying a flat rate regardless of how much is still running on the seller’s side. BD Emerson’s guidance on TSA scoping makes this point directly: without step-down pricing built into the schedule, there is no financial pressure driving the exit forward, and TSAs tend to run to the maximum permitted term almost by default.

Extension pricing should escalate, not stay flat. A common structure adds 10 to 20 percent to the base rate for each extension period beyond the original term, which discourages either side from treating extensions as a costless default.

Two mechanics protect against disputes. First, third-party pass-throughs (software licenses, carrier fees paid on the buyer’s behalf) need itemized invoicing with the underlying vendor invoice attached, not a lump sum. Second, one-time migration fees for data extraction or system cutover work should be quoted separately from the recurring service fee, so they do not get buried inside monthly billing. Build in audit rights letting either party request supporting documentation for any invoiced amount within a defined window, typically 90 days.

Contract Clauses Logistics Teams Miss (and Regret Later)

Some clauses in a TSA look like boilerplate until they become the reason a transition stalls in month seven. Four deserve close attention specifically because of how logistics operations actually run.

• Subcontracting rights. Sellers routinely rely on subcontractors, freight brokers, IT vendors, staffing agencies, to deliver TSA services. The contract needs to state whether the seller can subcontract freely or needs the buyer’s approval, and critically, that the seller remains fully liable for a subcontractor’s performance regardless of approval. Standard SEC exhibit language typically requires notice before subcontracting and preserves the seller’s liability, which is the right default. Do not let a seller subcontract away accountability along with the work.
• Data access and host system constraints. If the buyer needs read access to the seller’s WMS or TMS during the transition, the agreement needs a connection agreement addressing security protocols, data extraction rights, and what happens to that access on exit. Vague data access language is one of the most common sources of mid-transition friction.
• Liability caps and carve-outs for operational failures. A general liability cap is standard, but logistics TSAs need explicit carve-outs for failures that cause direct operational harm, a dispatch error that strands a load, a mislabeled shipment that triggers a customer chargeback. Capping liability at the service fee paid works for a software glitch; it undercompensates for a freight loss caused by a broken integration.
• Confidentiality, IP over migration artifacts, and regulatory compliance. Clarify who owns the documentation, scripts, and process maps created during migration itself, and confirm the TSA does not create unintended regulatory exposure, particularly around carrier operating authority and any product that requires FDA, USDA, or DOT-specific handling documentation.

Building the Exit Plan: Acceptance Tests and the 0-30-60-90 Map

An exit plan without a defined acceptance test is just a hope. Every service on the TSA needs a specific, evidence-based test that proves it is ready to leave the seller’s environment for good, and a milestone map that keeps everyone honest about the calendar.

1. Define acceptance tests per service before day one. For IT, that might mean a clean data migration report with zero critical errors. For WMS, matched inventory counts across three consecutive cycle counts. For carrier integrations, 30 days of error-free EDI transactions at production volume.
2. Set cutover gates that must all pass before a service goes live independently. Integration validated against production data, operating authority active and confirmed with the regulator, and DC-level tests (pick accuracy, labeling, dispatch) completed for at least one full peak-volume day.
3. Build the milestone map on a 0-30-60-90 structure. Guidance on staged 3PL transitions frames this as stabilize, standardize, then optimize, and it maps cleanly onto a logistics TSA exit.

Do not treat the 90-day mark as a finish line. It is the point where the riskiest services should be validated and exiting; slower-moving back-office functions often run longer, and that is fine as long as step-down pricing keeps the incentive intact.

RJR Worldwide’s Notes From Running Linehaul and Supplier Transitions

RJR Worldwide Corp. operates directly from its California terminals, running dedicated FedEx linehaul lanes it has acquired rather than brokering them, which means every transition question in this article is one we manage on our own operations, not just on paper.

Index-linked, multi-year contracts on the chemical sourcing side do the same job for supplier continuity that step-down pricing does for a TSA: they remove the guesswork. When a buyer or seller knows the pricing formula in advance, index-linked to a published benchmark rather than renegotiated, there is far less friction during a supplier or operational handoff, because nobody is fighting over the number.

A staged terminal cutover for linehaul operations follows the same logic as the DC-by-DC sequencing described earlier: validate one terminal’s dispatch, carrier accounts, and driver assignments before moving to the next, rather than flipping an entire regional network at once. That sequencing is not a legal nicety. It is the difference between a clean acquisition and a lane going dark on a customer who was never told ownership changed.

Negotiation Priorities: Buyer vs. Seller

If you represent the buyer, push hardest for exit certainty: named acceptance tests, step-down pricing, and a hard cap on how many extensions the seller can force. Vague scope language is the buyer’s biggest enemy.

If you represent the seller, insist on liability caps that reflect actual risk, not just the service fee paid, and on clear subcontracting rights so you are not personally staffing a transition team for eighteen months.

The workable middle ground: extension pricing that escalates enough to discourage delay without being punitive, and a change control process both sides trust enough to use instead of fighting over. Continuity and deal value both depend on getting that balance right, not on either side winning outright.

— RJR Worldwide

How RJR Worldwide Supports Logistics Transition Planning

RJR Worldwide Corp. is the option for logistics leaders who need a transition executed, not just documented. Where a legal team can draft the TSA, RJR brings direct operating experience: we acquire and run FedEx linehaul lanes from our own California terminals and manage multi-year, index-linked chemical supply contracts that keep pricing predictable through a handoff instead of leaving it to renegotiate month to month.

If you are evaluating a linehaul acquisition or need a supplier transition that does not disrupt production schedules, the first step is a direct conversation, not a lengthy proposal process. We walk through your service inventory, flag the integration and operating-authority gates likely to slow you down, and scope what a staged cutover actually looks like for your network. Reach out through our contact page to set up a confidential discussion and get a straight answer on timeline and fit.

Model Forms and Guidance Worth Saving

Four sources belong in every logistics legal and ops team’s reference file. The SEC exhibit form shows real schedule and subcontracting language from actual carve-outs. Deloitte’s negotiation guidance covers buyer/seller positioning. The BD Emerson TSA guide explains scoping and why overruns happen. The Practical Law model TSA offers a standard clause baseline.

Build your service schedules from the entangled-asset list first, then draft the master agreement around what that list actually reveals.

Sources

• Recommendations for transition service agreement negotiations — Deloitte US
• Form of Transition Services Agreement (SEC exhibit)
• Transition Services Agreement: What It Covers and How to Scope It — BD Emerson
• Logistics & Transportation TSA Exit | TSA Advisory LLC

Recommended

• FedEx Linehaul Acquisitions