How to prepare a deal issues list from transaction documents for Business Merger Transactions

Prepare an acquirer-side deal issues list by connecting material findings in the merger documents to specific negotiating decisions. Review the merger agreement, disclosure schedules, diligence evidence, and ancillary documents together; identify the affected provisions; separate verified facts from unanswered questions; and record the acquirer’s requested treatment, the target’s position, and the person authorized to decide. The deliverable is a source-linked decision record—not a document inventory—that identifies matters requiring drafting, further evidence, escalation, or express acceptance of business risk.

When to use this workflow

Use this workflow when acquirer counsel has a merger agreement draft and enough diligence material to identify mismatches between the proposed risk allocation and the target’s business. Concrete triggers include preparing for a negotiating call, receiving disclosure schedules, or discovering evidence that changes an earlier drafting position.

The scope is issue identification and negotiation control, not a 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 rights depend on the actual wording, applicable law, facts, and deal context.

What you need

Assemble a dated review set rather than working from whichever attachment arrived last. Include:

• The current merger agreement and comparison against the previous negotiated draft, including definitions and exhibits.
• Disclosure schedules, identifying incomplete sections and the provisions each exception purports to qualify.
• The entity chart, charter documents, capitalization records, equity plans, and individual award instruments.
• Diligence findings and their underlying contracts, amendments, financial records, permits, and dispute materials.
• Relevant ancillary documents, including financing, support, employment, escrow, and paying-agent arrangements.
• The acquirer’s instructions on commercial priorities, acceptable exposure, negotiating authority, and unresolved structural choices.

Assign stable document IDs and preserve version dates, execution status, and amendment relationships. Keep the detailed document index separate from the issues list. An unanswered request is missing evidence, not confirmation that an obligation does not exist.

Use the template

Use the Business Merger Transactions — Deal issues list to connect evidence, drafting, and decisions. You can copy this table into your working document or spreadsheet. Use one row per decision; split a concern when separate treatments require different owners or approval authority.

In Evidence / gap, record the document ID, version, clause, page, or spreadsheet cell, followed by the observed fact and missing material. Distinguish inference from source wording. Deal provision identifies the relevant representation, disclosure exception, covenant, condition, remedy, or proposed new language.

Record the commercial reason beside the acquirer’s request so negotiators can evaluate alternatives. Target position preserves the actual competing proposal and its source, not an assumed objection. Identify the decision-maker alongside the action owner when they differ.

Use statuses such as “awaiting evidence,” “drafting open,” “decision required,” “accepted risk,” and “resolved.” Closure requires supporting evidence or an authorized decision, not merely a date.

Step by step

1. Fix the review baseline and identify structural dependencies

Confirm the represented acquirer, constituent entities, intended survivor, consideration structure, and current draft. Identify assumptions that could change the analysis, such as whether a subsidiary remains outside the merger or equity awards receive replacement treatment.

Under Delaware §251(b), each constituent corporation’s board approves the merger agreement and declares its advisability. Section 251(c) generally requires adoption by a majority of outstanding stock entitled to vote, subject to statutory exceptions. Check the charter, voting classes, and structure, including applicable exceptions, rather than assuming identical approvals for every constituent. See Delaware Code §251(b)–(c). (delcode.delaware.gov)

Record: each unresolved structural or approval question affecting negotiation, the relevant entity, the source gap, and the responsible corporate lawyer.

2. Convert diligence findings into decision questions

Read the source behind each diligence summary. Ask what the acquirer must decide: request consent, change economics, strengthen a covenant, add a condition, seek a remedy, or accept exposure. Background findings can remain in the diligence tracker until they affect those decisions.

Delaware §259(a) provides for constituent corporations’ property and rights to vest, and liabilities and duties to attach, to the survivor. Statutory succession does not itself answer whether a particular contract triggers consent, termination, or notice rights. Review the actual contract and applicable law. See Delaware Code §259(a). (delcode.delaware.gov)

Record: the available wording, missing amendments, affected business relationship, and specific decision needed—not simply “assignment issue.”

3. Map the concern across the merger agreement

Trace each concern through definitions, representations, disclosure exceptions, interim covenants, closing conditions, and remedies. A scheduled exception may qualify a representation without providing the operational protection the acquirer wants. Check cross-disclosure rules rather than assuming an exception affects only its numbered section.

Use the agreement’s own categories. Section 3.18(a) of the SEC-filed Dayforce/Dawn agreement defines Material Contracts and requires a corresponding disclosure-letter list. That historical agreement illustrates negotiated architecture, not universal materiality standards. See the SEC-filed agreement, §3.18(a). (sec.gov)

For award discrepancies, connect individual grant evidence to the proposed treatment formula, vesting assumptions, funding, and payment timing—not just the capitalization representation.

Record: all provisions needed to understand the treatment. Where none addresses the concern, identify proposed new language rather than inventing an existing reference.

4. Rank issues by consequence and decision timing

Set priorities against this transaction’s objectives: closing ability, purchase economics, control of the survivor, critical relationships, and evidence availability. Keep exposure separate from confidence. An unverified concern can warrant urgent investigation without being described as an established breach.

For HSR, distinguish reportability, filing status, the waiting restriction, and contractual allocation of regulatory risk. The FTC explains that notification applies only to certain transactions, 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 waiting restriction. See FTC merger-review guidance. (ftc.gov)

Verify operative requirements separately for the transaction. Do not treat HSR expiration as universal regulatory approval.

Record: priority and rationale, evidence needed, the next decision date, and any dependency on signing, closing, or an outside date.

5. Develop an opening request and an authorized fallback

State the preferred treatment in terms the drafting team can implement. For a critical contract, distinguish a covenant to seek consent from a condition requiring receipt of consent. Check the beneficiary, satisfaction standard, and permitted waiver mechanism before describing either as adequate protection.

Develop a fallback only after identifying residual exposure. If the acquirer could accept missing consent with another protection, specify who may approve that trade and what evidence is required. Do not assume indemnification, escrow, or a termination right exists; check survival provisions and remedy limitations in the actual draft.

Record: the opening request, rationale, authorized fallback, and target response. Reference proposed language by draft ID or clause rather than pasting lengthy alternatives into the list.

6. Reconcile negotiating changes and obtain decisions

Before each session, compare the latest draft with the issues list. A definition change may affect several rows; a concession in one section may be offset elsewhere. Review related schedules and ancillary documents before marking treatment implemented.

After discussion, distinguish agreement in principle from incorporated wording. Route commercial trade-offs to the authorized acquirer executive and legal questions to responsible counsel. If the target offers evidence instead of a drafting change, keep the row open until that evidence is evaluated.

Record: the response source, decision-maker, agreed treatment, residual risk, and next action. Preserve prior positions in dated versions so the final rationale remains understandable.

7. Close rows against evidence and approved treatment

Close an issue only when the designated reviewer confirms that the evidence and current documents support the outcome. Verify cross-references, schedule treatment, and related conditions. A promise to send consent or revise language is not closure evidence.

Record accepted exposure as “accepted risk,” with the decision authority and scope of acceptance. If treatment requires later performance, assign it to the closing or integration tracker and retain the reference. Closing the negotiation decision does not establish that the future obligation has been performed.

Record: the final provision or evidence citation, reviewer confirmation, authorized acceptance where applicable, and each remaining assigned dependency.

Worked example

Fictional scenario: Alder Quay Holdings proposes to acquire Beacon Vale Systems by merging Beacon Vale into Alder Quay’s acquisition subsidiary, which will survive. Every party, document, amount, and clause below is fictional. Counsel reviews merger agreement MA-04 and incomplete disclosure schedules DS-02 before a negotiating call.

Management’s unverified summary attributes $4.8 million of annual revenue to a customer agreement. Uploaded contract CT-17 requires consent for a merger involving Beacon Vale, but referenced Amendment 2 is missing. MA-04 §3.14 addresses material contracts, §5.8 requires consent efforts for scheduled contracts, and §6.3 contains the disputed consent condition. The target’s markup deletes that condition.

Separately, CAP-03 labels an award unvested, while AW-09 contains a scheduled vesting provision. The capitalization spreadsheet’s measurement date and the complete amendment history have not been supplied. These materials raise a reconciliation question; they do not yet establish inconsistent treatment.

Rows 01 and 03 share evidence but address different decisions. A schedule supplement could resolve covenant coverage without answering whether closing should depend on consent. Counsel should cross-reference the rows, not merge away that distinction.

Row 02 prevents a spreadsheet label from becoming an approved payment assumption. Counsel has neither invented an amendment nor calculated unsupported liability. The immediate action is reconciliation against the proposed treatment date and formula.

Common mistakes

• Copying every diligence observation. Include findings that create a deal-document or risk-acceptance decision; retain background detail elsewhere.
• Treating disclosure as a complete cure. Check whether the acquirer still needs operational protection, a pricing response, or another negotiated treatment.
• Combining all approvals. Separate corporate approvals, governmental review, counterparty consents, and notices by source and owner.
• Losing competing positions. Record actual responses and draft references to distinguish rejection, silence, and conditional agreement.
• Calling acceptance “resolved.” Preserve residual exposure and authorized acceptance; do not imply the concern disappeared.

Final quality check

• Each row cites the correct source version and clause, page, or cell.
• Facts, missing evidence, and interpretations are distinguishable.
• Relevant amendments, schedules, definitions, and ancillary documents have been reviewed.
• Each concern connects to a concrete decision and affected provision.
• Priority reflects transaction objectives and decision timing.
• Current drafting matches the recorded agreement, including dependencies.
• Every open issue has an owner and next action; closure and acceptance have evidence and approval.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its contract review workflow in Word supports represented-party selection and deal-specific instructions. Findings quote and locate clauses, rank severity, and identify missing language as not present. Lawyers can edit or insert suggestions as ordinary tracked changes in the signed-in Word user’s name, or dismiss findings with reasons. Due diligence classification can organize documents for human review; tabular review supports work across documents. The issues list remains counsel’s work product, with legal and commercial decisions retained by the team. Book a demo to discuss this acquirer-side workflow.

Frequently asked questions

Should every disclosure exception become an issue?

No. Record exceptions that change economics, requested protection, or the decision to proceed. Identify the affected representation and any related covenant or condition.

How should an unavailable amendment be recorded?

Identify the missing document and the conclusion it prevents. State what the available contract says without presenting it as confirmed current wording. Assign the request and keep the decision open.

Can one issue link to several merger provisions?

Yes. One decision may require coordinated representation, covenant, and condition changes. Split rows when decision authority, treatment, or closure evidence differs, and cross-reference related entries.

When should an issue leave the negotiating list?

When treatment is verified or exposure is expressly accepted. Transfer remaining performance tasks with an owner and tracker reference, while preserving the negotiation decision and its supporting evidence.

Sources

• Delaware Code, Title 8, §§251 and 259: merger approval and statutory succession.
• FTC, Premerger Notification and the Merger Review Process: federal merger-review overview.
• SEC-filed Dayforce/Dawn merger agreement: historical negotiated wording, not market-standard evidence.

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.