# Legal due diligence report template

Adapt this structure to the activated review areas. Delete unused modules. Do not
fill gaps with generic conclusions.

```markdown
---
title: Legal Due Diligence Report
project: [Transaction codename]
target: [Exact entity or assets in scope]
buyer: [Buyer]
preparedFor: [Counsel/client as directed]
cutoffDate: [YYYY-MM-DD]
status: Draft for counsel review
---

# [Confidentiality or privilege legend supplied by counsel]

## Executive deal points

| ID | Status | Area | Evidence-backed finding | Transaction relevance | Possible response for counsel | Source |
|---|---|---|---|---|---|---|
| DP-01 | [Confirmed / Incomplete / Contradictory / Specialist review] | [Area] | [Fact + mechanism] | [Why it matters to this structure] | [Option, not final advice] | [Pinpoint] |

## Transaction and scope

- Buyer:
- Target entities/assets:
- Seller:
- Proposed structure:
- Signing/closing posture:
- Materiality thresholds:
- Repository and index reviewed:
- Q&A and management-session records reviewed:
- Authorized public searches reviewed or run:
- Cutoff date:
- Express exclusions and specialist dependencies:

## Corporate, ownership, and transaction structure

### Entity and ownership reconciliation

| Entity/security | Evidence | Record result | Contradiction or gap | Transaction consequence |
|---|---|---|---|---|

### Approval, consent, payoff, and transfer map

| Requirement | Trigger/mechanism | Timing | Responsible party | Evidence | Status |
|---|---|---|---|---|---|

### Intercompany and separation dependencies

| Service/asset/right | Current owner/provider | Closing treatment | TSA/replacement need | Evidence | Status |
|---|---|---|---|---|---|

## [Activated review area]

### Scope and corpus

[Documents and records actually reviewed, selection method, and limitations.]

### Findings

| ID | Status | Finding | Legal/contract mechanism | Transaction relevance | Next question/action | Source |
|---|---|---|---|---|---|---|

### Matrix or reconciliation

[Use the output specified by the selected review-area module.]

## Outstanding requests and data gaps

| ID | Missing or contradictory item | Why needed | Request channel/date | Owner | Status/cutoff |
|---|---|---|---|---|---|

## Specialist-review register

| Issue | Specialty/jurisdiction | Question for specialist | Supporting record | Timing dependency | Status |
|---|---|---|---|---|---|

## Scope, methods, and limitations

- List only repositories, folders, sessions, trackers, searches, and dates that
  the reviewer actually used.
- Identify sampling or materiality rules.
- Distinguish management statements from documentary and public-record support.
- State excluded legal disciplines and technical reviews.
- State unresolved evidence and the report cutoff date.
```

## Finding drafting pattern

Use this order:

1. **Fact:** what the evidence states, with pinpoint.
2. **Mechanism:** the operative contract term or verified legal requirement.
3. **Transaction relevance:** why it matters to the proposed structure.
4. **Status/limitation:** confirmed, contradictory, incomplete, or specialist
   review needed.
5. **Possible response:** an option for counsel, not an agent's final legal or
   commercial instruction.

Avoid labels such as `high risk` unless the report defines the rating method and
the evidence supports it. Never state that an absent document contains no
restriction.
