whistleblower / retaliation investigation — methodology
whistleblower retaliation is not a routine hr dispute. it is an ethics hotline report (Navex/EthicsPoint export) followed by adverse employment action — pip, demotion, transfer, or termination — often paired with unauthorized case dismissal across ethics, employee relations, and hrsd platforms. your job is to preserve multi-system exports before retention windows expire, prove the timeline from report to action, and document who closed cases without authority before counsel or regulators ask why NAV-2026-0312 disappeared while E-22901 got demoted.
what evidence exists and how fast it dies
| artifact | volatility | time to loss |
|---|---|---|
| Navex / EthicsPoint / Allvoices hotline export | persistent if exported | vendor retention 3–7 years; admin can purge earlier |
| ethics case audit log (status + actor) | rolling in platform | 90–365 days unless legal hold |
| HCM job / compensation change audit | persistent in hcm | varies by tenant; some fields overwrite on rehire |
| HR Acuity investigation export | persistent if exported | case archive policies differ by org |
| ServiceNow HRSD case + task history | rolling | retention tied to sn instance config — often 1–3 years |
| reporter identity token / deanonymization log | highly sensitive | access logged; improper lookup is its own finding |
| manager email / chat re: reporter | rolling in mail archive | 30–90 days to years depending on ediscovery hold |
the first 10 minutes
- issue legal hold on ethics, hcm, hr acuity, and servicenow hrsd — before anyone “cleans up” case status.
- export the hotline report by case id — do not rely on dashboard screenshots.
- pull ethics audit log for status changes, dismissals, and reassignment on the report date forward.
- export hcm employee history for the reporter id — job code, title, manager, compensation effective dates.
- pull HR Acuity investigation by employee or case number linked to the ethics report.
- export ServiceNow HRSD tickets referencing the same employee or er case id.
- record who requested exports and utc timestamps — chain of custody starts here.
- do not deanonymize the reporter without counsel — improper identity access is retaliation evidence too.
- notify compliance / board audit committee if the report category is sox or financial fraud.
- begin the path below.
the path
1. navex ethics hotline export forensic analyzer
Navex / EthicsPoint hotline csv export. parses report id, category, reporter token, status transitions, and assigned investigator across the ethics queue.why first: the hotline record is the anchor — every retaliation claim starts with when the report was filed and who touched it before adverse action.
2. ethics retaliation pattern detector
ethics event timeline csv. flags pip, demotion, transfer, and termination events inside the post-report retaliation window — e.g. pip and hcm demotion within 17 days of NAV-2026-0312.why second: adverse employment action timing is the prima facie signal — map it before you chase dismissal metadata.
3. ethics unauthorized case dismissal detector
ethics audit and dismissal event export. surfaces closes by non-investigator accounts, missing approval chains, and audit tamper rows — svc-hr-ethics-admin from 198.51.100.55 in the morgan bundle.why third: a dismissed ethics case is not a resolved ethics case. unauthorized close is often the cover-up, not the conclusion.
4. cross ethics hcm retaliation correlator
paired ethics + hcm exports. links hotline report timestamps to job-code changes, title demotions, and compensation adjustments on the same employee id.why fourth: ethics and hcm live in different systems — correlation proves the employment action followed the report, not a scheduled review cycle.
5. hr acuity investigation export forensic analyzer
HR Acuity investigation csv. parses case id, allegation type, investigator, status, and close reason — ER-22901 premature close without findings in the fixture.why fifth: employee relations runs parallel to ethics — acuity holds the formal investigation record counsel will subpoena.
6. cross er hrsd case correlator
paired HR Acuity + ServiceNow HRSD exports. correlates ER case ids to HRSD ticket numbers — ER-22901 ↔ HRSD-884 in morgan.why sixth: er and hrsd tickets split across platforms — link them before you accept “case closed” on either side.
7. servicenow hrsd case export forensic analyzer
ServiceNow HRSD case export csv. parses case state, task history, assigned group, and close actor — flags unauthorized resolution from non-hrsd admin accounts.why seventh: hrsd is where hr ops closes the loop — premature close from an ethics admin ip is a separate artifact from the acuity investigation.
8. case report generator
structured case report form + evidence file hashes. assembles examiner, dates, findings, and manifest inputs into a court-ready report pdf.why last: board, counsel, and regulators want one narrative — generate it after the cross-system timeline is stable.
common false leads
- performance pip predates the report — check effective dates; backdated pips after hotline filing are common.
- ethics case closed means resolved — unauthorized dismissal by hr admin is closure without investigation.
- er and hrsd are duplicate records — they often diverge; one closed prematurely while the other still open.
- reporter was not demoted — title and job-code changes in hcm may not match what the employee sees on the org chart.
- hotline report was anonymous so no retaliation possible — deanonymization access logs and manager timing still matter.
- adverse action was “business restructuring” — correlate headcount events against individual reporter id, not department averages.
what we can tell you, what we can't
we can tell you:
- hotline report metadata and status transition timelines from navex exports
- retaliation-window hits — pip, demotion, transfer clusters after report date
- unauthorized case dismissal patterns — actor, ip, missing approval chain
- cross-system correlation between ethics reports and hcm employment actions
- HR Acuity investigation lifecycle and premature close indicators
- ER ↔ HRSD case linkage and inconsistent close states
- structured case report assembly with evidence file hashes
we can't tell you:
- whether retaliation was legally proven — that is counsel, agency, or court territory
- reporter identity from anonymous reports without your authorized deanonymization export
- live platform state — we analyze exports you provide, not vendor apis
- manager intent or “pretext” quality — artifacts show timing; interviews show motive
- guaranteed regulatory outcome — osha, sec, or state whistleblower statutes vary by jurisdiction
handing it off
- employment counsel: cross-system timeline csv, unauthorized dismissal findings, hcm action dates, case report pdf with evidence hashes.
- compliance / audit committee: hotline case summary, ethics admin actors, sox-category escalation if applicable.
- outside forensic / ediscovery: full platform exports under legal hold, export chain of custody, and tool outputs as json/csv attachments.
- regulatory agency (if referred): representative ethics + hcm + er/hrsd export set, timeline of adverse action relative to report date — not conclusory labels.
further reading
reference investigation
synthetic fixture morgan-whistleblower-retaliation — Morgan Industries anonymous Navex report NAV-2026-0312 on billing fraud, unauthorized dismissal by svc-hr-ethics-admin from 198.51.100.55, pip and HCM demotion on E-22901 within 17 days, HR Acuity ER-22901 and ServiceNow HRSD-884 closed without resolution. seed morgan-whistleblower-retaliation:v1. compare output via npm run check:flagship.
fixture download: evidence zip · proof page: /forensics/proof/morgan-whistleblower-retaliation · case playbook: case type tools