How to build a due diligence findings and risk tracker for Business Merger Transactions

Build an acquirer-side merger diligence tracker by turning each supported finding or material evidence gap into a decision record. Identify the affected entity, cite the controlling documents, separate facts from interpretation, and assign an owner, response, and escalation point. Connect each finding to the proposed merger agreement or a specific business decision. The deliverable is a source-linked register showing what could affect signing, closing, valuation, or integration—and what evidence and authority are needed to resolve or accept each risk.

When to use this workflow

Use this workflow when the acquirer’s legal team begins substantive review of a target’s data room and needs a consolidated view across corporate, commercial, employment, regulatory, and disputes workstreams. Start before the first diligence report so unsupported conclusions and duplicate issues do not become embedded in negotiations.

The tracker is an exception-and-decision register, not a document inventory or complete closing checklist. Capture findings requiring investigation, drafting, escalation, or express risk acceptance.

This guide uses a US baseline, focused on Delaware corporate mergers and federal HSR review where relevant. Other formation jurisdictions, entity types, regulated businesses, and contractual governing laws require separate analysis. Identify the proposed survivor and each transaction step: the acquisition parent, merger subsidiary, target, and operating subsidiaries may have different obligations and approval requirements.

What you need

Collect the structure chart, proposed merger structure, entity jurisdictions, current merger-agreement draft, disclosure schedules, diligence request list, and data-room index. Include the acquirer’s commercial priorities, review scope, decision authority, and target signing and closing dates.

Request complete source families: executed contracts and amendments; charters and approval records; capitalization records, equity plans, and individual awards; permits; dispute materials; and relevant financial support. Identify missing schedules and incorporated terms expressly.

Give documents stable IDs. Preserve filenames, data-room paths, versions, execution status, upload dates, and amendment relationships in the document index. Tracker citations should lead through that index to retrievable sources. An affirmative seller response that no document exists is different from an unanswered request; preserve the response and its scope.

Use the template

The Business Merger Transactions — Diligence findings tracker below is a working template. You can copy this table into your working document or spreadsheet. Put lengthy analysis in a linked issue note rather than compressing it into a status label.

Use immutable issue numbers in the first column. In “Source / request,” record document IDs, versions, clause or page references, and outstanding request numbers. Distinguish source wording from reviewer interpretation in the next two columns; mark evidence confidence as complete, partial, or unverified.

“Priority / timing” combines impact with the next decision point. “Deal response” identifies proposed treatment and the relevant agreement section. “Owner / escalation” names the accountable person, escalation recipient, and date. The final column records status, completion evidence, reviewer approval, and acceptance authority where applicable. Use linked notes when these details exceed a readable cell.

Step by step

1. Define which decisions the tracker must support

Agree with the deal lead which findings warrant entry: potential closing impediments, material commercial exposures, unresolved ownership or capitalization questions, significant drafting exceptions, and evidence gaps preventing a reliable conclusion. Do not adopt the agreement’s defined materiality thresholds as universal diligence filters.

For example, the historical Dayforce/Dawn agreement uses a negotiated Material Contract definition and corresponding disclosure-letter list in §3.18(a). That illustrates agreement architecture, not a universal diligence threshold or market standard (SEC-filed agreement, §3.18(a)).

Record: affected entity, issue category, decision point, and provisional priority. Keep routine document-processing tasks in the request list unless they create a substantive gap.

2. Establish the evidence before writing the conclusion

Read the complete document family and confirm which version controls. For a customer contract, check amendments, schedules, incorporated terms, signatures, and counterparty identity before assessing merger-related consent language. For capitalization, compare the summary table with underlying issuance, approval, and award records.

Capture a factual statement with a precise citation. Record unanswered questions separately. “No consent provision identified in supplied documents” is not equivalent to “no consent required,” particularly where incorporated terms are missing.

Record: source IDs and locations, observed facts, missing materials, evidence confidence, and follow-up request number. Identify whether the finding rests on executed text, a draft, or a seller response.

3. Analyze the finding against the merger structure

Ask which entity holds the right or obligation, whether it survives, and which transaction step could trigger a consequence. Delaware §259(a) provides for property and rights to vest in the survivor and liabilities and duties to attach to it. Do not treat that succession rule as a substitute for analyzing contractual consent, notice, or termination language (Delaware Code §259(a)).

For corporate approvals, §251(b) addresses board approval and advisability; §251(c) generally requires adoption by a majority of outstanding stock entitled to vote, subject to statutory exceptions. Check the charter, voting classes, and applicable exceptions rather than assuming identical approvals for every constituent (Delaware Code §251).

Record: preliminary interpretation, structural assumptions, affected entity, commercial consequence, and specialist question. Preserve uncertainty rather than presenting a provisional conclusion as settled.

4. Rank impact separately from evidence confidence

Define priorities with the deal lead. Reserve the highest priority for findings that could alter the acquisition decision, disrupt the timetable, or require senior approval. A high-priority issue may rest on incomplete evidence; urgency and confidence answer different questions.

Regulatory uncertainty can justify early escalation without a definitive reportability conclusion. The FTC explains that only certain transactions require HSR notification, thresholds change annually, exemptions exist, and reportable transactions cannot close before the applicable waiting period expires or is terminated early. A Second Request extends review and the waiting restriction (FTC merger-review guidance).

Record: priority, supporting rationale, evidence confidence, and next decision date. Assign transaction-specific HSR analysis separately; do not equate waiting-period expiration with universal regulatory approval.

5. Connect each finding to a proposed deal response

Choose a response addressing the exposure: obtain evidence, secure consent, correct records, negotiate language, reconsider economics, or seek authorized risk acceptance. Link drafting proposals to the relevant representation, disclosure exception, covenant, condition, or remedy in the current agreement version.

A disclosure entry does not explain the acquirer’s practical response to threatened customer termination. Likewise, a proposed condition is not an agreed protection. Identify whether treatment is requested, under negotiation, or incorporated into the draft, and assess what the negotiated wording actually accomplishes.

Record: proposed action, agreement section and version, responsible negotiator, and fallback decision. Distinguish the diligence recommendation from the parties’ agreed allocation of risk.

6. Assign ownership and escalation dependencies

Assign one accountable owner per issue, even when specialists contribute. State the required output and prerequisite information. Separate the lawyer interpreting a provision from the business executive authorized to accept the exposure.

Set escalation dates against signing, closing, financing, or other actual decisions. Use the team’s calendar and reporting process; a date in a table does not ensure follow-up. Consolidate duplicates under a lead issue while retaining links to affected contracts and entities.

Record: owner, required output, dependencies, escalation recipient, and date. Preserve a disputed seller position alongside the acquirer’s analysis rather than overwriting the finding.

7. Close issues only through a documented decision

Define statuses such as investigating, awaiting evidence, negotiating, ready for approval, resolved, and accepted risk. An upload or proposed redline is not necessarily resolution. Require evidence addressing the original concern and reviewer approval of the disposition.

Distinguish accepted risk from cured risk. If an issue moves to a closing checklist or integration plan, retain the tracker entry and identify the receiving owner and record. Transfer alone is not substantive resolution.

Record: completion evidence, approving reviewer, decision date, residual exposure, and continuing action. Reopen the issue when new documents or structural changes undermine the conclusion.

Worked example

Fictional scenario: Alder Quay Holdings proposes to acquire Briar Signal Systems through a merger of its acquisition subsidiary into Briar, with Briar surviving. All parties, documents, amounts, and clause descriptions below are fictional.

A customer relationship accounts for $2.8 million in annual revenue according to the supplied revenue schedule. Diligence also reveals an option discrepancy and incomplete regulatory inputs. Merger-agreement draft M-001 v3 does not expressly condition closing on the customer’s consent. Missing evidence is not assumed to exist.

These entries change three decisions. The customer issue requires amendment verification and a consent strategy before recommending the proposed protection; annual revenue is not treated as damages. The option discrepancy blocks reliance on either figure without declaring one correct. The regulatory gap requires a qualified timetable, not an invented filing conclusion. Named individuals and calendar dates would replace role-based milestone assignments in the live tracker.

Common mistakes

• Treating seller silence as a clean result. Record the unanswered request and decision impact; obtain an affirmative response or assign residual uncertainty.
• Assuming succession eliminates consent risk. Analyze merger, assignment, change-of-control, and notice wording against the structure and applicable law.
• Combining distinct exposures in one row. Separate issues when owners, remedies, or approval paths differ; cross-reference common sources.
• Closing a finding because disclosure was added. Assess the negotiated effect of disclosure and whether operational exposure remains.
• Using “business accepted” without authority. Identify the authorized decision-maker, accepted exposure, supporting analysis, and continuing obligations.

Final quality check

• Every material finding identifies the affected entity and transaction step.
• Citations reach the reviewed version, clause or page, and relevant amendments.
• Facts, missing evidence, interpretation, and commercial exposure remain distinguishable.
• Priority and evidence confidence are separately explained.
• Proposed protections are distinguished from agreed language and checked against the current draft.
• Open issues have accountable owners, next actions, and escalation dates.
• Resolved or accepted entries retain evidence, approval, residual risk, and any receiving-workflow reference.

Complete the workflow with DecoverAI

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. In contract review, lawyers can choose the represented party, give deal-specific instructions, and assess findings that quote and locate clauses, rank severity, and identify missing language as not present. Treat those findings as review inputs, not tracker dispositions: lawyers retain responsibility for verification, structural analysis, and risk decisions. Book a demo to discuss this diligence workflow.

Frequently asked questions

Should every reviewed document get a tracker row?

No. Keep review coverage in the document index. Create tracker rows for actionable findings and significant evidence gaps, linked to the documents and requests supporting them.

How should we track one consent issue affecting several contracts?

Use a parent issue for the shared question and separate entries where wording, counterparties, timing, or consequences differ. One obtained consent should not clear unrelated contracts.

Can an issue be resolved before the definitive agreement is signed?

Yes, where evidence demonstrates that the underlying concern is cured. If treatment depends on negotiated language, keep that dependency visible until controlling text and approval are confirmed; reopen the issue if the language changes.

What should the deal committee receive?

Provide decision-critical entries showing exposure, evidence confidence, recommendation, alternative, and approval requested. Preserve links to the full tracker so a concise report does not erase uncertainty or competing positions.

Sources

• Delaware Code, Title 8, §§251 and 259: corporate merger approvals and statutory succession.
• FTC, Premerger Notification and the Merger Review Process: federal HSR overview, not a transaction-specific determination.
• SEC-filed Dayforce/Dawn merger agreement, §3.18(a): historical example of negotiated Material Contract disclosure architecture.

Scope: General professional workflow guidance, not advice for a particular transaction. Conclusions depend on actual documents, governing law, facts, and deal context.

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.