How to build a document-backed case chronology for Shareholder Derivative Matters

Build a shareholder derivative chronology around the challenged corporate acts, the plaintiff’s ownership history, and the board’s opportunity to address the alleged wrong. Give each event a stable identifier, distinguish its occurrence date from its source-document date, and attach pinpoint evidence. Separate supported propositions, allegations, inferences, and conflicts. The resulting deliverable is a source-linked event record that lets counsel examine demand-related positions, reconstruct director knowledge and decision-making, identify evidentiary gaps, and prepare targeted witness questions without turning a chronological narrative into a legal conclusion.

When to use this workflow

Use this workflow when counsel receives an inspection production, a litigation demand and response, board materials concerning challenged conduct, or discovery that changes the apparent sequence of director knowledge and action. It serves plaintiff’s counsel, defense counsel, and in-house teams coordinating corporate records with litigation counsel.

The scope is the event record—not a complete claims analysis or discovery plan. Prioritize ownership, board composition, conflicts, information received, approval, implementation, and demand-related events.

Separate forum procedure from governing corporate law. Federal Rule 23.1(b) requires a verified complaint, contemporaneous ownership allegations subject to its operation-of-law exception, and particularized allegations addressing demand efforts and reasons for not obtaining action or making demand. It does not supply the substantive demand-futility test. State proceedings require separate procedural analysis. Federal Rule of Civil Procedure 23.1(b).

What you need

Start with the operative complaint or draft allegations, challenged conduct and date range, incorporation jurisdiction, entity type, forum, and counsel’s demand position. Assemble:

• Ownership records showing acquisition, transfers, and gaps in the available history.
• Dated board and committee rosters, governing documents, delegations, meeting packets, minutes, consents, attendance, and recusal records.
• Transaction proposals, adviser materials, conflict disclosures, communications, and implementation records.
• Separate inspection-demand and litigation-demand files, including attachments, delivery evidence, investigation authority, and responses.
• Production indexes, Bates ranges, native-file identifiers, redaction information, and witness accounts.

Preserve originals and document versions. Note missing attachments and whether metadata reflects creation, modification, transmission, or collection. A filename containing a meeting date does not establish that the meeting occurred then. Identify source-set limits at the outset so later reviewers can distinguish missing evidence from an event that did not occur.

Use the template

Use Shareholder Derivative Matters — Case chronology as the working record. You can copy this table into your working document or spreadsheet. Keep stable event IDs when sorting or inserting rows.

Distinguish exact dates, supported ranges, and unknown dates. Put a different document date in the source field. Write neutral descriptions: “Minutes record approval” is narrower than “Board validly approved.”

Use issue tags such as ownership, demand, board composition, conflict, information, approval, implementation, and loss. Evidence status describes the proposition, not the entire document: supported proposition, allegation, inference, or conflict. “Supported” does not mean conclusively established or admissible.

Cite Bates numbers and pages, or stable document IDs with native locations. Use a linked event note for lengthy qualifications, related event IDs, and verification history. Assign each open action to a named reviewer in the actual working record; a role is sufficient only until staffing is settled.

Step by step

1. Define the legal questions and relevant dates

Write a scope statement identifying the challenged conduct, entities, date range, ownership questions, and whether counsel is examining demand futility, demand refusal, or another demand-related issue. Do not treat these as interchangeable.

For Delaware corporations, Zuckerberg applies a director-by-director demand-futility inquiry addressing material personal benefit, substantial likelihood of liability, and independence from someone receiving that benefit or facing that liability. Demand is excused when at least half the demand board meets a prong. The court frames this analysis around the board in place when the complaint was filed; it is not a demand-refusal standard. Zuckerberg, opinion pp. 40–41.

Build dated rosters rather than selecting one roster for every issue. Counsel should identify the legally relevant board and date for the particular question.

Template output: Tag relevant events and assign gaps for missing ownership periods, filing dates, or roster changes. Keep standing and demand conclusions outside factual event descriptions.

2. Establish a traceable source set

Inventory custodians, production batches, versions, attachments, and access restrictions before extracting dates. Preserve relationships between board packets and supplements, and between draft and approved minutes. Later-approved minutes may describe an earlier meeting; capture both dates.

Keep inspection records separate from litigation-demand records. Delaware Section 220(b)(2) conditions inspection on good faith, proper purpose, reasonable particularity, and requested records specifically related to that purpose. Those conditions are not the entire statutory framework: assess the full provision, record categories, additional requirements, and applicable transition provisions. 8 Del. C. § 220.

Record production limits, such as an inspection production confined to specified categories or an incomplete board-portal collection. Do not describe a limited source set as the corporation’s complete record.

Template output: Enter stable references, identify missing versions or attachments, and assign retrieval tasks without assuming an absent record never existed.

3. Extract discrete events and preserve uncertainty

Create one row per proposition that matters independently. Separate preparation of a presentation, transmission, the meeting, the recorded vote, and implementation. Combining them into “transaction approved” can conceal whether directors received information before acting.

Distinguish ownership acquisition from the date a broker statement was generated. Separate sending a litigation demand from documented receipt. Preserve original timestamps for communications across time zones and record any normalization convention in the source register.

Use “before,” “after,” or a bounded range only when supported. Where a document reports an earlier event, attribute that account rather than silently treating the document’s author as an eyewitness.

Template output: Record date precision, document dates, and the basis for inferred sequencing. Use “unknown” instead of supplying a convenient date.

4. Reconstruct director knowledge and decision-making

For each challenged act, connect authority, information received, deliberation, conflicts, approval, and implementation. Identify individuals at each stage rather than relying on the current roster. Distinguish the transaction board from the board relevant to counsel’s demand analysis.

Test what each source establishes. Packet distribution supports transmission, not necessarily reading or discussion. Minutes may record attendance without showing when an attendee joined. A relationship disclosure may require further evidence before counsel can assess independence.

Track the approval mechanism actually documented: meeting vote, committee action, or written consent. Record the claimed authority and underlying documents without declaring the action valid. Keep approval separate from closing, payment, and the alleged corporate loss.

Template output: Link related event IDs, identify each actor, and flag unclear receipt, recusals, authority, or implementation as gaps—not adverse findings.

5. Separate support, allegation, inference, and contradiction

Check every material row against its precise source. Label complaint allegations as allegations even when they give specific dates. Attribute witness recollections and distinguish firsthand accounts from document-assisted reconstruction.

Preserve competing accounts. If minutes report unanimous approval but a contemporaneous message reports an objection, retain both and identify what needs resolution. Do not prefer the cleaner narrative merely because one document appears more formal.

Control privileged analysis and restricted materials. Decide which audience may see the source, factual entry, and counsel’s reasoning. Separate the factual chronology from legal assessments where appropriate; do not assume counsel’s involvement alone establishes protection.

Template output: Assign proposition-level evidence status, cite contrary records, and identify the reviewer responsible for conflicts or access decisions.

6. Convert gaps into focused verification tasks

Translate uncertainty into answerable questions: Which packet version circulated? Who received the supplement? When did a director resign? Does delivery evidence identify the demand and its attachments?

Use these questions to guide collection, witness preparation, or discovery decisions. In federal proceedings, Rule 26(b)(1) limits discovery to nonprivileged, relevant, proportional matter; applicable orders also matter. Federal Rule of Civil Procedure 26(b)(1).

For anticipated witness use, identify authentication and personal-knowledge questions. Federal Rules of Evidence 901 and 602 address those foundations; authentication does not resolve hearsay or other admissibility objections. Federal Rules of Evidence 901 and 602.

Template output: Give each gap a task, owner, and expected source. Record unsuccessful verification and leave the issue unresolved when evidence remains unavailable.

7. Verify and prepare the intended view

Have a second reviewer trace decisive entries to exact pages or native records. Check sorting, date distinctions, contrary evidence, and overstatement. Preserve a version identifier and substantive change history in the linked event notes or chronology header.

Prepare a focused view for pleading analysis, board interviews, deposition preparation, or motion drafting without deleting qualifications from the underlying record.

Keep the working chronology distinct from a proposed evidentiary summary. Federal Rule of Evidence 1006 concerns summaries of voluminous admissible materials that cannot conveniently be examined in court and requires access to underlying originals or duplicates. An internal chronology does not automatically qualify; illustrative aids are separately addressed by Rule 107. Federal Rules of Evidence 1006 and 107.

Template output: Record verification completion and assigned unresolved issues before releasing the selected view.

Worked example

Fictional scenario: Counsel represents a stockholder of fictional Delaware corporation Alder Quay Systems, Inc. The stockholder challenges a $14 million asset purchase from fictional Westmere Components LLC, allegedly connected to a director. Counsel has a partial board production and a litigation-demand file. All parties, documents, amounts, and events below are fictional.

The immediate question is whether the record supports the allegation that directors approved the purchase without receiving a conflict supplement. Available documents include a packet email, minutes, and demand correspondence, but no complete portal-access history. The chronology is being built for factual verification, not a demand-futility conclusion.

The email supports omission from that transmission, not proof that directors never received the supplement. The minutes offer a competing account but do not establish the supplement’s contents. Counsel therefore narrows the allegation under review and investigates transmission and presentation rather than treating nonreceipt as established.

The acknowledgment anchors a separate demand event. It does not establish when the demand arrived, who considered it, or how the board responded. Those remain assigned gaps; no missing response or delivery evidence is invented.

Common mistakes

• Substituting document dates for event dates. Record the meeting and later approval of its minutes separately.
• Merging inspection and litigation demands. Maintain distinct attachments, delivery records, and response chains.
• Using one board roster throughout. Track tenure changes and identify the board relevant to each legal question.
• Treating directors as a collective actor. Identify individual receipt, participation, relationships, and recusals.
• Reading production silence as factual absence. Check collection limits before drawing an inference.
• Removing contradictions for readability. Preserve competing accounts and assign focused verification questions.

Final quality check

• Every material proposition has an event ID and pinpoint source, or an explicit unsupported status.
• Event dates, document dates, and inferred ranges remain distinguishable.
• Ownership history and relevant board rosters have been checked for gaps.
• Inspection, litigation demand, investigation, and response events remain distinct.
• Allegations, inferences, and contrary evidence remain visible.
• Decisive sources have been opened and checked against the recorded propositions.
• Privilege and confidentiality restrictions match the intended audience.
• Open issues are resolved or assigned; counsel has identified applicable law, rules, orders, and authority versions.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, privilege and confidentiality analysis, chronology, evidence analysis, and deposition preparation capabilities can support this source-centered workflow. Use its chronology capabilities and deposition preparation capabilities while retaining counsel’s verification and legal judgment. The table is your working record, not a promised dedicated template module. To discuss the workflow, book a demo.

Frequently asked questions

Should ownership events appear alongside board decisions?

Yes. Include acquisition and transfer events with sources, using issue tags for separate review. Do not treat one statement as complete ownership history or resolve standing solely from chronological ordering.

Can a complaint supply chronology entries?

Yes, as attributed allegations. Link supporting or contradictory evidence through related event IDs. Preserve the allegation’s origin when updating its evidentiary status.

How should demand refusal be recorded?

Separate demand, receipt, investigation, board consideration, response, and communication of the response. Record what each source establishes. Do not substitute the demand-futility inquiry for counsel’s refusal analysis.

When is the chronology ready for witness preparation?

When material entries are traceable and questions distinguish recollection from document-assisted reconstruction. Open issues may remain if assigned and clearly framed; the chronology should not suggest that a witness personally observed every recorded event.

Sources

• Federal Rules of Civil Procedure: Rules 23.1 and 26.
• Federal Rules of Evidence: Rules 602, 901, 1006, and 107.
• Delaware General Corporation Law, Section 220.
• Delaware Supreme Court, United Food & Commercial Workers Union v. Zuckerberg.

Scope: This general professional workflow uses a research foundation dated October 13, 2026, not an exhaustive subsequent-treatment review. Matter-specific use requires checking applicable statutory versions, transition provisions, procedural requirements, and later decisions.

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.