How to organize a legal due diligence document index for Share Purchase Transactions

A buyer’s diligence document index should identify each document, the target entity it concerns, its relationship to other records, and its review status. Start with a preserved data-room inventory, assign stable document IDs, and connect base agreements to amendments, ownership records, and missing attachments. Reconcile the collection against buyer requests and assign unresolved gaps. The resulting deliverable is a controlled evidence map—not merely an upload list or a substitute for legal findings—that supports ownership reconciliation, contract review, and targeted follow-up.

When to use this workflow

Use this workflow when buyer’s counsel receives data-room access, inherits a disorganized repository, or consolidates supplemental uploads before reporting. It supports outside counsel and in-house teams coordinating corporate, commercial, employment, IP, tax, and regulatory reviewers.

For a share purchase, distinguish the acquired company, subsidiaries, selling shareholders, and excluded affiliates. An excluded affiliate’s documents may remain relevant where the target depends on its services, licenses, or premises. Organize records around the actual acquisition perimeter, not just the seller’s folders.

This is a general US-oriented workflow. The Delaware provisions discussed below concern Delaware corporations; other jurisdictions require separate analysis. The index organizes evidence rather than determining title, transferability, or disclosure sufficiency.

What you need

Obtain the transaction perimeter, entity chart, buyer request list, available data-room inventory, and authorized access to source files. Include the current purchase agreement and disclosure schedules when available, clearly identifying draft versions.

For ownership, collect capitalization tables, stock ledgers, certificates or uncertificated-share records, issuance approvals, equity plans, options, prior transfers, and shareholder agreements. For contracts, request schedules, exhibits, amendments, side letters, joinders, and notices affecting operation.

Agree who maintains the master index, which repository is authoritative, and who may access restricted material. Set a reporting cutoff with a time zone. Preserve the initial inventory separately so later additions, replacements, and removals remain identifiable.

Use the template

Use the Share Purchase Transactions — Diligence document index below. You can copy this table into your working document or spreadsheet.

Assign one row to each distinct document version. If a PDF contains independent instruments, use separate rows with page ranges and a shared source-file reference. These eight columns combine related information; use consistent labels within cells so dates and statuses remain distinguishable.

• Doc ID: A stable reference that survives renaming or folder moves.
• Entity / category: Full legal entity name and review category, including multiple entities where relevant.
• Document / date: Substantive title; distinguish stated execution and effective dates.
• Execution / version: Draft, apparently signed, partially signed, or uncertain, plus version identifier.
• Source / pinpoint: Original path, receipt batch or date, and page, clause, worksheet, or cell reference.
• Family / request: Related document IDs, buyer request IDs, and relevant schedule references.
• Review / gap: Intake and review status, missing evidence, priority rationale, and linked issue ID where needed.
• Owner / next action: Responsible reviewer, specific action, and follow-up date.

Keep “not supplied,” “seller reports none,” “restricted,” and “not applicable” separate. An absent document has no document ID until supplied; record its request ID and gap against the relevant family or in a clearly labeled request-only row.

Step by step

1. Fix the transaction perimeter and index conventions

Create a reference list of acquired entities, sellers, relevant affiliates, and excluded businesses. Use full legal names and record former names or aliases. Distinguish direct acquisition of target shares from indirect acquisition of subsidiary interests.

Choose an ID sequence such as D-0001 without encoding conclusions that may change. Establish category and status terms before indexing. A software business requires different contract categories from a regulated manufacturer; both need ownership records tied to the correct entity.

Record: Entity and category for every row. Mark uncertain affiliations “entity unresolved” and assign clarification rather than guessing.

2. Preserve provenance before reorganizing files

Capture original filenames, paths, receipt batches, and available upload information. Keep upload dates separate from document dates: a new upload may contain an old agreement.

Do not silently replace a file when the seller provides a cleaner or signed copy. Give each distinct version a row, link it to its predecessor, and identify the review version. Preserve index history for removed files without retaining content contrary to applicable access restrictions or agreed protocols.

Record: Source location and receipt information in the source field; predecessor and successor IDs in the family field. Retain the baseline inventory outside the editable master.

3. Inspect identity, completeness, and execution evidence

Open source files rather than relying on filenames. Check titles, parties, dates, page sequence, readability, signatures, and referenced attachments. Confirm whether a file called “executed” actually includes signatures and whether it contains all apparent counterparts.

An apparently signed copy does not establish authority, effectiveness, or completeness. Record visible evidence. If effectiveness depends on another event, identify that dependency rather than assuming a date.

Distinguish identical duplicates from differently signed copies, changed text, and incomplete scans. Preserve duplicate source paths even where only one copy receives substantive review.

Record: Document identity, apparent execution status, version, and specific missing pages or attachments. Label unreadable material for replacement.

4. Connect ownership records and agreement families

Link each base agreement to amendments, side letters, joinders, waivers, and relevant notices. Identify the apparent operative set for reviewer confirmation; do not assume that the latest-dated document replaces everything earlier.

For ownership, connect the ledger with capitalization tables, issuance approvals, certificates, and transfers. Delaware’s stock-ledger definition includes record holders, addresses, registered share amounts, and recorded issuances and transfers. It is not a statutory assurance of clean title or complete beneficial-ownership information (DGCL § 219(c)). (delcode.delaware.gov)

Record: Related IDs and the agreement or ownership family. Identify chronological inconsistencies, unmatched issuances, and missing transfer evidence without resolving them through indexing alone.

5. Reconcile the collection against buyer requests

Map documents to the requests they answer, then work backward through every request. Identify unanswered categories, partial responses, and assertions unsupported by files. One populated folder cannot establish completeness across all subsidiaries or periods.

Keep access-limited responses visible without reproducing protected substance. The AMD–ZT agreement illustrates negotiated preclosing access subject to confidentiality, law, and privilege limitations, with provisions addressing alternative access. It does not establish a general buyer inspection entitlement (§ 7.2). (sec.gov) Ask deal counsel which access arrangements the actual transaction permits.

Record: Request IDs, precise remaining gaps, access restrictions, response source and date, and a follow-up owner. Close administrative requests separately from substantive review questions.

6. Route review and preserve the distinction between evidence and conclusions

Assign ownership records to corporate counsel and other categories to appropriate specialists. Prioritize evidence affecting the acquisition perimeter, selling holders, essential business dependencies, or potential consent requirements. Keep received, indexed, assigned, and reviewed as separate statuses.

Where transfer restrictions matter, collect the charter, bylaws, shareholder agreements, certificates, notices, and adoption records together. Delaware § 202 addresses notice or actual knowledge and restrictions adopted after issuance; absence of a legend alone does not establish unrestricted transferability (DGCL § 202(a)–(b)). (delcode.delaware.gov)

Record: Reviewer, priority reason, unresolved dependencies, and a findings-tracker issue ID. Keep substantive legal analysis in that tracker rather than reducing it to “OK” in the index.

7. Reconcile updates and issue a controlled snapshot

At each reporting cutoff, compare the repository with the preserved inventory. Identify new files, changed versions, relocated paths, and unanswered follow-ups. Reopen affected families when later documents could change earlier review.

Cross-reference draft representations and schedules without equating availability with contractual disclosure. The Booz Allen Hamilton–PAR agreement separately addresses complete copies of written Material Contracts and cross-disclosure where relevance is reasonably apparent on the disclosure’s face. Those are negotiated terms, not universal effects of uploading documents (§§ 5.14(b), 10.9). (sec.gov)

Record: Updated status, superseded versions, linked findings, and unresolved actions. Put the snapshot cutoff and index version in the working document header; preserve earlier snapshots.

Worked example

Fictional scenario: Alder Quay Holdings proposes to acquire all shares of Juniper Signal Systems, Inc., a Delaware corporation, for $46 million. Its wholly owned subsidiary, Juniper Signal Operations, Inc., supplies monitoring software. The seller uploads a capitalization spreadsheet, a customer agreement labeled “final,” and a partially signed shareholder agreement.

The spreadsheet lists four holders, but no ledger has been supplied. The customer agreement refers to a missing amendment and pricing schedule. The shareholder agreement contains transfer-consent wording, but the copy lacks some signatures. All parties, documents, amounts, dates, and references in this example are fictional.

The index changes review priorities without inventing conclusions. Corporate counsel cannot reconcile ownership from the spreadsheet alone. Commercial counsel can begin reviewing the base agreement but should leave pricing analysis open. The partial shareholder agreement warrants further evidence, not an assumption that every holder is bound or that consent is necessarily required.

When missing documents arrive, give them IDs and link them to these families. Until then, keep the gaps open; neither the proposed price nor the seller’s folder labels resolve them.

Common mistakes

• Adopting the seller’s folders as the buyer’s classification. Organize by actual entity and review category while retaining original paths.
• Closing requests after receiving one responsive file. Check coverage across entities, periods, amendments, and attachments.
• Overwriting unsigned copies with signed versions. Preserve both versions and check whether the substantive text changed.
• Treating assignment and change of control as interchangeable. Locate each relevant provision separately and route interpretation to counsel.
• Using “reviewed” to mean “cleared.” Separate review completion from missing evidence, findings, and commercial risk acceptance.
• Including protected substance in a broadly shared index. Record restricted availability and the authorized owner without exposing the content.

Final quality check

• Every document version has a stable ID and reproducible source location.
• Entity names match the acquisition perimeter; uncertain affiliations have owners.
• Document dates, receipt dates, execution status, and effectiveness uncertainty are distinguishable.
• Agreement families link known amendments, attachments, side letters, and replacement versions.
• Ownership entries identify reconciliation gaps rather than imply a capitalization table proves title.
• Every request maps to evidence or an explicit missing, restricted, seller-reported-none, or inapplicable response.
• Pinpoints and descriptions match source files; legal references retain jurisdictional and contractual limits.
• Open issues are resolved with evidence or explicitly assigned; the snapshot version and cutoff are visible.

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 collections and prioritize human review; tabular review supports work across multiple documents. Use these capabilities to support the index, while reviewers verify identity, versions, relationships, and gaps against source files. The index remains the team’s work product, and legal judgment remains with counsel. To discuss this workflow, book a demo.

Frequently asked questions

Does every data-room file need a separate row?

Every distinct document version should be traceable. Identical duplicates can share a review record if their source paths remain recorded. Combined PDFs may require several rows with page ranges for independent instruments.

How should we index selling-shareholder documents?

Identify the holder and link the document to the relevant target equity. Do not exclude it merely because the target is not a party. Include holder agreements, transfer records, and waivers in the ownership family.

What if the seller says a document does not exist?

Record who responded, when, and precisely what was said. Distinguish that response from nonproduction. Ask the responsible reviewer whether alternative evidence is needed before closing the underlying diligence question.

Should disclosure-schedule references appear in the index?

Yes, where available. Preserve the schedule version and precise reference alongside request or findings IDs. This helps locate evidence; whether disclosure satisfies the purchase agreement remains a separate interpretive question.

Sources

• Delaware Code, Title 8, § 219(c): stock-ledger definition.
• Delaware Code, Title 8, § 202: transfer restrictions.
• AMD–ZT Group Stock Purchase Agreement, § 7.2: negotiated information access.
• Booz Allen Hamilton–PAR Stock Purchase Agreement, §§ 5.14(b), 10.9: contract copies and cross-disclosure.

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.