How to build a discovery request and response tracker for Shareholder Derivative Matters

Build the tracker around individual discovery obligations, not production batches. Give each request a stable identifier, connect it to a derivative-action issue, and record the response, objections, withholding position, production references, unresolved gaps, and responsible lawyer. Separate stockholder inspection materials from litigation discovery and distinguish litigation-demand records from merits evidence. The resulting deliverable should show what was requested, what was promised, what was supplied, and what remains unresolved—with traceable support for each material status, deadline, and closure decision.

When to use this workflow

Use this workflow when litigation counsel or an in-house team serves or receives document requests concerning challenged board conduct, director conflicts, ownership, litigation demands, or committee investigations. Begin when requests are finalized or first received. Requesting counsel uses it to assess responses and deficiencies; responding counsel uses it to reconcile commitments with collection, review, and production.

Keep the tracker focused on document discovery, not the entire case. Record the forum, incorporation jurisdiction, procedural posture, and operative orders before assigning obligations. The federal rules discussed here concern federal proceedings; check state-court or arbitral requirements separately. Delaware statutory references concern Delaware corporations, not every entity. Record whether discovery is authorized, limited, stayed, or disputed rather than assuming that an issue’s importance makes it presently discoverable.

What you need

Assemble a controlled source set:

• Operative pleadings identifying challenged transactions, ownership allegations, and the demand or demand-futility position.
• Served requests, service evidence, signed responses, amendments, definitions, and attachments.
• Orders, stipulations, and correspondence establishing scope, response dates, production commitments, and privilege-description arrangements.
• Stockholder inspection demands and productions, separated from litigation demands and litigation discovery.
• Board and committee rosters by date, governing documents, meeting packets, minutes, consents, and available investigation records.
• Custodian and repository information covering board portals, email, messaging, advisers, and potentially relevant personal-device business records.
• Production manifests, Bates ranges, redaction records, privilege descriptions, and prior deficiency correspondence.

Assign document IDs to materials without Bates numbers. Preserve original identifiers alongside later production numbers. Identify the actual responding party: the corporation, an individual director, and a committee may require separate records and counsel decisions.

Use the template

The Shareholder Derivative Matters — Discovery response tracker is a working template. Copy this table into your working document or spreadsheet. Use one row per request; add linked child rows when custodians, periods, or separate commitments require different outcomes.

Identify the serving and responding parties, request set, number, and source page. The issue field distinguishes ownership, demand, independence, challenged approval, causation, and loss; an issue tag is not a discoverability conclusion.

Separate objections, narrowed commitments, and withholding positions. In the dates field, distinguish service, response deadlines, production commitments, internal targets, and completed events. Give each material date a source and verifier; link to a controlled date log if necessary.

Production citations should identify the batch, Bates range, and exact pages assessed. Record each gap as an answerable question with one accountable owner. Use distinct statuses—response served, production received, review pending, deficiency open, and resolved—rather than an unexplained “complete.” Link lengthy collection or privilege notes instead of overcrowding cells.

Step by step

1. Establish the procedural boundary and request register

Create a matter-level note identifying applicable orders and current discovery limits. Enter each request’s exact text or link to its source, including incorporated definitions. Preserve amendments and superseded positions rather than overwriting them.

Keep inspection requests in a separate series. Delaware Section 220 conditions stockholder inspection on requirements including proper purpose and particularity; inspection is distinct from plenary discovery and a litigation demand. Check the full statute, record categories, and applicable transition provisions before characterizing an inspection obligation. See 8 Del. C. § 220.

Record: stable IDs, parties, source pages, request type, and scope restrictions. Cross-reference inspection records where a litigation request seeks overlapping materials.

2. Connect requests to derivative-action issues

Identify the proposition each request addresses. Director communications may concern independence, information received before approval, or handling of a litigation demand. Each purpose may require different custodians and periods. Identify the relevant board at the relevant time rather than using the current roster indiscriminately.

Federal Rule 23.1(b) addresses verification, ownership allegations, and particularized demand allegations; it does not supply the substantive demand-futility test. Rule 26(b)(1) limits discovery to nonprivileged, relevant, proportional matter. Keep those procedural questions separate from governing corporate-law analysis. See Federal Rules of Civil Procedure 23.1 and 26.

Record: issue, period, scope rationale, and any decision needed from counsel. Do not tag every board record as relevant merely because directors are defendants.

3. Map record holders and approval mechanisms

Identify likely custodians, repositories, and expected record types. Separate corporate repositories from individual directors’ records and outside advisers’ files. Flag access and control questions for counsel rather than assuming every identified source can be collected by the responding party.

For challenged approvals, look beyond minutes. Delaware Section 141(f) generally permits board or committee action through all members’ written or electronic consent, subject to certificate or bylaw restrictions, with consents filed with the minutes. This approval mechanism does not establish compliance with fiduciary duties. See 8 Del. C. § 141(f).

Record: custodians, systems, expected materials, and collection uncertainties. Write “consent not located in reviewed materials,” not “approval never occurred.”

4. Capture responses, objections, and verified dates

Read each response against the request. Distinguish an objection, an agreement to produce, a proposed narrowing, and a statement that no responsive materials were located. Link later agreements to their correspondence and preserve the original position.

Federal Rule 34(b)(2)(C) requires objections to state whether responsive materials are withheld. Flag an unclear withholding position rather than filling the gap by inference. See Federal Rule of Civil Procedure 34.

Label dates as legal deadlines, agreed commitments, proposals, internal targets, or completed events. Counsel should verify deadlines against applicable procedure, service facts, orders, and agreements. An internal follow-up date cannot substitute for an unresolved response deadline.

Record: response position, withholding statement, date category, source, verifier, and ambiguity requiring clarification.

5. Reconcile production against the commitment

Compare received materials with both the request and the operative commitment. A Bates range proves receipt, not completeness. Check board-packet attachments, referenced presentations, relevant versions, and links between approval and implementation. Identify which materials came from inspection and which arrived through litigation production.

Separate collection gaps from withheld materials. Rule 26(b)(5)(A) requires express privilege claims and descriptions enabling assessment without revealing protected information; Rule 26(f)(3)(D) addresses compliance timing and method. These provisions do not establish substantive privilege. See Federal Rule of Civil Procedure 26.

Record: production references, reviewed pages, missing categories, privilege-description references, and review limits. Escalate mixed business/legal communications for analysis rather than treating counsel’s participation as dispositive.

6. Turn deficiencies into answerable actions

Describe each deficiency narrowly. Instead of “board production incomplete,” write: “Minutes identify Appendix B; attachment not located in cited production. Confirm whether produced elsewhere, withheld, or not located.”

Separate administrative reconciliation from substantive disagreement. An incorrect Bates reference needs clarification; a disputed period requires a scope decision. Preserve the deficiency and append the response. Requesting counsel should identify supporting evidence and requested clarification. Responding counsel should link the inquiry to the collection or review decision requiring verification.

Record: deficiency, supporting citation, requested resolution, owner, target date, and correspondence reference. Distinguish a proposed escalation from an authorized procedural step.

7. Close obligations with evidence and preserve open work

Review each row before closure. Resolution may mean verified production, counsel’s acceptance of a limitation, or an identified order deciding the dispute. Keep these outcomes distinct. Link later production to the original request and deficiency rather than creating an unconnected batch entry.

Retain qualifications, including unsearched repositories and disputed withholding. Include supplementation questions in periodic review; do not assume the final scheduled batch settles them. Restrict sensitive internal assessments separately from any operational tracker shared outside the legal team.

Record: closure basis, approving lawyer, supporting source, and remaining assigned action. Generate an open-issues list from unresolved rows for the next team discussion.

Worked example

Fictional scenario: A federal derivative action concerns Mariner Orchard Corporation, a fictional Delaware corporation, and an equipment purchase from a director-affiliated seller. A fictional order permits specified approval and litigation-demand discovery. All parties, documents, dates, and identifiers below are fictional.

The corporation previously supplied inspection records. Its litigation production includes minutes, a partial transaction folder, and a demand-response letter. Requesting counsel must distinguish supported deficiencies from assumptions about missing evidence. The dates below are documented events or commitments, not statements of generally applicable deadlines.

The first entry justifies an attachment-specific inquiry, not a demand to reproduce every board record. The second calls for search verification, not an allegation of unauthorized action. The third requires separate evaluation of privilege descriptions and timing. None supports closure merely because documents concerning the right subject were produced.

Common mistakes

• Combining inspection and discovery status. Preserve separate obligations and provenance; cross-reference overlap without assuming identical scope.
• Using one board custodian. Identify directors, committees, secretarial records, and repositories by relevant period.
• Treating objections as production explanations. Capture the actual withholding position and flag ambiguity.
• Equating missing records with missing conduct. Identify the reviewed universe and investigate the search gap before drawing conclusions.
• Closing requests on batch receipt. Compare the production with commitments, attachments, and unresolved qualifications first.

Final quality check

• Each request has stable identifiers, parties, and an exact source reference.
• Forum, permitted scope, and operative orders are recorded.
• Inspection, litigation-demand, and discovery records remain distinguishable.
• Dates have verified sources and clearly labeled categories.
• Objections, withholding, and narrowed commitments are separately captured.
• Production citations resolve to the correct documents and pages.
• Legal sources and applicable versions have been checked against the matter’s dates.
• Every open issue has an owner; every closure has supporting evidence and approval.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its litigation capabilities include document review, privilege and confidentiality analysis, redaction, and production. Use those capabilities to support underlying document review while maintaining this tracker as counsel’s work product. Linked records can also support deposition preparation. Counsel retains responsibility for scope, privilege, dates, and closure decisions. To discuss this discovery-review workflow, book a demo.

Frequently asked questions

Should demand-futility and merits requests share a tracker?

They can share a register, with separate issue tags and scope notes. Record any order limiting discovery. Shared subject matter does not establish that discovery for both purposes is authorized.

How should earlier Section 220 productions be recorded?

Preserve their inspection origin, original identifiers, and later Bates references. Link them to litigation requests, then assess whether they satisfy the operative commitment. Prior receipt alone does not establish resolution.

What if a response promises documents without a production date?

Record the commitment and mark timing unresolved. Assign counsel to seek clarification and verify the applicable obligation. Keep any internal follow-up target separate from the production date.

Should the tracker contain privileged internal analysis?

Separate operational fields from restricted assessments. Use controlled references for sensitive notes and have counsel determine access and circulation. Do not assume a privilege label establishes protection.

Sources

• Federal Rules of Civil Procedure: Rules 23.1, 26, and 34.
• Delaware General Corporation Law § 220: stockholder inspection.
• Delaware General Corporation Law § 141(f): board and committee consents.

This is a general professional workflow, not advice for a particular matter; apply the governing law, source versions, and case-specific orders.

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.