How to create a claims and defenses evidence matrix for Fiduciary Duty Disputes

Create a fiduciary duty evidence matrix by separating each claim and defense into propositions tied to a defendant, challenged decision, alleged duty, causation theory, and remedy. Map supporting and contrary evidence using stable document identifiers and pinpoint references. Distinguish source facts from inferences, missing records, and unresolved legal questions. The resulting working table shows counsel which positions the record supports, what could defeat them, and the targeted research or evidence task needed before making the next litigation decision.

When to use this workflow

Use this workflow when outside counsel or an in-house legal team evaluates a conflicted transaction, diverted corporate opportunity, allegedly deficient board process, or other challenged fiduciary conduct. Concrete triggers include a stockholder demand, proposed pleading, first document production, or testimony that changes an existing theory.

Define the review question and record cutoff before starting. A matrix evaluating a sale approval should not become an inventory of every corporate grievance.

This guide uses US practice assumptions. Federal procedural references concern district-court litigation; federal evidentiary rules apply within their stated scope, not automatically in state proceedings or arbitration. Delaware corporate statutes provide a bounded approval example. Confirm entity type, governing law, forum, transaction date, and applicable statutory version. The cited sources do not supply a complete fiduciary-duty framework.

What you need

Assemble a defined record set:

• Pleadings, demand correspondence, asserted defenses, and requested remedies, distinguishing allegations from proof.
• Charter, bylaws, committee mandates, appointment records, and documents establishing each defendant’s authority.
• Board packs, minutes, consents, attendance, recusals, disclosures, and circulation histories.
• Transaction terms, valuation versions, alternatives considered, adviser materials, and implementation records.
• Records of alleged financial, familial, employment, or advisory relationships at relevant decision dates.
• Witness accounts, production indexes, discovery responses, and known collection limitations.

Prepare an authority worksheet addressing standing, direct or derivative characterization, duties, defenses, review standards, burdens, remedies, and limitations. Record jurisdiction, entity type, procedural posture, relevant dates, and subsequent history. Assign unresolved questions rather than borrowing rules from a different entity or transaction category.

Use the template

Use the Fiduciary Duty Disputes — Claims and defenses matrix below. You can copy this table into your working document or spreadsheet.

Use stable row IDs, not spreadsheet positions. Create separate rows for materially different defendants, duties, acts, causation theories, and remedies; link related rows through their IDs.

In Party / decision, include the relevant date. In Proposition / authority, identify the claim or defense and state the proposition to be tested, with an authority reference or assigned legal question. Do not label an allegation as an established fact.

Evidence cells need document IDs, page or paragraph citations, and versions. Gap / readiness captures missing records, authentication, hearsay, and access restrictions. Assessment explains the inference and its limits. Action / owner assigns the next task, including a target date where appropriate. Keep lengthy legal analysis in linked notes rather than making cells unreadable.

Step by step

1. Define the decision and each defendant’s role

Identify the challenged act and divide its decision sequence into proposal, information circulation, deliberation, approval, execution, and implementation. Participation at one stage should not be treated as evidence of participation at every stage.

Establish each defendant’s role on the relevant date from appointment records, mandates, attendance, signatures, and communications. Distinguish a director’s individual conduct from committee conduct and an officer’s implementation instructions. An announced intention, authorization, executed agreement, and completed transaction are different events.

Record: Party-specific decision rows, dated role sources, and uncertainty about participation.

2. Translate claims and defenses into testable propositions

Break counsel’s theory into propositions rather than copying complaint paragraphs. For a conflicted sale, separate the alleged economic interest, disclosure content and recipients, influence over negotiations, approval conduct, causal connection, and requested relief.

Identify the opposing explanation early. Records might contradict the alleged interest, show a different decision-maker, support an informed approval process, or weaken the asserted loss. These possibilities are evidence questions, not a substitute for jurisdiction-specific elements and defenses.

Link each proposition to verified authority or a research assignment. Record alternative legal pathways when classification or the applicable standard remains unresolved.

Record: Discrete claim and defense propositions, related row IDs, and authority dependencies.

3. Map support and contradiction to exact sources

Read the underlying document before treating an extracted passage as proof. Distinguish an operative valuation from a draft, a circulated board pack from proof of receipt, and approved minutes from an unapproved draft.

Separate event date, document creation, transmission, and later recollection where sequencing matters. An email stating that a committee received materials does not necessarily identify the version received by each member.

Preserve adverse evidence with the same precision as favorable evidence. Identify whether a witness describes firsthand observation, inference, or another person’s account. Do not silently harmonize inconsistent accounts or treat repeated copies as independent corroboration.

Record: Source IDs, pinpoint citations, versions, relevant dates, and the precise inference supported or contradicted.

4. Test the asserted approval defense

Reconstruct approval from committee mandates, disclosures, attendance, recusals, votes, minutes, and consents. Ask who received which information before deciding. Separate evidence that approval occurred from evidence supporting its claimed legal effect.

For Delaware corporations, § 144 distinguishes director/officer transactions, non-going-private controller transactions, and controller going-private transactions. For the last category, subsection (c) provides routes involving both specified committee and stockholder procedures, or fairness. Classification, definitions, conditions, exceptions, and temporal applicability require analysis; a disclosure reference or vote entry alone does not establish protection. See 8 Del. C. § 144. (delcode.delaware.gov)

If approval rests on written consent, § 141(f) generally permits action through all members’ written or electronic consent unless restricted by the certificate or bylaws, with consents filed with the minutes. Inspect effectiveness, revocation, and governing-document issues rather than relying solely on a signature page. See § 141(f). (delcode.delaware.gov)

Record: Asserted approval route, condition-specific evidence, unresolved facts, and assigned legal analysis.

5. Evaluate evidentiary readiness and protected material

Identify a foundation for each important item. Federal Evidence Rule 901 requires sufficient evidence to support a finding that an item is what its proponent claims; knowledgeable-witness testimony is one method. Authentication does not resolve hearsay, relevance, or other objections. See Rule 901. (uscourts.gov)

Do not spread potentially privileged advice throughout the matrix. Identify restricted sources and route uncertain communications or attachments for separate review. Rule 26(b)(5)(A) addresses express privilege or protection claims and descriptions permitting assessment without revealing protected information; it does not establish substantive privilege. See Rule 26. (uscourts.gov)

Record: Foundation candidates, separate admissibility questions, and access or privilege-review restrictions.

6. Convert gaps into targeted evidence tasks

Describe the missing proposition before choosing a collection or discovery task. Instead of requesting every board email, ask whether the final valuation reached the voting committee before approval. Identify likely custodians, repositories, dates, and the evidence needed to answer that question.

Consider board portals, committee workspaces, business messaging, calendars, adviser files, and model histories where relevant. Record collection limitations without assuming every repository is discoverable.

In federal district-court litigation, Rule 26(b)(1) limits discovery to nonprivileged matter relevant to claims or defenses and proportional to the case’s needs. A matrix gap does not independently establish discoverability. See Rule 26(b)(1). (uscourts.gov)

Record: Bounded task, expected proposition, owner, target date, and discovery or collection constraints.

7. Reassess the theory against the complete row set

Review support, contradiction, legal dependencies, and readiness together. Distinguish missing evidence from disputed interpretation, an unresolved rule, or a weak causal connection. Each requires a different response.

Use assessments such as “receipt supported; reviewed version unresolved,” not unexplained confidence scores. Preserve material revisions and their reasons. Before recommending a position, identify whether unresolved rows could change the claim, defense, or remedy analysis.

Record: Current assessment, revision reason, decision dependency, and next action or express decision not to pursue further evidence.

Worked example

Fictional scenario: Juniper Harbor Components, Inc., a Delaware corporation, sells equipment to Cobalt Mill Holdings for $6.4 million. A stockholder alleges that director Mara Vale held an undisclosed buyer interest and influenced approval. Defense counsel points to committee review and an external valuation. All parties, amounts, documents, and described evidence are fictional.

The limited record contains an investor schedule, draft minutes, a committee approval record, a packet index, and two valuation versions. The transaction date, applicable statutory version, controller status, standing, and legal prerequisites remain research assignments. The following three entries represent linked conflict, approval, and loss inquiries—not complete claims analysis.

The matrix changes three decisions. Counsel must investigate the disclosure reference before presenting nondisclosure as established. The approval defense needs factual reconstruction and legal classification, not merely a vote record. The loss theory must explain the final model rather than select the higher figure. No missing attachment, delivery record, or valuation input is presumed favorable to either side.

Common mistakes

• One row for the entire board. Separate defendants when interests, information, authority, or participation differ.
• Treating missing minutes as proof that nothing occurred. Identify the record limitation and investigate other contemporaneous sources.
• Recording approval without its conditions. Connect the asserted defense to the relevant legal route and condition-specific evidence.
• Using a price difference as the damages analysis. Reconcile assumptions, asset scope, transaction terms, and the causal theory.
• Hiding adverse evidence in notes. Place it beside supporting evidence and explain its effect on the assessment.

Final quality check

Before relying on the matrix, confirm:

• Each proposition identifies the relevant defendant, decision, and date or date uncertainty.
• Citations resolve to the correct source and version.
• Extracts and paraphrases match the underlying record in context.
• Adverse evidence and competing explanations remain visible.
• Authorities fit the entity, forum, relevant dates, and theory.
• Foundation, hearsay, privilege, and access issues are separately identified.
• Causation and remedy rows are not inferred solely from an alleged conflict.
• Every material open issue has an owner and next action, or an express decision not to pursue it.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, evidence analysis, privilege and confidentiality analysis, chronology, and deposition preparation capabilities can support review of the sources underlying this matrix. Use chronology capabilities and trial preparation to support the workflow while counsel retains legal characterization and proof assessment. Book a demo focused on your fiduciary duty evidence-review needs.

Frequently asked questions

Should claims and defenses share the same matrix?

Usually, yes. Shared evidence can support competing positions. Keep distinct legal propositions in separate linked rows, especially where defendants, burdens, or requested remedies differ. Do not force an entire defense into a contrary-evidence cell.

How should we record an alleged conflict?

Identify the relationship, person, decision date, and source. Separately test disclosure content, recipients, timing, and participation. A relationship entry is not itself a liability conclusion.

What if the governing standard is unresolved?

Continue factual mapping while identifying alternative legal pathways and assigning research. Specify which factual gaps matter under each pathway. Avoid describing a claim or approval defense as established before counsel verifies the applicable standard.

Can the matrix become a trial exhibit?

Not automatically. An internal advocacy table differs from an evidentiary summary. Federal Rule 1006 concerns summaries of voluminous admissible materials that cannot conveniently be examined in court and requires reasonable access to originals or duplicates. Evaluate admissibility and proposed use separately under the applicable forum’s rules. See Rule 1006. (uscourts.gov)

Sources

• Federal Rules of Civil Procedure: Rule 26 discovery scope and protection claims.
• Federal Rules of Evidence: Rules 901 and 1006.
• Delaware General Corporation Law, §§ 141 and 144: written consent and specified transaction protections.

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.