How to build a case law research matrix for Fiduciary Duty Disputes

Build a fiduciary duty case law research matrix by separating disputed legal propositions, fixing the governing jurisdiction and entity type, and recording what each authority decided in its procedural and factual setting. Connect those holdings to the challenged conduct, defendants, approval record, and requested relief. The deliverable is a source-linked table distinguishing applicable holdings from factual analogies, adverse authority, and unresolved questions. It should let another lawyer reconstruct the proposed argument, identify its limits, and complete targeted research without repeating the entire assignment.

When to use this workflow

Use this workflow when corporate disputes counsel or an in-house litigation team must evaluate a complaint, prepare a dispositive motion, assess a conflicted transaction, or update research after a statutory change. It is particularly useful when defendants participated differently or authorities address different transaction structures.

The task is research organization and application—not completing discovery or writing a comprehensive fiduciary-duty treatise. Start with the immediate decision and include authorities that advance, limit, or contradict a proposed position.

This guide uses US practice and Delaware corporations as a bounded substantive example. Do not transfer those authorities to an LLC, another jurisdiction, or a different statutory period without analysis. Forum procedure requires separate research; federal district-court requirements do not automatically govern state litigation or arbitration. The steps below are workflow recommendations, not prescribed legal requirements.

What you need

Prepare a short research instruction stating the client’s position, immediate decision, forum, and cutoff date. Assemble:

• Matter documents: operative pleadings, relevant orders, certificate and bylaws, transaction agreements, committee mandates, conflict disclosures, and approval materials.
• A dated transaction outline: negotiations, committee formation, disclosures, votes, signing, and closing, with disputed dates identified.
• A defendant-and-conduct list: each person’s role, alleged duty, challenged act, causal theory, and requested remedy.
• Research materials: full opinions, applicable statutory versions, relevant procedural rules, and resources for checking subsequent history and later treatment.
• An evidence index: stable document IDs and page references for facts supporting and undermining proposed analogies.

Frame questions before collecting favorable cases. Ask which transaction category is implicated, what procedural issue the court resolved, and whether the proposed proposition concerns standing, review standard, liability, or relief. Keep those questions distinct.

Use the template

Use the Fiduciary Duty Disputes — Case law research matrix below. You can copy this table into your working document or spreadsheet. It is a research work product, not a prescribed court form.

Create one row per authority-proposition pair. Repeat an opinion when separate holdings address different defendants, challenged acts, or remedies. Label statutory entries as statutes rather than implying that they contain judicial holdings.

Authority / pinpoint should contain the full citation, primary-source link, and printed page or paragraph. Posture / dates captures the motion or trial setting, decision date, transaction dates, and relevant statutory period.

Within Holding / standard / burden, distinguish the substantive review standard from the appellate review standard and pleading threshold. Record an ultimate burden only if the authority addresses it. Use “not resolved” where appropriate.

History / status identifies what was checked and when. Matter fit / evidence records similarities and differences with document citations. Gap / action / owner identifies a specific question, its effect on the argument, and the responsible lawyer. Keep lengthy extracts in linked notes keyed to row IDs.

Step by step

1. Define the decision and separate the research questions

State the assignment in one sentence: for example, assess whether authorities support dismissal of claims challenging a director-associated acquisition. Divide the assignment by defendant, alleged duty, challenged conduct, causation theory, and relief.

Create separate issue IDs for threshold questions such as direct versus derivative characterization, standing, demand, limitations, or exculpation when relevant. Do not let research on an approval process silently answer those questions. Identify the opponent’s strongest expected position at the outset.

Record: issue IDs, propositions to test, affected defendants, and intended use. These entries determine which authorities belong in the matrix and which belong in a separate research assignment.

2. Fix jurisdiction, entity, and temporal boundaries

Confirm entity type from governing documents. Record the basis for the governing-law assumption and identify any dispute about it. Keep substantive corporate-law questions separate from forum procedure.

For Delaware corporations, § 144 distinguishes director/officer transactions, controller transactions other than going-private transactions, and controller going-private transactions. Definitions, conditions, exceptions, and applicability provisions matter; an approval notation alone does not establish protection. Use these distinctions to frame searches rather than announce an outcome. See 8 Del. C. § 144(a)–(e).

Record: entity, jurisdiction, relevant dates, candidate statutory provisions, and unresolved applicability questions. Include litigation-related dates where an amendment’s application provision makes them relevant; transaction date alone may not answer the version question.

3. Retrieve full opinions and capture their procedural setting

Search each issue alongside transaction structure, alleged conflict, defendant role, and procedural posture. Run searches for unfavorable outcomes and distinguishing facts, not just the desired rule. Secondary materials can identify candidates, but verify propositions against the full primary-source opinion.

Read the issues presented, reasoning, and disposition. Determine whether the court accepted allegations, made factual findings, or left a question unresolved. Do not convert a party’s argument reproduced in the opinion into a holding.

Record: citation, official link, pinpoint, posture, relevant dates, and disposition. Mark inaccessible candidates “unverified”; a search-result excerpt is not sufficient support for a recommendation.

4. Separate holding, review standard, and burden allocation

Write a narrow paraphrase of the proposition actually decided. Identify separately the standard governing judicial scrutiny of the transaction, the procedural threshold, and any ultimate burden the court allocated.

For example, in Olenik v. Lodzinski, the Delaware Supreme Court found allegations sufficient to support an inference that substantive economic negotiations preceded the procedural protections at issue, and reversed dismissal on that ground. That is a pleading-stage conclusion, not a finding of ultimate liability. See No. 392, 2018, slip op. at 23–27 (Del. Apr. 5, 2019, revised Apr. 11, 2019).

Record: the holding, pinpoint, applicable standard, burden or threshold, and limiting facts. Keep counsel’s application in the matter-fit field, separate from the court’s reasoning.

5. Test subsequent history and statutory compatibility

Check appeals, modifications, withdrawal, and later decisions addressing the particular proposition. Research tools can flag candidates; read the relevant later primary sources before characterizing their effect. Distinguish procedural history from subsequent judicial treatment.

Compare the opinion’s legal framework with the provisions applicable to the matter. Treat Olenik, for example, as an older authority requiring compatibility analysis before using its approval-process reasoning to support a current conclusion; compare § 144 and its application cross-reference.

Record: later authorities and pinpoints, check date, search scope, and proposition-specific status. “Opinion verified; subsequent treatment and statutory applicability open” is more useful than an unexplained “good law.” Never treat this article’s research cutoff as proof that a matter-specific history check occurred.

6. Match authorities to the actual approval and conflict record

For each analogy, identify supporting and contrary documents. Trace who received conflict information, when, and what action followed. Distinguish committee evaluation authority, negotiating authority, final approval, and transaction completion.

If a Delaware corporate board purportedly acted without a meeting, § 141(f) generally contemplates all members’ written or electronic consent unless restricted by the certificate or bylaws, with consents filed with the minutes. Review the full provision and governing documents before assessing effectiveness. See 8 Del. C. § 141(f).

Record: document IDs, precise citations, similarities, differences, and missing evidence. An incomplete consent set raises an inquiry; it does not establish that a director never consented. Keep documentary gaps separate from unresolved legal questions.

7. Resolve competing readings and deliver the research position

Group rows by issue and compare the strongest supporting and contrary authorities. Explain which difference—transaction category, defendant role, procedural posture, disclosure, or timing—changes the proposed argument. If no verified case supports a necessary proposition, say so.

Assign each unresolved question to a responsible lawyer and state whether it prevents reliance, requires qualification, or concerns a secondary point. Do not turn research-generated document questions into a full discovery plan.

Record: recommended position, adverse authority, limiting assumptions, and next action. Deliver a short issue summary linked to row IDs. Preserve the matrix version used for the recommendation so later research changes remain identifiable.

Worked example

Fictional scenario: Counsel represents North Quay Devices, Inc., a Delaware corporation, concerning a $38 million asset acquisition from a business associated with director Elise Rowan. A draft complaint alleges that Rowan influenced negotiations and that directors lacked adequate conflict information. The immediate assignment is to assess a proposed pleading-stage approval-process argument.

All parties, transaction terms, and matter documents in this scenario are fictional. The legal authorities below are real.

NQD-014 authorizes a committee to evaluate the acquisition but does not expressly authorize final approval. NQD-031 contains consents signed by three of four directors. NQD-042 describes Rowan’s relationship with the seller; its complete recipient list is unavailable. NQD-009 contains a pre-committee valuation presentation, but the supplied record does not establish whether it reached the seller.

These three representative rows show completed initial analysis, not completed legal research. Each retains a concrete barrier to reliance.

R1 tests the timing analogy without assuming an internal valuation was bargaining. R2 prevents treating a director relationship as established controller status. R3 isolates authorization evidence from the fiduciary-duty argument. Together, the rows change counsel’s next task: investigate targeted factual gaps and statutory applicability before presenting “independent committee approval” as an established basis for dismissal.

Common mistakes

• Treating fiduciary duty as one issue. Separate defendant conduct, duty theory, causation, and remedy; a holding on one does not answer all four.
• Combining allegations with findings. Record posture and preserve the opinion’s treatment of facts rather than presenting accepted allegations as proven events.
• Confusing review standards. Separate appellate review, transactional scrutiny, pleading thresholds, and ultimate burdens.
• Reusing older approval analysis mechanically. Check applicable statutory text and later treatment before relying on the proposition.
• Collecting only favorable cases. Add the strongest contrary authority and identify why the distinction matters, rather than hiding it in notes.

Final quality check

• Each recommended proposition has a full primary source and accurate pinpoint.
• Jurisdiction, entity, transaction category, and applicable statutory period are recorded.
• Holdings are separated from party arguments and counsel’s inferences.
• Procedural posture, relevant standards, and burdens are addressed or expressly unresolved.
• Subsequent history and later treatment have dated, proposition-specific checks.
• Supporting and contrary factual comparisons cite identifiable matter documents.
• Open issues are resolved or assigned, with their effect on reliance stated.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, chronology, and evidence-analysis capabilities can support the factual comparisons in this matrix. Use the chronology viewer to organize approval sequencing and trial preparation capabilities to support evidence-focused preparation. Keep opinion verification, subsequent-history research, and legal conclusions with counsel; these are not claimed case-law research functions. To discuss the document-centered portion of this workflow, book a demo.

Frequently asked questions

Should every case receive its own row?

Use one row per authority-proposition pair. An opinion may require multiple rows for distinct issues or defendants. Remove repetitive entries that add neither a new proposition nor a meaningful distinction.

Can statutes appear in a case law matrix?

Yes, as clearly labeled framework entries. They help identify the relevant case searches but do not replace opinions addressing disputed interpretations. Do not populate their cells as though a court decided a holding.

How should counsel handle a missing approval document?

Identify the missing record and the comparison it affects. Assign the document inquiry separately from legal research, and qualify the recommendation until the relevant assumption is verified or expressly accepted.

When is the matrix ready for a motion team?

When proposed arguments link to verified authorities, adverse treatment is addressed, and factual assumptions are visible. Open issues may remain, but their owners and consequences must be explicit; an unresolved essential proposition should not appear as settled support.

Sources

Scope: general professional workflow using an October 13, 2026 research cutoff, not advice for a particular dispute.

• Olenik v. Lodzinski, No. 392, 2018 (Del. Apr. 5, 2019, revised Apr. 11, 2019): primary opinion illustrating pleading-stage process-timing analysis; later treatment and matter-specific applicability require separate checks.
• Delaware General Corporation Law, §§ 141 and 144: bounded statutory examples for written consent, transaction classification, and approval-process research.

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.