Vendor consents decide the real timeline.

What a consent actually is.

A third-party consent is the formal permission a vendor gives to move a contract from the original counterparty to a new legal entity. The technical mechanics vary. Some contracts allow assignment by notice. Some require written consent. Some bar assignment entirely without a renegotiation. In a carve-out, the original counterparty was the parent. Newco is a new legal entity that did not sign the contract. The vendor has every right to insist on a fresh agreement, a fresh credit review, and often a fresh price.

The legal mechanism splits into three patterns. Pure assignment moves the contract to Newco unchanged. Novation replaces the contract with a new agreement between the vendor and Newco on the same terms. A new contract resets the entire commercial relationship. Vendors prefer new contracts because each new contract is a chance to reprice. Buyers prefer pure assignment because the existing pricing and term survive intact.

The TSA bridges the gap between Day One and the consented state. While the consent is pending, the seller continues to receive the service under the original contract and passes the cost through to the buyer. That bridge is the entire point of the TSA on this workstream. The pass-through mechanics are covered in TSA pass-through pricing.

Why consents drive the actual timeline.

Most carve-out timelines are built around the technical exit work. Migrate the ERP. Stand up the email tenant. Move the data. The technical work usually finishes on schedule. The vendor consents do not. A typical mid-market carve-out has between 150 and 400 third-party contracts that need attention. The top 10 vendors are responsive. The middle 50 are slow. The long tail is unresponsive, unreachable, or insists on a full repaper.

Each unconsented contract is a TSA service that cannot exit on Day One. The seller has to keep the contract in place, keep paying the vendor, and keep invoicing the buyer. The TSA term lengthens. The TSA extension fee rolls up. The exit cost goes up. The original deal math starts to slip, and the operating partner ends up explaining a TSA bill that was supposed to be done by month nine and is still running at month fifteen.

The consent workstream therefore drives the real TSA exit timeline, not the technical work. Buyers who pressure-test the consent inventory before signing end up with a defensible plan. Buyers who do not end up paying a long tail of extension fees. The fee mechanics are covered in TSA extension fees explained.

The consent inventory is diligence work.

The consent inventory is built in diligence and refined through the first 30 days. Every contract that supports the carve-out perimeter is read for its assignment clause. The clause is coded into one of five categories. Silent contracts allow assignment without consent. Notice clauses require notice but not approval. Consent clauses require approval that may not be unreasonably withheld. Strict consent clauses require approval at the vendor's sole discretion. Some clauses bar assignment outright at any price.

Each contract is also coded for criticality. A contract supporting Day One payroll is critical. A contract for a niche analytics tool used quarterly is not. The product of clause type and criticality drives the work plan. A critical contract with a strict consent clause is the highest risk item and is worked first. A low criticality contract with a silent clause sits at the bottom of the queue.

The inventory is also priced. Each consent has a probability of being granted, a probability of being granted with a price increase, and a probability of being refused. Sellers often want to treat all consents as routine. Disciplined buyers price the three outcomes and reserve against the expected loss. The mechanics overlap with the broader TSA due diligence checklist.

Pricing the consent risk into the TSA.

Consent risk lands in the TSA in three places. First, the service level fee for any service that depends on an unconsented contract. The buyer should require the seller to absorb the cost of any consent fee charged by the underlying vendor. Without that clause, the vendor's repricing demand is passed straight to the buyer.

Second, the extension fee schedule. The standard seller posture is a steep extension fee curve from month six onward, sometimes 25 to 50 percent month over month. That curve is unworkable when the consent timeline is uncertain. Disciplined buyers negotiate a flat extension fee through the consent window, then a step up after a defined date that the buyer can control. That structure prices in the consent reality without giving the seller a punitive lever.

Third, the seller's obligation to cooperate. The TSA should include a defined assistance clause. The seller commits to making reasonable efforts to obtain consents, to providing access to the original signature authority, and to escalating to vendor management at the seller's level when a consent stalls. Without that clause, the seller can sit on consent requests and let the buyer carry the extension cost.

Alternatives when consent is refused.

When a vendor refuses consent or demands a punitive repricing, the buyer has four moves. First, accept the new terms if the vendor is irreplaceable and the price is within the modeled range. Second, walk away and replace the vendor with an alternative. Third, restructure through a sublicense or services arrangement that does not trigger the assignment clause. Fourth, accept an extended TSA on this single contract while a replacement is built.

The right answer depends on the contract. For a deeply integrated ERP or a regulated payroll provider, replacement is slow and risky, and the buyer often accepts a repricing. For a commodity tool with five viable competitors, replacement is the right move because it caps the vendor's leverage on every future renewal. The decision should be made cluster by cluster, not vendor by vendor.

The sublicense path is often misunderstood. Some vendors will not consent to assignment but will accept a sublicense where the seller remains the legal counterparty and Newco operates the service. The sublicense is a workable interim. It is not a permanent answer. It leaves the seller in the middle of an operating relationship long after the original deal logic suggests a clean break. The pattern is part of broader TSA vendor management.

Operating discipline through the TSA.

Once the TSA is signed, the consent workstream becomes a tracked program. A single owner runs the inventory. A weekly meeting reviews the top 20 open consents, the legal status of each, the commercial position of the vendor, and the next action. Each consent has a single named driver inside the buyer organization and a single named counterpart inside the seller.

The data is reported monthly to the governance committee. Open consent count. Consents granted in the month. Consents refused. Consents repriced. Consents in dispute. The data is the early warning indicator for the TSA exit timeline. When the consent backlog rises three months in a row, the exit date is moving regardless of what the technical workstream says.

Consent management is the work that buys back the exit date. It is not glamorous, and it is not the part of the TSA that anyone wants to spend time on. It is the part that determines whether the deal closes the TSA on plan or carries an extension bill into the value creation period. Specialist support on this workstream is part of TSA renegotiation when an extension is already running.

More on TSA negotiation.