Wrongful Termination Matters

How to create a claims and defenses evidence matrix for Wrongful Termination Matters

Create a wrongful termination claims and defenses evidence matrix with a copyable template, verified sources, targeted gap analysis, and a fictional example.

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

Create a wrongful termination evidence matrix by separating each asserted claim into verified elements, adding each defense, and linking disputed propositions to favorable evidence, contrary evidence, and missing proof. Record the applicable burden, distinguish source facts from counsel’s inferences, and assign a concrete action for each material gap. The resulting deliverable is a source-linked working table showing which termination theories the reviewed record supports, where the employer’s explanation is contested, and what counsel must verify before relying on the assessment.

When to use this workflow

Use this workflow to assess a potential termination claim, test an employer’s response, or evaluate a discovery record before depositions or dispositive-motion preparation. It serves employee counsel, defense counsel, and in-house teams coordinating investigation with outside counsel.

Treat wrongful termination as a matter category, not a single cause of action. Establish the governing law, statutory coverage, administrative prerequisites, limitations questions, and contractual rights for each proposed theory before entering its elements. Keep discrimination, retaliation, contract, and public-policy analyses separate.

This guide emphasizes US federal district-court litigation. Check state, agency, or arbitral requirements separately rather than importing federal rules. The federal civil rules govern district-court civil proceedings, subject to their stated exceptions. See Federal Rules of Civil Procedure, Rule 1. The matrix is an evidence-analysis tool, not a substitute for a discovery tracker or verified legal analysis.

What you need

Begin with the pleadings or proposed theories, identified defenses, relevant employment agreements, and verified authority for elements and burdens. Record unresolved legal questions instead of borrowing a framework from a different claim.

Assemble the termination notice, approval chain, separation documents, policies and acknowledgments, performance reviews, discipline, improvement plans, attendance records, complaints, investigation materials, and decisionmaker communications. Include agency submissions and other termination explanations when available. For contract theories, include the operative agreement and amendments; for complaint-related theories, identify the complaint, recipients, and timing.

Give documents stable IDs. Preserve page references, attachments, authorship, recipients, and dates. Distinguish event dates, document creation dates, and the effective termination date. Maintain a witness index recording each person’s role and basis of knowledge.

Define the reviewed collection and cutoff. “Not located” after reviewing a personnel file is different from “not located” after reviewing manager communications and HR records. Keep collection limits visible throughout the analysis.

Use the template

Copy the Wrongful Termination Matters — Claims and defenses matrix into your working document or spreadsheet. Use one row per element or defense, with linked subrows for distinct factual propositions. Include challenged employer explanations as analytical subrows, not automatically as affirmative defenses.

Row / theory Element / defense Authority / burden Favorable evidence Contrary evidence Gaps / status Action / owner Assessment / reason

Define whose position “favorable” describes in the table header. Record the forum, review purpose, collection cutoff, and version there as well.

In Authority / burden, identify the governing source, pinpoint, and burden at the present stage. Separate production and persuasion burdens. Cross-reference a legal-authority worksheet where the explanation would overwhelm the cell.

Evidence cells should contain a stable document ID, page or contract-section citation, factual proposition, and necessary date. For testimony, use transcript pages and lines; identify interview notes as notes. Label inferences expressly.

Use Gaps / status for disputed accounts, missing records, collection limits, and foundation questions. Action / owner should identify the next task, responsible person, and review point. Assessment / reason explains significance rather than supplying only a color or strength score.

Step by step

1. Fix the theories, perspective, and review boundary

List claims and defenses without deciding their merits. Specify whether the assignment concerns initial evaluation, a particular production, or readiness for a motion. Record the represented side, forum, relevant employment period, and collection cutoff in the header.

Separate challenges to the employer’s reason from other theories. A contractual notice dispute needs rows tied to the notice provision and communications; it should not inherit a discrimination framework merely because both concern discharge.

Record: stable theory IDs, scope exclusions, and the reviewed evidence boundary.

2. Build rows from verified legal propositions

Enter each element and defense using authority applicable to the claim and forum. Record dependencies such as coverage, decisionmaker knowledge, or operative contract language. Label unresolved standards “legal verification required” and assign counsel to resolve them.

Use pretext authority narrowly. In Reeves, an ADEA disparate-treatment case reviewing judgment as a matter of law, a prima facie case combined with sufficient evidence rejecting the employer’s explanation could permit—not compel—a finding of intentional discrimination. The overall record mattered. The employer’s articulation burden was production, while the ultimate persuasion burden remained with the plaintiff. See Reeves, 530 U.S. 133, 142–149. Do not automatically transfer that framework to retaliation or contract claims.

Record: authority, burden, procedural stage, and unresolved legal dependencies.

3. Map the termination decision to source evidence

Identify who recommended, investigated, approved, communicated, and implemented discharge. Link the stated reason to information available at each decision point; later-produced records do not establish what an approver knew earlier.

Compare the termination notice with internal approvals, agency submissions, unemployment responses, and testimony when available. Record when each reason first appears and who supplied it. Preserve alternative readings: a later explanation may clarify, supplement, or contradict an earlier account.

For complaint-related theories, distinguish evidence that a complaint existed from evidence that a relevant participant received it before acting.

Record: cited decision-sequence facts and competing explanations in separate evidence cells.

4. Test favorable evidence against the strongest contrary account

For every row, identify support and contradiction. A positive review’s significance depends on its date, scope, reviewer, and relationship to the conduct cited for discharge. Test an alleged policy deviation against the applicable policy version, exceptions, and actual approval process.

For comparator evidence, list known similarities and differences: role, supervisor, conduct, timing, decisionmaker knowledge, and disciplinary history. Do not assume shared job titles establish comparable circumstances.

Avoid counting repeated accounts as independent corroboration. Trace forwarded emails and investigation summaries to their original factual source.

Record: both accounts, distinguishing source facts, and expressly labeled inferences.

5. Separate probative value from foundation and use

Identify each important item’s origin, completeness, proposed use, and potential authentication route. Federal Rule 901 requires sufficient evidence to support finding that an item is what its proponent claims; testimony from a knowledgeable witness is one recognized route. Authentication alone does not settle hearsay or other admissibility questions. See Federal Rules of Evidence, Rule 901.

Distinguish signed statements, interview notes, recordings, and deposition testimony. Do not present counsel’s summary of an alleged statement as verified witness testimony. Check whether an excerpt omits attachments or surrounding messages that change its meaning.

Record: foundation questions, completeness concerns, and proposed evidentiary use.

6. Convert gaps into targeted evidence tasks

Replace “need more evidence” with a resolvable question: obtain the approval email and attachments to determine whether HR received the complaint before approving discharge. Identify the likely custodian, source, owner, and review point.

In federal district court, discovery concerns nonprivileged matter relevant to claims or defenses and proportional to the case; information need not be admissible to be discoverable. See Federal Rules of Civil Procedure, Rule 26(b)(1). Explain how a defined comparator population or period addresses the gap instead of requesting unrestricted personnel files.

Cross-reference a request or interview task in the separate tracker; do not expand this matrix into deadline management.

Record: the factual question, targeted action, responsible person, and task reference.

7. Reassess each row without overstating certainty

Classify propositions as supported, contested, unsupported in the reviewed set, or awaiting legal verification. Explain the classification briefly. An absent document does not establish that an event never occurred.

When new material arrives, update affected rows and note which assessment changed. Preserve the prior version so counsel can trace the change to its source. Examine a changed termination explanation’s timing and support without treating the change as an automatic liability conclusion.

Record: current assessment, supporting rationale, revision date, and the next decision it informs.

Worked example

The following parties, documents, and facts are entirely fictional. Cedar Quay Instruments terminated Alex Rowan, a 57-year-old operations analyst, citing repeated reporting errors. Rowan alleges age discrimination. Employee counsel is examining the stated reason; these entries are analytical subrows, not a complete claim-element matrix or a finding that coverage is established.

The reviewed set contains a termination notice, two performance records, a manager email, and a staffing spreadsheet. A favorable review preceded discharge by three weeks. The notice alleges two errors after that review. Counsel lacks the underlying reports, complete approval chain, and proposed comparator’s disciplinary history. The spreadsheet does not establish the other analyst’s age.

Row / theory Element / defense Authority / burden Favorable evidence Contrary evidence Gaps / status Action / owner Assessment / reason
AGE-04 Challenge to stated reason Reeves, 147–149; employee persuasion burden; framework fit pending CQ-014 p. 2 praises reporting accuracy three weeks before discharge CQ-031 pp. 1–2 alleges two later reporting errors Underlying reports absent; occurrence disputed Associate: obtain reports before assessment update Contested; earlier praise does not resolve later alleged errors
AGE-05 Timing of employer explanation Linked to AGE-04; explanation is not itself an affirmative defense CQ-022 p. 1 asks HR to add examples after termination meeting CQ-031 p. 1 already identifies reporting errors Approval attachments absent; prior error review unknown Lead counsel: obtain attachments and question approver Post-meeting request established; fabrication remains an inference
AGE-06 Comparative treatment Claim-specific comparator standard pending verification CQ-045 row 18 records another analyst’s reporting correction Spreadsheet shows neither severity nor disciplinary outcome Age, supervisor, history, and outcome unknown Associate: define targeted inquiry before interview Investigative lead only; unequal treatment not established

The first row redirects counsel toward the later alleged errors rather than treating praise as dispositive. The second supports questions about contemporaneous knowledge, not a conclusion that reasons were invented. The third narrows the inquiry to missing comparison facts; a spreadsheet’s silence about termination is not proof of retention. Missing reports and attachments remain gaps, with no reconstructed contents.

Common mistakes

  • One row for “wrongful termination.” Separate claims, elements, and defenses so the narrative cannot conceal an unsupported requirement.
  • Treating the stated reason as an affirmative defense. Distinguish explanatory evidence from separately pleaded defenses and record each applicable burden.
  • Counting documents as corroboration. Trace repeated manager accounts to their source before assessing independence.
  • Treating changed explanations as conclusive. Compare wording, timing, authorship, and supporting records; preserve clarification and contradiction readings.
  • Declaring comparator equivalence prematurely. Record similarities, differences, and unknowns before assessing comparative treatment.
  • Turning inference into fact. Record “requested examples after the meeting,” not “fabricated reasons,” unless additional evidence supports that inference.

Final quality check

  • Every scoped claim and defense has distinct rows; exclusions are explicit.
  • Authorities, burdens, procedural stages, and jurisdictional fit are verified.
  • Material citations reopen to the correct document and passage.
  • Favorable and contrary cells preserve the strongest supported competing accounts.
  • Event, creation, approval, and effective termination dates remain distinguishable.
  • Source facts, allegations, testimony, and counsel’s inferences are labeled accurately.
  • Collection limits, missing attachments, and foundation questions remain visible.
  • Material open issues are resolved or assigned, and revised assessments identify their supporting source.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, chronology, evidence analysis, and deposition-preparation capabilities can support source comparison and follow-up planning. Use chronology review to examine the decision sequence and trial preparation capabilities to develop witness questions. The matrix is counsel’s work product, not a promised dedicated module. Lawyers verify authorities, assess competing inferences, and decide what the record supports. To discuss this workflow, book a demo.

Frequently asked questions

Should damages appear in the same matrix?

Include separately labeled damages rows when valuation is within scope. Link propositions to payroll, benefits, mitigation, or other relevant records. Do not merge damages proof with liability analysis; otherwise cross-reference a separate assessment.

Can one document support several claims?

Yes. Reuse the stable citation but explain its relevance separately. A manager’s receipt of a complaint may inform knowledge; it does not establish every proposition about motive, causation, or the discharge decision.

How should counsel record missing manager communications?

Identify the custodian, channel, period, and collection searched. State “not located in the reviewed set” and assign a targeted follow-up. A personnel-file search does not establish completeness of the decisionmaker’s communications.

Is the completed matrix an admissible summary?

Not automatically. Federal Rule 1006 concerns voluminous admissible materials that cannot conveniently be examined in court, whether or not introduced, and requires access to underlying originals or duplicates. Purely illustrative aids fall under Rule 107. A legal-analysis matrix does not qualify merely because it summarizes documents. See Federal Rules of Evidence, Rules 1006 and 107.

Sources

Scope: General professional workflow guidance with an October 13, 2026 research cutoff; verify matter-specific law 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