Build a fiduciary duty chronology around decisions, not merely document dates. Identify the challenged transaction, map participants’ roles and alleged conflicts, and reconstruct what decision-makers received, considered, approved, and implemented. Support each factual proposition with a stable document identifier and pinpoint citation. Keep contrary evidence, inferred sequencing, and unresolved questions visible. The deliverable is a source-linked chronology that counsel can use to test competing accounts of disclosure, deliberation, authorization, and causation without presenting disputed allegations or later recollections as established facts.
Use this workflow when litigation counsel or an in-house team must reconstruct a contested board decision, related-party transaction, alleged corporate opportunity diversion, or controller-led transaction. Triggers include inconsistent director accounts, an incomplete minute book, or valuation revisions shortly before approval.
The scope is the decision sequence and its evidentiary support—not a complete claims analysis or discovery plan. Begin early enough to capture relevant relationships and information flows; end after implementation and the consequences material to the dispute.
This is a US-oriented workflow guide. Federal rules do not automatically govern state proceedings or arbitration. Delaware corporate provisions are bounded examples, not nationwide fiduciary-duty law. Confirm entity type, governing law, applicable statutory version, forum requirements, and case-specific orders before assessing legal significance.
Assemble a focused source set:
Retain native files and available metadata alongside review copies. Identify custodians and collection sources where known; do not infer provenance from filenames. Keep the source inventory separate from the event table so one document can support several events without duplicating collection records.
Target collection questions to the disputed decisions. In federal district court, discovery under Rule 26(b)(1) must concern nonprivileged matter relevant to claims or defenses and be proportional to the case’s needs; relevance alone is insufficient. See Federal Rule of Civil Procedure 26(b)(1). (uscourts.gov)
Use Fiduciary Duty Disputes — Case chronology as the working record. You can copy this table into your working document or spreadsheet. Stable event IDs preserve references when rows are sorted or cited in interview outlines.
| Event ID | Event time / basis | Actor / role | Factual proposition | Decision stage | Source / pinpoint | Contrary evidence / gap | Action / owner |
|---|---|---|---|---|---|---|---|
“Event time / basis” distinguishes a recorded timestamp, witness-reported date, range, or inference. Include time zones when sequence matters. Keep document creation and transmission dates in the source inventory or linked notes when they differ from event time.
Use one testable proposition per row. Identify the document and page, message, attachment, or model cell—not merely its folder. Decision stages include information receipt, conflict disclosure, deliberation, approval, and implementation. The gap column captures conflicting evidence and uncertainty. The final column states the verification task and responsible person. Keep legal conclusions in linked counsel notes.
Describe the decision neutrally: “approval of the asset sale to an entity affiliated with Director A,” rather than “approval of the disloyal sale.” Identify whose authority, knowledge, and conduct matter at each stage.
For an opportunity-diversion allegation, start with when the opportunity reached the relevant person and in what capacity. For a conflicted sale, capture negotiations, relationships, and the approval structure. Include later consequences only where they bear on the disputed conduct or claimed loss.
Record: the earliest supported events, relevant actors, and assigned scope questions. State inclusion criteria in the table’s cover note so reviewers do not select only favorable evidence.
Assign stable document IDs and preserve relationships among messages, attachments, and versions. Separate the event date from document creation, transmission, and later recollection. Minutes prepared afterward and messages sent during a meeting have different evidentiary roles.
Normalize timestamps only if the original values and conversion basis remain recoverable. Retain a month, range, or competing dates rather than inventing a day for sorting. Mark inferred sequencing expressly.
Record: source IDs, pinpoints, the event-date basis, and unresolved metadata questions. Split a document describing multiple decisions into separate event rows.
Tie each alleged financial, familial, employment, or advisory relationship to a person and relevant period. Distinguish evidence of an interest from evidence that it was disclosed. Identify recipients rather than assuming delivery to counsel or a board administrator establishes receipt by every director.
For valuations, track the circulated version, recipients, assumptions, and subsequent revisions. A model’s existence does not establish that decision-makers saw it before approval. Likewise, an email address on a distribution list does not establish that an attachment was opened or understood.
Record: separate relationship, disclosure, transmission, and acknowledgment events where supported. Assign missing recipient or attachment questions for verification.
Reconcile agendas, packs, attendance, recusals, minutes, committee mandates, votes, and consents. Keep an announced intention, authorization, agreement execution, and closing distinct. Identify whether a committee recommended action or purported to authorize it; inspect the mandate rather than treating those functions as interchangeable.
For Delaware corporations, § 141(f) generally allows board or committee action without a meeting through all members’ written or electronic consent, subject to certificate or bylaw restrictions. Consents must be filed with the minutes after action is taken. Check the full provision and governing documents before determining effectiveness. See 8 Del. C. § 141(f). (delcode.delaware.gov)
Record: the supported action, participating body, authority source, and missing effectiveness evidence. Do not infer a consent merely because signing occurred later.
Read the sequence against each side’s explanation. Does a contemporaneous record contradict a later assertion that alternatives were considered? Could an apparent disclosure gap reflect an uncollected pack? Preserve both possibilities until evidence resolves them.
Avoid labeling a row “cleansed transaction.” Delaware § 144 treats director/officer transactions and categories of controlling-stockholder transactions separately. Its protections depend on the relevant statutory conditions, definitions, exceptions, and applicability—not simply an approval entry. See 8 Del. C. § 144. (delcode.delaware.gov)
Record: contrary sources, the exact unresolved factual question, and a separate legal-analysis assignment. Do not convert a sequence correlation into a conclusion that the challenged act caused the claimed loss.
For important events, identify who could explain the record and whether the proposition rests on firsthand knowledge, reported information, or inference. Federal Rule of Evidence 901 requires evidence sufficient to support a finding that an item is what its proponent claims; knowledgeable-witness testimony is one method. Authentication does not resolve hearsay or other admissibility questions. See Federal Rule of Evidence 901. (uscourts.gov)
Separate factual references from privileged interview impressions and legal analysis. Review mixed business/legal threads and attachments before copying their contents into a broadly circulated chronology. An internal label should not replace counsel’s privilege assessment.
Record: witness links, authentication questions, source limitations, and assigned privilege or access-review tasks.
Sort by supported event time and inspect dependencies: information before deliberation, authorization before execution, and implementation afterward. Review undated entries separately rather than letting them disappear below dated events.
Have a second reviewer trace material propositions to the actual cited records, including attachments and contrary sources. Preserve substantive revision history and identify the source cutoff. Set a review point for later productions or witness accounts; updating remains an assigned task.
Record: corrected citations, resolved discrepancies, and expressly assigned open issues. Release a dated version identifying its internal audience and the limits of the reviewed record set.
Fictional scenario: Marlow Components, Inc., a Delaware corporation, is alleged to have approved an $18 million production-line sale to Cedar Span Holdings. Director Dana Vale allegedly held an ownership interest in the buyer. Counsel must determine what the committee received and which valuation it considered. All parties, documents, amounts, and events below are fictional.
The record contains a circulated pack, draft minutes, a revised valuation, and an execution email. It lacks complete portal activity records, the executed agreement, and records establishing whether additional authorization was required or obtained. The committee’s precise authority remains under review.
| Event ID | Event time / basis | Actor / role | Factual proposition | Decision stage | Source / pinpoint | Contrary evidence / gap | Action / owner |
|---|---|---|---|---|---|---|---|
| E-01 | May 6, 2026, 09:10; email timestamp, zone unverified | Secretary; committee addressees | Sent email attaches pack containing Vale’s ownership disclosure | Disclosure circulation | FIC-014, p. 1; attachment p. 8 | Sending shown; receipt and reading unverified | Associate: seek acknowledgments before attributing knowledge |
| E-02 | May 8, 2026; meeting date reported in draft | Committee | Draft minutes report approval using valuation v3 | Reported approval | FIC-032, p. 2; FIC-041, v4 cover | v4 bears May 7 date; transmission unproved | Counsel: reconcile circulation before alleging v4 was ignored |
| E-03 | May 10, 2026, 16:20; email timestamp, zone unverified | CFO | CFO reports signing sale agreement | Reported execution | FIC-047, p. 1 | Executed agreement and authority records incomplete | Associate: obtain agreement; counsel: check authorization separately |
E-01 supports circulation, not every member’s knowledge. E-02 makes version transmission the next inquiry; an earlier date on v4 does not establish that the committee rejected it. E-03 establishes a signing report, not completed authorization or closing.
The immediate decision is therefore to seek acknowledgments, valuation-transmission records, and authority documents before adopting either side’s account. Missing records remain gaps, not proof that disclosure, consent, or closing never occurred.
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its chronology capabilities can support organizing a document-backed sequence for counsel’s review. Keep source verification, competing-account analysis, and legal characterization with the legal team. The checked chronology can then inform deposition and trial preparation. To assess this workflow against your record set, book a demo.
No. Include communications that establish or materially qualify relevant knowledge, relationships, alternatives, decisions, or consequences. Apply consistent inclusion criteria to favorable and unfavorable evidence. Retain source-inventory references for excluded records so selection remains reviewable.
Use the supported range or competing dates and cite each basis. Separate the meeting, subsequent documentation, and any written-consent process. Assign verification rather than forcing all three into one approval event.
Use them as an attributed account, not an unqualified fact. Record the interview date, asserted event date, and whether the witness describes personal observation or secondhand information. Link corroborating and inconsistent documents, while addressing access and privilege separately.
Not automatically. Federal Rule of Evidence 1006 concerns summaries of voluminous admissible materials that cannot conveniently be examined in court. Originals or duplicates must be available to other parties at a reasonable time and place. Assess its requirements separately; Rule 107 addresses illustrative aids. See Federal Rules of Evidence 1006 and 107. (uscourts.gov)
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.