How to map merger approvals and consent requirements for Business Merger Transactions

Map merger approvals by tracing the proposed structure through each constituent entity, regulatory review path, and affected contract. For every requirement, identify the source, trigger, owner, prerequisites, timing, and evidence needed to clear it. Keep corporate approvals, governmental permissions, waiting periods, counterparty consents, and notices separate. The resulting merger approval matrix should tell acquirer counsel what remains unresolved, which items restrict closing or effectiveness, and which risks require an authorized decision—not merely whether someone has requested a signature.

When to use this workflow

Use this workflow when acquirer counsel has a proposed merger structure and enough target information to test approval requirements. Start before relying on the signing-to-closing timetable. Refresh the matrix when the survivor, ownership chain, financing, consideration, or relevant agreement language changes.

The scope is approval diligence: identifying requirements, testing their application, and retaining clearance evidence. It is not the complete closing checklist.

This guide uses a US baseline focused on Delaware corporate mergers and federal HSR review. Other formation jurisdictions, entity types, regulated businesses, foreign investment rules, and securities requirements need separate analysis. Contract conclusions depend on actual wording, governing law, facts, and deal context. The steps below are workflow recommendations, not additional legal requirements.

What you need

Begin with a structure diagram identifying the acquirer, merger subsidiary, target, proposed survivor, and affected subsidiaries. Record formation jurisdictions and distinguish constituent corporations from entities affected only through ownership changes.

Collect:

• The current merger agreement, disclosure schedules, draft certificate of merger, and provisions governing conditions, efforts, waivers, and notices.
• Charters, bylaws, capitalization and voting records, voting agreements, and board or stockholder approval materials.
• Complete contract families for financing, customers, suppliers, leases, and licenses, including amendments and incorporated terms.
• Permits, regulatory correspondence, and transaction information requested by specialist counsel.
• Consent requests, responses, delivery evidence, and proposed counterparty conditions.

Preserve document IDs, versions, execution status, and amendment relationships. “Not uploaded” differs from a confirmed absence. Give missing information a request number and owner rather than treating an incomplete data room as a clean approval record.

Use the template

The companion template is Business Merger Transactions — Merger approval matrix. You can copy this table into your working document or spreadsheet. Use one row per distinct requirement; a contract requiring both consent and notice generally needs two rows.

Assign stable row IDs for references from the issues list and closing checklist. Source / citation should include the document ID, version, and clause or page, or the supporting legal provision.

Prerequisites / timing identifies required information, the triggering event, and any supported deadline or expiry. Closing link distinguishes an express contractual condition from another legal restriction, a covenant, or a notice obligation.

Use the final column for status, evidence location, reviewer, and next action. Distinguish “source missing,” “analysis pending,” “request pending,” “evidence received—review pending,” and “cleared.” Link longer reasoning rather than compressing uncertainty into a green status.

Step by step

1. Fix the structure being analyzed

Create a dated structure note naming each constituent corporation, the survivor, and ownership changes relevant to target contracts. Check it against the merger agreement rather than relying solely on a presentation.

Identify alternative structures still under consideration. A conclusion based on the target surviving should not carry over automatically to a structure in which it disappears. Record indirect ownership changes even where the contracting subsidiary remains unchanged.

Matrix output: populate affected entities and triggers, link each row to the structure version, and mark conclusions dependent on unresolved structuring choices as provisional.

2. Identify corporate approvals entity by entity

For a Delaware merger under DGCL §251, subsection (b) requires each constituent corporation’s board to approve the merger agreement and declare its advisability. Subsection (c) generally requires adoption by a majority of outstanding stock entitled to vote. Check the charter, voting classes, approval route, and applicable exceptions, including §251(f) or (h), before applying that baseline. See DGCL §251. (delcode.delaware.gov)

Do not assume the acquirer parent is a constituent corporation or that its approvals match those of the merger subsidiary. Separately examine any parent-level authorization questions arising from the proposed transaction.

Compare required approvals with resolutions, the approved agreement version, and voting evidence. Assign claimed exceptions and additional approval questions to corporate counsel.

Matrix output: create separate board and stockholder rows where applicable; record missing evidence and the basis for any conclusion that approval is unnecessary.

3. Separate regulatory permissions from waiting periods

Route reportability and permission questions to specialist counsel with the structure note and requested transaction facts. Use separate entries for distinct regimes rather than one “regulatory approval” row.

The FTC explains that only certain transactions require HSR notification; thresholds change annually and exemptions exist. Reportable transactions cannot close before the applicable waiting period expires or is terminated early. A Second Request extends the review process and applicable waiting restriction. See the FTC’s merger-review guidance. (ftc.gov)

Have counsel verify operative thresholds, exemptions, filing requirements, and timing for the actual transaction. Record HSR waiting-period clearance precisely, not as universal regulatory approval. Assign separate screening questions for other potentially applicable regimes.

Matrix output: identify the decision owner, missing inputs, reportability conclusion or open question, submission dependencies, and required clearance evidence.

4. Test contracts against the actual merger

Read assignment, merger, change-of-control, termination, consent, and notice provisions together. Check definitions, amendments, exceptions, and delivery mechanics before classifying a requirement. Search terms locate language; they do not determine applicability.

DGCL §259(a) addresses statutory succession of property, rights, debts, liabilities, and duties while preserving creditors’ rights and liens. It does not supply the contract-specific consent analysis. Test the wording and applicable law against the structure rather than assuming succession eliminates consent questions. See DGCL §259(a). (delcode.delaware.gov)

For ambiguity, record competing readings, the missing legal or factual input, and the operational consequence. Avoid converting “assignment clause found” into “consent required.”

Matrix output: capture the trigger, recipient, required act, timing, and unresolved interpretation with clause-level evidence.

5. Map dependencies and the closing connection

Read the merger agreement’s conditions and consent covenants beside each row. Do not treat a duty to seek consent as an express closing condition without checking the conditions article. Equally, do not treat the absence of a named condition as clearance of another restriction.

Identify prerequisites such as finalized transaction descriptions, ownership information, approved forms, or replacement credit support. Record who controls each prerequisite and who authorizes outreach. Coordinate requests so business teams do not send inconsistent explanations.

Escalate demands for fees, amendments, guarantees, or commercial concessions separately from the consent-trigger analysis.

Matrix output: add condition or covenant citations, dependency row IDs, submission owners, and decision authority for concessions or proposed waivers.

6. Verify responses and retain clearance evidence

Check each approval against the requirement: legal entities, transaction description, signatory authority, scope, conditions, and expiry. Do not treat acknowledgment of receipt as consent without supporting operative language. Keep an approval subject to an unsigned amendment marked conditional.

Separate requested, received, reviewed, and cleared statuses. If counsel concludes approval is unnecessary, retain the sources and reasoning. If a waiver is available, identify the right being waived, who holds it, and the required documentation. Keep commercial risk acceptance separate from satisfaction or waiver of the underlying requirement.

Matrix output: link the executed approval, delivery evidence, or legal conclusion; name the reviewer and identify remaining conditions.

7. Reconcile the matrix with the closing sequence

Compare the matrix with the final structure, agreement, schedules, and execution set. Reopen rows affected by amendments, new documents, or expired approvals.

DGCL §251(c) permits filing a certificate of merger instead of the merger agreement and specifies certificate contents. Use that provision to check the statutory filing route, not as evidence that contractual closing conditions are satisfied. Keep approval verification, filing preparation, release authority, and effectiveness distinct. See DGCL §251(c). (delcode.delaware.gov)

Matrix output: identify unresolved restrictions and decision makers. Transfer post-closing notices only with a named owner, triggering event, delivery requirements, and completion evidence.

Worked example

Fictional scenario: Alder Harbor Holdings proposes to acquire Brookmere Analytics through a merger of its wholly owned merger subsidiary into Brookmere, with Brookmere surviving. Both constituents are Delaware corporations. All parties, documents, and provisions below are fictional.

The data room contains a target board consent, software license, and warehouse lease, but incomplete voting records and a missing lease amendment. The draft merger agreement expressly conditions closing on target stockholder adoption and the software provider’s consent. Corporate counsel has not completed the adoption analysis. These three entries are illustrative, not the complete approval map.

A-01 prevents the team from treating a board package as complete corporate authorization. A-02 identifies both a contractual trigger and an express closing condition; the supplied acknowledgment does not establish satisfaction. A-03 prevents a premature notice-only conclusion without inventing a consent right in the missing amendment.

The acquirer therefore requires three focused actions before finalizing the sequence: complete the voting analysis, obtain qualifying software consent, and recover the lease amendment. None of these rows is cleared merely because outreach has begun.

Common mistakes

• Combining all approvals. Separate corporate acts, regulatory restrictions, consents, and notices so owners and evidence remain visible.
• Treating an unchanged contracting entity as dispositive. Test direct and indirect ownership triggers against the structure.
• Reviewing only the base agreement. Reconcile amendments and incorporated terms before recording a conclusion.
• Equating a consent covenant with a condition. Cite each separately and identify the relevant decision path.
• Marking correspondence as clearance. Check operative language, scope, conditions, authority, and expiry before closing the row.

Final quality check

• Every row uses the current structure and correct affected entity.
• Legal conclusions link to verified sources within their jurisdictional scope.
• Contract conclusions cite complete document families and exact provisions.
• Approvals, notices, filings, and waiting periods remain distinguishable.
• Timing and dependencies derive from identified sources.
• Cleared items retain reviewed evidence and reviewer identification.
• Open issues have owners and escalation paths; closing links, waivers, and handoffs reconcile with the final agreement.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use its due diligence capabilities to organize materials through bulk document classification and prioritize human review; tabular review supports work across documents. In contract review, lawyers can provide deal-specific instructions in Word and review findings that quote and locate clauses, rank severity, and identify missing language as not present. Use findings to support your own matrix; counsel retains responsibility for applicability and clearance. To discuss this workflow, book a demo.

Frequently asked questions

Should every target contract enter the matrix?

Index the reviewed population, but create requirement rows for identified triggers, unresolved interpretations, and evidence gaps. Preserve traceable conclusions for contracts excluded from further consent work so omission does not become undocumented clearance.

Does statutory succession eliminate consent analysis?

No. Section 259 addresses succession; it does not replace review of contractual triggers and applicable law. Record that analysis rather than assuming either that every merger requires consent or that none does. See DGCL §259. (delcode.delaware.gov)

Can a missing consent become accepted business risk?

First identify the restriction and available decision path. Record any authorized commercial decision separately from satisfaction, waiver, or an unresolved restriction. Do not relabel an outstanding requirement as completed merely because the business accepts exposure.

When should notices leave the matrix?

Transfer them when the trigger, timing, recipient, delivery method, owner, and completion evidence are established. Keep a reference to the receiving tracker. A task should not disappear merely because it does not prevent closing.

Sources

• Delaware Code, Title 8, §251: corporate merger approvals, exceptions, and certificate filing.
• Delaware Code, Title 8, §259: statutory succession and preservation of creditors’ rights and liens.
• FTC, Premerger Notification and the Merger Review Process: HSR overview and waiting restrictions.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.