How to Prove Harassment at Work: What to Document

By David M. · Published 16 August 2026, updated 12 September 2026 · Verified 16 August 2026 · Editorial policy

Applies to the United States.

Not legal advice. The rules change from state to state, and federal courts do not all read them the same way. No page can cover your own facts, so if a deadline or a decision is close, talk to an employment lawyer where you live.

A record holds up when it was made the day the thing happened, records what was seen and heard rather than what it meant, names who else was there, and lives somewhere the employer cannot delete or read. The second point is where logs fail. Everything below is US law and practice.

“Document everything” is not wrong, it is unfinished. A folder of angry notes written in one sitting three months later, stored in the employer’s Google Workspace, is not documentation. It is a liability.

What does it mean to document workplace bullying in a form that survives review?

Start with what the law does not do, because it sets what the log is for. No US federal statute prohibits workplace bullying as such. Title VII, the ADEA and the ADA reach conduct tied to a protected characteristic; nothing federal reaches cruelty on its own.

One US jurisdiction has a general workplace-bullying statute reaching private employers with a private cause of action: Puerto Rico, under Act 90-2020. Its Article 11 imposes liability “por una suma igual al doble del importe de los daños que el acto haya causado al empleado” (double damages). Its Article 12 gives one year from when the employee was subjected to the harassment.

Tennessee is named as the second such state, and it is not one: Tenn. Code Ann. § 50-1-504 is titled “Immunity of employer when policy adopted — Cause of action against employer not created,” and runs the other way.

The state model policy is optional: § 50-1-503 says each employer “may adopt” it. An employer that adopts it becomes “immune from suit for any employee’s abusive conduct that results in negligent or intentional infliction of mental anguish.” So everywhere except Puerto Rico, the log is not proving “bullying.” It is proving conduct, dates and a link to something the law does reach.

Three different people will eventually read the log, and they want different things from it.

An HR investigator wants dates, names and quoted words, because those are the only things they can put to the other person in an interview. Nobody can act on “he was hostile.” They can act on “on 4 August at 09:28, in front of these four named people, he said: ‘Stop. We don’t need the version where you make it complicated.'”

An EEOC investigator wants the same, plus whatever links the conduct to a protected characteristic: Title VII reaches race, color, religion, sex and national origin, with age 40+ and disability under the ADEA and ADA, and not conduct that is merely unpleasant. Note the coverage floor. 42 U.S.C. § 2000e(b) defines a covered employer as one “who has fifteen or more employees for each working day in each of twenty or more calendar weeks in the current or preceding calendar year.”

Under fifteen, federal discrimination law does not reach the employer at all. State law can sit lower. California’s Fair Employment and Housing Act defines an employer as “any person regularly employing five or more persons” (Cal. Gov. Code § 12926(d)). So check your own state’s threshold rather than assuming the federal one.

Opposing counsel wants to show the log was written to win an argument rather than to record an event. Every adjective and every conclusion in it is theirs. The date it was written is the first thing they will attack.

Why does the date a note was written matter more than what it says?

Because a personal log becomes hearsay only when it is offered to prove that what it records actually happened. Rule 801(c) defines hearsay as a statement the declarant “does not make while testifying at the current trial or hearing” and that “a party offers in evidence to prove the truth of the matter asserted in the statement.”

The log can also be offered to show that a complaint was made, or that the employer was on notice. Used that way, it is not hearsay at all. Offered for its truth, it needs an exception, and the exceptions that let it in are built around when it was made, not how detailed it is.

Read the three rules that matter, at the Federal Rules of Evidence, Rule 803:

• Rule 803(1), present sense impression: “A statement describing or explaining an event or condition, made while or immediately after the declarant perceived it.” The Advisory Committee’s Notes give the reason in one line: “substantial contemporaneity of event and statement negative the likelihood of deliberate … misrepresentation.” A note written eleven minutes after the meeting carries a guarantee one written in November does not.
• Rule 803(5), recorded recollection: a record that “(A) is on a matter the witness once knew about but now cannot recall well enough to testify fully and accurately; (B) was made or adopted by the witness when the matter was fresh in the witness’s memory; and (C) accurately reflects the witness’s knowledge.” Subsection (B) is the whole game. Note the sting in the tail: “If admitted, the record may be read into evidence but may be received as an exhibit only if offered by an adverse party.” The log gets read aloud; it does not go into the jury room as an object. Someone may later deny what they told you. The page on workplace gaslighting covers the same-day email that asks them to confirm it.
• Rule 803(6), business records: requires that the record “was kept in the course of a regularly conducted activity of a business, organization, occupation, or calling” and that “making the record was a regular practice of that activity.” The rule reaches an “occupation, or calling” as well as a business, so a record kept as a routine part of the reader’s own job (a nurse’s shift log, a site supervisor’s daybook) is a different question. A diary started because of one manager is not that: it is neither a regularly conducted activity nor a regular practice of one, and formatting it neatly does not convert it. The claim to distrust is that a well-kept employee log is admissible as a business record. On its own, it is not.

The Advisory Committee’s Notes to Rule 803(5) flag the failure mode a lawyer will exploit: the impaired-memory requirement exists to keep out statements “carefully prepared for purposes of litigation under the supervision of attorneys, investigators, or claim adjusters.” A log that begins the week after a lawyer is retained looks like the thing the rule was written to exclude.

A fourth rule has practical bite. Under Rule 612, where a writing is used to refresh a witness’s memory while testifying (or before testifying, “if the court decides that justice requires”), the adverse party can demand it, inspect it, cross-examine on it, and “introduce in evidence any portion that relates to the witness’s testimony.” A log used to prepare for a deposition is a log the other side may get to read. Write it knowing that.

How each rule treats a personal log.

Rule	What it covers	What it means for the log
Rule 801(c)	Defines hearsay	A log is hearsay only when offered to prove that what it records happened
Rule 803(1), present sense impression	A statement made while or right after the event	A note written minutes after the event can qualify. One written months later cannot
Rule 803(5), recorded recollection	A record made when the matter was fresh, used when the witness can no longer recall it well	The log can be read aloud, but it goes in as an exhibit only if the other side offers it
Rule 803(6), business records	Records kept as a regular practice of a business or job	A diary started because of one manager does not qualify
Rule 612	Writings used to refresh a witness’s memory	A log used to prepare for a deposition may be read by the other side

What is the difference between an observation and a conclusion in a log entry?

An observation is what a camera in the corner would have captured. A conclusion is what it meant. Log the first; the second is the reader’s job.

What does the same incident look like logged badly and logged well?

Logged badly:

Aug 4. Okafor was being a total bully again in the team meeting. He humiliated me in front of everyone and it’s obviously because I’m the only woman on the team. Classic hostile work environment. HR won’t do anything anyway.

Seven failures. No clock time, no location, no list of who was present. Not one quoted word, so nothing in it can be put to Okafor in an interview. Four conclusions: “bully,” “humiliated,” “obviously because” and “hostile work environment.” The writer will be asked to justify each one, and witnessed none of them. A prediction about HR that sets an adversarial posture before any complaint was made. And no record of what happened next.

The same incident, logged well:

4 August 2026, 09:15–09:40. Weekly ops meeting, Conference Room B, 3rd floor. Present: M. Okafor (manager), R. Silva, T. Nguyen, D. Barros, me. 09:28. I began the Q3 forecast update. Okafor said: “Stop. We don’t need the version where you make it complicated.” I said I would finish in one minute. He said: “No. Silva, take it.” Silva then presented the same three numbers from slide 4 of my deck. Okafor said: “That’s what I was after.” 09:40. Meeting ended. No one raised it with me afterward. 10:05. Told T. Nguyen in the 3rd-floor kitchen. Nguyen said: “He did that to you in June too.” Corroboration: calendar invite “Weekly Ops 09:15” sent 1 Aug; my deck emailed to Okafor 3 Aug 17:42; Silva’s screen share logged in the Teams meeting record. Pattern note: fourth time since 12 May that work assigned to me in writing has been handed to someone else verbally in a meeting. Dates: 12 May, 2 June, 21 July, 4 August. Written 4 August 2026 at 10:20 from direct memory. Not reconstructed.

Nothing in the good version calls anyone a bully, and it does not need to. The quoted words do the work, a named witness volunteered an unprompted corroboration, and the only interpretive element is a count of four dated occurrences, which is a number, not an adjective. An investigator can act on every line. A cross-examiner has little to grip.

The two versions of the 4 August entry, side by side.

What the entry needs	Logged badly	Logged well
Time	“Aug 4” with no clock time	09:15 to 09:40, with the exchange at 09:28
Place	Only “the team meeting”	Weekly ops meeting, Conference Room B, 3rd floor
Who was there	Only “everyone”	Okafor, Silva, Nguyen and Barros, by name
What was said	Not one quoted word	Okafor’s words, quoted exactly
Conclusions	Four: bully, humiliated, obviously because, hostile work environment	None. Only a count of four dated occurrences
What happened next	Not recorded	Told Nguyen at 10:05, who said it happened in June too
Proof held elsewhere	None named	Calendar invite, emailed deck and the Teams meeting record

If a protected characteristic is in play, record the evidence of it, not the inference. Not “he did it because I’m the only woman,” but: “Okafor has interrupted and reassigned my items in 4 of the last 6 ops meetings. In the same period he did not interrupt Silva, Nguyen or Barros. I am the only woman on the team of five.” Three observations, and the inference is now available to the reader without you having sworn to it.

What fields does a single log entry need?

Ten fields. Anything shorter loses the entries that matter later.

1. Date: full date, not “last Tuesday.”
2. Start and end time: clock times. “Morning” is worthless against a calendar record.
3. Location: specific enough to be checked: room, floor, building, or the platform and meeting name if remote.
4. Who was present: full names and roles, and separately who was within earshot but not part of it. Those are the neutral witnesses.
5. What was said: direct quotes, and only words you are certain of. Anything else goes in marked (paraphrase, not exact). One invented quote contaminates every other quote in the log.
6. What was done: actions, documents shown, screens shared, doors closed, phones taken out.
7. What you did in response: including “nothing.” Silence is a fact; omitting it leaves a gap someone else fills.
8. Who you told, when, and how: name, time, channel. This is what turns one person’s account into two.
9. Where the corroboration sits: calendar invite, email timestamp, Slack thread, badge swipe, meeting recording, ticket number. Record the pointer now; the underlying record may be purged on the employer’s retention schedule first.
10. Contemporaneous or reconstructed: say which. If reconstructed, say from what. The field easiest to leave out, and the one that protects the rest of the log.

Keep out: self-diagnosis, legal labels (“harassment,” “discrimination,” “hostile work environment”), speculation about motive, other people’s medical or personal information, and anything you would not want read aloud with the other person in the room. Under Rule 612, that last scenario is live.

How do you date-stamp a record so it is not just your word later?

Put the timestamp on a server the employer does not control: an email from a personal account to that same personal account, one incident per message. Send your own notes this way. Do not send the employer’s documents that way. See when taking your employer’s documents is protected for why.

Template. Subject line carries the date and place; the framing sentence comes first; then the ten fields in order, one per line, so the whole thing can be copied and refilled. Field 10 is the one that gets dropped, so it is worked in full below. Fields 5 and 8 point back to the worked entry above rather than reprinting the dialogue. In a real message, the quoted words go in there in full, word for word.

To: your own personal email address Subject: Record of 4 Aug 2026, 09:15–09:40, Conference Room B

Written 4 August 2026 at 10:20, approximately 40 minutes after the events described, from direct memory. Not edited after sending.

1. Date: 4 August 2026. 2. Start and end time: 09:15 to 09:40. 3. Location: weekly ops meeting, Conference Room B, 3rd floor. 4. Who was present: M. Okafor (manager), R. Silva, T. Nguyen, D. Barros, me. Within earshot but not part of it: J. Pratt, at the desk outside Room B, door open throughout. 5. What was said: the 09:28 exchange set out word for word in the log entry above: Okafor’s two instructions to me, his instruction to Silva, and his remark after Silva finished. Quotes only, in full, and nothing added around them. 6. What was done: I began the Q3 forecast update; Silva then presented the same three numbers from slide 4 of my deck. 7. What I did in response: said I would finish in one minute; after the item was handed to Silva, said nothing further in the meeting. 8. Who I told, when, and how: T. Nguyen, 10:05, in person, 3rd-floor kitchen. Nguyen’s reply is quoted in the log entry above. 9. Where the corroboration sits: calendar invite “Weekly Ops 09:15” sent 1 Aug; my deck emailed to Okafor 3 Aug 17:42; Silva’s screen share in the Teams meeting record. Pattern note: fourth occurrence since 12 May. Dates: 12 May, 2 June, 21 July, 4 August.

10. Contemporaneous or reconstructed: contemporaneous. Written from direct memory 40 minutes after the meeting ended. Not reconstructed from any other record, and not edited after sending.

The sentence to include is the framing line: written [date] at [time], approximately [N] minutes after the events described, from direct memory, not edited after sending. Be clear about what it does and does not do.

What it does not do: it does not make the note self-authenticating. “Self-authenticating” is a term of art. Rule 902 lists the categories of evidence that need no extrinsic proof of authenticity, and a note an employee wrote to themselves is not among them. Anyone telling you a magic sentence makes your log self-authenticating is describing something that does not exist.

What it does do, which is more useful:

• It puts the making-time on the face of the record, which is exactly what Rule 803(1) and Rule 803(5)(B) turn on, and makes the gap between event and record explicit so nobody has to establish it by cross-examination.
• It supports authentication under Rule 901(b)(4), which covers “the appearance, contents, substance, internal patterns, or other distinctive characteristics of the item, taken together with all the circumstances.”
• The server-side timestamp is separately reachable under Rule 902(13), “Certified Records Generated by an Electronic Process or System,” via a certification from the mail provider. That is a lawyer’s task, not yours. Your job is to make sure the timestamp exists somewhere you do not control.

One message per incident, never a running document: a file edited fifty times has one modification date and no internal history, where fifty emails have fifty independent timestamps. If a running document is unavoidable, never edit a past entry. Instead, add a correction as a new dated entry saying what is being corrected and why.

Where should the log live?

Not on anything the employer owns, administers or pays for: not the work laptop or phone, company email, the company Drive, OneDrive, Notion, Slack DMs or ticketing system, and not a personal account opened through a company-managed browser profile or an MDM-managed device.

The reason is not that storing it there is illegal. It is that the employer can read it and retain it. The day the relationship ends, the employer can cut access to it in minutes. A log the employer read in September is a log the employer had six months to build around.

The privilege risk is sharper still, and US courts split on it:

• In Holmes v. Petrovich Development Co., No. C059133 (Cal. Ct. App. 3d Dist., 13 January 2011), emails an employee sent to her own attorney on the company computer through the company email account were held not privileged. The handbook restricted computers to company business, banned personal email, stated employees had “no right of privacy,” and warned of monitoring. The court’s analogy is the one to remember: “akin to consulting her lawyer in one of defendants’ conference rooms, in a loud voice, with the door open.”
• In Stengart v. Loving Care Agency, Inc., No. A-16-09 (N.J. 30 March 2010), emails to counsel sent through a personal, password-protected web-based account on a company laptop did remain privileged. The New Jersey Supreme Court leaned on the vagueness of a policy that permitted “occasional personal use” while declaring email not private, and never warned that such messages are written to the hard drive and can be forensically retrieved.

The operative difference is the account, not the hardware. But do not rely on it, because this is a state-by-state question and the hardware still holds a cached copy. The decision criterion: write nothing to a lawyer, and store nothing about the situation, on a device or account the employer supplies. Use a personal device on a personal network.

The mirror-image question is whether you can copy the employer’s own documents and take them home. It runs on a different body of law and has its own page. The test is short. Do not get a document if that means breaching a confidentiality policy, using someone else’s credentials, or entering a system outside your role. Write down what it is, where it is held, who has it and what it would show. A lawyer can then get it through discovery. See whether you can take your employer’s documents home.

How long do you keep it?

Until the shortest deadline that could apply has passed, plus the length of any case. The deadlines are shorter than the internal process that precedes them, and they run from the conduct, not from the day you decided to act.

Route	Deadline	Source
OSHA safety-retaliation complaint (§ 11(c))	30 days from the violation	29 U.S.C. § 660(c)(2)
NLRB unfair labor practice charge	6 months from the conduct	29 U.S.C. § 160(b)
EEOC charge, general rule	180 calendar days from the discriminatory act	42 U.S.C. § 2000e-5(e)(1); EEOC time limits
EEOC charge where a state or local agency enforces a law prohibiting the same basis	300 calendar days	EEOC time limits
Age discrimination (ADEA), 300-day extension	Only where a state law and state enforcing agency exist. A local law alone is not enough	EEOC time limits
Equal Pay Act	2 years from the last discriminatory paycheck; 3 years if willful	EEOC time limits
Federal employees	Contact an agency EEO Counselor within 45 days	EEOC time limits
Unpaid wages / overtime (FLSA)	2 years; 3 years for a willful violation	29 U.S.C. § 255(a)
Suit after an EEOC notice of right to sue	90 days from the giving of notice	42 U.S.C. § 2000e-5(f)(1)

Three things about that table that catch people out.

The 300-day extension is not automatic, and not a property of your state alone. It depends on a state or local agency enforcing a law prohibiting discrimination on the same basis. The EEOC’s FEPA and dual filing page sets out the worksharing mechanism: where an agreement exists, a charge filed with either body is dual-filed with the other. Unsure which clock you are on? Assume 180 days.

Missing the EEOC deadline is not the same as being outside a court’s jurisdiction. In Fort Bend County v. Davis, 587 U.S. 541 (2019), a unanimous Supreme Court held Title VII’s charge-filing requirement is “not jurisdictional” but “a mandatory claim-processing rule,” which a defendant can forfeit “if the party asserting the rule waits too long to raise the point.” That is not a reason to relax. Missing the deadline will usually end the claim. But the ruling is a reason not to give up on a case because one date looks bad. That is a question for a lawyer, not for you.

The OSHA 30-day window can expire while you are still deciding whether to say anything at all. If safety is any part of your situation, that clock is already running.

One duty runs the other way. Under FRCP 37(e), a party that loses electronically stored information it should have preserved faces curative measures on a finding of prejudice, and on a finding of “intent to deprive another party of the information’s use in the litigation” faces an adverse-inference instruction, dismissal or default judgment. That runs to you too: once litigation is reasonably anticipated, wiping a phone or deleting the log is the worst available move.

What does HR actually do with what you hand over?

HR opens a file, and that file does a second job whether or not anyone describes it to you: it establishes what the employer knew, when, and what it did next.

That structure comes from two Supreme Court decisions handed down the same day in June 1998. It does not come from agency guidance, which is why the January 2026 rescission of the EEOC’s 2024 harassment guidance did not touch it. In Burlington Industries, Inc. v. Ellerth, 524 U.S. 742 (1998) and Faragher v. City of Boca Raton, 524 U.S. 775 (1998), the Court held that where a supervisor’s harassment produces no tangible employment action, the employer may raise an affirmative defense that “comprises two necessary elements: (a) that the employer exercised reasonable care to prevent and correct promptly any sexually harassing behavior, and (b) that the plaintiff employee unreasonably failed to take advantage of any preventive or corrective opportunities provided by the employer or to avoid harm otherwise.”

The limit is stated just as plainly: “No affirmative defense is available, however, when the supervisor’s harassment culminates in a tangible employment action, such as discharge, demotion, or undesirable reassignment.”

Where the conduct comes from co-workers rather than a supervisor, the standard is different, and the Court stated it in Vance v. Ball State University, 570 U.S. 421 (2013): “If the harassing employee is the victim’s co-worker, the employer is liable only if it was negligent in controlling working conditions.” What the employer was told, and when, is the evidence that negligence question turns on. That is what the file records.

Read element (b) again. The employer’s defense partly depends on you having delayed. Hand over a 40-page log covering fourteen months and you have proved, in your own handwriting, that you knew for fourteen months and, if no earlier complaint exists, did not use the complaint procedure. The log that was supposed to be your strongest asset has supplied the employer’s affirmative defense.

There is a second cost. A full log names every witness at once, so the employer’s investigator speaks to all of them, in an order the employer chooses, before you have spoken to any of them. Each is interviewed by someone who signs their pay. See your rights in an HR investigation for how those interviews are actually run.

So split the job across two documents.

The log is your private working record. It goes to nobody at this stage; it is what you write the complaint from.

The complaint is short, dated, in writing, and does one job: put the employer on notice. Name the conduct, name the protected characteristic if one is in play, give three to five of the strongest dated incidents in full, state that further dated records exist, say what outcome you are asking for, and stop. The line about further records can read: “A contemporaneous dated record of these and further incidents has been kept since 12 May 2026 and is available to the investigation on request.” That sentence preserves the log’s existence and start date without surrendering its contents or its witness list.

Written, not verbal: a verbal complaint HR does not minute did not happen. The EEOC’s 2016 Enforcement Guidance on Retaliation and Related Issues puts the standard broadly: “‘[w]hen an employee communicates to her employer a belief that the employer has engaged in . . . a form of employment discrimination, that communication’ virtually always ‘constitutes the employee’s opposition to the activity.'” It was issued 25 August 2016 and was still live at 16 August 2026. The January 2026 rescission reached the harassment guidance only. The value of that standard is entirely in proving the communication happened, and when. More in what makes an HR complaint legally protected.

If the EEOC route opens, the detail has a proper home. The EEOC sets out what to expect after a charge is filed: notice to the employer within 10 days, a position statement from the employer, and 30 days for you to respond through the EEOC Public Portal. That response is where the log’s chronology earns its keep. It answers a specific account with dated specifics, rather than opening with everything and letting the employer aim.

Two things go wrong repeatedly once a complaint is in HR’s hands.

The employer’s policy is treated as the final word, in either direction. A policy forbidding employees from discussing an investigation or from documenting their treatment may itself be unlawful: under Stericycle, Inc., 372 NLRB No. 113 (2 August 2023), summarized in the NLRB’s own account, a rule with “a reasonable tendency to chill employees” is presumptively unlawful unless the employer proves a legitimate business interest that no narrower rule could meet. That doctrine is volatile. Stericycle itself overturned Boeing (2017) and LA Specialty Produce (2019), so check the current rule before relying on it.

The practical criterion: the Board may vindicate you eventually, but the employer can fire you now and litigate later, so do not treat § 7 as armor. Acting with colleagues does bring you inside 29 U.S.C. § 157, which protects “concerted activities for the purpose of collective bargaining or other mutual aid or protection,” and the NLRB’s protected concerted activity page covers a single employee “bringing group complaints to the employer’s attention.” That matters where the problem is a group dynamic rather than one person (see workplace mobbing).

Recording is treated as a documentation method. It is not, and where a policy prohibits it, it hands the employer a dismissal ground independent of the merits of your complaint. 18 U.S.C. § 2511(2)(d) makes it lawful under federal law for a party to the conversation to record it, absent a criminal or tortious purpose. But state law is where this bites.

Cal. Penal Code § 632(a) reaches anyone who “intentionally and without the consent of all parties to a confidential communication, uses an electronic amplifying or recording device to eavesdrop upon or record the confidential communication,” and RCW 9.73.030(1) makes it unlawful in Washington to record a private conversation “without first obtaining the consent of all the participants in the communication.”

Check your state before assuming the federal rule is the whole of it, and treat the employer’s policy as a separate question from the criminal law: whether you can record a meeting with HR.

Which route applies to your situation?

If this is your situation	Route now	Why, and the clock
Conduct is unpleasant but not tied to a protected characteristic, safety, wages or collective action	Log only. No complaint yet.	Federal discrimination law reaches protected characteristics, not incivility. Keep building dated entries until a pattern or a protected basis emerges
Conduct is tied to race, color, religion, sex, national origin, age 40+, disability or genetic information (GINA, 42 U.S.C. § 2000ff-1)	Written internal complaint first, then EEOC charge	Puts the employer on notice, which is what its affirmative defense turns on. 180 days, or 300 in a deferral state
You already complained and your treatment measurably worsened	Written complaint identifying it as retaliation, then EEOC	Retaliation is separately actionable. Same 180/300 clock, running from the retaliatory act. See proving retaliation after a complaint
The issue is pay discussion, group grievances, or acting with colleagues	NLRB charge	§ 10(b) allows 6 months and no more. NLRB investigations state a typical 7–14 week timeline (page verified 16 August 2026)
You raised a safety issue and were disciplined	OSHA § 11(c) complaint immediately	30 days, the shortest clock on this page
You are being managed toward the exit (sudden PIP, stripped duties, a new “concerns” file)	Lawyer before you resign, not after	Resigning first can foreclose the better claims. See how quiet firing works when you are being managed out, signs your boss wants you to quit, what to check before signing a written warning, and the page on constructive discharge and forced resignation
You have been fired, or handed an agreement to sign	Lawyer before signing anything	The 90-day right-to-sue clock and any severance deadline both run fast

Where two rows apply, the shortest clock governs your next 30 days. Nothing here stops you continuing to log; logging never becomes the wrong move.

Do this in the next seven days

Open a personal email account you use for nothing else. Write up the three most recent incidents you still remember clearly, one email per incident, using the ten fields. Mark them reconstructed, because they are. From tomorrow, write them the same day and mark those contemporaneous.

Then leave the log alone and work out which clock you are on. If any part of the situation touches safety, that is 30 days. If you are unsure whether the conduct is tied to a protected characteristic, the signs of a toxic workplace sets out the wider pattern. What actually counts as a hostile work environment is the legal test, which is not the same thing. A charge is filed through the EEOC Public Portal after an online inquiry and an intake interview; how to file an EEOC charge covers the mechanics.

Common questions about documenting workplace mistreatment

What is considered mistreatment in the workplace?

There is no single legal category called mistreatment. The law divides conduct into two groups. The first is what a statute reaches: treatment because of a protected characteristic, or because you engaged in protected activity. The second is everything else, which is generally lawful however damaging. Documenting is worth doing before you know which side you are on, because the record has to be contemporaneous and you cannot make it retrospectively.

What is a hostile work environment?

A legal term with a specific meaning, not a description of an unpleasant workplace. It requires unwelcome conduct based on a protected characteristic that is severe or pervasive enough to alter the conditions of employment. A workplace can be miserable, unfair and badly run without meeting it. That gap is the most common misunderstanding in this area.

How hard is it to prove a hostile work environment?

Harder than most people expect, and the difficulty is usually evidentiary rather than legal. The conduct must be tied to a protected characteristic, and it must be severe or pervasive. Isolated incidents rarely meet that threshold. What makes the difference is a dated contemporaneous record rather than a recollection assembled afterwards.

How to talk to HR about unfair treatment?

In writing, and with the connection stated. HR is not obliged to act on unfairness as such, but a complaint that identifies conduct tied to a protected characteristic or to earlier protected activity engages obligations that a general grievance does not. Describe events with dates and exact words rather than conclusions, and keep a copy outside employer systems.

What are some HR trigger words that might indicate a hostile work environment?

The phrase usually means language a complaint should contain, not language to avoid. Name the protected characteristic and state the connection: that the treatment happened because of it. That is what moves a complaint from general grievance into territory where an employer has legal obligations. This is also why recording exact words rather than paraphrase matters: the specific language used is often the evidence.

What are 7 signs that a work environment might be toxic?

Fear-based leadership, high turnover, cliques, micromanagement, blurred boundaries, favoritism and fear of retaliation are the usual list. Recognition is the easy part. Which of those signs the law actually reaches is the question that changes what you can do, and the answer is: fewer than most lists imply.

Sources

• 42 U.S.C. §§ 2000e(b), 2000e-5(e)(1), 2000e-5(f)(1): Title VII coverage, charge deadline and right to sue (Cornell LII)
• 42 U.S.C. § 2000ff-1: GINA (Cornell LII)
• 29 U.S.C. §§ 157, 160(b): NLRA Section 7 and the six-month charge period (Cornell LII)
• 29 U.S.C. § 660(c)(2): OSH Act retaliation complaints (Cornell LII)
• 29 U.S.C. § 255(a): FLSA limitations period (Cornell LII)
• 18 U.S.C. § 2511(2)(d): federal one-party consent recording rule (Cornell LII)
• Federal Rules of Evidence 801(c), 803, 612, 901(b)(4), 902: hearsay, present sense impression, refreshing recollection and authentication (Cornell LII)
• Federal Rule of Civil Procedure 37(e): loss of electronically stored information (Cornell LII)
• Tenn. Code Ann. §§ 50-1-503, 50-1-504: Healthy Workplace Act (Justia)
• Cal. Gov. Code § 12926(d); Cal. Penal Code § 632(a): FEHA employer definition and all-party recording consent (FindLaw)
• RCW 9.73.030(1): Washington all-party consent (Washington State Legislature)
• Act 90-2020: Puerto Rico workplace harassment statute (Oficina de Gerencia y Presupuesto)
• Burlington Industries, Inc. v. Ellerth, 524 U.S. 742 (1998); Faragher v. City of Boca Raton, 524 U.S. 775 (1998); Vance v. Ball State University, 570 U.S. 421 (2013)
• Fort Bend County v. Davis, 587 U.S. 541 (2019)
• Stengart v. Loving Care Agency, Inc., No. A-16-09 (N.J. 30 March 2010); Holmes v. Petrovich Development Co., No. C059133 (Cal. Ct. App. 3d Dist., 13 January 2011)
• EEOC: charge time limits, FEPA dual filing, the 2016 Enforcement Guidance on Retaliation and Related Issues, what to expect after a charge is filed, and the EEOC Public Portal
• NLRB: protected concerted activity, and how NLRB investigations proceed

This is general information, not legal advice for your situation.