Build a shareholder-dispute chronology by separating each disputed corporate event into a dated proposition, linking it to a specific document passage, and recording contrary evidence and unresolved gaps. Start with ownership, voting authority, disclosures, approvals, and money movements—not merely the order in which emails arrived. The deliverable is a source-linked working chronology that distinguishes documented facts from reported or inferred events, preserves competing accounts, and assigns targeted follow-up. Counsel can use it to test the narrative and prepare witnesses without treating the chronology itself as proof.
Use this workflow when outside counsel or an in-house legal team must reconstruct a contested share issuance, stockholder consent, board approval, related-party transaction, dividend, or exclusion from corporate decision-making. A concrete trigger is a mismatch between formal corporate records and contemporaneous communications, ownership records, or payment evidence.
Define the disputed transaction and relevant period before reviewing the entire corporate history. Include earlier events where they explain ownership, authority, disclosures, or relationships material to the dispute.
This guide uses US litigation practice with Delaware corporate-law illustrations. Confirm entity type, incorporation, governing instruments, forum, and historically applicable law. Federal rules do not govern every state proceeding or arbitration; Delaware corporation provisions are not nationwide shareholder-dispute rules. This is an organizational workflow, not a determination of liability or corporate validity.
Collect an initial source set addressing corporate authority and what actually happened:
Identify records that are available, withheld, missing, or merely described elsewhere. Inspection materials are not necessarily a complete litigation production. Delaware § 220 specifies inspection categories and purpose-related requirements, including good faith, proper purpose, reasonable particularity, and records specifically related to that purpose. Categories have differing temporal limits and conditions for additional records. Check the applicable statutory version before treating an inspection gap as an entitlement to more documents. See 8 Del. C. § 220.
The companion template is Shareholder Disputes — Case chronology. Copy this table into your working document or spreadsheet. Give each event a durable ID that survives sorting and later insertions.
| Event ID | Date / basis | Event / actors | Issue / phase | Source / pinpoint | Status / conflict | Gap / next action | Owner / state |
|---|---|---|---|---|---|---|---|
“Date / basis” distinguishes the asserted event date from the date a document recorded it. Use a range or “unknown” where necessary. “Issue / phase” connects the event to a disputed question and identifies negotiation, authorization, execution, delivery, payment, or accounting.
“Source / pinpoint” contains a stable document ID plus the page, paragraph, message timestamp, or spreadsheet tab and cell range. “Status / conflict” distinguishes a directly documented event from a report, inference, or contested proposition. Documentary support does not make an event undisputed.
The last two fields make uncertainty actionable: identify the missing evidence, verification task, responsible person, and current state. Link related events by ID. Maintain provenance and version details in a supporting source register rather than overloading each chronology row.
Write an issue list before extracting dates. In a dilution dispute, ask when ownership changed, who had voting authority, what consideration was proposed, and when approvals and disclosures occurred. In a related-party payment dispute, separate authority to enter the arrangement from payment and the recipient’s benefit.
Do not encode disputed legal classifications as facts. “Controller transaction approved” assumes too much; “minutes record approval of a contract with the founder’s alleged affiliate” identifies a testable proposition. Assign controller status, standing, and direct-versus-derivative classification for separate legal analysis.
Record: an issue code and phase for each initial row, with a gap entry where the necessary event is undocumented.
Assign document IDs before building narrative entries. Preserve existing production numbers and connect internal IDs to them. Record the custodian, collection source, version, and attachment relationships in the source register.
Treat draft minutes, adopted minutes, and later corrections as distinct sources. A later packet reproducing a resolution does not, by itself, establish when it was adopted. An updated capitalization table may also describe a transaction retrospectively.
Keep counsel’s legal assessments identifiable and restrict access appropriately. Do not label the entire chronology privileged merely because lawyers prepared it; separately assess protection and intended recipients before circulation.
Record: exact source IDs and pinpoints, with version or provenance limitations in “Status / conflict.”
Create one row per consequential event. An email may report an earlier vote, transmit an agreement, and request payment. Those are separate propositions with potentially different dates and evidentiary strength.
Distinguish event time, document creation, transmission, and later recollection. Preserve time zones where hours matter. If a witness recalls approval “the previous week,” retain the range and identify the interview source rather than choosing a date.
Use neutral descriptions: “treasurer instructed bank to transfer funds” is narrower than “company paid.” Check completion against bank evidence; an accounting posting date need not be the payment date.
Record: date and basis, actors, precise event, and whether the source directly documents or merely reports it.
Build the voting sequence from record-date ownership, share classes, voting rights, proxies, consent versions, delivery proof, revocations, and notices. Link denominator calculations to reproducible working papers. Preserve competing calculations when ownership is contested.
For Delaware stockholder consents, § 228 permits action without a meeting subject to the certificate and statutory conditions. Sufficient signed consents must be delivered in the required manner within 60 days of the first qualifying delivery. Signature dates alone do not establish effective action. Examine record dates, delivery methods, notice, and transaction-specific requirements. See 8 Del. C. § 228.
Keep board authorization distinct from stockholder action; neither should be assumed to replace the other.
Record: separate signing, transmission, qualifying delivery, and claimed effective-action rows where material. Identify missing evidence rather than supplying an assumed approval date.
For every material proposition, seek the strongest contrary source. Minutes may describe unanimous approval while a director’s contemporaneous message denies attendance. Preserve both rather than collapsing them into a reconciled sentence.
Compare what each source establishes, its timing and provenance, and the author’s basis of knowledge. Neither formality nor contemporaneity automatically resolves a conflict.
Identify potential foundation witnesses without treating that identification as an admissibility determination. Federal Evidence Rule 901 requires sufficient evidence that an item is what its proponent claims; knowledgeable-witness testimony is one method. Authentication does not itself resolve hearsay or other objections. See Federal Rules of Evidence, Rule 901.
Record: both source pinpoints, the precise contradiction, and a targeted verification action.
Prioritize gaps that could change the sequence or its significance: an absent consent attachment, disputed delivery timestamp, missing pre-vote valuation, or unexplained difference between approved and transferred amounts.
Instead of “obtain all finance records,” identify the bank confirmation and ledger support for a particular transfer. In federal district-court litigation, Rule 26(b)(1) limits discovery to nonprivileged matter relevant to claims or defenses and proportional to case needs. Chronology usefulness alone does not establish discoverability. See Federal Rules of Civil Procedure, Rule 26(b)(1).
Record: the missing source or witness question, why it matters, the responsible lawyer, and next review point. Keep procedural deadlines in the separately verified matter calendar.
Read by event date, then by issue. The first review exposes sequence problems; the second reveals unsupported assumptions across scattered rows. Open every material source and confirm the pinpoint supports the proposition.
Retain substantive revision history. New delivery evidence may replace an inferred date, but preserve why the entry changed. Prepare witness-facing or external versions separately from internal assessments.
A working chronology is not automatically an evidentiary summary. Federal Evidence Rule 1006 addresses summaries of voluminous admissible materials that cannot conveniently be examined in court and requires access to underlying originals or duplicates. Purely illustrative aids are addressed by Rule 107. See Federal Rules of Evidence, Rules 1006 and 107.
Record: verified status or an expressly assigned open issue for every material row, together with the version’s review date.
Fictional scenario: Counsel represents a minority stockholder of fictional Alder Quay Devices, Inc., a Delaware corporation. The dispute concerns a $640,000 purchase from fictional Bellwick Components LLC, allegedly owned by Alder Quay’s founder. All parties, documents, amounts, and document language below are fictional.
Unsigned draft minutes recite board authorization of a purchase up to $600,000 on February 4, 2026. A stockholder consent PDF bears February 7 signature dates. An outgoing email dated February 11 addresses that PDF to the corporate secretary. A February 10 bank record shows a $640,000 debit naming Bellwick. Counsel lacks the operative charter, complete voting and delivery files, and purchase agreement.
These three representative entries each address one event; the signature-date proposition requires its own linked row in the full chronology.
| Event ID | Date / basis | Event / actors | Issue / phase | Source / pinpoint | Status / conflict | Gap / next action | Owner / state |
|---|---|---|---|---|---|---|---|
| EV-01 | Feb. 4, 2026; draft recital | Board reportedly authorized purchase up to $600,000 | Authority / authorization | F-D01, p. 2, ¶3 | Unsigned draft; adoption unverified | Obtain adopted minutes and packet; test authorization scope | Counsel A / open |
| EV-02 | Feb. 11, 2026; outgoing timestamp | Sender transmitted consent PDF to secretary’s address | Voting / transmission | F-D03, 9:14 a.m. message; attachment F-D02 | Transmission shown; receipt and qualifying delivery unproved | Check delivery file, charter, ownership, and voting rights | Counsel B / open |
| EV-03 | Feb. 10, 2026; bank transaction date | Company account debited $640,000; Bellwick named | Funds / payment | F-D04, p. 1, transaction 18 | Debit shown; $40,000 above amount recited in draft | Obtain agreement, amendments, recipient confirmation, and ledger support | Counsel A / open |
The sequence redirects follow-up from a general approval narrative to two concrete questions: whether sufficient consents were delivered before the debit and what explains the amount difference. The outgoing email does not establish receipt or exclude an earlier delivery. Nor does the draft establish an adopted spending limit. Counsel should therefore avoid describing the debit as unauthorized or the consent as ineffective. Founder ownership, ultimate benefit, and the legal significance of any stockholder action remain separate unresolved questions.
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, evidence analysis, chronology, and privilege and confidentiality analysis capabilities can support review of the shareholder-dispute record. Explore the chronology viewer and trial preparation capabilities, while retaining lawyer verification of sources, dates, and inferences. To assess the workflow against your document set, book a demo.
Only if incorporation-era provisions or ownership events matter. Otherwise, begin with the earliest event needed to explain the contested authority, disclosure, vote, or transaction.
Record that minutes were not supplied, not that no meeting occurred. Seek notices, packets, participant communications, and witness accounts, preserving each source’s limitations.
It may support transmission or receipt. Evaluate qualifying delivery, voting power, the governing instruments, and applicable requirements separately; do not substitute an email date for that analysis.
Yes. Link them to the proposition they undermine and identify the conflict. Excluding adverse evidence makes the chronology unreliable for witness preparation and factual 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.