Product
Analyze
Review
Produce
Draft
Solutions
Litigation
- Early Case Assessment
- Investigations & Subpoenas
- Trial Preparation
- Enterprise eDiscovery
- Cloud eDiscovery
Transactional
Who it’s for
Resources
Learn
Customers
Events & CLE
Create a claims and defenses evidence matrix by breaking each disputed harassment theory into factual propositions, then linking supporting evidence, contrary evidence, and missing proof to stable source citations. Separate alleged conduct from employer attribution, notice, corrective action, tangible employment actions, and damages. Record governing authority and an assigned verification task for each unresolved proposition. The resulting working table shows counsel what the record supports, which defenses remain conditional, and what targeted evidence could change the assessment.
When to use this workflow
Use this workflow when employment counsel evaluates a complaint, receives an investigation file, reviews a production, or prepares focused discovery. It serves claimant counsel, defense counsel, and in-house teams coordinating outside counsel. Evidence classifications should remain neutral regardless of representation.
The substantive discussion uses the Title VII framework, not a universal harassment test. Federal discovery and evidence rules apply within their respective scope, not automatically to state litigation, arbitration, administrative proceedings, or internal investigations. Confirm applicable substantive law, controlling precedent, coverage, administrative prerequisites, and limitation periods separately. This is a general professional workflow, not advice about a particular matter.
What you need
Assemble the operative allegations, asserted defenses, policy versions, reporting channels, organizational records, and available evidence. Include messages, hotline records, interview materials, schedules, training acknowledgments, investigation records, employment decisions, and claimed-loss documentation.
Identify complainant, accused, witness, HR, management, and IT custodians, with relevant date ranges and collection gaps. Obtain evidence of the accused person's actual decision authority, not merely a title.
Use stable document IDs and page, paragraph, message, or transcript references. Maintain a linked chronology distinguishing incident date, reporting date, document creation date, and collection date. Label estimates and competing accounts.
Prepare an authority list for the theories actually asserted. Record its jurisdiction and pinpoint references; do not import elements from a generic checklist without checking applicability.
Use the template
The companion template is Workplace Harassment Matters — Claims and defenses matrix. You can copy this table into your working document or spreadsheet. Use one testable proposition per row, with linked rows for distinct components of a claim or defense.
| Row ID | Issue / authority | Proposition | Supporting proof | Contrary proof | Missing / uncertain | Assessment | Action / owner |
|---|---|---|---|---|---|---|---|
Issue / authority identifies the element, attribution question, or defense component and governing reference. Proposition states a factual assertion rather than “hostile environment established.” Both proof columns require precise source citations and a description of what the source establishes.
Missing / uncertain captures disputed dates, incomplete collections, and unresolved interpretations. Assessment explains the provisional conclusion and its limits; avoid unexplained numerical confidence scores. Action / owner states the verification task, responsible reviewer, and review date. Use row IDs to link related issues without collapsing them. Keep sensitive analysis in an access-controlled working version.
Step by step
1. Define the theories before assessing proof
Translate each asserted theory and defense into factual propositions. Separate protected-basis connection, unwelcome conduct, severity or frequency, context, employer attribution, tangible employment actions, notice, corrective measures, and claimed harm. Keep separately asserted retaliation theories distinct.
The EEOC describes hostile-environment harassment as sufficiently severe or pervasive and considers the entire record and incident context. Its overview is expressly under review and is not a complete statement of elements. Ordinary workplace mistreatment is not automatically unlawful harassment. Confirm the controlling test rather than using incident counts as a substitute. EEOC — Harassment
Record: Initial proposition rows, applicable authority, and unresolved legal questions. Include separate rows for subjective experience and objective context where the governing test requires them.
2. Identify the employer-attribution framework
Determine the accused person's authority during the relevant period. Examine delegations, approval practices, and actual employment decisions, including whether recommendations effectively determined outcomes.
For Title VII vicarious liability, Vance defines a supervisor by employer-conferred power to take tangible employment actions against the affected employee. Where supervisor harassment culminates in a tangible employment action, the prevention-and-correction affirmative defense is unavailable. Without such an action, that defense requires both reasonable employer care to prevent and promptly correct harassment and the employee's unreasonable failure to use available preventive or corrective opportunities or otherwise avoid harm. Policy possession alone proves neither component. Vance v. Ball State University, majority opinion, 570 U.S. 421, 424, 429–431 (2013)
For nonsupervisory employees or controlled nonemployees, the EEOC describes liability involving actual or constructive knowledge and failure to take prompt, appropriate corrective action. Keep this separate from supervisor vicarious liability. EEOC — Employer liability
Record: Conditional attribution rows and separate defense components, identifying what evidence would resolve the applicable framework.
3. Link conduct evidence without manufacturing corroboration
Read surrounding messages, attachments, and original versions. Capture alleged words or behavior accurately, with evidence connecting the conduct to the asserted protected basis. Identify what each witness personally observed and what came from another person.
Three records repeating one report are not three independent observations. Conversely, a witness who heard nothing may have had little opportunity to observe. Preserve that limitation alongside the account rather than treating it as a categorical contradiction.
Connect related incidents through row IDs and the chronology. Assess the alleged pattern without erasing individual evidentiary weaknesses or assuming every workplace disagreement belongs in it.
Record: Supporting and contrary citations, knowledge sources, observation opportunities, disputed context, and uncertain dates.
4. Reconstruct notice and corrective action separately
For each notice event, identify recipient, content, date, reporting route, and evidence of receipt. Distinguish sending a message from establishing what a recipient learned.
Trace escalation, interim measures, interviews, findings, discipline, and follow-up. Compare documented responses with later reported incidents. A scheduled interview does not establish a completed investigation; an absent outcome document does not establish that no action occurred.
Where an affirmative defense is potentially available, examine reporting-channel accessibility and implementation. Preserve explanations for delayed reporting or bypassing a channel without deciding their reasonableness prematurely.
Record: Linked notice and response rows, implementation evidence, recurrence allegations, and the limits of any provisional defense assessment.
5. Test competing accounts and claimed consequences
Challenge each assessment with the strongest contrary source. Identify whether a conflict concerns occurrence, interpretation, timing, personal knowledge, or completeness. Preserve original witness materials separately from counsel's synthesis.
Create distinct rows for employment consequences and losses. Link schedules, decision records, compensation materials, and relevant testimony to the precise assertion supported. Keep tangible-action analysis separate from damages: the same record may matter to both without answering either question completely.
Do not infer motive or causation from timing alone. State alternative explanations and identify evidence capable of distinguishing them.
Record: The competing account, its evidentiary basis, the unresolved inference, and the verification task most likely to affect the decision.
6. Turn material gaps into focused evidence tasks
Prioritize gaps that could change the assessment. Define the factual question before selecting a document request, interview, or deposition topic. Uncertain reporting-channel implementation might justify relevant training records and testimony about routing practices, not every HR communication.
In federal civil discovery, Rule 26(b)(1) confines discovery to nonprivileged matter relevant to claims or defenses and proportional to case needs. Information within that scope need not be admissible to be discoverable. Apply those limits and applicable orders when translating gaps into requests. Federal Rules of Civil Procedure, Rule 26(b)(1)
Record: Target source, factual purpose, owner, priority, and review date. Cross-reference any separate discovery tracker rather than turning this matrix into a deadline calendar.
7. Verify source usability and revise assessments
Reopen material citations and check surrounding text. Identify an authentication route and potential hearsay or other admissibility questions for proposed exhibits. Federal Evidence Rule 901 requires sufficient evidence to support a finding that an item is what its proponent claims; authentication does not resolve other objections. Federal Rules of Evidence, Rule 901
Separate routine HR records from legal-advice communications for individual protection analysis. Do not assume that counsel's participation or a privilege label resolves the issue. Flag whether proposed reliance on an investigation requires further privilege or waiver analysis.
Record: Verification status, source-usability questions, revised assessment, and assigned open issues. Preserve a dated prior version when new evidence materially changes the analysis.
Worked example
Fictional scenario: Mara Vale alleges that shift lead Owen Pike repeatedly made sex-based remarks at Harbor Loom Services. The employer says HR responded promptly and Mara should have used its hotline earlier. Owen assigned daily stations, but the collected file does not establish his tangible-employment-action authority.
The fictional file contains partial chat exports, an HR ticket, three interview notes, an organizational chart, and a station-assignment sheet. All parties, events, documents, and citations below are invented. These three representative rows are not a complete merits assessment.
| Row ID | Issue / authority | Proposition | Supporting proof | Contrary proof | Missing / uncertain | Assessment | Action / owner |
|---|---|---|---|---|---|---|---|
| H-01 | Conduct / confirm controlling test | Owen made repeated sex-based remarks | CHAT-014, p. 2: one attributed remark; INT-003, ¶4: witness recalls two occasions | INT-005, ¶6: another witness heard none during shared shifts | Earlier thread absent; dates and observation opportunities unclear | Some support; accounts may overlap; frequency unresolved | Review lead: obtain thread and clarify witness dates |
| H-02 | Attribution / Vance, 424, 431 | Owen could take tangible employment actions | ORG-002, p. 1 and SCH-009, p. 3 show lead role and assignments, not tangible-action power | INT-006, ¶8: manager says personnel decisions required her approval | Delegations and actual decision records absent | Status unresolved; title and assignments insufficient | Employment counsel: examine approval and authority records |
| H-03 | Corrective response / applicable framework unresolved | HR's measures addressed reported conduct | HR-011, pp. 1, 3: receipt and scheduled interview show response initiation only | CHAT-021, p. 1: Mara alleges another remark afterward | Interview outcome, measures, and follow-up not collected | Effectiveness unresolved; later allegation not independently verified | Review lead: obtain response records and test recurrence account |
The matrix changes the next decision. Counsel should not treat potentially overlapping accounts as proof of separate incidents, select supervisor liability from Owen's title, or characterize a scheduled interview as an effective remedy. Authority records, complete message context, and the response trail have higher decision value than accumulating more copies of the same report. The missing outcome remains a collection gap, not proof that HR did nothing.
Common mistakes
- Using claim labels as facts. Replace “harassment proved” with propositions about conduct, context, protected-basis connection, and the applicable test.
- Combining employer defenses. Separate attribution, notice, corrective action, and each affirmative-defense component; state conditional dependencies.
- Counting repetition as corroboration. Trace knowledge sources and distinguish independent observation from retelling.
- Treating policy existence as implementation. Examine accessibility, training, reporting practices, and actual responses.
- Equating missing records with missing events. Record collection limits and seek alternative evidence before drawing conclusions.
Final quality check
- Each row states a testable proposition under an identified theory.
- Authority fits the jurisdiction and liability framework.
- Material citations have been reopened and checked in context.
- Supporting and contrary evidence include knowledge limitations.
- Dates, duplicate accounts, and independent observations remain distinguishable.
- Attribution and defense assessments identify unresolved dependencies.
- Material gaps are resolved or assigned to a named owner.
- Sensitive analysis and proposed exhibits are separated, with usability questions recorded.
Complete the workflow with DecoverAI
DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use its chronology capabilities to examine event sequence alongside counsel's matrix, and connect evidence gaps to deposition preparation. Document review, evidence analysis, and privilege and confidentiality analysis can support the underlying review. Lawyers retain responsibility for legal relevance, competing accounts, and citation verification. To discuss this workflow, book a demo.
Frequently asked questions
Should claims and defenses share one matrix?
Usually. A shared source may support a claim proposition while undermining a defense. Use separate linked rows for distinct propositions, with explicit cross-references rather than unexplained duplication.
What if supervisor status remains disputed?
Keep alternative attribution frameworks open. Separate title, delegated authority, recommendations, and actual decisions. Do not treat the supervisor defense as available merely because the employer calls the accused a manager.
Should investigation materials appear in the matrix?
Use source references in a restricted working version where appropriate. Assess protection individually and determine what can be circulated before sharing. Do not assume every investigation record is privileged or that every factual reference can be disclosed safely.
Can the matrix become a trial exhibit?
Not automatically. Rule 1006 permits summaries of voluminous admissible materials that cannot conveniently be examined in court, subject to access requirements for underlying originals or duplicates. Purely illustrative aids fall under Rule 107. Evaluate any proposed exhibit separately from counsel's analytical matrix. Federal Rules of Evidence, Rules 1006 and 107
Sources
- EEOC — Harassment: agency overview, expressly under review.
- Vance v. Ball State University — majority opinion: Title VII supervisor status and vicarious-liability framework.
- Federal Rules of Civil Procedure: Rule 26 discovery scope.
- Federal Rules of Evidence: authentication, summaries, and illustrative aids.
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.
