How to create a claims and defenses evidence matrix for Employee Retaliation Matters

Build an employee retaliation evidence matrix by separating each claim element and asserted defense, then linking supporting and contrary evidence to exact source locations. Trace the employee’s activity, each relevant actor’s knowledge, the challenged action, and the employer’s explanation without treating chronology as a liability finding. Record missing proof, competing inferences, and an accountable next step for each unresolved issue. The deliverable is a source-linked working table that helps counsel assess competing theories and direct focused investigation, discovery, and witness preparation.

When to use this workflow

Use this workflow when employment counsel or an in-house team receives a retaliation charge or complaint, completes an initial collection, prepares targeted discovery, or reassesses evidence after interviews. Keep both sides’ accounts visible regardless of whom you represent.

This guide principally addresses US EEO retaliation and federal district-court litigation, not every wage, safety, securities, or other whistleblower claim. Identify the statute, employer category, forum, and controlling authority first. Separately assess exhaustion, timeliness, and other threshold issues. State litigation, arbitration, administrative proceedings, and internal investigations require their own procedural analysis.

The matrix is an evidence-analysis tool, not a liability determination. The steps below are workflow recommendations; cited legal requirements apply only within their stated scope.

What you need

Start with the operative allegations, asserted defenses, relevant policies, and counsel’s issue list. Obtain the employee’s actual complaint rather than relying on an HR label such as “employee concern.” Preserve recipients, attachments, and receipt evidence.

Identify these materials and their collection limits:

• Complaint-channel records, investigation materials, and complaint-transmission communications.
• Performance histories, schedules, compensation records, discipline, and potentially comparable personnel decisions.
• Decision drafts, recommendations, approvals, meeting records, and implementation notices.
• Witness accounts distinguishing firsthand observations, inferences, and secondhand reports.
• A source index containing stable document IDs, pinpoints, custodians, and collection scope.

Maintain event dates, document creation dates, and collection dates separately in that index, including time zones where material. A later memorandum describing an earlier event is not contemporaneous evidence of that event. Keep sensitive personnel information and counsel’s analysis within appropriate access controls.

Use the template

Use the Employee Retaliation Matters — Claims and defenses matrix below. You can copy this table into your working document or spreadsheet. Stable row IDs preserve references when rows move.

Create separate rows for applicable elements and asserted defenses. Split causation into subrows where actor-specific knowledge or decision timing needs independent analysis. Distinguish an employer’s denial or alternative explanation from a separately asserted affirmative defense.

“Supporting evidence” supports the proposition stated in that row, not necessarily your client. Cite document ID and page, message, paragraph, or testimony lines. Put the governing test and authority reference in the third column; maintain longer legal analysis separately.

Use “Gap / assessment” for a specific uncertainty and its significance, not a percentage chance of success. The action field names the task and owner. Status should distinguish source verification from legal assessment: a verified email can support a disputed inference.

Step by step

1. Define the claims and applicable tests

List each alleged protected activity and challenged action by statutory claim. Separate actions whose actors, dates, or explanations differ. Confirm the applicable substantive and procedural standards before assessing the evidence.

The EEOC distinguishes participation from opposition and describes a reasonable, good-faith belief requirement for opposition. Its guidance is nonbinding; verify the statute and controlling decisions rather than treating every workplace grievance as protected (EEOC guidance, section II.A). (eeoc.gov)

Record: Element and defense rows, authority references, and assigned legal-research questions. Keep factual concessions separate from conclusions about legal protection.

2. Map the alleged protected activity precisely

Read the original complaint, message, charge, or account. Identify its content, asserted right, recipient, channel, and acknowledgments. Do not replace the employee’s words with an investigator’s characterization.

For an alleged oral complaint, separate testimony about content from evidence that a meeting occurred. A calendar entry may establish the latter without establishing the former. Preserve competing accounts and identify whether a later summary came from the speaker, recipient, or another person.

Record: Activity pinpoints, the asserted participation or opposition theory, and gaps about content, receipt, or context. Assign retrieval of originals or recipient interviews.

3. Trace knowledge through individual actors

Identify the supervisor, HR recipient, influential recommender, approver, and implementer. Trace when each allegedly learned of the activity and how information moved between them. Do not equate organizational receipt with universal awareness.

The EEOC identifies decisionmaker or influential-recommender awareness, timing, inconsistent explanations, and comparative evidence as relevant to causation—not automatic proof (EEOC guidance, section II.C). (eeoc.gov)

Record: Actor-specific knowledge subrows with dates and transmission evidence. Label inferred knowledge and competing accounts. An unsuccessful email search describes collection results; it does not exclude oral communications.

4. Reconstruct the challenged decision and explanation

Separate initiation, recommendation, approval, communication, and implementation. Compare these milestones with activity and knowledge dates. Preserve earlier proposals and test whether their scope changed after the complaint.

Describe the alleged harm concretely. The EEOC’s material-adversity analysis asks whether conduct could deter protected activity, considering context; apply the governing law to the actual consequences (EEOC guidance, section II.B). (eeoc.gov)

Identify each employer explanation and its records. For comparators, document the relevant decisionmaker, conduct, timing, policies, and differences that affect the comparison.

Record: Action and explanation rows, decision milestones, contrary documents, and disputed effects. Identify the source of each explanation and when it was given.

5. Test competing inferences rather than count documents

Assess what each source proves. Multiple messages repeating one account are not necessarily independent corroboration. A single contemporaneous draft may change the analysis substantially.

Write the strongest competing account beside your inference. If performance concerns predate the complaint, ask whether they explain this action and timing. If explanations changed, identify the exact differences and whether they are substantive.

The EEOC explains that but-for causation does not require retaliation to be the sole cause, while distinguishing standards across claims and employer categories. Verify the applicable standard (EEOC guidance, section II.C). (eeoc.gov)

Record: A provisional assessment, supporting reasoning, and the missing fact most likely to change it.

6. Convert material gaps into focused evidence requests

Prioritize gaps that could change an element or defense assessment. Replace “get more emails” with custodians, dates, subject matter, and purpose. Distinguish uncollected records, unanswered questions, withheld material, and records whose existence is uncertain.

In federal district court, Rule 26(b)(1) permits discovery of nonprivileged matter relevant to claims or defenses and proportional to the case; discoverability does not require admissibility. Apply case-specific orders and the actual forum’s rules (Federal Rules of Civil Procedure, Rule 26). (uscourts.gov)

Record: A targeted request or interview question, owner, priority, and expected analytical effect. Keep discovery-response administration in a separate tracker.

7. Verify foundations and reconcile the matrix

Open decisive sources and verify pinpoints, context, completeness, and attribution. Identify potential authentication witnesses and distinguish personal knowledge from inference. Federal Rules of Evidence 901 and 602 address these separate foundations; an exhibit link alone establishes neither (Federal Rules of Evidence). (uscourts.gov)

Reconcile inconsistent dates and descriptions across rows. Preserve unresolved contradictions rather than replacing them with the preferred account. Have another reviewer test the strongest adverse evidence and assess distribution restrictions before circulation.

Record: Verification status, foundation gaps, reviewer, and unresolved assignments. Retain a dated version showing the record available at that stage.

Worked example

Fictional scenario: Mara Voss works for fictional Alder Basin Services, a private employer. Counsel is assessing an alleged Title VII retaliation claim involving removal from premium weekend shifts after a complaint that promotions favored men. All parties, records, dates, and facts are fictional.

An April 8 complaint email reached HR. An April 10 message forwarded it to the scheduling supervisor. A March 29 staffing draft proposed rotating several employees away from weekends, but its approval history is unavailable. The April 15 roster removes only Voss. A subsequent employer position memo attributes the change to coverage needs. An HR note instead characterizes her complaint as scheduling dissatisfaction.

The following are three representative rows, not the complete matrix. Authority references use the verified EEOC sections above pending controlling-law analysis.

The earlier draft weakens a simple “complaint, then punishment” narrative without proving that Voss’s removal was already decided. The narrower final roster directs investigation toward why a general rotation became a single-employee change.

The HR characterization does not override the original email. Nor does forwarding prove that the supervisor read it before deciding. Each uncertainty produces a different follow-up task.

Add a separate material-adversity row addressing shift value and practical effects. Compensation records are missing: do not invent lost earnings or assume the change was inconsequential. Likewise, do not label the coverage explanation an affirmative defense merely because it supports the employer.

Common mistakes

• Treating every grievance as protected. Preserve the actual language and research the applicable protection.
• Equating HR receipt with supervisor knowledge. Trace transmission and distinguish receipt, reading, and inference.
• Using implementation as the only decision date. Examine recommendations, approvals, and later changes.
• Mixing propositions within one row. An earlier proposal concerns decision development, not necessarily lack of knowledge; place evidence accordingly.
• Treating absent records as established facts. State search scope and collection limits before drawing an inference.

Final quality check

• Each claim element and asserted defense has a distinct, clearly framed row.
• Governing tests match the statute, employer category, and forum.
• Decisive sources have been opened and pinpoints verified.
• Knowledge assessments identify actors, dates, and transmission evidence.
• Supporting and contrary evidence address the same proposition.
• Decision milestones and alleged practical consequences are separately documented.
• Foundation questions, confidentiality concerns, and collection limits are identified.
• Material open issues are resolved or assigned with concrete next steps.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its verified document review, evidence analysis, privilege and confidentiality analysis, chronology, and deposition preparation capabilities can support this assessment. Use the chronology viewer for timing analysis and trial preparation capabilities as evidence gaps become witness questions. The matrix remains counsel’s work product; lawyers retain legal judgment and source-verification responsibility. To assess this workflow with your documents, book a demo.

Frequently asked questions

Should each challenged action have its own rows?

Yes, when actors, dates, explanations, or alleged harm differ. A warning and termination may share documents without sharing a decision history. Cross-reference common evidence rather than collapsing the assessments.

How should counsel record uncertain oral complaints?

Identify the speaker, alleged recipient, approximate date, account source, and disputed wording. Separate evidence of the conversation from evidence of its content. Never present reconstructed wording as a verbatim quotation.

Does close timing establish causation?

Treat timing as evidence to assess, not a completed finding. Compare verified activity, knowledge, and decision dates with competing explanations under the applicable standard; the EEOC discusses timing among several causation considerations (section II.C). (eeoc.gov)

Can the matrix itself be used as evidence?

Not automatically. Rule 1006 addresses summaries of voluminous admissible materials and access to underlying records. Rule 107 separately addresses illustrative aids, which are not evidence. Determine the intended use and applicable requirements before creating a courtroom version (Federal Rules of Evidence). (uscourts.gov)

Sources

• EEOC, Enforcement Guidance on Retaliation and Related Issues — nonbinding agency interpretation, particularly sections II.A–C.
• Federal Rules of Civil Procedure — Rule 26(b)(1), federal discovery scope.
• Federal Rules of Evidence — Rules 602, 901, 1006, and 107.

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.