The questions deal teams ask most about reviewing change of control clauses in a software estate, answered plainly, with the actions each answer points to.
A change of control clause review FAQ collects the questions deal teams ask most often when they set out to understand the licensing risk hidden in a target software estate. A change of control clause review reads every software contract for the clauses that bite on a transaction, scores them, and turns a sprawling set of agreements into a ranked register the buyer can act on. This change of control clause review FAQ answers the practical questions plainly: what the review covers, how clauses are scored, who should run it, how it relates to legal advice, and what the buyer does with the findings. Inherited software licensing exposure is usually latent and unquantified in standard due diligence, and a clause review is the instrument that makes it visible before a publisher does it for the buyer after close.
The first question is always scope. A proper review reads the full document stack for every publisher, not just the master agreements, because the controlling clause often sits in an order form, a regional addendum, or an amendment signed years later. It reads each contract for five clause types: change of control, anti assignment, consent, termination, and notice. It then scores each clause by combining the severity of the remedy it gives the publisher, the criticality of the system it governs, and the exposure in the underlying deployment. The output is a register sorted by risk. The discovery step that feeds it is described in finding change of control clauses before you sign, and the foundational definition of the clause itself in what a change of control clause in software is.
The most common follow up question is how a clause earns its place at the top of the register. The answer is a blend of three factors. Remedy severity ranks the clauses by what the publisher can do: a termination right outranks a repricing right, which outranks a consent requirement, which outranks a notice obligation. System criticality weights the score toward the systems the business cannot run without, because the same clause is far more dangerous on a core platform than on a peripheral tool. Deployment exposure surfaces the contracts where usage has drifted beyond entitlement, because a transaction tends to bring that drift into the open. Together these produce a ranking that concentrates the deal team effort where refusal, repricing, or termination would actually hurt, rather than spreading it evenly across hundreds of contracts. The way deal structure changes which clauses are even triggered is set out in how change of control clauses affect M&A deals.
| Question | Short answer |
|---|---|
| Which contracts get read | Every one, including order forms, addenda, and amendments |
| Which clauses matter | Change of control, anti assignment, consent, termination, notice |
| How is risk scored | Remedy severity, system criticality, and deployment exposure combined |
| Who commissions it | The buyer, independently, paid only by the acquirer |
| Is it legal advice | No, it is commercial advisory that counsel then interprets |
| What is the output | A ranked register with a recommended action per clause |
Two timing questions come up on every deal. The first is duration. A focused review of a mid sized estate is usually measured in weeks, not months, provided the contract records are reasonably complete. The work front loads the highest risk publishers, so the clauses that could move price or break the deal are surfaced early, while the long tail of low risk contracts is cleared in parallel. The second question is when in the deal to run it. The honest answer is as early as the access allows, ideally before signing, because the value of the findings falls the later they arrive. A clause that is discovered before signing can be reflected in price, addressed in the structure, or made a condition. The same clause discovered after close is a problem the buyer now owns outright. Where access is limited during a competitive process, a staged review that reads the largest and most critical publishers first gives the deal team a defensible early read while the full picture is assembled. The negotiation that the findings feed is covered in negotiating around a change of control clause, and the structure question in stock versus asset purchase and which triggers assignment issues.
It is worth being clear about the limits of the exercise, because misunderstanding them creates false comfort. A clause review identifies, scores, and prioritises the clauses that create transaction risk, but it does not interpret their legal effect, which is the role of the buyer own counsel working from the findings. It does not negotiate with vendors, though it arms the team that will. And it is only as complete as the contract records it is given, which is why a review that uncovers gaps in the record is itself a finding, not a failure. A target that cannot produce the full document stack for a major publisher has told the buyer something important about the state of its licensing, and the review flags that gap so it can be priced as uncertainty rather than ignored.
A question that deserves a direct answer is who should commission the review. The buyer should, on its own behalf, through an independent adviser paid only by the acquirer. The seller has every commercial incentive to present the estate as clean and the licensing as compliant, and a review run for the seller answers to the seller. An independent, buyer side review holds no affiliation with any software publisher or reseller, so its only interest is the accuracy of the picture it hands the buyer. That independence matters most precisely where the findings are uncomfortable, because the clauses that carry eight figure consequences are the ones a seller is least motivated to surface. The review is commercial and licensing advisory, not legal advice, and the buyer own counsel interprets the specific legal effect of any clause the review identifies.
The final question is what happens after the register is delivered. The findings drive four decisions. They build the consent strategy, because the register identifies the small number of consents that genuinely matter, as covered in consent strategy for software license assignment. They inform the structure decision, because the register shows which clauses each structure would trigger. They prioritise negotiation, because the ranking points the deal team at the few clauses where leverage and exposure meet. And they quantify exposure in the deal model, because a known repricing or termination risk belongs in the price rather than as a surprise after close. The public record shows how large inherited licensing disputes can become: SAP pursued AB InBev for a reported 600 million dollars and Diageo for a reported 60 million pounds over disputed and inherited licensing, as reported and accurate as of June 2026. A clause review is how a buyer avoids becoming the next such headline.
We run the change of control clause review across the target software estate, score every clause that matters, and hand the deal team a ranked register with a recommended action for each.
Request a change of control clause review