Extract Key Allegations From Employment Discrimination Complaint

---
name: extract-key-allegations-from-employment-discrimination-complaint
task_id: employment-labor/extract-key-allegations-from-employment-discrimination-complaint
description: Guides preparation of a structured allegation summary memorandum for an employment discrimination complaint, covering the asserted counts, alleged incidents, comparators, timing issues, and damages categories.
activates_for: [planner, solver, checker]
---

# Skill: Extract Key Allegations from Employment Discrimination Complaint

## 1. Subject-matter triage

- Treat the complaint as the core pleading, but read it alongside the right-to-sue letter, client email, handbook excerpt, and org chart to identify timing, exhaustion, policy, reporting, and decision-maker issues.
- Identify every count and every theory pleaded or fairly implied; do not stop at the headline discrimination label.
- Separate discrete adverse actions from hostile-work-environment allegations and retaliation theories, because they often carry different timing and proof rules.
- If the source set shows only one actionable theory, say so expressly; otherwise enumerate all theories before analyzing them.

## 2. Failure modes the skill is correcting

- Analyst extracts allegations for the primary discrimination count but omits parallel counts that may independently affect exposure.
- Analyst identifies incidents without testing which ones fall within the administrative charge period, and without assessing whether any earlier acts may be swept in by a continuing-violation theory.
- Analyst states damages exposure qualitatively without mapping the alleged claims to the correct remedies, statutory caps, and potentially uncapped categories.
- Analyst misses statements by supervisors, HR, or final decision-makers that may function as direct evidence and alter the ordinary burden-shifting analysis.
- Analyst summarizes the plaintiff’s story without isolating comparators, reporting chain, policy references, and temporal sequencing that defense counsel needs for response planning.

## 3. Legal frameworks / domain conventions that apply

- Title VII, ADA, ADEA, and analogous state or local anti-discrimination statutes may appear together; extract the governing statute for each count before analyzing it.
- Administrative exhaustion and charge timing are controlled by the applicable statute and right-to-sue process; use the charge filing window stated or implied in the materials, and note any ambiguities.
- Under National Railroad Passenger Corp. v. Morgan, discrete acts are ordinarily time-barred if outside the filing period, while hostile-work-environment allegations may use the continuing-violation doctrine when related acts straddle the window.
- Under McDonnell Douglas Corp. v. Green, comparator treatment, prima facie elements, and employer explanations matter when the complaint relies on circumstantial proof.
- Direct evidence analysis turns on whether the alleged statement or act is attributable to a supervisor or decision-maker and tied to the challenged action.
- Damages analysis should distinguish back pay, front pay, compensatory damages, punitive damages, liquidated damages, and attorney’s fees, and apply the governing statute’s cap structure where applicable.
- For ADEA claims, damages treatment is materially different from Title VII-style compensatory/punitive remedies; do not assume the same exposure model.
- Handbook excerpts may create policy, reporting, discipline, accommodation, or leave issues that affect both liability and defense themes; org charts may clarify authority, comparators, and causation.

## 4. Analytical scaffolds

- Count-by-count extraction: for each count, identify the statute, protected characteristic or activity, adverse action, causation theory, and the facts pleaded to support each element.
- Timeline extraction: list every specific incident in chronological order, using the source documents to capture date, actor, conduct, and the count or theory it supports.
- Filing-window screening: for each incident, determine whether it falls inside or outside the applicable administrative window and whether the complaint pleads facts supporting a continuing-violation theory.
- Comparator mapping: extract each comparator named or fairly described, including role, reporting line, relevant conduct or performance, and alleged differential treatment.
- Decision-maker mapping: identify each supervisor, manager, HR participant, or officer linked to the challenged action; note who recommended, approved, executed, or learned of the event.
- Direct-evidence screening: flag any alleged statement that can plausibly be read as discriminatory or retaliatory animus and identify the speaker’s authority.
- Policy and process overlay: compare the allegations against the handbook and org chart to surface discipline, reporting, accommodation, leave, escalation, or approval mismatches.
- Remedies extraction: identify each damages category pleaded or implied and map it to the statute governing the claim.

## 5. Vertical / structural / temporal relationships

- For each incident, note whether it precedes, follows, or coincides with protected activity, protected status disclosure, complaint escalation, performance criticism, discipline, leave request, or termination.
- Track whether the same actor appears across multiple incidents, because repeated involvement may support motive, knowledge, or pretext themes.
- Track whether different actors occupy the same supervisory level or different levels in the org chart, because that may affect comparator relevance and attribution.
- Distinguish one-off decisions from recurring conditions; repeated assignments, schedule changes, exclusions, or comments may support a pattern theory even when no single event is severe.
- When the complaint references “similarly situated” employees, compare role, supervisor, work rules, timing, and discipline history rather than relying on job title alone.
- If the right-to-sue letter or charge date is provided, anchor the chronology to that date and identify the practical litigation significance of any timing gap.

## 6. Output structure conventions

- Write as an allegation summary memorandum for defense counsel, not as a client-facing narrative.
- Lead with a concise executive overview: counts pleaded, core factual themes, timing posture, and likely defense pressure points.
- Use a count-by-count format. For each count, include:
  - governing statute or cause of action;
  - elements plausibly alleged;
  - key incidents and actors;
  - comparators or differential-treatment allegations;
  - timing/exhaustion issues;
  - direct-evidence or circumstantial-proof issues;
  - damages or remedy implications.
- Include a standalone incident chronology table with columns such as: Date | Actor | Conduct Alleged | Theory/Count | Timing Status | Significance.
- Include a comparator table if comparators appear in the materials, with columns such as: Comparator | Role/Reporting Line | Alleged Similarity | Alleged Favorable Treatment | Defense Relevance.
- Include a remedies table that separates uncapped and capped categories and identifies the governing statute or rule for each claim.
- If the source materials are silent on a point, say “not stated in the materials” rather than inferring.
- Close with a short recommended-actions section for defense counsel that prioritizes preservation, timing review, comparator verification, and policy-based fact development.
- Use only the conventional section shapes needed for the memo; do not mimic the source rubric’s internal checklist language.