Private Company Acquisitions

How to build a due diligence findings and risk tracker for Private Company Acquisitions

Build a buyer-side private company acquisition diligence tracker with a copyable template, source verification, risk decisions, and a fictional worked example.

October 17, 2026  ·  10 min read
Book a Demo →

Build a buyer-side diligence tracker by linking each material finding to the affected target entity, reviewed evidence, buyer exposure, unresolved questions, and a decision owner. Separate sourced facts from legal assessments and commercial recommendations. Connect each finding to its proposed treatment: further investigation, consent, revised acquisition terms, a closing requirement, or expressly accepted risk. The resulting deliverable is a decision record showing what is known, what remains uncertain, and what action or approval the buyer needs before signing or closing.

When to use this workflow

Use this workflow when substantive documents begin arriving for a private-company acquisition and buyer counsel must translate review results into decisions. It suits in-house teams coordinating specialists and external counsel reporting to an investment committee or business sponsor.

The scope is findings management, not a replacement for the document index, acquisition-agreement issues list, or closing checklist. Link those records rather than maintain competing versions of the analysis.

This guide uses a US transactional perspective. Establish whether the transaction is a stock purchase, asset purchase, or merger before assessing consequences. Entity type, governing law, industry, contract wording, and transaction structure matter. A subsidiary’s restriction may affect the acquisition even when only its parent is named in the purchase agreement.

What you need

Start with the proposed structure, target organization chart, acquisition perimeter, draft purchase or merger agreement, and buyer priorities. Identify essential revenue streams, facilities, technology, employees, and licenses.

Collect these inputs:

  • A document index recording stable IDs, affected entities, execution status, versions, amendments, and schedules.
  • A request list distinguishing missing materials, unavailable materials, and seller confirmations that no responsive documents exist.
  • Executed material contracts, capitalization and governance records, debt and lien materials, and relevant specialist reports.
  • Dated seller responses and disclosure schedules tied to an identified agreement draft.
  • Buyer review criteria, decision authorities, escalation contacts, and the anticipated signing and closing sequence.

Review criteria should identify decisions requiring business approval. A restriction affecting essential technology may warrant immediate escalation even when financial exposure cannot yet be quantified.

Use the template

Use the Private Company Acquisitions — Diligence findings tracker below. Copy this table into your working document or spreadsheet; no separate download is required.

ID / entity Topic / source Sourced fact Assessment / exposure Gap / confidence Action / treatment Owner / escalation Status / resolution proof

Assign a stable ID to each distinct finding requiring a decision. In “Topic / source,” record document IDs and clause or page references; link to the index for location and version details. Label draft provisions as drafts.

“Sourced fact” states what the evidence establishes. “Assessment / exposure” records counsel’s interpretation, buyer impact, and priority. “Gap / confidence” identifies missing evidence and what could change the assessment. Confidence measures evidentiary completeness, not importance: an uncertain issue can be critical.

“Action / treatment” identifies the next investigation or proposed risk allocation. Name an accountable owner and escalation date or deal milestone. Use defined statuses such as open, awaiting evidence, decision required, accepted risk, and resolved. The final column should link to supporting proof or a decision record. Use linked detail for lengthy analysis rather than unexplained shorthand.

Step by step

1. Define the perimeter and decision criteria

Map acquired entities and assets, excluded businesses, and proposed pre-closing restructuring. Identify the entity holding each material right or obligation. Record assumptions about ownership changes rather than treating every acquisition as an assignment.

Agree a priority scale with the buyer. Reserve the highest priority for potential transaction barriers or threats to essential operations. Distinguish those issues from risks needing financial protection or later remediation.

Record: affected entity, buyer exposure, priority, and the structural assumption supporting the assessment. Link a common assumptions note where several findings depend on the same transaction step. Revisit those findings if the structure changes.

2. Establish the evidence before stating the finding

Review executed documents with relevant amendments, exhibits, and side letters. Seller summaries can identify questions but should not become proof of underlying obligations. State when only an unsigned version is available.

Distinguish “not found in materials reviewed” from “does not exist.” Attribute seller confirmations to a dated response and identified responder. For ownership questions, reconcile the available capitalization records rather than treating one spreadsheet as conclusive.

Record: document ID, version, clause or page, concise factual description, and execution or completeness gaps. Identify the request needed to close each gap. Preserve conflicting evidence instead of selecting the more convenient source.

3. Separate exposure from uncertainty

Describe the consequence for this buyer: loss of an essential contract, disputed equity ownership, restricted technology use, unexpected expenditure, or incomplete authority evidence. Explain the acquisition dependency instead of labeling the finding simply “legal risk.”

Do not invent financial estimates. Ask business or finance owners to assess exposure and identify whether an estimate is gross, contingent, recurring, or dependent on mitigation. Keep legal priority separate from evidentiary confidence.

Record: counsel’s assessment, commercial dependency, confidence level, and unanswered question. “High operational impact; low confidence pending amendment” is more useful than an unexplained red rating. Identify who must supply the missing commercial information.

4. Route approval and regulatory questions correctly

Separate corporate approval evidence from regulatory restrictions. For a Delaware domestic-corporation merger, DGCL § 251(b)–(c) addresses board approval and advisability, stockholder adoption, and filing, subject to statutory exceptions and alternative procedures. It is not a universal approval checklist for stock purchases, asset purchases, or LLC transactions. Have corporate counsel confirm the applicable route. Delaware General Corporation Law, § 251

Flag HSR reportability for antitrust review rather than infer it from transaction value alone. Covered acquisitions require notification and observance of the applicable waiting period; a second request extends review and prevents closing until the required process is satisfied. Thresholds and exemptions require transaction-specific analysis. FTC premerger notification guidance

Record: specialist owner, question presented, evidence required, and escalation milestone. Buyer acceptance of commercial risk does not establish satisfaction of a statutory restriction.

5. Connect each finding to a proposed buyer treatment

Choose an actionable response: obtain evidence, seek consent, revise a representation, allocate identified losses, adjust economics, require remediation, or request business acceptance. Keep alternatives visible until the authorized decision-maker chooses.

Distinguish contractual recourse from insurance coverage. One SEC-filed acquisition agreement directs representation-and-warranty breach losses solely to R&W insurance, except Fraud. That allocation does not establish policy coverage; the policy requires separate review. Granite Southeast–Roberts Family agreement, § 8.6

Record: proposed treatment, linked agreement section or issues-list ID, fallback, decision-maker, and residual exposure. For financial protection, identify unresolved questions about recovery limits, funding, or exclusions. A proposed indemnity is not an agreed protection.

6. Reconcile findings with schedules and the agreement

Check whether disclosure schedules describe the same facts as the tracker and whether the proposed response survived the latest agreement draft. Disclosure alone is neither remediation nor recorded buyer acceptance.

Read the actual document hierarchy. In one filed stock purchase agreement, § 13.11 incorporates schedules and related agreements but gives the agreement body precedence over inconsistent provisions, subject to expressly stated disclosure exceptions. This illustrates drafting, not a universal hierarchy. Molina–Bright Health agreement, § 13.11

Record: reviewed draft version, schedule reference, inconsistency, and drafting owner. Preserve the previous assessment when revisions change buyer protection. Link the finding to the negotiation record without duplicating every drafting comment.

7. Close findings against a stated resolution test

Define the evidence required before changing status. A consent issue might require the correct counterparty’s executed consent covering the proposed transaction, reviewed for qualifications and effectiveness. An unrelated notice acknowledgment would not meet that test.

Accepted risk differs from a resolved problem. Identify the accepting authority, decision date, basis, and remaining exposure. Transfer post-closing work to a linked record with an accountable owner; transferring a task does not establish remediation.

Record: resolution evidence, reviewer, decision date, and residual exposure or follow-up ID. Keep unresolved issues visible in the buyer’s decision summary. Reopen findings if new evidence undermines the recorded resolution.

Worked example

Fictional scenario: Harbor Lantern Holdings proposes to acquire all shares of Cedar Vale Instruments, Inc. for $42 million. Cedar Vale’s wholly owned subsidiary, Cedar Vale Operations, LLC, uses a licensed calibration platform essential to its principal product line. Buyer draft A-001 requires designated consents before closing. All parties, documents, amounts, and provisions below are fictional.

The seller supplies signed license D-014, customer contract D-028 referencing an absent amendment, and draft disclosure schedule DS-003 identifying equipment defects. Seller response R-019 states that repairs are complete. The buyer has not independently established completion.

ID / entity Topic / source Sourced fact Assessment / exposure Gap / confidence Action / treatment Owner / escalation Status / resolution proof
F-01 / Cedar Vale Operations License; D-014 § 12.3 Prior written consent required for indirect control change High priority: parent acquisition implicates wording; platform essential High confidence in trigger; consent outstanding Seek consent; link A-001 § 7.2 Buyer deal counsel / signing recommendation Open; reviewed, effective consent required
F-02 / Cedar Vale Operations Customer contract; D-028 § 16 Contract references Amendment 2; amendment absent Potential termination exposure; complete terms unassessed Low confidence; amendment and customer dependency missing Request amendment; obtain finance assessment Commercial counsel / next issues meeting Awaiting evidence; request R-020 open
F-03 / Cedar Vale Instruments Defects; DS-003 § 4.9; R-019 Draft lists defects; seller asserts repairs complete Potential cost and downtime; completion unverified Low confidence; service and acceptance reports absent Obtain reports; consider specific protection pending review Operations lead / signing decision Decision required; seller assertion only

F-01 warrants immediate consent work because the reviewed clause addresses indirect control changes. Confidence in that finding is high even though its treatment remains incomplete. F-02 supports neither a clean conclusion nor a definitive consent requirement: the missing amendment could change the analysis. F-03 requires technical substantiation, not merely a revised schedule deleting the defects.

The buyer therefore pursues consent, keeps the customer question open, and requests repair evidence. If signing proceeds before those requests are answered, the decision record must identify the authorized acceptance and any agreed protection. The rows prevent incomplete treatment from being mistaken for uncertain evidence—or seller assurances from being reported as verified remediation.

Common mistakes

  • One row per document. That produces an index. Combine sources supporting one finding; split issues requiring different decisions or resolution evidence.
  • Treating disclosure as resolution. Reconcile the schedule with the agreement and assess residual buyer exposure separately.
  • Collapsing consent, notice, and termination provisions. Preserve each trigger and consequence, including direct and indirect control changes.
  • Closing an issue as “insured.” Separate contractual recovery from policy coverage and assign unresolved coverage questions.
  • Replacing evidence with seller assurances. Attribute the statement and apply the resolution test; record acceptance if the buyer proceeds without further proof.

Final quality check

  • Every material finding identifies the affected entity and transaction step.
  • Source links open the intended version; clause or page references support the stated facts.
  • Executed documents, drafts, seller assertions, and missing evidence remain distinguishable.
  • Priority reflects buyer impact; confidence reflects evidence quality and completeness.
  • Proposed treatments match the current agreement and disclosure schedules.
  • Every open issue has an accountable owner and escalation milestone.
  • Resolved and accepted-risk items contain supporting evidence or an authorized decision, with residual work expressly assigned.

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. Use those capabilities for the evidence review behind your tracker, while lawyers verify sources, assess exposure, and approve dispositions. When findings require agreement changes, contract review supports review and redlining. Book a demo to discuss this buyer-side workflow.

Frequently asked questions

Should every missing document become a finding?

No. Keep routine requests in the request list. Create a finding when the absence prevents a material assessment, raises an acquisition-specific concern, or requires buyer escalation. Link the request ID and explain the decision that cannot yet be made.

Can several contracts support one finding?

Yes, when they support the same decision and treatment. Preserve individual references and exceptions. Split findings when counterparties, triggers, or consent requirements require separate decisions or proof. A shared commercial concern does not make distinct contractual requirements identical.

Who should decide whether the buyer accepts a risk?

Follow the buyer’s agreed decision authority. Counsel explains legal exposure, evidence gaps, and available protections; the authorized decision-maker approves commercial acceptance. Record the recommendation and decision separately. Acceptance does not establish legal compliance or satisfaction of a closing restriction.

What belongs in the signing report?

Summarize unresolved high-priority findings, material accepted risks, and decisions needed for signing. Link stable finding IDs. Distinguish pre-signing action from proposed closing or post-closing treatment, and identify whether protections are proposed, agreed, or verified—not simply “addressed.”

Sources

Scope: General professional workflow guidance, not advice for a particular acquisition. Filed agreements illustrate negotiated wording, not market standards; applicable law and operative transaction documents require matter-specific verification.

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.

Run this workflow in DecoverAI

Clause-quoted findings, missing-language flags, and tracked changes in your name — with your team deciding every call. Plans from $299 per seat per month, SOC 2 Type II certified.

Book a demo
to learn more.
Book a Demo