# Compare Employment Discrimination Complaint Against Personnel File Records

> Guides defense counsel through a systematic cross-check of factual allegations in a complaint against personnel records, HR investigation materials, and compensation data, producing a structured discrepancy analysis.

- Skill: `finchipaiorg/compare-employment-discrimination-complaint-against-personne` (Agent Skill)
- Install (CLI): `npx get-skill add finchipaiorg/compare-employment-discrimination-complaint-against-personne`
- Raw SKILL.md: https://api.skillmd.com/api/skills/finchipaiorg/compare-employment-discrimination-complaint-against-personne/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: FinchipAIOrg (https://skillmd.com/u/finchipaiorg)
- Updated: 2026-11-11
- Page: https://skillmd.com/skills/finchipaiorg/compare-employment-discrimination-complaint-against-personne

---


# Skill: Compare Employment Discrimination Complaint Against Personnel File Records

## 1. Subject-matter triage
- Treat the complaint, personnel file, HR investigation report, compensation summary, and internal complaint email as a single source set for one integrated factual comparison.
- Identify whether the matter implicates discrimination, retaliation, hostile work environment, compensation disparity, or performance-management issues, because each theory turns on different factual anchors.
- If the record contains multiple comparators, time periods, or alleged adverse actions, enumerate them before analysis and keep each comparison separate.

## 2. Failure modes the skill is correcting
- Analyst summarizes the complaint at a high level instead of extracting and verifying each factual allegation one by one against the record.
- Analyst treats the HR investigation narrative as conclusive without checking the underlying personnel materials that confirm, refine, or contradict it.
- Analyst builds separate timelines for protected activity, performance management, and adverse action rather than one integrated chronology.
- Analyst characterizes a pay issue as material or immaterial without using the compensation records to compute the comparator baseline and the plaintiff’s relative position.
- Analyst states that meetings occurred or were missed without counting the actual attendance and documenting the source for each entry.
- Analyst stops at “consistent/inconsistent” labels without explaining how the discrepancy affects defense posture, credibility, causation, or pretext.
- Analyst relies on legal conclusions without identifying the governing doctrine that makes the discrepancy significant.

## 3. Legal frameworks / domain conventions that apply
- Allegation-by-allegation comparison: each factual assertion in the complaint should be tested against documentary support, contradiction, or partial corroboration.
- Retaliation sequencing: the order of protected activity and adverse action matters; the analysis should flag whether the complained-of action occurred before, after, or long after the protected event.
- Disparate-treatment and compensation analysis: where pay disparity is alleged, compare the plaintiff to the identified comparator group using the compensation records, not the complaint’s characterization alone.
- Pretext analysis: inconsistencies between the stated reason for an action and the documentary record, deviations from ordinary process, and differential treatment may support pretext under the applicable anti-discrimination statute and burden-shifting framework.
- Evidence hierarchy: personnel records, dated emails, investigation notes, and compensation summaries generally provide stronger factual anchors than narrative allegations.
- Governing authority should be named whenever a legal proposition is invoked, including the relevant anti-discrimination statute, retaliation provision, evidence rule, or burden-shifting doctrine relied on in the memo.

## 4. Analytical scaffolds
- Extract every discrete factual allegation from the complaint and assign it a unique reference number before comparing it to the records.
- For each allegation, identify the best source document, then classify the result as consistent, inconsistent, or partially consistent.
- For each inconsistency, state what the record shows, what the complaint says, and why the difference matters to the defense.
- Build one integrated chronology covering hiring, performance events, complaints, investigations, compensation changes, and adverse actions; use source dates and preserve sequence.
- For any compensation issue, identify the comparator set, then calculate the actual comparison from the records and compare it to the complaint’s stated disparity.
- For any performance-management issue, count the relevant meetings, attendance, missed sessions, warnings, or milestones from the source documents and compare those counts to the allegation.
- For each issue, close the analysis by tying the discrepancy to scale or magnitude, the related source document or event that it interacts with, and the downstream litigation consequence.
- If only one comparator, one time period, or one adverse action is in scope, say so expressly; otherwise, analyze each item separately and do not collapse distinct comparisons into one pass.

## 5. Vertical / structural / temporal relationships
- Preserve the vertical relationship between allegation, source document, and litigation significance; do not present isolated facts without linking them back to the pleaded theory.
- Preserve temporal relationships across protected activity, investigation, performance intervention, and discipline; sequence can change whether an event is merely adverse or plausibly retaliatory.
- Preserve cross-document relationships where the complaint conflicts with the personnel file but is partially explained by the HR investigation or email record.
- When one document updates or qualifies another, note whether it narrows, expands, or contradicts the alleged event.
- If the complaint alleges a pattern over time, chart the progression rather than analyzing events as disconnected snapshots.

## 6. Output structure conventions
- Write the result as a privileged discrepancy analysis memorandum.
- Open with a short executive summary identifying the most material factual disputes and why they matter.
- Use a table or equivalent structured format for each allegation: Complaint Allegation | Source Document | Consistent / Inconsistent / Partially Consistent | Defense Significance.
- Include a standalone chronology that integrates all relevant events in order.
- Include a compensation comparison section when pay is at issue, showing plaintiff compensation, comparator compensation, computed comparison from the records, and the complaint’s stated gap.
- Include a performance or attendance comparison section when the complaint relies on meetings, warnings, or completion status.
- For each material discrepancy, state the governing authority or doctrinal lens that makes the issue significant.
- End with a concise Recommended Actions block that assigns each step to a responsible role and ties it to the next litigation milestone or internal deadline.
- Keep the tone privileged, defense-oriented, and document-driven; avoid advocacy slogans and avoid restating allegations without testing them against the record.

