Securities Disclosure Disputes

How to create a claims and defenses evidence matrix for Securities Disclosure Disputes

Create a securities disclosure claims and defenses evidence matrix linking statements, contrary evidence, speaker knowledge, source citations, and proof gaps.

October 17, 2026  ·  10 min read
Book a Demo →

Create a securities disclosure evidence matrix by breaking disputed disclosures into statement-specific propositions, mapping each proposition to the applicable claim or defense, and linking supporting and contrary evidence with precise citations. Keep pleading sufficiency separate from merits proof, and distinguish information the company possessed from information a particular speaker demonstrably knew. The deliverable is a working table showing which propositions have support, which depend on inference, and which require legal research or permissible evidence development before use in a brief or examination.

When to use this workflow

Use this workflow when a complaint, dismissal motion, production, or witness account changes the evidence surrounding an issuer’s disclosures. It serves outside counsel organizing contested propositions and in-house teams coordinating factual investigation across disclosure versions, internal reporting, and individual decision-makers.

The orientation is US private Exchange Act litigation in federal district court. Confirm the pleaded claims, controlling appellate authority, local rules, operative orders, and historically applicable disclosure requirements. Federal procedure and evidence rules do not automatically govern state litigation, arbitration, or SEC administrative proceedings. The steps below are organizational recommendations, not a universal elements-and-defenses checklist.

What you need

Start with the operative pleadings and counsel’s issue list. Assemble challenged statements in context: original filings, amendments, earnings releases, presentation slides, call transcripts, and incorporated materials. Preserve accession identifiers and distinguish prepared remarks from analyst-question responses.

Identify disclosure-committee materials, forecast versions, accounting workpapers, board packets, auditor communications, investor-relations drafts, and approval histories. List possible sources even when uncollected; do not imply unavailable materials were reviewed.

Obtain discovery and preservation restrictions, production indexes, witness accounts, and existing legal research. Maintain a separate, access-controlled evidence inventory for provenance and privilege decisions. The matrix should link to that inventory rather than reproduce every collection detail or protected communication.

Use the template

The companion template is Securities Disclosure Disputes — Claims and defenses matrix. You can copy this table into your working document or spreadsheet. Use one row for each testable proposition about a particular disclosure, not one row for an entire cause of action.

Row / statement ID Disclosure / pinpoint Proposition / authority Support / witness Contrary evidence Knowledge / timing Gap / status Action / owner

Assign stable row and statement IDs. The disclosure field identifies wording, speaker, publication date, and location. The proposition field states what counsel is testing, identifies the claim or defense, and links to legal research labeled by procedural posture.

Evidence cells need document IDs, page, paragraph, or spreadsheet-cell references, and relevant witnesses. Timing distinguishes creation, circulation, receipt, and publication. Use explanatory statuses such as “receipt unverified” rather than unexplained scores. Give each open action an owner; link longer reasoning, admissibility questions, and reviewer decisions to a row-specific note.

Step by step

1. Define the propositions and legal questions

Break each disclosure into propositions evidence could support or contradict. A renewal-rate statement may need separate rows for metric definition, underlying data, speaker knowledge, and the asserted explanation. Identify whether a defense row tests an affirmative defense or rebuts a plaintiff’s proposition.

For covered private Exchange Act complaints, Section 78u-4(b)(1) requires statement-specific allegations explaining misleadingness and particularized supporting facts for information-and-belief allegations. Subsection (b)(2)(A), where applicable, requires particularized facts supporting a strong inference of the required state of mind. These are pleading requirements, not a complete liability test. See 15 U.S.C. § 78u-4(b)(1)–(2).

Record: statement ID, factual proposition, claim or defense, procedural posture, and authority-note reference. Assign unresolved legal questions rather than treating them as settled.

2. Establish the disclosure actually at issue

Preserve the original public source and surrounding qualifications. Identify whether the allegation concerns a number, definition, omission, or period comparison. Keep drafts separate from published versions and amendments separate from originals. For oral remarks, distinguish the recording from any corrected transcript.

For Form 10-K disclosures, inspect relevant incorporated documents. General Instruction G permits specified incorporation by reference under stated conditions, so the annual-report text may not be the complete source set. Use the instructions applicable to the registrant and disputed period; incorporation does not establish substantive accuracy. See SEC Form 10-K, General Instruction G.

Record: public-source ID, accession identifier where available, speaker, release date, pinpoint, and incorporated-source dependencies.

3. Trace internal facts to particular people

Follow the internal fact through circulation, escalation, drafting, and publication. A forecast’s creation date does not establish when a speaker received it. An emailed attachment may differ from a workbook stored elsewhere, and access permission does not establish actual review.

Separate demonstrated receipt from inference. Identify whether a witness personally observed an event, heard about it, or reconstructed it later. Preserve conflicting accounts. Before treating internal and public figures as inconsistent, compare reporting periods, included business units, metric definitions, and version histories.

Record: source pinpoints, demonstrated recipients, timestamps and time zones, witness basis of knowledge, and each inference’s limits. Link separate rows where the same document bears differently on different speakers.

4. Build the opposing account alongside the supporting account

For every proposition, identify evidence that weakens it. Consider different reporting boundaries, intervening developments, revised assumptions, and incomplete attachments. Test defenses equally: a plausible explanation is not a verified factual account.

Distinguish affirmative contradiction, failure of reviewed evidence to establish a proposition, and evidence not yet obtained. These conditions require different responses. Silence in a partial production does not establish that an event never occurred. Where a defense depends on a qualification, examine its actual wording and placement rather than summarizing it as adequate caution.

Record: contrary sources, competing interpretations, reviewed scope, and what the record establishes. State why a competing explanation remains viable or requires further testing.

5. Convert gaps into permissible evidence-development tasks

Write a narrow task for each material gap: locate the circulated workbook, verify a recipient’s receipt, or reconcile a public metric with its source data. Distinguish preservation, authorized internal review, and proposed discovery.

In covered private Exchange Act actions, Section 78u-4(b)(3) stays discovery and other proceedings during a pending dismissal motion. A court may authorize particularized discovery necessary to preserve evidence or prevent undue prejudice. During the stay, the preservation provision reaches allegation-relevant materials in the custody or control of parties with actual notice, unless otherwise ordered. See 15 U.S.C. § 78u-4(b)(3).

When federal discovery is available, assess relevance, privilege, and proportionality under Rule 26(b)(1).

Record: missing proof, proposed source, authorization dependency, owner, and next decision. Do not invent a deadline or assume a gap permits discovery.

6. Evaluate source usability separately from persuasiveness

Retain native files, metadata, collection records, and document-family relationships. Identify a witness or other basis for establishing what an item is; assess its proposed use separately from the inference counsel draws.

Evidence Rule 901 requires evidence sufficient to support finding that an item is what its proponent claims. Authentication does not independently resolve hearsay, relevance, or other objections. Flag potentially protected materials for separate privilege review rather than copying legal advice into widely circulated cells.

Record: provenance reference, authentication question, intended use, and unresolved evidentiary or privilege review in the row-specific note. Do not reduce these questions to a single evidence-strength rating.

7. Review the matrix against its intended use

Before using the matrix for a motion, examination, or settlement assessment, have a second reviewer open the cited sources and challenge the reasoning. Check that legal research addresses the correct claim and procedural posture; a dismissal-stage holding should not silently become a merits-proof standard.

An internal matrix is not automatically admissible. Rule 1006 separately governs summaries offered to prove the content of voluminous admissible materials that cannot conveniently be examined in court, with underlying originals or duplicates available to other parties. Rule 107 addresses illustrative aids. See Federal Rules of Evidence, Rules 1006 and 107.

Record: reviewer disposition, intended use, remaining limitations, and responsibility for updating affected rows.

Worked example

The parties, documents, dates, figures, and wording below are entirely fictional.

Oriole Sensor Systems reported on February 18, 2025, that its annual customer renewal rate remained 92%. Investors allege unresolved cancellations made the statement misleading. Counsel has the CFO-delivered release, two internal workbooks, an email describing an earlier transmission, and an interview memorandum, but not the transmission’s attachment.

Workbook F-02 calculates 86% across all service plans. F-03 calculates 92% for annual subscriptions, the category identified in the release’s footnote. Both predate publication, but circulation is unverified. The email says a cancellation analysis was sent to the CFO; the record does not establish its contents or receipt. The interview memorandum records a sales manager’s concerns without identifying the period.

Row / statement ID Disclosure / pinpoint Proposition / authority Support / witness Contrary evidence Knowledge / timing Gap / status Action / owner
M-01 / S-01 F-01 release, p. 2; CFO; Feb. 18, 2025 92% inaccurate; merits; L-01 unresolved F-02, Total!B18: 86% F-03, Annual!C22: 92%; F-01 n. 1 limits category Workbooks predate release; circulation unknown Different populations; contradiction unestablished Analyst: reconcile populations before relying on comparison
M-02 / S-01 F-01, p. 2; CFO; Feb. 18, 2025 CFO knew conflicting data; pleading/merits separate; L-02 open F-04 email, p. 1: analysis described as sent None identified; absence does not establish receipt Described transmission predates release; attachment missing Contents, receipt, and review unverified Counsel: assess permitted inquiry and stay before seeking attachment
M-03 / S-01 F-01, p. 2 n. 1; CFO; Feb. 18, 2025 Rebuttal: annual-subscription boundary; L-01 open F-03, Annual!C22; category footnote F-05 interview memo, ¶ 8: cancellations recalled Recollection lacks period and subscription type Category explanation provisional; cancellation treatment unresolved Interview lead: clarify period, population, and firsthand basis

The comparison does not yet establish falsity: 86% and 92% describe different populations. The email supports investigating a transmission, not concluding the CFO knew a particular calculation. The next work is population reconciliation, attachment identification, and witness clarification. Even if the populations explain the numerical difference, counsel still needs to test whether annual-subscription cancellations were properly included. The matrix narrows the inquiry without deciding liability.

Common mistakes

  • One row per claim: This hides differences among statements and speakers. Split claims into testable, disclosure-specific propositions.
  • Company possession equals speaker knowledge: Record demonstrated transmission, receipt, and review separately from inference.
  • Unlike metrics labeled contradictory: Reconcile denominator, period, business boundary, and version first.
  • Only favorable documents recorded: Require contrary evidence and preserve conflicting accounts instead of silently reconciling them.
  • Unavailable evidence labeled nonexistent: Identify the reviewed scope and distinguish incomplete collection from affirmative proof.
  • Discovery tasks assigned without authorization: Record the stay or order and permissible method before proceeding.

Final quality check

  • Each proposition identifies the disclosure, speaker, date, and pinpoint.
  • Evidence citations open to the correct document and location.
  • Drafts, public versions, amendments, and incorporated materials remain distinguishable.
  • Support, contrary evidence, and counsel’s inferences are separately identified.
  • Knowledge assertions identify the person, timing, and demonstrated basis.
  • Authority matches the claim, forum, procedural posture, and relevant period.
  • Open issues are resolved or assigned with an explicit next decision.
  • Intended use, access restrictions, and evidentiary questions are recorded.

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 this work. Use chronology analysis for timing questions and trial preparation for evidence and witness preparation. The matrix remains counsel’s work product: lawyers verify citations, test competing inferences, and determine legal significance. To discuss this workflow, book a demo.

Frequently asked questions

Should pleading and merits analysis share a row?

They may share sources, but label assessments separately. Factual support does not itself answer pleading sufficiency. Split the row when combined notes obscure the distinction or the relevant legal standards differ.

How should we record an alleged omission?

Identify the public statement or disclosure location, allegedly missing fact, and legal question about disclosure. Link evidence of timing and availability. Do not infer a disclosure obligation merely because internal information existed.

What belongs in a loss-related row?

State the precise proposition being tested. Link relevant disclosures, price data with source and measurement period, and competing explanations. Keep observed movements separate from causal conclusions; assign unresolved legal and expert-analysis questions.

When should we update the matrix?

Update affected rows after new productions, transcript corrections, clarified accounts, amended pleadings, or material research developments. Preserve prior assessments and explain changes by reference to new evidence or reasoning, not merely a revised status.

Sources

Scope: this guide uses the supplied October 13, 2026 research cutoff; confirm historical disclosure instructions and matter-specific authorities separately.

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.

Run this workflow in DecoverAI

Clause-quoted findings, missing-language flags, and tracked changes in your name — with your team deciding every call. Plans from $299 per seat per month, SOC 2 Type II certified.

Book a demo
to learn more.
Book a Demo