How to build a due diligence findings and risk tracker for Corporate Carve-Out Transactions

Build a buyer-side carve-out diligence tracker around the business the buyer must operate, not just the documents available for review. Define the acquisition perimeter, index the evidence, and record each finding with its uncertainty, buyer impact, proposed response, dependencies, and accountable owner. Connect those findings to purchase-agreement allocations, transition services, and required decisions. The deliverable is a source-linked register that distinguishes documented problems from unanswered questions and shows which risks require negotiation, further investigation, or an operational solution.

When to use this workflow

Use this workflow when a buyer acquires a division, product line, or subsidiary that depends on the seller’s wider organization. A concrete trigger is a data room containing target-company contracts but little evidence of parent-level software, procurement, payroll, premises, or intercompany support.

Buyer’s counsel should maintain the legal findings with input from finance, IT, HR, procurement, and integration leads. Begin when the proposed perimeter and initial documents are available. Update the same register as evidence and drafts change, preserving decisions rather than replacing their history.

This is a general US-oriented transactional workflow. Analyze contract rights against the operative language, governing law, transaction structure, and facts. Assign cross-border transfers and local regulatory questions separately. The tracker identifies decisions; it does not establish a right to refuse closing.

What you need

Collect the proposed purchase agreement, disclosure schedules, organization charts, and asset and liability schedules. Include the transition services agreement (TSA), service schedules, and proposed supply, IP, lease, employee, and other separation documents.

Request a perimeter matrix identifying who owns each material asset or right, who uses it, and how the buyer will obtain title or access. Cover entities, employees, IP, data, permits, premises, and liabilities—not merely transferred contracts.

Obtain shared and parent-level arrangements separately. Ask business owners which support disappears at closing. Request amendments, order forms, statements of work, incorporated schedules, and relevant consent correspondence alongside principal agreements.

Agree buyer priorities, escalation criteria, access restrictions, and reviewers. Identify both the legal reviewer and the business owner who can validate operational consequences. Obtain the buyer’s intended standalone operating model so reviewers can distinguish temporary dependence from a permanent gap.

Use the template

Use the Corporate Carve-Out Transactions — Diligence findings tracker as the central register. You can copy this table into your working document or spreadsheet. Maintain one row per actionable issue, not one row per document.

Assign a stable finding ID and identify the affected business component. The source field should contain document ID, version, and clause or page citation. Use a separate document index for locations and supporting records when several sources inform one issue.

Separate documentary facts from interpretation in the finding field. Use the gap field for missing amendments, redactions, incomplete schedules, and unresolved assumptions. Confidence describes evidence quality; priority describes potential consequence. A serious issue can have low evidential confidence.

Record the response and dependencies together: “negotiate standalone license; dependent on vendor agreement and IT migration estimate.” Name one accountable owner. Distinguish internal decision targets from contract-derived dates; retain the source, trigger, and calendar convention for contractual dates. In the final field, identify the resolution evidence or authorized risk acceptance, not just a status label.

Step by step

1. Establish the perimeter and operating dependencies

Compare the proposed acquired business with legal ownership of its assets and supporting arrangements. Ask which entity owns each critical resource, whether that entity or resource transfers, and what supplies continuity if transfer is delayed.

Trace shared services beyond their descriptions. Payroll review should identify supporting applications, identity access, personnel data, and vendor arrangements. Ask the relevant business owner to confirm dependencies rather than inferring completeness from a service name.

Record: perimeter identifiers, affected operations, known support arrangements, and an owner for each unresolved ownership or access question. Treat the seller’s perimeter schedule as an input to verification, not proof that no items are missing.

2. Index the evidence before drawing conclusions

Assign stable document IDs and capture parties, execution status, version, business coverage, and data-room location. Check amendments and incorporated schedules. Distinguish unavailable, redacted, superseded, and reviewed materials.

Review parent arrangements for coverage of the acquired business even when the target is not a named party. Examine assignment, change-of-control, and partial-transfer language separately against the proposed structure. Also check termination rights, renewal timing, minimum purchases, and replacement options where they affect continuity.

Record: precise citations and the limits of each conclusion. “Consent requirement unresolved because amendment missing” is more useful than an unsupported “consent required” or “no issue.” Link each missing item to a specific request and responsible reviewer.

3. Write findings as facts, uncertainty, and buyer impact

State the verified fact first, the unresolved question second, and the consequence third. Replace “IP risk” with the affected right, evidence gap, and decision needed.

Compare proposed assumed and retained liabilities with the relevant contracts and operational history. Section 2.02 of the Emergent–BTG agreement illustrates separate treatment of pre-closing contract breaches and delayed-transfer contracts. It is a negotiated allocation, not a generally applicable liability rule. (sec.gov)

Do not treat that example as resolving the buyer’s exposure in another transaction. Assign any third-party or statutory liability question for separate analysis.

Record: affected liability or right, evidence, unresolved interpretation, and buyer consequence. Prioritize using continuity, financial exposure, replacement difficulty, and decision timing—not document volume.

4. Separate operational criticality from contractual closing significance

For each high-priority issue, ask whether the buyer can operate without resolution and whether the current agreement makes resolution relevant to a closing condition. Read the condition, exceptions, representations, and covenants together. Label draft provisions as proposed rather than existing rights.

Section 5.5(e) of the Matthews–Duravant agreement generally excludes missing third-party consents or specified transfers and arrangements from assessing closing conditions, except to the extent of a breach of Section 3.4 or 5.5. This illustrates why operational importance and contractual closing significance require separate analysis. (sec.gov)

Regulatory timing requires its own review. The FTC’s HSR overview explains that covered acquisitions cannot close before the applicable waiting period expires or is terminated early. (ftc.gov) Not every acquisition requires filing; thresholds change annually and exemptions may apply. (ftc.gov)

Record: operational priority, contractual significance, governing source, and assigned regulatory questions. Do not invent a clearance date or equate a requested deliverable with a condition.

5. Connect each proposed response to the separation documents

Select a response addressing the exposure: further evidence, revised allocation, consent, replacement agreement, price treatment, insurance evaluation, or integration action. Identify the document requiring change and who must approve the solution.

For TSA-dependent solutions, map upstream services, licenses, people, data, duration, and exit requirements. The Seres–Nestlé TSA schedule expressly identifies HR administration’s dependence on IT.03. Its service identifiers and dependency fields illustrate a useful comparison; redactions limit conclusions about commercial terms. (sec.gov)

Compare proposed service scope with exclusions, capacity, charges, and replacement plans. Ask technical owners what evidence will demonstrate continuity and readiness to exit.

Record: proposed response, affected agreement sections, linked finding IDs, dependencies, and the resolution test. A listed TSA service should not close an issue while necessary access or upstream support remains unverified.

6. Assign decisions and verify resolution

Give every open issue one accountable owner, a next action, and a decision target. List supporting reviewers without diluting accountability. Escalate before the negotiation or operating decision the issue affects.

When evidence arrives, test it against the original finding. A replacement vendor agreement might resolve access while introducing minimum purchases or migration obligations. Revise or split the finding rather than closing it prematurely.

Record: decision, rationale, approver, and supporting document version. Use distinct statuses: open, awaiting evidence, response agreed, accepted risk, and resolved. Accepted risk retains its consequence and approval; resolved identifies proof. Hand off continuing obligations with their source and owner without turning this register into a complete integration plan.

Worked example

Fictional scenario: Harbor Finch Holdings proposes to acquire the laboratory-instrument division of Cedar Vale Industries through an asset purchase. The division uses Cedar Vale’s enterprise resource planning (ERP) system and shared freight arrangement. Harbor Finch expects six months of transitional ERP support, but TSA draft v2 provides only three months of identity administration.

All parties, documents, terms, and findings below are fictional. The purchase agreement and TSA are unsigned. Counsel has the executed principal freight agreement but not its referenced amendment. The draft schedule identifying consents for the proposed closing condition is incomplete. No vendor confirmation of post-sale software access has been supplied.

The entries change the negotiation agenda. F-01 requires evidence of permissible access, not simply a longer TSA term. F-02 prevents counsel from declaring either a consent failure or a closing right while essential sources remain missing. Because the purchase agreement is unsigned, the immediate question is what condition the buyer should negotiate.

F-03 establishes a duration mismatch, but not a proven outage. Technical confirmation determines whether the buyer needs extended identity support or can use its own replacement. Linking F-01 and F-03 prevents approval of “six months of ERP support” before both license access and supporting services have been tested.

Common mistakes

• Tracking only target contracts. Reconcile the document list with the operating map and request parent arrangements supporting the acquired business.
• Treating missing evidence as clean diligence. Identify the omitted amendment or schedule, its effect on the conclusion, and who will obtain it.
• Equating criticality with a closing condition. Analyze actual conditions and qualifications separately; distinguish proposed drafting from executed rights.
• Recording “covered by TSA” as mitigation. Verify access, exclusions, dependencies, duration, and replacement readiness before accepting the response.
• Closing issues when drafting is agreed. Specify whether resolution requires execution, third-party acceptance, delivery, technical validation, or an authorized risk decision.

Final quality check

• Each high-priority finding identifies an affected asset, liability, service, or process.
• Document IDs, versions, clauses, and page references match the source materials.
• Facts, interpretations, missing evidence, and redactions are distinguishable.
• Priority reflects buyer consequences independently of evidential confidence.
• Closing significance is supported by identified provisions and their qualifications.
• TSA responses address upstream dependencies and mismatched durations.
• Every open issue is resolved or expressly assigned an owner, action, and decision target.
• Resolved and accepted-risk entries retain proof or approval, respectively.

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. For resulting drafting issues, contract review in Word supports selecting the represented party and providing deal-specific instructions. Findings quote and locate clauses, rank severity, and identify missing language as not present. Lawyers remain responsible for source verification, risk decisions, and the tracker. Book a demo to discuss this carve-out review workflow.

Frequently asked questions

Should each document have its own findings row?

No. Keep document-level records in the index and actionable issues in the tracker. One finding may require several sources; one agreement may generate separate transfer, continuity, and liability findings.

How should we prioritize incomplete evidence?

Assess potential buyer consequences separately from confidence. A missing amendment affecting a critical application can justify urgent investigation without supporting a final conclusion that access is prohibited. State what evidence would change the assessment.

Can a TSA resolve a shared-contract problem?

Treat it as a proposed response to test, not a completed solution. Review the underlying arrangement, vendor involvement, required access, service scope, duration, and replacement plan. Record permission or dependency questions separately from service drafting.

When should a finding leave the diligence tracker?

Close it when its resolution test is met, or record authorized risk acceptance. If action continues after signing or closing, retain the finding and link its assigned handoff. Preserve sources, rationale, and proof rather than deleting the history.

Sources

• FTC — Premerger Notification and the Merger Review Process.
• Emergent–BTG Stock and Asset Purchase Agreement — Section 2.02.
• Matthews–Duravant Equity Purchase Agreement — Section 5.5(e).
• Seres–Nestlé Transition Services Agreement — Schedule of Services.

SEC-filed agreements illustrate negotiated provisions, not generally applicable law or market standards.

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.