How to prepare a document collection checklist for Fiduciary Duty Disputes

Prepare the checklist around the challenged corporate decision, not simply around custodians’ email accounts. Identify who proposed, evaluated, approved, and implemented the decision; map their records to alleged conflicts, information gaps, and approval defects; then assign collection methods and owners. The resulting deliverable connects each evidence category to a repository, date range, collection status, and unresolved question. It distinguishes records collected from records merely identified and preserves source references for later review. Counsel should approve the scope and expressly resolve or assign remaining gaps.

When to use this workflow

Use this workflow when litigation counsel or an in-house team must organize collection concerning alleged self-dealing, diverted opportunities, conflicted compensation, misuse of corporate assets, or a disputed sale process. Triggers include a complaint, a document request, or an internal assessment identifying a challenged board decision.

The scope is collection planning and verification—not deciding liability or completing production. Start with applicable preservation instructions; the checklist does not replace them. Confirm whom counsel represents before seeking records from directors, officers, or separately represented participants.

This guide uses a US orientation. Federal district-court discovery reaches nonprivileged matter relevant to claims or defenses and proportional to the case’s needs; relevance alone does not settle scope. State proceedings and arbitration require separate procedural analysis. See Federal Rule of Civil Procedure 26(b)(1). Confirm entity type, governing law, forum, orders, and transaction dates before setting collection priorities.

What you need

Assemble these inputs before assigning collection work:

• Dispute definition: pleadings or allegations, challenged decisions, defendants, relevant periods, and counsel’s preliminary evidence questions.
• Governance records: certificate, bylaws or operating agreement, board and committee membership, delegated authority, and committee mandates.
• Decision materials: agendas, board packs, minutes, consents, valuations, adviser presentations, transaction drafts, and implementation records.
• People and relationships: directors, officers, controlling owners, advisers, assistants, and alleged financial, employment, familial, or advisory connections.
• Systems information: board portals, committee workspaces, email, messaging, calendars, shared drives, devices, retention settings, and former-user access.
• Collection constraints: preservation instructions, discovery requests, agreed scope, protective orders, privilege protocols, and third-party repositories.

Distinguish record creation from custody. An assistant may retain circulated materials while a finance analyst holds the model underlying the presentation. Identify both, rather than assuming the board’s records contain every relevant input.

Use the template

The companion template is Fiduciary Duty Disputes — Document collection checklist. You can copy this table into your working document or spreadsheet. Use one row for a distinct evidence category and source; split rows when methods, owners, or statuses differ.

Give each row a stable identifier, such as FC-01. Name the disputed decision or relationship in ID / issue. Period / versions should specify collection boundaries and required revisions; distinguish event dates from creation and circulation dates where material.

Collection plan records the method and links to approved scope, access decisions, and the collection manifest. Evidence / gap records collection references and, once available, document IDs with page, clause, sheet, or cell citations. Keep detailed file inventories in the manifest rather than overloading the checklist.

Use consistent statuses: identified, awaiting scope decision, scheduled, collected, verified, or blocked. Add “partial” where necessary. “Verified” means checked against approved collection scope—not proof that every relevant record exists or that materials are production-ready. Each open row needs an owner, next action, and target date in that final field or a linked task record.

Step by step

1. Define the decisions and evidence questions

Break the dispute into proposal, information gathering, alternatives, conflict disclosure, deliberation, approval, and implementation. For each stage, identify records that could support or contradict the allegation.

For a related-party asset sale, separate the buyer’s relationship with an officer from pricing, disclosure, recusals, and authorization. Do not combine those questions into “sale documents.” For a diverted opportunity, identify when the opportunity arose, who received it, and records of corporate consideration or rejection. Counsel should separately assess governing duties, defenses, and remedies.

Record the decision, evidence question, records sought, and preliminary period. Explain date boundaries in a linked scope note, including earlier relationship evidence or later implementation records. Avoid defining scope solely through documents expected to favor the client.

2. Map people to repositories and access

Interview the corporate secretary, relevant business personnel, and systems staff about where records were created, circulated, and retained. Ask specifically about board-portal annotations, committee-only workspaces, personal business messaging, calendar attachments, adviser exchanges, and departed directors’ accounts.

Identify repository ownership and access separately from the custodian’s name. Possession of an adviser’s presentation does not establish access to its underlying files. Refer third-party and personal-account questions to counsel rather than treating every source as available for collection.

Record custodian, repository, access owner, relevant retention settings, and access questions in the row or linked source inventory. Flag fragile sources for prompt preservation and collection decisions without assuming discoverability. Distinguish inaccessible accounts from accounts searched without locating records.

3. Build the approval and conflict record categories

Collect more than final minutes. Identify agendas, circulated packs, versions, attendance records, recusals, votes, committee mandates, conflict questionnaires, disclosure communications, and written consents. Map each alleged relationship to a person and decision date; seek records showing who received the disclosure, not merely that someone drafted it.

For a Delaware corporation, Section 141(f) generally permits board or committee action without a meeting through all members’ written or electronic consent, unless restricted by the certificate or bylaws, and requires filing consents with the minutes. Collect governing documents and the complete consent record; a signature page alone does not resolve effectiveness. See 8 Del. C. § 141(f).

Record expected sources and missing components. Distinguish announced intentions, authorizations, executed agreements, and completed transactions. Do not use the presence of an approval entry as a substitute for governing-law analysis.

4. Set collection scope and method

Approve custodians, periods, repositories, versions, and file types before execution. For valuation models, identify source spreadsheets and linked inputs; a presentation PDF may omit assumptions or formulas. For messaging, collect sufficient context to understand isolated statements while respecting approved boundaries.

Choose a method with qualified personnel that preserves needed source information. Document exclusions, access limitations, failed attempts, and reasons for narrowing scope. Test search terms against known decision records before relying on them; terms alone do not establish completeness.

Record method, scope approval, responsible collector, and manifest reference. Where a request drives collection, add its identifier. Distinguish records outside collection scope, records not located, and collected records withheld from production. These categories require different follow-up decisions and should not share a generic “excluded” label.

5. Plan privilege and confidentiality handling

Identify likely legal-advice sources, including counsel’s board communications and mixed business/legal threads. Flag participant roles and review attachments separately. Collection into a controlled review environment is different from disclosure to an opponent; apply access restrictions appropriate to the matter.

In federal district court, Rule 26(b)(5)(A) requires express privilege or protection claims and descriptions permitting assessment without revealing protected information. Rule 26(f)(3)(D) includes planning the timing and method of compliance. Neither prescribes a universal spreadsheet. See Federal Rules of Civil Procedure 26(b)(5)(A) and 26(f)(3)(D).

Record review restrictions and the lawyer responsible for unresolved privilege questions. Do not presume every communication involving counsel is privileged or exclude it from collection without an explicit decision. Keep collection status separate from privilege-review status.

6. Verify collection against the decision history

Compare collected records with known events and cross-references. If minutes list four attachments but only three were collected, identify the missing attachment. Reconcile the board pack with distribution records and check whether later versions replaced earlier files.

Check source files, metadata, collection logs, and access failures. Identify people who can explain provenance. Federal Evidence Rule 901 requires sufficient evidence that an item is what its proponent claims; knowledgeable-witness testimony is one authentication method. Authentication does not settle hearsay or other admissibility questions. See Federal Rule of Evidence 901.

Record verified references, discrepancies, and follow-up assignments. Distinguish “not located in this collection” from “never existed.” A missing attachment should trigger source-specific inquiry, not an unsupported conclusion about deletion or concealment.

7. Close or assign every collection gap

Review blocked and partial rows with matter counsel. Decide whether to pursue another source, refine scope, investigate an apparent deletion, seek third-party records, or document a reasoned limitation. Assign one accountable owner to prevent duplicate collection efforts.

For request-linked rows, coordinate the collection record with response drafting. Federal Rule 34 requires specific objection grounds and disclosure of whether responsive materials are withheld on an objection. Its party-request provisions do not replace separate subpoena analysis. See Federal Rule of Civil Procedure 34(b)(2)(B)–(C).

Record final status, remaining uncertainty, responsible lawyer, and next action. Identify the source of any target date—order, agreement, or internal decision. Retain prior dispositions when reopening a row so that later reviewers can understand what changed.

Worked example

Fictional scenario: Harbor Lantern Systems, Inc., a Delaware corporation, sold a product line to Cedar Basin Holdings for $18 million. A stockholder alleges that Harbor Lantern’s chief executive held an undisclosed interest in the buyer and that directors approved the sale using an outdated valuation. All parties, amounts, documents, and references below are fictional.

Counsel receives signed minutes, a presentation, and the executed agreement. The minutes list two valuation attachments, but the collection contains one. A secretary’s distribution email mentions a revised model. The presentation reports management’s statement that there were no relevant conflicts. The model’s contents and directors’ receipt remain unverified; the presentation does not establish the statement’s accuracy.

These entries change the immediate priority from treating collection as complete to targeted follow-up. Counsel seeks the revised model, the basis for the conflict statement, and evidence of circulation. FC-01 and FC-03 remain separate because locating a model does not establish that directors received it. The checklist neither invents missing evidence nor infers concealment, unfair pricing, or defective approval from collection gaps.

Common mistakes

• Collecting only final board packs. Seek circulation records and relevant versions to establish what decision-makers received.
• Using identical periods for every issue. Relationship evidence may precede the transaction; document separate boundaries.
• Treating corporate email as exhaustive. Investigate portals, messaging, adviser files, and calendars before closing source mapping.
• Equating counsel’s involvement with privilege. Assign mixed-purpose threads and attachments for individualized legal review.
• Marking received files as complete. Reconcile attachments, cross-references, and collection failures before verification.
• Closing gaps without reasons. Record the limitation, approving lawyer, and any remaining follow-up rather than silently removing the row.

Final quality check

• Each row identifies a challenged decision or specific evidence question.
• Custodians, repositories, ownership, and access limitations are recorded.
• Date ranges and version requirements have documented reasons.
• Collected files are traceable to source and collection manifests.
• Document citations, formulas where relevant, and attachment counts have been checked against originals.
• Privilege-sensitive material has an assigned review path distinct from collection status.
• Every gap is resolved, expressly limited, or assigned to an owner and next action.
• Governing sources, forum requirements, and applicable orders have been verified for the matter.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, chronology, and evidence analysis capabilities can support examination of collected decision records and follow-up questions. The checklist remains counsel’s work product; collection scope and legal conclusions remain counsel’s decisions. Explore trial preparation and the chronology viewer, or book a demo to discuss reviewing this collection.

Frequently asked questions

Should every director be a custodian?

Assess participation, communications, and unique records. Document inclusion or exclusion reasons. A shared board pack does not establish that directors’ annotations or separate exchanges are duplicative.

How should personal messaging be handled?

Identify business use, account ownership, relevant periods, retention settings, and access questions. Counsel should determine appropriate scope and method before collection proceeds; do not direct an unrestricted search of personal content.

Does a missing consent establish defective approval?

No. Seek the complete consent, governing documents, and related records. Distinguish failure to locate a document from its absence, and refer effectiveness to counsel’s governing-law analysis.

When is the checklist complete?

When approved collection tasks are verified and every limitation has an explicit disposition or assigned follow-up. A checklist with open follow-up is ready for handoff, not an unqualified declaration of completed collection. Privilege review and production readiness remain separate.

Sources

• Federal Rules of Civil Procedure: Rules 26 and 34; December 1, 2025 edition.
• Federal Rules of Evidence: Rule 901.
• Delaware General Corporation Law, Chapter 1, Subchapter IV: Section 141(f).

This general workflow guide uses the supplied research as of October 13, 2026. Federal procedure and evidence provisions are not automatically applicable in state proceedings or arbitration; the Delaware example concerns Delaware corporations.

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.