A document-backed fraud chronology connects each alleged statement or omission to what was known, communicated, decided, and lost—and identifies the evidence for each connection. Build it around discrete events, stable document references, and clearly identified date types, not a narrative copied from pleadings. Link representations to contemporaneous records, recipient decisions, contrary evidence, and unresolved gaps. The deliverable is a sortable chronology that counsel can verify against sources and use to test allegations, direct targeted follow-up, and prepare witnesses without presenting inference as established fact.
Use this workflow when commercial litigation counsel or an in-house team must reconstruct disputed disclosures in an acquisition, investment, financing, or supplier relationship. Triggers include allegations of inflated revenue, concealed customer losses, or communications contradicting pre-closing assurances.
Start with the disputed representations and relevant commitment dates. Expand backward to contemporaneous knowledge and forward to discovery of the alleged fraud and claimed loss. Keep the chronology focused on disputed issues rather than the entire business relationship.
This guide uses a US practice orientation. The cited procedural rules govern federal district-court civil litigation; state litigation and arbitration require their own procedural analysis. Federal evidence rules also have applicability limits. Identify governing substantive law, local rules, and case orders before assigning legal significance to events. See the Federal Rules of Civil Procedure and Federal Rules of Evidence.
Gather the operative allegations and responses, transaction documents, disclosure versions, and records surrounding the business decision. For alleged revenue inflation, relevant inputs may include customer communications, CRM history, invoices, credits, ledgers, board presentations, diligence questions, and data-room access records.
Obtain native files and metadata where available, complete threads and attachments, production identifiers, and collection information. Record missing custodians, unavailable versions, and limitations in access logs. Check whether a searchable PDF preserves the information needed to establish spreadsheet revisions or recipients.
Prepare an issue list identifying each disputed statement, alleged omission, speaker, recipient, actual decisionmaker, commitment, and loss theory. Flag integration, nonreliance, exclusive-remedy, and fraud-carveout wording for separate governing-law analysis. Keep the chronology’s factual descriptions distinct from conclusions about those provisions.
The companion template is Business Fraud Disputes — Case chronology. Copy this table into your working document or spreadsheet. Use one row per event; repeat citations when one document supports several distinct events.
| Event / statement ID | Date / type / zone | Actor → recipient | Event / wording | Source / pinpoint | Issue / decision link | Status / contrary evidence | Gap / owner / action |
|---|---|---|---|---|---|---|---|
Assign stable event IDs such as E001 and separate statement IDs such as S01. A statement ID groups related knowledge, communication, and decision events; it does not mean every linked event contains the statement. Sorting must not change identifiers.
The date field identifies creation, sending, receipt, transaction, or discovery. Retain original timestamps and zones; label conversions separately. Split events into additional rows when different dates or actors matter.
The source field identifies the document, Bates number or internal ID, and page, paragraph, worksheet cell, or message location. Distinguish source-supported facts, disputed assertions, inferences, and unknowns in the status field. Assign a concrete next action and owner in the final field. Maintain the source inventory and version history alongside the table rather than overcrowding each row.
List alleged statements or omissions before extracting dates. Identify each speaker, recipient, subject, reporting period, and allegedly influenced decision. For omissions, ask neutrally what information existed, who possessed it, and what was disclosed before commitment. Keep the asserted disclosure duty as a separate legal question.
Map issues to the selected law. New York’s Connaughton decision describes fraud elements encompassing false representation or material omission, knowledge, inducement, justifiable reliance, and injury. Its damages analysis concerns New York law at the pleading stage, not a nationwide rule. See the opinion, pages 6–9.
Record: statement IDs and issue links in the table; place the chosen time window and assigned legal questions in its accompanying notes.
Create a source inventory before merging events. Preserve production identifiers and original filenames; assign internal IDs to unnumbered records. Connect attachments to parent messages and distinguish drafts from sent versions. Keep duplicate copies traceable without counting them as independent corroboration.
Inspect provenance limitations. Determine whether a CRM export contains historical changes and whether a forwarded email preserves original recipients. Identify a possible authentication route, such as a knowledgeable witness or supporting system records. Rule 901(a) requires evidence supporting a finding that an item is what its proponent claims. Authentication does not itself resolve other admissibility questions. See Federal Evidence Rule 901.
Record: source pinpoints, version relationships, provenance concerns, and the owner responsible for resolving them.
Separate drafting, approval, sending, receipt, and later discovery. A presentation dated April 8 does not establish April 8 delivery. Treat data-room upload and decisionmaker access as different events.
Use only the precision supported by the source. If a witness recalls “the week before signing,” record that range and attribution, not an invented day. Identify the interview date separately. Preserve original timestamps, document conversions, and retain conflicting dates with an explanation of what each system records.
Split compound events when actors, timing, or evidentiary support differ. Attribute allegations in pleadings and recollections in interviews rather than allowing them to become unmarked contemporaneous facts.
Record: event IDs, date types, original zones, supported precision, and unresolved sequencing in the relevant fields.
For each statement ID, connect wording, contemporaneous knowledge, delivery, recipient understanding, decision, and claimed loss. Preserve necessary language and surrounding qualifications. Determine whether contrary internal information predated the statement and which individuals received it; avoid equating one employee’s knowledge with every participant’s knowledge.
Rule 9(b) requires particularity for circumstances constituting fraud while permitting knowledge and intent to be alleged generally. This is a federal pleading rule, not a substitute for evidence or substantive elements. See Federal Civil Rule 9(b).
Record: statement links, actual decisionmakers, commitment dates, knowledge evidence, and missing connections. Keep authorization, signing, funding, and closing separate where supported.
Review warnings, diligence responses, alternative motivations, revised forecasts, and contract wording alongside favorable records. Ask whether the recipient knew the relevant information before commitment and whether the assurance addressed the same customer, reporting period, and degree of certainty as the contrary evidence.
Distinguish material available from material delivered, accessed, or discussed. Separate a customer’s notice from when executives learned of it and when finance revised its forecast. Test claimed loss against later operational developments without treating later deterioration as proof of earlier falsity.
Where sources conflict, preserve competing accounts rather than selecting the helpful one or averaging incompatible dates.
Record: adverse citations, competing interpretations, the disputed factual connection, and evidence needed to resolve it.
Convert material gaps into specific tasks: retrieve a missing attachment, identify the board-pack version reviewed before authorization, or obtain a forecast revision history. Link each task to the disputed statement and decision it could clarify. For witness follow-up, identify whether the question concerns firsthand observation, organizational information, or inference.
Rule 26(b)(1) limits federal discovery to nonprivileged matter relevant to claims or defenses and proportional to the case; information need not be admissible to be discoverable. See Federal Civil Rule 26(b)(1). Apply that scope rather than treating every interesting gap as a production demand.
Record: requested evidence or question, relevance, owner, and limitation. Keep privileged analysis separately controlled under counsel’s privilege and access decisions.
Have a reviewer reopen every source supporting a material event. Check quotations, qualifiers, recipients, date types, and pinpoints. Reconcile later productions without silently overwriting earlier interpretations. Record what changed, why, and which event IDs are affected.
State the released version’s purpose: internal analysis, witness preparation, or proposed presentation. Keep theories distinct from factual descriptions. Rule 1006 permits evidentiary summaries of voluminous admissible materials that cannot conveniently be examined in court, whether or not those materials are introduced. It requires underlying originals or duplicates to be available to other parties at a reasonable time and place. A working chronology is not automatically such a summary. See Federal Evidence Rule 1006.
Record: verification status and assigned open issues in the table; version date, reviewer, and intended use in accompanying notes.
Fictional scenario: Alderbridge Holdings purchased Quayline Analytics’ assets for $12 million, closing June 20, 2025. Alderbridge alleges concealment of an impending major-customer loss. All parties, documents, amounts, dates, and wording below are invented.
A June 4 deck predicted renewal by the five largest customers. A June 2 internal message reported one customer’s intention not to renew. June 12 investment committee minutes nevertheless discussed possible loss of that customer and authorized the acquisition. The original customer notice, deck delivery records, and committee financial model have not been located. These are three representative entries, not the complete chronology.
| Event / statement ID | Date / type / zone | Actor → recipient | Event / wording | Source / pinpoint | Issue / decision link | Status / contrary evidence | Gap / owner / action |
|---|---|---|---|---|---|---|---|
| E001 / S01 | June 2, 2025; sent; 09:14 EDT | Sales lead → CFO | Reports customer plans not to renew | QAY-000214, message 1 | Possible knowledge preceding S01 | Internal report established; original customer wording unknown | Associate: obtain notice and complete thread to test certainty |
| E002 / S01 | June 4, 2025; document date; delivery unknown | CFO listed as presenter; recipients unknown | “All five largest customers are expected to renew” | QAY-000330, slide 8 | Alleged assurance before commitment | Forecast wording; E001 potentially inconsistent; delivery unproved | Paralegal: locate sent deck and recipient records to establish communication |
| E003 / S01 | June 12, 2025; meeting date; time unknown | Investment committee, internal | Discusses possible customer loss; authorizes purchase | ALD-000078, p. 3 | Pre-closing knowledge and decision | Challenges uninformed-purchase account; model assumptions unknown | Counsel: obtain model and question decisionmaker about risk assessment |
The sequence changes counsel’s next task. The deck cannot yet be described as a proven communication causing an uninformed purchase. Delivery is unverified, and the minutes show awareness of some risk. But “possible loss” does not establish knowledge of a definite nonrenewal. Counsel should determine what decisionmakers understood, whether the deck influenced their assessment, and which financial assumptions supported authorization.
The $12 million price is not a calculation of fraud loss. Add separately sourced events addressing the claimed economic consequence and competing explanations. Do not reconstruct missing evidence of intent, reliance, or loss from the allegation alone.
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use its chronology capabilities alongside document review, privilege and confidentiality analysis, and evidence analysis to support this workflow. Connect verified events and exhibits to trial preparation. Counsel retains responsibility for source verification, legal significance, and conflicts. To discuss your team’s chronology and review needs, book a demo.
Not necessarily. Begin early enough to test the speaker’s contemporaneous information. A preceding customer notice or forecast revision may matter more than months of general negotiations. Set the boundary by disputed issues, not document volume.
Record affirmative facts: information received, a disclosure circulated, a diligence question asked, or a response delivered. Describe the allegedly missing disclosure separately. Test other communications before inferring nondisclosure; assign any disclosure-duty question to governing-law analysis.
Use attributed entries with ranges and uncertainty. Identify the interview date separately from the recalled event and specify corroboration sought. Distinguish firsthand observation from inference or secondhand reports, and preserve conflicting recollections rather than combining them into certainty.
Maintain one controlled factual chronology with visible contrary evidence. Task-specific presentation versions can select relevant events, but should reconcile to the same IDs and sources. Review omissions and sequencing before using any presentation version with witnesses or externally.
Scope: General professional workflow guidance, using authorities applicable to the October 13, 2026 assignment cutoff; not advice for 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.