How to build a case law research matrix for Shareholder Disputes

Build a shareholder-dispute research matrix around discrete legal propositions, not a list of case names. For each proposition, record the authority’s court, date, precedential status, procedural posture, statutory version, holding, factual fit, and subsequent treatment. Connect the research to governance documents and disputed events using stable document identifiers and pinpoints. The resulting deliverable should identify supporting and adverse authority, explain material distinctions, and assign unresolved legal or factual questions before counsel relies on the analysis in a pleading, advice memorandum, or hearing submission.

When to use this workflow

Use this workflow when litigation counsel or an in-house team must evaluate shareholder rights, challenged approvals, inspection demands, or alleged conflicted transactions. Concrete triggers include receiving a complaint, assessing whether a proposed claim belongs to the shareholder or corporation, and preparing a memorandum on demand futility or transaction protections.

Keep the scope tied to a decision. A matrix addressing dismissal risk needs authorities on pleading requirements and procedural thresholds, not simply decisions discussing liability after trial.

This guide uses a US orientation and Delaware corporate-law illustrations. October 13, 2026 is the assigned research cutoff, not a representation that every authority below received a comprehensive treatment check through that date. Confirm incorporation, entity type, governing law, forum, historical statutory applicability, and relevant procedural rules. Federal procedure does not govern every state proceeding or arbitration.

What you need

Gather a focused research packet:

• Matter definition: client and represented capacity, proposed claims and defenses, requested relief, anticipated forum, and the decision research must support.
• Governance records: certificate, bylaws, shareholder agreements, amendments, stock ledger, capitalization records, and voting arrangements.
• Disputed-event evidence: approval materials, disclosures, consents, transaction documents, and a chronology separating authorization, execution, delivery, and payment.
• Claim-specific facts: alleged corporate and individual harm, proposed recipient of recovery, relevant board composition, ownership relationships, and asserted director conflicts.
• Research controls: existing memoranda, candidate authorities, cutoff date, assigned researchers, official-source locations, and access to subsequent-treatment research.

Use references such as “GOV-04, Article VI” rather than “charter in email.” Flag disputed ownership, missing attachments, and unsupported relationship allegations before researchers treat them as established facts.

Use the template

The Shareholder Disputes — Case law research matrix is a working research record. You can copy this table into your working document or spreadsheet. Use one row per authority-proposition pair; one opinion may require several rows.

“Status” identifies precedential status and relevance to the selected forum. “Posture” specifies the ruling under review; “law version” identifies statutory language addressed or an unresolved applicability issue. Mark statutes as statutory anchors, not case holdings.

Separate the holding from counsel’s application. In “Matter evidence / fit,” include document pinpoints, similarities, adverse distinctions, and missing facts. “Treatment / verified” records the review date, researcher, search scope, and material later authorities—not merely a database symbol.

For crowded fields, use a linked research note keyed to the row ID. Record adverse authority in its own row rather than hiding it in a favorable case summary. A pending row should state exactly what remains unverified.

Step by step

1. Define the decision and divide the legal questions

State whether counsel is evaluating inspection, claim classification, demand futility, a challenged approval, or a transaction defense. Identify the client’s capacity and requested deliverable. “Research fiduciary duties” is too broad.

Separate classification, standing, demand, controller status, review standards, and remedies. For classification, Delaware’s Tooley analysis asks who suffered the alleged harm and who would receive the benefit of recovery or relief. That inquiry does not itself answer every standing or merits question. See Tooley v. Donaldson, Lufkin & Jenrette, Inc., 845 A.2d 1031, 1033, 1039 (Del. 2004).

Record: question ID, proposed proposition, forum, decision informed, and responsible lawyer. Identify dependent questions without prematurely answering them.

2. Establish the statutory and temporal baseline

Identify the relevant provision, text version, disputed-event dates, and amendment-applicability questions before relying on older opinions. Current online text alone does not establish which provisions govern historical conduct.

For Delaware inspection research, § 220 specifies record categories and requirements including good faith, proper purpose, reasonable particularity, and a specific relationship between requested records and purpose. Category-specific temporal limits and provisions for additional records require separate analysis. Inspection is not interchangeable with litigation discovery. See 8 Del. C. § 220(b), (f)–(g).

Record: statutory anchor, version examined, event dates, and applicability conclusion or assigned gap. Keep statutory requirements separate from your practical research recommendations.

3. Search by proposition and counterproposition

Develop paired searches: the alleged basis for a direct claim and the argument that the harm belongs to the corporation; asserted director dependence and facts supporting independence; a proposed protective route and alleged failures to satisfy its conditions.

For Delaware controller transactions, § 144(b) addresses transactions other than going-private transactions, while § 144(c) addresses going-private transactions. Their approval and fairness routes differ. Definitions, conditions, exceptions, and applicability require separate examination; these are conditional protections against specified fiduciary-duty relief, not blanket transaction validation. See 8 Del. C. § 144(b)–(e).

Record: supporting and opposing propositions, candidate authorities, searches performed, and coverage gaps. Do not use “related party” as a substitute for researching controller status.

4. Read the opinion and extract the narrow holding

Retrieve the court-issued opinion where available. Verify caption, date, court, disposition, and the pinpoint supporting each proposition. Distinguish the court’s analysis from allegations, party arguments, quoted authorities, and issues expressly left unresolved.

Capture what the procedural stage permits the decision to establish. A dismissal ruling should not become a summary of proven misconduct. Identify whether the court decided the proposition or merely assumed it for another issue.

For example, Zuckerberg adopted a director-by-director demand-futility test and affirmed dismissal under Delaware Court of Chancery Rule 23.1. Its demand inquiry should not be recorded as a finding of transaction liability. See United Food & Commercial Workers Union v. Zuckerberg, 262 A.3d 1034, 1059 (Del. 2021), official opinion pp. 41–42.

Record: narrow paraphrase, pinpoint, posture, disposition, and limits. Preserve the official opinion or its stable link.

5. Compare legally significant facts against the record

Test the proposed analogy using actual documents. For classification, identify the alleged injury and requested recipient of relief. For demand research, distinguish the board approving the transaction from the board relevant to the proposed litigation-demand analysis. For controller questions, separate ownership evidence from unsupported assertions of influence.

Record both helpful and adverse differences. A committee’s membership list does not supply missing evidence about relationships, authority, or its work. Likewise, an allegation that a buyer is affiliated with a shareholder is not a completed factual analysis.

Record: document IDs and pinpoints, material similarities, distinctions, conflicting evidence, and specific missing records. Label inferences explicitly rather than converting them into facts.

6. Verify subsequent treatment and competing authority

Check appellate history and later treatment for each proposition intended for the final analysis. Read relevant portions of later opinions rather than relying solely on treatment symbols or excerpts. Evaluate statutory changes separately from judicial treatment.

Keep two conclusions distinct: whether the authority remains usable for this proposition and whether it persuasively fits this matter. A valid holding may still be a weak analogy. Conversely, a later decision’s factual distinction need not invalidate every proposition in the earlier opinion.

Record: review date, researcher, cutoff coverage, material later authorities, and remaining update work. Mark “not checked” where appropriate. An official-source holding check is not a comprehensive subsequent-treatment check.

7. Turn the matrix into a research decision

Group rows by question and write a short synthesis: best support, strongest counterargument, decisive factual distinctions, and unresolved dependencies. Do not rank positions by case count.

Assign legal gaps to a researcher and factual gaps to a defined records task. Specify whether the available analysis supports a conditional recommendation or remains insufficient for the intended decision.

Record: provisional conclusion, supporting row IDs, limitations, next action, and owner. Keep collection, discovery, and briefing as separately scoped tasks rather than expanding the matrix into a complete litigation plan.

Worked example

Fictional scenario: Counsel represents minority shareholder Larkspur Capital in fictional Delaware corporation Cedar Quay Robotics. Cedar Quay completed a fictional $6.8 million asset sale to a buyer allegedly associated with a major shareholder. Larkspur seeks advice on a proposed challenge; no complaint or litigation demand has been made.

DRAFT-02, § 4 alleges that Cedar Quay received inadequate consideration but requests payment directly to Larkspur. MIN-08, p. 2 lists the transaction committee. GOV-05, p. 1 lists five current directors, but the packet lacks relationship evidence. CAP-04 records voting ownership without establishing the buyer’s beneficial ownership or the shareholder’s broader influence.

The entries below apply real authorities to fictional facts. Holdings are source-checked illustrations; subsequent treatment remains expressly unverified.

The matrix changes the assignment. Counsel must reconcile the alleged corporate injury with the requested individual recovery before assuming that a direct challenge is available. If derivative analysis is relevant, committee membership alone does not answer the demand question. The alleged buyer connection also requires factual development before choosing a controller-transaction framework.

The output is therefore a conditional research memorandum, not a conclusion that the sale is invalid or demand is excused. Missing evidence stays visible; no row invents relationships, findings, or completed treatment research.

Common mistakes

• Organizing only by case name. Use authority-proposition rows so different holdings and limits remain visible.
• Treating a merits standard as the demand answer. Research each procedural and substantive question separately, then explain their relationship.
• Ignoring statutory change. Record the text interpreted, relevant dates, and applicability analysis before adopting older reasoning.
• Turning allegations into findings. Identify posture and distinguish assumed facts from adjudicated facts.
• Calling an official-opinion check a treatment review. Record source verification and subsequent-treatment coverage separately.

Final quality check

• Each operative proposition has a primary-source pinpoint or an explicit pending designation.
• Court, date, status, posture, and disposition match the opinion.
• Statutory version and historical applicability are resolved or assigned.
• Holdings, allegations, and counsel’s inferences remain distinct.
• Factual comparisons include stable IDs, pinpoints, and adverse distinctions.
• Treatment coverage and competing authority are documented without overstating completeness.
• Every open issue has an owner and a defined action before reliance.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, evidence analysis, and chronology viewer can support organizing the factual record used to test case-law analogies. Its trial-preparation capabilities support related litigation work. The matrix remains counsel’s work product; authority selection, holding verification, treatment research, and legal conclusions remain counsel’s responsibility. To discuss this evidence-to-research workflow, book a demo.

Frequently asked questions

Should inspection and fiduciary-duty authorities share a matrix?

They can share a workbook, but separate issue groups and record each authority’s question and posture. An inspection analysis should not silently become a liability conclusion.

How many authorities should each question contain?

Enough to explain the governing analysis, material disagreement, and meaningful distinctions. Remove duplication only after preserving differences in posture, statutory version, and treatment.

What if the closest factual match predates an amendment?

Retain it with a version warning. Research applicability and later interpretations, then explain which proposition remains potentially useful. Do not label the entire opinion obsolete without support.

Can counsel recommend action while facts remain missing?

Yes, conditionally. Identify the missing record, the conclusion that depends on it, and the assigned next task. Do not substitute a confidence score for that explanation.

Sources

• Tooley, Delaware Supreme Court, April 2, 2004 — direct-versus-derivative classification.
• Zuckerberg, Delaware Supreme Court, September 23, 2021 — demand-futility analysis.
• Delaware General Corporation Law, § 220 — inspection requirements and records.
• Delaware General Corporation Law, § 144 — conditional transaction protections.

This is a general professional workflow guide, not advice on a particular dispute.

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.