Investigations
An ELR investigation is a fact-finding inquiry into alleged misconduct, policy violation, safety incident, or threat — anything where the workspace needs an objective record before deciding on discipline or other corrective action. The Investigation file holds the scope, the witness interview log, the documentary evidence, the findings memo, and the discipline recommendation in a single chain of custody.
TL;DR — Open ELR → Investigations → New investigation. State the scope, list the witnesses, run interviews from the file, attach evidence as you collect it, write a findings memo, recommend discipline (if any). The file is the discoverable record if the matter is ever litigated.
Before you start
- An investigation should have a written scope before it starts. Vague scopes ("look into how Team X works") drift, take too long, and produce weaker findings. Pin it: "Did employee Y violate the Workplace Threats policy on date Z?"
- For union-represented employees, Weingarten rights apply: if the interview could reasonably lead to discipline, the employee is entitled to union representation on request. Don't deny. Deny once and the discipline is vulnerable on review.
- For public-sector workplaces, Garrity warnings may apply to compelled interviews — talk to counsel before compelling testimony.
- Confirm whether the workspace's policy treats certain matters as mandatory referral to outside counsel (executive misconduct, board-level matters, matters involving HR/ELR staff). The workspace's alternate intake path applies in those cases.
Open an investigation
Open ELR → Investigations → New investigation
The intake form opens.
Write the scope statement
One paragraph. Who is the subject, what is alleged, against which policy, over what timeframe. Specific is better than broad.
Identify the parties
Subject(s) of the inquiry, reporter (if known and willing to be named), initial witness list. You'll add witnesses as you go; the initial list is the starting set, not the final.
Run the conflict check
The form blocks self-assignment when you appear in the parties list — including reporting-chain involvement. Route to a peer or your director if flagged.
Pick the confidentiality posture
Standard (need-to-know inside ELR) or restricted (named investigators only). Use restricted sparingly; overuse hampers pattern detection across matters.
Set the target completion
Workspace standard is 30 days for routine inquiries, 60 for complex. Long-overrun investigations attract grievance + EEOC risk; the file flags overruns for you.
Conduct interviews
Open Interviews → "New interview"
Each interview is one row. Don't combine multiple sessions or multiple witnesses into a single row — the record needs the cadence.
Set the witness's status
Subject / witness / complainant. Subject interviews trigger Weingarten + Garrity prompts as applicable.
Log the present parties
Interviewer, witness, witness's representative (if any), notetaker. Anyone present matters for later challenge.
Capture the statement
Free-text. The platform doesn't transcribe automatically — the record is what you write. Be neutral; quote when possible.
Mark confidentiality
Default confidential within the investigation. Cross-investigation use requires the originating file owner's permission, logged.
Save
Each saved interview is immutable thereafter; corrections are additive (a new row) rather than edits.
Collect documentary evidence
| Field | What it does | Accepted values / default |
|---|---|---|
| Source of record | Where the document came from. | HCM, expense, communications system, third-party export, etc. Required. |
| Date acquired | When the investigator received it. | Auto-stamped on upload; cannot be back-dated. |
| Chain of custody | Who handled it between source and the file. | Each transfer is one row. Most documents move source → investigator with no intermediary. |
| Relevance note | One line on why this evidence matters. | Skipping the note now means future investigators (or counsel) re-derive it; just write the line. |
| Integrity hash | SHA-256 hash of the uploaded artifact. | Auto-computed. If the file is modified later, the platform flags the divergence. |
Write the findings memo
Open Findings → New memo
The structured editor opens with the workspace's preferred sections pre-filled.
Scope recap
Restate the scope verbatim. If the investigation expanded mid-stream, document the scope amendment — never silently widen.
Methodology
What you did. How many interviews, how many documents reviewed, what timeframe you covered.
Findings of fact
Numbered findings, each anchored to specific evidence rows. Distinguish fact from opinion. Most challenges to investigation outcomes attack the strength of fact-vs-inference here.
Conclusions
Whether the alleged conduct occurred + the standard of proof you applied. Workplace investigations use a preponderance-of-evidence standard by default.
Recommended action
Sustain / non-sustain. If sustain: recommended discipline (verbal counseling / written warning / final written / PIP / suspension / termination) per the workspace's progressive discipline ladder.
Submit for second-eye review
Findings memos go through a second-investigator or HR Director review before any discipline is issued — the second eye catches process gaps + bias issues.
Common gotchas
- "The subject wants to record the interview." Workspace policy controls. Document the request + outcome. Don't deny union representation as a workaround if the request is from a represented worker — that's a separate (Weingarten) right.
- "A witness changed their statement between sessions." Log both statements as separate interview rows. The fact of inconsistency is itself evidence — don't suppress one.
- "The subject's manager wants to issue discipline before the findings memo is complete." Block it. Discipline issued pre-findings is vulnerable to procedural attack and undermines the investigation's value. The exception is administrative leave during the inquiry — that's not discipline.
- "Counsel is asking for the draft findings memo." Drafts shared with counsel for legal advice may be privileged, but the underlying facts (interviews, documents) are not. Coordinate the privilege posture with counsel before sharing.
- "The investigation is 90 days overdue." Pause. A long-overrun investigation that ends in discipline often gets reversed for delay. Either close it with the findings you have, or document in the file precisely why the delay is justified.
Troubleshooting
| Error code | What it means | Fix |
|---|---|---|
INVESTIGATION_CONFLICT_OF_INTEREST | You're in the parties list (directly or in reporting chain). | Reassign to a peer or your director. |
INVESTIGATION_INTERVIEW_WEINGARTEN_DENIED | A subject interview was conducted after a union-rep request was denied. | Reschedule with the requested representation; consider whether the prior statement can stand. |
INVESTIGATION_FINDINGS_NOT_REVIEWED | Discipline recommendation issued without second-eye review. | Route the findings memo for review before any discipline issues. |
INVESTIGATION_OVERDUE | Target completion has passed. | Either close with current findings or document the delay justification on the file. |
How this is recorded
The investigation file holds every interview, every evidence row, every draft + final findings memo, every recommendation. The ledger is append-only. If the investigation results in discipline that becomes a grievance or external charge, this file is the discoverable record. Treat every row like it will be read aloud.
Related