This change-of-control due diligence checklist asks a deceptively narrow question: does the proposed transaction activate a contractual right, restriction, notice, consent, termination, acceleration, pricing change, or other consequence? The answer rarely appears in one clause. It may depend on defined terms, ownership thresholds, indirect changes, affiliate provisions, assignment language, amendments, side letters, and the exact sequence of the deal.
This guide owns the clause-analysis and consent-tracking task. If the problem is controlling amendments, superseded files, review cut-offs, and late uploads across the room, use the M&A due-diligence version-control checklist instead. For the broader sequence across every workstream, use the India legal due diligence checklist. These controls connect, but they answer different deal-team questions.
The work therefore begins with evidence, not keyword hits. The Indian Contract Act, 1872 provides an official starting point for general contract law. Company records and the Ministry of Corporate Affairs portal can provide corporate context. Listed-company transactions may also require counsel to consult current SEBI legal materials. None of these sources replaces analysis of the operative agreement and transaction facts.
What exactly counts as a change of control in the contract?
Use the agreement's words. Some definitions focus on voting power, ownership, the ability to appoint directors, or power over management and policy. Others import a statutory definition, cover direct and indirect changes, treat a sale of substantially all assets as equivalent, or define control by reference to a named parent. A clause may also catch a merger, reorganisation, competitor acquisition, or change in beneficial ownership without using the phrase “change of control.”
Review the definition together with connected provisions:
- control, affiliate, group, ownership, transfer, and permitted transferee definitions;
- assignment, delegation, novation, subcontracting, and succession clauses;
- termination, suspension, default, acceleration, and pricing provisions;
- notice and consent mechanics, including address and delivery rules;
- competitor, sanctions, licensing, or eligibility restrictions;
- guarantees, security documents, schedules, and side letters; and
- amendments or waivers that alter the original bargain.
Do not convert a defined percentage into a conclusion before mapping the transaction. Voting arrangements, convertible instruments, staged closings, reserved matters, and intermediate holding companies may affect the analysis. Preserve the clause text, section, document version, and reviewer note with every extracted result.
Which change-of-control trigger patterns should reviewers test?
Review for legal effect rather than searching only for the heading “change of control.” The following patterns are prompts for reading the operative drafting, not substitute clause language.
| Trigger pattern | Facts to test | Connected provisions to read |
|---|---|---|
| Ownership threshold | Direct, indirect, beneficial, diluted, or voting ownership before and after each step | Control, ownership, securities, affiliate, and transfer definitions |
| Board or policy power | Appointment rights, veto rights, reserved matters, shareholder arrangements, or other management influence | Control definition, governance schedule, side letters |
| Parent-level change | Whether the named party, its parent, or ultimate holding company is tested | Group definitions, permitted reorganisation exception |
| Merger or succession | Merger, amalgamation, scheme, consolidation, or succession by operation of law | Assignment, successor, termination, and notice clauses |
| Asset transfer | Transfer of all or a material part of assets or business | Assignment, subcontracting, novation, licence, and continuity terms |
| Competitor event | Acquisition by, or control shared with, a defined competitor or restricted person | Competitor definition, sanctions, eligibility, confidentiality terms |
A single transaction can meet more than one pattern. Record each route separately because its consequence, notice period, or exception may differ.
How should the deal structure be mapped against each trigger?
Prepare a one-page transaction sequence that both corporate and contract reviewers can use. Show ownership before and after each step, the entities signing and closing, assets or shares transferred, financing steps, mergers, internal reorganisations, and any options or later closings. Give every version a date.
| Transaction fact | Contract question | Evidence | Review outcome |
|---|---|---|---|
| Direct share acquisition | Does the clause test direct ownership or voting power? | Structure chart and transaction agreement | Triggered, not triggered, or unclear |
| Parent-level acquisition | Are indirect changes or ultimate control covered? | Full ownership chain and definitions | Rationale with cited language |
| Asset sale | Does the clause include asset transfers or assignment? | Asset schedule and operative contracts | Consent or notice path |
| Merger or amalgamation | Are successors, mergers, or transfers by law addressed? | Scheme and corporate documents | Counsel review required |
| Staged investment | Are steps aggregated or independently tested? | Subscription, option, and voting documents | Analysis for each relevant date |
| Internal reorganisation | Is there an affiliate or permitted-transfer exception? | Group chart and exception conditions | Conditions and evidence |
Record assumptions explicitly. If the final voting arrangements or merger steps are unsettled, mark the conclusion provisional and state what fact would change it. A static “yes/no” column conceals this uncertainty.
How do you build a complete contract population?
Start with the counterparty relationships that matter to continuity, value, financing, regulatory permissions, data, people, property, and key inputs. Reconcile the data room against authorised finance, sales, procurement, entity, licensing, and operations records. A folder name is not proof of completeness.
For each relationship, build a document family: original agreement, amendments, renewals, statements of work, orders, guarantees, notices, waivers, and relevant correspondence. Link every amendment to the clause it changes. Distinguish executed copies from drafts and expired arrangements from live ones. Apply the deal-team version-control protocol before treating any clause conclusion as current at the reporting cut-off.
The bulk contract review workflow gives a fuller population and reconciliation method. Use the M&A data-room Q&A workflow when missing document-family items must be converted into precise, owned requests. Gotham's practice workspace is designed to keep documents and workflows near the matter context. Before loading sensitive transaction documents into any system, assess access, retention, and deployment questions using the security overview.
How should reviewers classify the clause and its consequence?
A useful classification separates the trigger from the remedy. “Change of control clause found” is not decision-ready. Reviewers need to state what event is covered, whose change matters, whether an exception applies, what the counterparty can do, when action is due, and what happens if the requirement is missed.
| Field | What to record | Avoid |
|---|---|---|
| Trigger | Concise rule plus exact citation | Keyword alone |
| Transaction match | Facts mapped to each element | Unexplained yes/no answer |
| Consequence | Consent, notice, termination, acceleration, repricing, or other right | Treating all hits as consent |
| Timing | Deadline, reference event, and calculation issue | Unsupported calendar date |
| Procedure | Recipient, address, delivery method, required content | Copying an obsolete notice block |
| Exception | Conditions and evidence needed | Assuming affiliate exception applies |
| Status | Confirmed, provisional, open, requested, or closed | Silent blanks |
Use an “unclear” route. Ambiguous drafting, missing amendments, incomplete deal facts, and conflicting provisions belong with senior counsel. Reviewers should not force certainty merely to complete a spreadsheet.
Which contracts should be prioritised for senior review?
Materiality is deal-specific. Agree the prioritisation rules before review begins and allow escalation outside them. High-priority candidates often include major customer and supplier agreements, financing and security documents, licences and permits, leases for essential sites, intellectual-property licences, data arrangements, joint ventures, government contracts, distribution agreements, and contracts containing exclusivity or competitor restrictions.
Prioritise both likelihood and consequence:
- Could the proposed structure plausibly meet the trigger?
- Can the counterparty block, terminate, accelerate, or materially reprice?
- Is the relationship difficult to replace?
- Is the action required before signing, before closing, or shortly afterward?
- Could approaching the counterparty create confidentiality or commercial risk?
- Is the evidence complete enough for a conclusion?
The contract risk scoring framework can help teams document scoring rules, but a score should never hide the cited text or legal rationale. A low-value contract with an essential licence can outrank a higher-value, easily replaceable service.
How should consents and notices be planned?
Create a consent register linked to the issues log. Each row should identify the contract, counterparty, trigger, required action, contractual deadline, deal deadline, responsible owner, approver, communication status, response, and stored evidence. Distinguish consent from notice and waiver. They are not interchangeable.
Use this copyable consent-tracker structure:
| Contract | Trigger and citation | Required action | Contract deadline | Deal deadline | Owner | Outreach | Response | Evidence | Closing status |
|---|---|---|---|---|---|---|---|---|---|
| Critical supplier agreement | Indirect control test, section 14.2 | Prior written consent | Before closing | 15 September | Legal lead | Approved draft | Awaiting response | Consent folder link | Open |
| Software agreement | Assignment language, section 9 | Confirm document family, then assess notice | Ten days after effective date | 25 September | Diligence counsel | Not started | Not applicable | Missing-amendment request | Blocked |
Download the editable change-of-control consent tracker to retain the transaction step, confidentiality clearance, approver, and last-review date beside the closing status. Replace the fictional rows and adapt the status vocabulary before use.
If the consent analysis depends on unanswered deal or contract facts, keep those dependencies in the due diligence question log template and link the question ID back to the consent row.
Plan communications with the transaction's confidentiality and stakeholder strategy. The contract may specify delivery mechanics, but the deal team must decide when it is appropriate to approach the counterparty. Prepare approved language, confirm authorised signatories, and track follow-ups without promising that silence equals approval unless counsel has established that result.
Use these gates before closure:
- the operative document family has been checked;
- the transaction version matches the analysis;
- the recipient and delivery method are verified;
- counsel approved the requested consent, waiver, or notice;
- delivery evidence and response are stored; and
- the closing checklist reflects any unresolved condition.
How do you quality-control a large clause review?
Pilot the protocol on varied agreements before scaling. Include scans, amendments, non-standard drafting, regional schedules, and contracts in which the relevant effect sits outside the expected heading. Measure missed clauses as well as extra hits.
Second-review all material triggered findings and a risk-based sample of negatives. Check consistency by clause family: similar language should receive compatible treatment unless transaction facts differ. When reviewers disagree, update the guidance and revisit affected records rather than quietly choosing one answer.
Automation can find candidate language, group documents, and populate fields. It cannot determine the legal effect without the operative context. Keep page or section citations, source text, document identity, model or rule output where relevant, human decision, and validation status. This trail makes errors correctable.
What should the closing and integration handoff contain?
The final output should not be a spreadsheet abandoned at closing. Hand off confirmed notices, continuing restrictions, renewal dates, reporting duties, security commitments, pricing changes, and unresolved consents to named owners. Preserve the source clause and deadline logic so the integration team can act without repeating diligence.
A closing-ready pack includes scope and limitations, the reconciled contract register, final trigger analysis, consent and notice evidence, missing-document list, unresolved questions, quality-control record, and an obligation schedule. Mark any conclusion that depended on an earlier deal structure and rerun it if the structure changes.
Use a final closing-status view that makes blockers unmistakable:
| Status | Minimum evidence | Closing treatment |
|---|---|---|
| Cleared | Final analysis and all required action evidence approved | Mark complete with reviewer and date |
| Cleared with post-closing action | Counsel-approved basis, owner, due-date logic, and handoff acceptance | Place in the signed-off post-closing schedule |
| Open | Required response or review is pending | Keep visible on the closing checklist |
| Blocked | Missing contract, amendment, deal fact, recipient detail, or authority prevents completion | Escalate the precise dependency and decision date |
| Risk accepted | Authorised decision records the known consequence and basis | Link the approval; do not relabel as cleared |
“Email sent” is an activity, not a closing status. Closure should identify what the contract required, what was done, who verified it, and where the evidence is stored.
If the team needs a traceable contract intake and exception workflow, contact Gotham. The useful outcome is not a large count of clause matches. It is a verified path from transaction fact to contract consequence, action owner, and evidence of completion.
