Vendor consent sits outside your control and gates everything behind it. Here is how to start early and keep it off the critical path.
Avoiding vendor consent delays in a carve out is the single highest leverage move a buyer can make on the separation timeline, because vendor consent is the one part of the plan that sits outside the buyer control and can hold every dependent task behind it. Many software contracts carry change of control or anti assignment clauses that require the publisher to agree before a license moves to the new entity. When that agreement is requested late, the consent track runs past the date migration needs to start, and the whole separation slips. Avoiding vendor consent delays in a carve out therefore begins long before close, at the moment the deal is signed.
Consent is on the critical path because nothing dependent can move until it lands. A license cannot be transferred, a tenant cannot be split and an integration cannot be rebuilt against a contract the publisher has not yet agreed to assign. Vendor response times are governed by the publisher, not the buyer, and they lengthen when the consent conversation turns commercial. As of June 2026, the major publishers, including Oracle, SAP, Microsoft, IBM and increasingly Broadcom for the former VMware estate, treat a change of ownership as a moment to review usage and terms, which means a consent request can become a negotiation rather than a formality. A request served at close, when migration is already under pressure, leaves no room for that negotiation, and every week of delay is a week of migration lost and TSA cost added.
Delays come from four sources, and each has a counter. The first is late identification, where the buyer does not know which contracts carry consent clauses until separation planning is underway. The counter is a contract review at signing that flags every change of control, anti assignment and notice clause across the estate. The second is a commercial review, where the publisher uses the consent moment to reprice or upsell. The counter is clean usage evidence prepared in advance, so the buyer negotiates from data rather than from a position of urgency. The third is a notice period, where the contract mandates a fixed notice before any transfer. The counter is to serve notice as early as the deal structure allows. The fourth is an audit tied to the transfer, where consent is granted only after a usage review. The counter, again, is evidence ready before the request goes in. The table sets these out against the buyer response.
The structure of the transaction decides which consent clauses are triggered. A stock purchase, where the legal entity holding the contracts is acquired intact, may avoid an assignment because the contracting party does not change, but it can still trip a change of control clause. An asset purchase or a carve out into a new entity moves the contracts to a different party, which engages anti assignment clauses directly and almost always requires consent. A merger sits between the two. Knowing which structure applies, and reading the clauses against it, tells the buyer which consents are genuinely needed and which are not, so effort is spent only where it matters. This analysis is commercial, and the interpretation of any specific clause belongs with the buyer own counsel.
The playbook is simple to state and demanding to execute. Review every contract at signing and build a consent register that lists the clause, the publisher, the notice period and the likely commercial posture. Prioritise the consents that sit on the critical path, which are usually the platform publishers whose licenses gate identity, data and integration work. Prepare usage evidence for each so the buyer can answer a publisher review immediately. Serve notices and open consent conversations at the earliest point the deal allows, in parallel rather than in sequence. And keep a fallback for each critical consent, whether a transitional license under the TSA or a fresh contract, so a refusal does not become an emergency purchase at list price. This sequencing is the heart of the TSA exit timeline and software critical path and connects to mapping software dependencies before a carve out. It is part of our carve out and TSA separation service and the carve out and TSA software playbook.
Because publishers increasingly treat consent as a commercial moment, the buyer should approach each critical consent as a negotiation to be prepared for, not a form to be filed. Preparation has three parts. The first is a clear, evidence backed picture of the unit actual usage, so that when the publisher asks how the software is deployed, the buyer answers precisely and is not drawn into a fishing exercise. The second is a defined ask, knowing exactly what the buyer wants the publisher to agree to, whether a straight assignment, a fresh standalone contract or a transitional right to use under the TSA. The third is a walk away, the fallback the buyer will use if the publisher overreaches, which removes the leverage that comes from the publisher knowing the buyer has no alternative.
Running consents in parallel rather than in sequence is the other half of the discipline. A buyer that approaches publishers one at a time, waiting for each to respond before starting the next, accumulates delay that no individual publisher caused. Opening every critical consent conversation at once, with a small team owning the register and chasing responses, compresses the total elapsed time to roughly the longest single consent rather than the sum of them all. For an estate with a dozen consent gated contracts, that difference can be the difference between exiting the TSA on plan and paying for months of extension.
Finally, document every consent outcome in writing and tie it back to the register. A verbal assurance from an account manager is not consent, and a consent granted on conditions the buyer has not recorded can unravel later. Capturing the agreed terms, the effective date and any conditions for each contract gives the new entity a clean entitlement record from day one and closes the loop between the consent work and the day one readiness gate that depends on it.
| Clause type | What it can trigger | How to avoid the delay |
|---|---|---|
| Change of control | Consent, repricing or termination | Identify and request at signing, not at close |
| Anti assignment | Block on moving the contract | Negotiate assignment or a fresh contract early |
| Notice requirement | Mandatory notice period before transfer | Serve notice as soon as the deal allows |
| Audit on transfer | Usage review tied to the consent | Prepare clean usage evidence in advance |
We build the consent register at signing and run the requests in parallel so vendor consent never sits on the critical path or forces an emergency purchase.
Request a carve out software assessment