How to prepare a document collection checklist for Shareholder Derivative Matters

Prepare the checklist by separating ownership, litigation demand, board decision-making, conflicts, and alleged corporate harm into distinct collection issues. For each issue, identify custodians, repositories, relevant periods, records sought, collection authority, and unresolved gaps. Keep books-and-records inspection separate from litigation demand and plenary discovery. The resulting deliverable should show what counsel needs, what has actually been collected, where each item originated, and who must resolve missing or restricted material—not merely list documents that might exist.

When to use this workflow

Use this workflow when litigation counsel or an in-house team must scope an initial collection, assess an inherited production, or investigate gaps concerning a challenged corporate decision. Counsel for a stockholder, the corporation, and individual defendants can use the same structure, but should not assume the same access to corporate records.

Identify the forum, incorporation jurisdiction, procedural posture, and applicable orders first. The federal rules discussed below concern federal proceedings; the Delaware authorities concern Delaware corporations. Verify applicable versions, transition provisions, local requirements, and later decisions against the matter’s dates. The collection recommendations are practical methods, not independent legal requirements.

Keep three channels distinct: stockholder inspection, a demand that the corporation pursue litigation, and discovery in an action. Delaware Section 220(b)(2) conditions inspection on good faith, proper purpose, reasonable particularity, and records specifically related to the stated purpose. The statute also addresses record categories and additional conditions; an inspection demand does not authorize unrestricted discovery. See 8 Del. C. § 220.

What you need

Assemble the materials that define collection scope before issuing instructions:

• Matter framework: complaint or draft allegations, challenged transactions, incorporation jurisdiction, relevant orders, and existing discovery requests or inspection demands.
• Ownership evidence: account statements, acquisition confirmations, transfer records, and records covering relevant holding periods.
• Demand history: litigation demand, attachments, delivery evidence, acknowledgments, responses, and separately identified inspection correspondence.
• Governance records: relevant charter and bylaw versions, board rosters, committee membership, delegations, meeting calendars, and adviser engagements.
• Transaction and harm records: agreements, valuations, approval materials, payment records, accounting entries, and records supporting or contradicting alleged corporate loss.
• Collection information: system inventories, retention settings, custodian interviews, prior exports, collection logs, access restrictions, and known missing attachments.

In federal proceedings, Rule 23.1(b) requires a verified complaint, contemporaneous ownership allegations subject to its operation-of-law exception, a noncollusion allegation, and particularized allegations concerning demand efforts and reasons for not obtaining action or making the effort. These pleading requirements inform collection priorities; they do not supply the substantive demand-futility test. See Federal Rule of Civil Procedure 23.1(b).

Use the template

The companion template is Shareholder Derivative Matters — Document collection checklist. You can copy this table into your working document or spreadsheet. Use one row for each issue-and-source combination; split rows when custodians, restrictions, or collection status differ.

“Scope basis” identifies the request number, inspection purpose, allegation, or approved internal instruction, including access restrictions. It records why the team seeks the material, not an assumed entitlement to obtain it.

“Evidence / citation” identifies the collection receipt and, after verification, the document ID, version, page, or Bates reference. “Status / gap” distinguishes requested, received but unchecked, verified, partially collected, unavailable, and restricted pending review. “Owner / next action” assigns a named person, concrete follow-up, and an internal target date where appropriate. Keep technical details in a linked collection log referenced by row ID.

Step by step

1. Define the collection question and authorized scope

Write a scope statement identifying the client, challenged conduct, procedural posture, and records counsel may presently obtain. Separate client-held records from materials requiring another party’s cooperation or a formal request. Resolve access questions before collecting personal-account or adviser files.

In federal discovery, Rule 26(b)(1) limits scope to nonprivileged matter relevant to a claim or defense and proportional to the case’s needs. Applicable orders also matter. Use that framework to test breadth rather than defaulting to every director’s entire mailbox. See Federal Rule of Civil Procedure 26(b)(1).

Choose periods by issue: transaction development, approval, implementation, ownership, and demand handling may require different windows.

Record: the issue, scope basis, approved period, and unresolved access restrictions.

2. Separate ownership, demand, and merits records

Create distinct rows for ownership evidence, inspection correspondence, litigation demand, the challenged act, and alleged corporate loss. Preserve attachments and delivery records with the relevant correspondence rather than combining everything under “demand documents.”

If litigation demand was made, identify the response and available records concerning its handling, subject to authorized scope and protection review. If not, identify the board whose ability to consider demand counsel must assess. Do not infer either posture from an ambiguous email.

For harm, distinguish the amount paid from the alleged loss. Seek the transaction terms, valuation inputs, performance records, and contrary evidence counsel needs to assess that distinction.

Record: separate issue IDs, document families, and missing links, such as “demand attachment referenced but not received.”

3. Map directors and decision authority to sources

Build a director-by-director source map. Include relevant officers, committee members, the corporate secretary, advisers, and portal administrators. Identify historical membership rather than relying exclusively on the current board roster.

For Delaware demand futility, Zuckerberg asks whether each director received a material personal benefit, faces a substantial likelihood of liability, or lacks independence from someone receiving that benefit or facing that liability. Demand is excused when at least half the demand board meets any prong. This is not the demand-refusal standard. See United Food & Commercial Workers Union v. Zuckerberg, pp. 40–41.

Seek underlying relationship and transaction records, not labels such as “conflicted director.” Keep collection leads separate from counsel’s legal conclusions.

Record: director-specific sources, relevant roster dates, issue connections, and unresolved relationship questions.

4. Trace approval from preparation to implementation

Identify meeting notices, agendas, distributed packages, supplemental materials, minutes, votes, recusals, delegations, and implementation instructions. Distinguish drafts from final versions and establish which version reached decision-makers.

Do not stop at minutes. Delaware 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; the consents must be filed with the proceedings’ minutes. That approval mechanism does not establish the underlying transaction’s fiduciary propriety. See 8 Del. C. § 141(f).

Record: governing-document versions, approval records, distribution evidence, and gaps between approval and implementation. Missing minutes are a collection question, not proof that approval never occurred.

5. Confirm repositories, preservation concerns, and collection method

Ask concrete custodian questions: Where were advance materials received? Were comments made in the portal or separate messages? Were business records retained on personal devices? Which assistants or administrators kept copies?

Ask the technical team to document source identifiers, available versions, attachments, message context, collection dates, and method. Do not assume a portal download includes annotations or prior versions. Preserve original receipts and record processing exceptions in the linked log.

Escalate deletion settings, inaccessible archives, departing custodians, and discontinued systems promptly. Source mapping can expose preservation concerns, but completing a checklist does not establish that preservation is adequate.

Record: repository inventory, approved collection method, receipt references, limitations, and owners for follow-up.

6. Reconcile receipts and route protected material

Compare receipts with the requested scope. Check date boundaries, attachment families, board-package versions, and unexplained gaps. Separate “not collected,” “collected but restricted,” and “reviewed with no responsive record located.” None establishes that a record never existed.

Route mixed business/legal communications and investigation files for assessment rather than classifying them solely by counsel’s participation. Record participants’ roles and the asserted protection without exposing sensitive substance in a broadly circulated checklist.

In federal proceedings, Rule 26(b)(5)(A) requires express protection claims and descriptions permitting assessment without revealing protected information. Rule 34(b)(2)(C) requires objections to state whether responsive materials are withheld on that basis. See Federal Rules of Civil Procedure 26 and 34. The checklist is neither a privilege log nor a discovery response.

Record: verified receipt status, restrictions, discrepancies, and the responsible reviewer.

7. Close each row with evidence or an assigned exception

Have a second reviewer spot-check important citations and source descriptions. Prioritize ownership, demand delivery, board composition, approval versions, and alleged corporate harm.

Close a row only against its defined scope. For incomplete collection, identify the missing source, why it matters, proposed follow-up, and decision-maker. An acceptable exception might explain that a repository remains inaccessible and further collection awaits counsel’s scope decision; it should not disguise the row as complete.

Preserve status history when scope changes. A later reviewer should understand why a source was added, narrowed, or excluded.

Record: verified completion or an explicit exception with an owner and next review point.

Worked example

Fictional scenario: Counsel for stockholder Larch Harbor Fund is assessing gaps concerning a $24 million asset purchase by Delaware corporation Meridian Beacon Systems. The fund alleges that a director had an interest in the seller. No litigation demand has been made. Counsel has a limited inspection production, client-held ownership statements, and public board information, but no access to directors’ email or the board portal.

All parties, documents, amounts, identifiers, and events below are fictional. These are three representative entries, not the entire collection plan.

The checklist changes the immediate decision from “collect all board email” to three targeted actions. Counsel seeks client-controlled acquisition evidence, investigates the missing consent through the available inspection channel, and defines director-specific gaps. The seller affiliation supplies a lead, not a completed demand-futility analysis. Counsel must separately add valuation and loss-source rows; neither the purchase price nor these entries establishes corporate harm. Nothing supplied establishes what uncollected portal records contain.

Common mistakes

• Combining all demands. Separate inspection and litigation demands, with their own attachments, delivery evidence, responses, and scope references.
• Using only today’s board roster. Identify relevant historical membership and assign unresolved dates for verification.
• Collecting minutes alone. Trace distributed materials, consents, delegations, and the versions decision-makers received.
• Closing a repository when files arrive. Reconcile custodians, periods, attachments, and technical limitations first.
• Treating restricted material as missing. Track collection and protection-review status separately, with controlled access.

Final quality check

• Every row connects to ownership, demand, challenged conduct, a defense, or alleged corporate harm.
• Inspection, litigation demand, and discovery have distinct scope references.
• Director and committee identities match relevant dates.
• Citations identify the correct document, version, and page; receipts remain traceable.
• Relevant portal, messaging, adviser, and personal-device business sources have been considered.
• Missing records, restricted records, and negative search results are distinguished.
• Each open issue is resolved or expressly assigned; counsel has checked controlling sources, applicable versions, and orders before relying on legal assumptions.

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 assessment of collected derivative-matter records. A chronology view can help organize events; the checklist remains the team’s work product. Lawyers retain responsibility for collection authority, completeness, protection decisions, and legal significance. To discuss this workflow, book a demo.

Frequently asked questions

Should collection wait until counsel settles the demand position?

Not necessarily. Identify sources and assess preservation concerns while counsel evaluates demand. Approve collection authority and scope separately; uncertainty does not justify unrestricted access.

Can an inspection production close the checklist?

Only for rows whose defined scope has been satisfied. Record production limitations and unresolved sources rather than equating inspection with complete discovery.

How should board investigation records be listed?

Separate investigative authority, participants, materials reviewed, communications, and reports. Assign access and protection review without assuming everything is protected or obtainable.

What if no approval record is found?

Document sources searched, periods, and limitations. Investigate consents and alternate repositories. Report the search result, not a conclusion that approval never occurred.

Sources

• Federal Rules of Civil Procedure: Rules 23.1, 26, and 34.
• Delaware General Corporation Law, Section 220.
• Delaware General Corporation Law, Section 141(f).
• Delaware Supreme Court, United Food & Commercial Workers Union v. Zuckerberg.

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.