How to build a discovery request and response tracker for Fiduciary Duty Disputes

Build the tracker around each document request and the corporate decision it tests—not production batches alone. Link the request to custodians, repositories, responses, objections, withholding statements, production identifiers, and unresolved deficiencies. Add the verified deadline source, responsible lawyer, and next action. The resulting work product should distinguish a served response from completed production and show whether the record addresses conflicts, information supplied to decision-makers, deliberations, and approval. Keep observed gaps separate from conclusions about what occurred or whether anyone breached a duty.

When to use this workflow

Use this workflow when litigation counsel or an in-house team coordinates document requests concerning an allegedly conflicted transaction, diverted corporate opportunity, disputed compensation decision, or defective approval process. It supports requesting and responding counsel; label each request’s direction and parties.

The scope runs from request intake through deficiency resolution, not the entire discovery lifecycle. US federal district-court procedure supplies the baseline; state litigation and arbitration require their own rules and orders. Confirm entity type and substantive law separately. A Delaware corporation’s approval records are not an interchangeable checklist for an LLC. The recommendations below organize counsel’s work; cited rules supply the identified legal requirements.

What you need

Gather operative requests, service evidence, responses, supplements, production correspondence, orders, and documented extensions. Include pleadings and counsel’s issue list to connect requests with disputed decisions without treating allegations as facts.

Assemble these matter-specific inputs:

• Decision map: challenged transaction, actors, decision stages, alleged conflicts, and disputed approvals.
• Source inventory: board portals, committee workspaces, business messaging, calendars, valuation models, adviser files, and associated custodians.
• Governance records: charter, bylaws, committee mandates, agendas, minutes, attendance, recusals, votes, and written consents.
• Review controls: production identifiers, confidentiality restrictions, privilege procedures, search descriptions, and collection exceptions.

Treat the inventory as a list of potential sources to investigate, not a determination that every repository is discoverable.

Use the template

The companion template is Fiduciary Duty Disputes — Discovery response tracker. Copy this table into your working document or spreadsheet. Start with one row per request; create linked subrows when different custodians, objections, or gaps require separate actions.

Use stable IDs such as RFP-07 and RFP-07a, qualified by party and request set where necessary. Cite the operative request paragraph and response page. In Decision / scope, identify the approval stage, period, and issue tested.

Response / withholding separates objections from stated withholding. Production / gaps carries document IDs, Bates ranges, pinpoint references, and unresolved coverage. Due / authority identifies whether a date concerns the response, production, or internal review, with its source and extension history. Status / verification states what someone checked, when, and with what result.

Keep detailed evidence lists and legal analysis in linked working records. References should remain intelligible to a colleague who did not create the row.

Step by step

1. Register requests and verify controlling dates

Enter the request set, parties, direction, service evidence, and operative version. Preserve amended wording and earlier responses rather than overwriting them. Assign counsel to confirm dates against applicable rules, orders, and documented extensions; do not rely on unexplained spreadsheet defaults.

Distinguish response deadlines, agreed production dates, discovery cutoffs, and internal targets. Track any applicable discovery-dispute deadline separately; a production agreement should not silently replace other obligations.

Record: request citation, date category, confirmed date and authority, extension history, and responsible lawyer. Assign unresolved timing questions immediately.

2. Connect requests to the challenged decision

Identify what each request tests: who disclosed an interest, which valuation directors received, whether alternatives were considered, or what was approved. Separate contemporaneous records from later explanations. Split committee formation and final approval into subrows when their sources or gaps differ.

In federal district court, Rule 26(b)(1) permits discovery of nonprivileged matter relevant to claims or defenses and proportional to the case’s needs. Relevance alone does not resolve scope. Apply that framework to disputed periods and repositories using the case’s circumstances. See Rule 26(b)(1). (uscourts.gov)

Record: decision stage, issue, requested period, and scope question for counsel. Preserve the request’s actual breadth rather than silently narrowing it to the reviewer’s preferred theory.

3. Map custodians and repositories

Connect each request to plausible sources. Minutes may describe approval without identifying everything circulated beforehand. A board-portal export may contain the final pack but omit earlier versions or linked attachments. Adviser correspondence and native valuation files may answer different components.

Identify who controlled each source, what searches or collections are documented, and reported limitations. Responding counsel should distinguish identified, collected, reviewed, and produced material. Requesting counsel should label unconfirmed repositories as questions, not established omissions.

Record: custodian, repository, supporting search or collection reference, limitation, and assigned follow-up. “Not located in production” should not become “never existed.”

4. Separate objections, withholding, and commitments

Read each response against the request. Identify narrowed periods, custodian restrictions, subject-matter limitations, and production commitments. For federal party document requests, Rule 34(b)(2)(B)–(C) requires specific objection grounds and a statement whether responsive materials are withheld on an objection. Analyze subpoenas separately. See Rule 34(b)(2). (uscourts.gov)

An objection, promise to produce, and withholding statement are different facts. When their relationship is unclear, formulate a specific clarification question rather than assuming complete production or improper withholding.

Record: response-page citation, objection, stated withholding, production commitment, and clarification sought. Distinguish counsel’s assessment from the responding party’s position.

5. Reconcile production with request components

Map records to each request and subpart. Check relevant document families, attachments, versions, and date coverage. A large Bates range does not establish that every component was addressed.

For approval requests, compare agendas, circulated materials, minutes, attendance, recusals, votes, and consents. Delaware section 141(f) generally allows 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. Review the full provision and governing documents before assessing effectiveness. See 8 Del. C. § 141(f). (delcode.delaware.gov)

Record: production IDs and pinpoints, covered components, inconsistent records, missing components, and the evidence supporting each gap assessment. Keep approval evidence separate from a legal conclusion about approval’s effect.

6. Route privilege questions to controlled review

Use the tracker to identify unresolved privilege work, not reproduce sensitive advice. Link controlled review records where appropriate. Examine mixed business/legal threads, adviser participation, and attachments rather than treating the entire family identically.

Federal Rule 26(b)(5)(A) requires express privilege or protection claims and descriptions permitting assessment without revealing protected information. That is not a prescribed universal spreadsheet format. See Rule 26(b)(5)(A). (uscourts.gov)

Rule 26(f)(3)(D) addresses planning the timing and method of compliance. Record the applicable arrangement rather than assuming a standard logging schedule. See Rule 26(f)(3)(D). (uscourts.gov)

Record: withheld-category reference, logging arrangement or order, review owner, and unresolved issue. Leave substantive privilege determinations to counsel.

7. Assign deficiency actions and verify closure

Convert gaps into specific actions: obtain a referenced attachment, clarify a search limitation, reconcile pack versions, or determine whether a consent was withheld. Prepare deficiency communications from verified references rather than an undifferentiated missing-document list.

Use distinct statuses for response served, production continuing, clarification pending, privilege review pending, and verified complete. Administrative closure with an accepted limitation is different from verified completeness.

Record: action owner, next review date, correspondence, resolution, reviewer, and verification date. Close after evidence supports closure or counsel expressly documents acceptance of remaining uncertainty. Reopen the row if a supplement changes its basis.

Worked example

Fictional scenario: Shareholder’s counsel challenges Alder Quay Corporation’s division sale to a director-affiliated buyer. Alder Quay is a fictional Delaware corporation. Requests seek conflict disclosures, valuation materials circulated to a special committee, and final approval records. Every party, document, identifier, and procedural arrangement below is fictional.

The production contains minutes and a board pack. An agreed production letter, EXT-02, sets November 9, 2026, for supplementation addressing these requests. It does not resolve disputed scope or establish any rule-derived deadline. The tracker records counsel’s review as of October 13, 2026.

The table produces three different next actions: obtain a referenced schedule, clarify the treatment of drafts, and distinguish planned consent from completed authorization. None establishes that disclosures were absent, directors lacked valuation information, or approval was ineffective. Counsel should pursue the identified gaps without converting incomplete production into proof of a fiduciary breach.

Common mistakes

• Treating minutes as the entire decision record. Compare circulated packs, referenced attachments, and approval instruments; explain mismatches.
• Combining response and production completion. Use separate statuses and date categories so a written response does not conceal outstanding documents.
• Recording objections without withholding information. Capture both and assign clarification when their relationship is uncertain.
• Calling every absent record a deficiency. Identify the request component and evidence; distinguish not located, not searched, withheld, and disputed scope.
• Equating approval records with legal protection. Record what documents show; reserve legal effect for analysis of governing law, entity documents, transaction context, and facts.

Final quality check

• Every row resolves to the operative request and response with paragraph or page citations.
• Each request identifies the disputed decision or issue it tests.
• Dates have verified sources; extensions, cutoffs, and internal targets remain distinguishable.
• Custodian and repository coverage is documented without unsupported completeness claims.
• Objections, withholding, privilege questions, and production commitments remain separately visible.
• Production references open correctly and support the stated coverage or gap.
• Open issues have owners and next actions; closed rows retain verification or expressly accepted limitations.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Document review, privilege and confidentiality analysis, chronology, and evidence analysis can support examination of records underlying tracker entries. Use chronology review to examine decision sequencing and litigation preparation to connect gaps with further work. The tracker remains counsel’s work product; lawyers verify citations, deadlines, scope, and closure. Book a demo to discuss this document-centered workflow.

Frequently asked questions

Should one row cover every responsive document?

Use one control row per request and link a document list. Add subrows when sources, objections, or completion dates require independent management. Retain the parent request ID so coverage remains traceable.

How should we track documents responsive to several requests?

Reference the same stable document ID in each relevant row and explain which component it addresses. Repeated references do not establish additional documents or broader production coverage.

What if the responding party says no additional records exist?

Record the statement and its source precisely. Determine whether it addresses the particular repository, attachment, or period at issue. Counsel can decide whether clarification is necessary; the tracker should not transform the statement into independent verification.

Can we send the internal tracker to opposing counsel?

Prepare a separate external version. Remove internal strategy, legal analysis, sensitive review notes, and unnecessary personal information. Retain request citations, supported deficiency descriptions, clarification questions, and proposed actions appropriate to the communication.

Sources

• Federal Rules of Civil Procedure, December 1, 2025 edition: Rules 26 and 34; federal district-court discovery requirements discussed above.
• Delaware General Corporation Law, section 141(f): board and committee action by consent, subject to statutory conditions and governing documents.

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.