How to organize demand and board response records for Shareholder Derivative Matters

Organize shareholder demand and board response records as an evidence-linked chronology, not simply a correspondence folder. Separate litigation demands from inspection requests, distinguish transmission, receipt, acknowledgment, and decision, and connect each board action to its authority, participants, supporting materials, and communicated response. The deliverable is a source-indexed chronology with a request-to-response map and assigned evidence gaps. It should allow counsel to identify what the collected record establishes without treating administrative acknowledgment, investigative activity, silence, or missing minutes as proof of a substantive board decision.

When to use this workflow

Use this workflow when litigation counsel or an in-house team receives a shareholder demand, inherits an incomplete investigation file, or must reconcile board records with a communicated response. It covers the demand-to-response record, including supplements—not a complete merits investigation.

Identify the incorporation jurisdiction, entity type, forum, and relevant dates first. Federal Rule 23.1(b) requires a verified complaint, specified ownership allegations subject to an operation-of-law exception, and particularized allegations concerning demand efforts and reasons for not obtaining action or making demand. It does not supply the substantive demand-futility test. See Federal Rule of Civil Procedure 23.1(b).

These are organizational recommendations for professional readers. Federal procedural references concern federal proceedings; state-court or arbitral requirements need separate checking. Delaware references concern Delaware corporations. Apply the governing law and statutory versions relevant to the matter’s dates.

What you need

Collect the source set before summarizing the board’s position:

• Demand package: every letter version, signature page, enclosure, referenced exhibit, delivery record, acknowledgment, and supplement.
• Demandant records: identity, asserted ownership, representative capacity, and supporting materials actually supplied.
• Corporate authority: contemporaneous charter, bylaws, board roster, committee resolutions, delegations, and director appointment or departure records.
• Consideration and response records: agendas, portal packets, minutes, consents, attendance, votes, recusals, investigation instructions, reports, and outgoing correspondence.
• Provenance and restrictions: custodians, collection locations, native files, document identifiers, privilege-review decisions, and access limitations.

Map sources such as the corporate secretary, directors, committee advisers, board portal, email, and business messaging. Record uncollected sources as gaps, not evidence that no responsive record exists. Keep counsel’s later analysis distinguishable from contemporaneous corporate records.

Use the template

Use the Shareholder Derivative Matters — Demand response chronology as the working record. You can copy this table into your working document or spreadsheet.

Assign stable event IDs even when later evidence changes the sequence. Give each distinct requested action a request ID, such as R01, in Request / event; repeat it in related consideration and response rows.

In Event / file dates, distinguish the asserted event date from document creation, signing, transmission, or export. Use “unknown” rather than manufacturing a date. Track / actor separates litigation demand, inspection, investigation, decision, and response, identifying each actor’s role at the relevant time.

Source / pinpoint should contain document ID, version, page or paragraph, and attachment reference; add Bates numbers when available. Use Evidence status for supported fact, allegation, inference, or conflict. “Supported” means supported by the cited record, not conclusively established.

Put missing evidence and access restrictions in Gap / restriction, without exposing protected substance in a broadly circulated table. Every consequential gap needs an action and responsible owner.

Step by step

1. Define the demand question and separate the tracks

State what the chronology must establish: what action was requested, when it was received, who considered it, and what disposition was communicated. Identify each demandant and distinct requested action; one letter may contain several.

Separate a books-and-records request from a demand that the corporation pursue claims. Delaware Section 220(b)(2) conditions inspection on good faith, proper purpose, reasonable particularity, and a specific relationship between the records and purpose. Check the full statute’s record categories, additional conditions, and applicable amendment transition provisions. Inspection is not interchangeable with litigation demand or plenary discovery. See 8 Del. C. § 220.

Record: a request ID, track, requested action, source, and unresolved characterization question for each request. Cross-reference related requests rather than merging them.

2. Establish document identity and package completeness

Inventory demand and response packages, including attachments and referenced materials. Preserve native messages and available headers alongside readable copies. Compare purported duplicates: an unsigned draft, transmitted PDF, and portal copy may differ materially.

Give each version a document ID. Map each listed enclosure to the file actually collected. Distinguish an attachment missing from the collection from evidence that it was omitted from transmission. Identify later supplements rather than silently treating them as part of the original package.

Record: document IDs, versions, and pinpoint references, with missing enclosures assigned to a collection owner. Use a companion inventory if package detail would overwhelm the chronology.

3. Reconstruct transmission, receipt, and acknowledgment separately

Read delivery evidence rather than relying on the letter’s date. Compare email headers, courier records, receiving-office logs, forwarding messages, and acknowledgment language. Identify the recipient and the event each source actually supports.

A signed letter, its dispatch, delivery to a corporate mailbox, and circulation to directors are separate events. Do not collapse them into “board received demand.” Preserve original timestamps and resolve time-zone differences when they affect sequence. An acknowledgment may confirm receipt without establishing completeness or substantive consideration.

Record: separate transmission, receipt, circulation, and acknowledgment rows where material. Label inferred receipt and assign unexplained differences for verification.

4. Connect board activity to composition and authority

Build a date-specific map of directors, committees, attendance, advisers, and recusals. Link referrals, investigation instructions, and decisions to contemporaneous authority. Do not substitute today’s roster for the body acting at the relevant time.

For Delaware corporations, 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. Consents must be filed with the proceedings’ minutes. This mechanism does not establish the underlying action’s substantive validity. See 8 Del. C. § 141(f).

Record: the action, decision-making body, authority source, and minute or consent reference. Flag absent consents, uncertain membership, or unclear delegation without declaring the action invalid.

5. Trace consideration without overstating what occurred

Connect meeting materials and investigation records to individual requests. Distinguish materials prepared, circulated, received, discussed, and adopted. A report’s presence in a portal folder does not alone establish that every director read or relied on it.

Preserve contrary accounts. If minutes describe referral but a response describes rejection, retain both propositions with exact sources. Identify whether witness information is firsthand recollection or document-assisted reconstruction.

Screen restricted materials before entering substantive summaries. Record participant roles and escalate mixed business/legal communications for privilege review rather than treating counsel’s involvement as a sufficient classification rule.

Record: the supported activity, competing account, limitation, restriction, and targeted follow-up—not an unsupported conclusion about investigative adequacy.

6. Match requested action to the communicated response

Compare the final transmitted response with the original demand and supplements. Identify requests answered, deferred, referred elsewhere, or unaddressed. Distinguish a status update from a disposition and the board’s recorded decision from the sender’s description.

Verify the response version, signer, stated capacity, delivery evidence, and attachments. If the response asserts board authorization, locate the supporting record or label that assertion uncorroborated within the collected set. Do not classify silence as refusal without separate legal analysis.

Record: response rows linked to request IDs, pinpointed disposition language, corresponding corporate action, and mismatches requiring clarification. List unresolved requests explicitly rather than describing the entire demand as answered.

7. Reconcile the chronology and prepare the handoff

Sort by event date while preserving file dates and stable IDs. Review against sources, then against counsel’s defined questions. Keep demand futility, demand refusal, investigative process, and underlying merits separate; do not use an authority addressing one as an unexplained substitute for another.

Check important propositions for support and contradiction. Federal Evidence Rule 901 addresses authentication, and Rule 602 generally requires a personal-knowledge foundation. Neither makes a source-linked chronology automatically admissible. See Federal Rules of Evidence 901 and 602.

Record: final evidence status, unresolved issue, reviewer, and next action. Deliver the chronology, source inventory, and short list of gaps that prevent a conclusion.

Worked example

Fictional scenario: Alder Quay Systems, Inc., a Delaware corporation, receives stockholder Mira Vale’s demand to pursue claims concerning a director-affiliated services contract. Vale separately requests inspection. All parties, records, dates, and described wording are fictional; dates below fall in 2026.

Counsel assigns R01 to the litigation demand and R02 to inspection. The collected demand lists two exhibits, but the mailbox export contains only one. Draft committee minutes describe referral to advisers. A later response states that the board declined R01; no corresponding board decision record has been collected.

Counsel can confirm a transmitted response but cannot yet equate it with a documented board disposition. The next review is targeted: recover Exhibit B, verify the committee record, and locate the asserted board action. R02 remains on its own inspection track; these three entries do not establish its disposition. Missing action records do not establish that the board never acted.

Common mistakes

• Using one “demand date.” Separate document, dispatch, receipt, circulation, and acknowledgment dates.
• Merging inspection and litigation requests. Assign independent request IDs even when correspondence overlaps.
• Treating draft minutes as final decisions. Label approval status and seek final records or corroborating evidence.
• Substituting response language for board evidence. Record the communication and verify authorization separately.
• Filling gaps with narrative. Preserve uncertainty and assign collection work instead of inferring nonoccurrence.

Final quality check

• Every material event has a stable ID and exact source pinpoint.
• Event dates remain distinct from file and transmission dates.
• Each request and supplement links to its response or an explicit open issue.
• Board composition and authority match relevant dates.
• Communicated outcomes remain distinct from documented corporate action.
• Circulation versions preserve privilege-review restrictions.
• Conflicts and missing evidence are resolved or assigned to named owners.
• Legal propositions match primary sources, applicable versions, jurisdiction, and procedural posture.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Document review, privilege and confidentiality analysis, evidence analysis, and its chronology capabilities can support review of demand correspondence and board records. Counsel retains responsibility for source verification, privilege decisions, and legal significance. To discuss this document-to-chronology workflow, book a demo.

Frequently asked questions

Should an inspection request appear in this chronology?

Yes, when it explains the sequence, but use a separate track and request ID. Cross-reference shared correspondence without assuming inspection constitutes litigation demand.

What if the board responded informally?

Record the communication, participants, date basis, and source. Distinguish firsthand recollection from reconstruction, then identify the corroboration needed before characterizing a board decision.

Should privileged investigation materials be summarized?

Only after counsel determines the appropriate treatment and audience. A general chronology can identify a restricted source and review owner without disclosing substance. Calling the chronology “work product” is not a substitute for that assessment.

Can this table become an evidentiary summary?

Not automatically. Federal Rule 1006 concerns voluminous admissible materials and requires access to underlying originals or duplicates. Counsel must assess its requirements separately and distinguish evidentiary summaries from Rule 107 illustrative aids. See Federal Rules of Evidence 1006 and 107.

Sources

• Federal Rules of Civil Procedure, Rule 23.1(b).
• Delaware General Corporation Law § 220, inspection requirements.
• Delaware General Corporation Law § 141(f), action by consent.
• Federal Rules of Evidence, Rules 602, 901, 1006, and 107.

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.