An acquirer’s merger diligence request list should connect each information request to a transaction decision: how the merger can be approved, which obligations affect the acquired business, what third-party rights require analysis, and what could change valuation or deal terms. Start with the proposed structure and entity map, then define document requests, inclusion criteria, priorities, response standards, and review ownership. The deliverable is a controlled request register that distinguishes missing evidence from substantive risk and produces targeted follow-up rather than repeated, open-ended demands.
Use this workflow when acquirer’s counsel or an in-house M&A team prepares an initial data-room request or replaces a generic checklist after receiving preliminary target information. A change in merger structure, proposed survivor, financing, or acquisition perimeter may also justify supplemental requests.
The scope is request preparation and response triage, not a complete investigation or closing checklist. The US orientation focuses on Delaware corporate mergers and federal HSR review. Assign separate analysis for other formation jurisdictions, entity types, regulated businesses, foreign investment, and securities requirements. Contract conclusions require the actual language, governing law, and transaction facts; statutory succession alone does not resolve contractual transaction rights. See DGCL §259(a). (delcode.delaware.gov)
Gather the proposed structure, letter of intent or draft merger agreement, target organizational chart, business description, preliminary capitalization table, and existing data-room index. Identify the constituent corporations, proposed survivor, and acquired subsidiaries outside the statutory merger.
Obtain the acquisition team’s investment assumptions, financing outline, anticipated signing sequence, and known concerns. Translate those inputs into evidence requests: a software target may warrant early IP-ownership and hosting requests; a manufacturer may require site, environmental, equipment, and supply-chain records first.
Establish the target response coordinator, specialist reviewers, and permitted recipients of sensitive information. Review the actual confidentiality and access arrangements before requesting restricted material. The historical Dayforce/Dawn agreement’s §5.05 illustrates negotiated access restrictions addressing legal limitations, sensitive information, and potential privilege loss; it is not a privilege-preservation rule. See the SEC-filed agreement, Annex A, §5.05. (sec.gov)
Use Business Merger Transactions — Diligence request list as the working register. You can copy this table into your working document or spreadsheet. Keep one independently answerable request per row and retain its ID through revisions.
| Request ID | Entity / topic | Request / scope | Decision / priority | Evidence / citation | Response / gap | Owner / due | Next action |
|---|---|---|---|---|---|---|---|
“Request / scope” identifies the document family, period, and inclusion criteria. “Decision / priority” explains what the evidence will inform and why timing matters. “Evidence / citation” records stable document IDs and clause or page references; connect those IDs to a separate document index.
“Response / gap” distinguishes awaiting response, partial, unavailable, affirmative none, restricted response, and reviewer-accepted complete. “Owner / due” names the reviewer and agreed response date or decision gate. Identify the target coordinator where needed. “Next action” states the precise follow-up and responsible person. Link substantive findings to a separate issues tracker rather than crowding legal analysis into the register.
Confirm which entities merge, which survive, and which subsidiaries remain outside the statutory merger but inside the acquired group. Mark unresolved structure assumptions. The entity holding a critical customer contract may not be a constituent corporation.
Organize requests around valuation, signing readiness, regulatory assessment, and closing preparation. Distinguish existing evidence from documents to be prepared later. For example, request current voting arrangements now; do not classify an unsigned future merger approval as an overdue historical record.
Record: entity-specific scope, affected decision, and structure assumptions in the relevant rows.
Request charter documents and amendments, bylaws, stockholder arrangements, capitalization records, relevant board and stockholder records, and instruments affecting voting or ownership. Separately request equity plans, individual grants, amendments, vesting records, and proposed merger treatment. Identify the date of each capitalization snapshot and request reconciliation of intervening issuances, exercises, transfers, and cancellations.
For mergers governed by Delaware §251, subsection (b) requires board approval and a declaration of advisability; subsection (c) generally requires adoption by a majority of outstanding stock entitled to vote, subject to statutory exceptions. Review the charter, voting classes, structure, and applicable exceptions before identifying the approval route. See DGCL §251(b)–(c). (delcode.delaware.gov)
Record: separate authority and capitalization requests, snapshot dates, missing instruments, and corporate or benefits reviewer assignments.
Build business-specific categories for debt and liens, customer and supplier contracts, real estate, IP, employees and benefits, tax, permits, insurance, and disputes. Specify entities and periods. Request known critical relationships expressly rather than relying solely on financial thresholds.
Delaware §259(a) provides for constituent property and rights to vest in the survivor and debts, liabilities, and duties to attach to it, preserving creditors’ rights and liens. It does not determine whether a particular contract triggers consent, termination, or notice rights. See DGCL §259(a). (delcode.delaware.gov)
Request complete contract families: executed agreements, amendments, schedules, incorporated terms, side letters, and relevant notices. Include expired agreements where identified surviving obligations matter. For acquired nonconstituent subsidiaries, request their obligations separately rather than describing them as merging into the survivor.
Record: document-family boundaries, affected entities, and the merger-related question each request addresses.
Replace “all material contracts” with criteria the target can apply: named counterparties, business-critical arrangements, stated financial criteria, or specified restrictions. If the draft agreement defines Material Contracts, cross-reference that definition and add requests needed to test the acquisition thesis.
The Dayforce/Dawn agreement’s §3.18(a) uses a negotiated Material Contract definition and corresponding disclosure-letter list. This illustrates agreement-specific request architecture, not a universal materiality threshold. See the SEC-filed agreement, Annex A, §3.18(a). (sec.gov)
Require responses to identify documents, affirmatively state none exist within the requested scope, explain unavailability, or identify an agreed restricted response. For “none,” record the respondent and scope checked. Treat that statement as evidence to assess, not conclusive proof.
Record: inclusion criteria, required response form, and unresolved scope ambiguities.
Ask regulatory counsel to specify the ownership, valuation, business activity, and jurisdictional information needed for reportability analysis. Keep governmental approvals, waiting periods, corporate approvals, and contractual consents distinct in the request list.
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 and waiting restriction. Verify operative thresholds, exemptions, rules, and timing separately. HSR expiration is not universal regulatory approval. See the FTC merger-review guidance. (ftc.gov)
For competitively sensitive or potentially privileged material, agree on a counsel-led response protocol before upload. Depending on counsel’s assessment and the actual arrangements, consider restricted recipients, redactions, or descriptions of withheld materials. Do not treat the confidentiality agreement alone as resolving every disclosure concern.
Record: specialist owner, priority, access protocol, and outstanding information needed for analysis.
Have the deal lead remove duplicates, reconcile specialist requests, and approve the first release. Explain response conventions and agree realistic dates with the target coordinator. Preserve revisions so changed scope remains distinguishable from an unanswered original request.
Assign stable document IDs as materials arrive. Preserve original filenames, data-room paths, upload dates, versions, execution status, and amendment relationships in the document index. Link each response to its request and reviewer. Cross-reference a document answering multiple requests rather than uploading or indexing duplicate copies unnecessarily.
Record: document references, response status, reviewer, and any revised scope or due date.
Check sufficiency before accepting completion. Compare coverage against entities, periods, schedules, and amendment references. Ask “provide Amendment 2 referenced in §8” rather than repeating the original broad request.
Separate evidence completion from risk resolution. A complete contract may establish a significant termination right; a missing amendment leaves the analysis uncertain. Transfer substantive concerns to the issues tracker and retain the link in the request row. Escalate gaps according to the decision they block. If the team accepts a gap, record the decision-maker and rationale without relabeling missing evidence as received.
Record: precise gap, follow-up owner, next decision gate, and reviewer-accepted completion or expressly assigned open status.
Fictional scenario: Alder Beacon Holdings proposes a $74 million acquisition through the merger of Alder Beacon Acquisition Corp. into Larkspur Instruments, with Larkspur surviving. Both constituent corporations are assumed to be Delaware corporations. All parties, documents, amounts, and clauses below are fictional. The investment case depends on a laboratory-customer relationship and retention of the engineering team.
The initial room contains a capitalization workbook, selected corporate records, and a customer master agreement. Individual equity grants and an amendment referenced in the customer agreement are missing. Counsel refines three requests:
| Request ID | Entity / topic | Request / scope | Decision / priority | Evidence / citation | Response / gap | Owner / due | Next action |
|---|---|---|---|---|---|---|---|
| R-01 | Larkspur / voting | Current charter, amendments, voting arrangements, relevant approvals | Approval route / high | D-001 charter, art. IV; D-002 cap table, Voting tab | Partial; preferred shares listed; voting arrangements unanswered | Corporate counsel / before approval analysis | Obtain arrangements or scoped none response; reconcile voting rights |
| R-02 | Larkspur / customer | Complete laboratory-customer contract family and notices | Revenue continuity / high | D-014 master agreement, §§8, 14 | Partial; §8 references missing Amendment 2 | Commercial counsel / before terms review | Obtain amendment; reserve consent conclusion |
| R-03 | Larkspur / awards | Plans, grants, amendments, vesting records, proposed treatment | Retention and pricing / high | D-002 cap table, Awards tab | Partial; aggregate options only | Benefits counsel / before pricing sign-off | Obtain grant-level records; reconcile population before treatment analysis |
The fictional customer agreement’s §14 contains a consent provision, but its application cannot be assessed confidently without the complete contract family. Counsel neither reports that consent is definitely required nor assumes it is unnecessary. Because customer continuity supports valuation, R-02 becomes a priority follow-up rather than a routine missing-document entry.
The workbook similarly supports targeted questions about preferred voting rights and award coverage; it does not establish the approval route or payout treatment. R-01 concerns Larkspur’s records, so corporate counsel separately scopes the acquisition subsidiary’s authority evidence. The revised list identifies evidence gaps without inventing their answers.
Before releasing or updating the list, confirm:
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its due diligence capabilities include bulk document classification to organize materials and prioritize human review. Tabular review supports work across multiple documents, and contract review supports examination of responsive agreements. The request register remains your team’s work product; lawyers determine scope, sufficiency, interpretation, and escalation. To assess support for this merger diligence workflow, book a demo.
Use schedules as a cross-check, not the sole organizing principle. Add evidence requests addressing valuation assumptions, contract continuity, financing, and business-specific dependencies. Preserve request IDs when schedule requirements change.
Choose periods by the question being tested and state them expressly. Ask specialists to justify broader scope. A current contract request may still require older amendments or records of surviving obligations.
Yes. Complete production can satisfy the information request while interpretation or negotiation continues. Link the row to the issues tracker so “complete” is not mistaken for “no risk.”
Record unavailability, respondent, search scope, and proposed alternative evidence. Assign counsel to assess further investigation or treatment in deal terms. Do not reconstruct missing wording from summaries or mark the evidence received.
Prepared for the October 13, 2026 assignment scope. This is a general professional workflow guide, not advice for a particular transaction.
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.