A sloppy investigation report can do more damage than no report at all.
Proper documentation is your paper trail, your legal defense, and your credibility—all in one file. But documenting an investigation isn't just typing up what happened. It's capturing facts with enough precision and neutrality that someone who wasn't there could pick up the file six months later and understand exactly what occurred, who said what, and what conclusion the evidence supported.
Here's what that looks like in practice, and the mistakes that most commonly derail it.
What solid documentation includes
- A clear, factual timeline of events
- Neutral language with zero editorializing
- Quotes that are accurate and properly attributed
- Credibility notes based on observable factors, not assumptions
- A summary of findings tied to policy—not to feelings about the outcome
Every item in that list matters. A timeline without attribution is hearsay. Credibility notes based on "they seemed defensive" are legally dangerous. A findings summary that references how you felt about the respondent will not survive scrutiny.
The most common mistakes
Writing as if you've already decided. The most damaging thing an investigator can do is write documentation that reads like it's building a case for one side. Even if the evidence is overwhelming, the report has to read as neutral. You're the fact-finder, not the prosecutor.
Vague or emotional language. "He was clearly hostile" is an interpretation. "He raised his voice and slammed his hand on the table" is a fact. Use the second kind. Always.
Skipping details that seemed minor. Minor facts become important later—especially when a party's account changes. Document everything relevant at the time of the interview. Don't filter based on what you think matters yet.
Missing interview logistics. Note the date, time, location, and format of every interview. Note who else was present. Note whether the subject was given an opportunity to add anything before the interview closed. These details establish process integrity.
Including personal opinions or unrelated history. Irrelevant background information doesn't strengthen your report. It creates exposure. If it's not directly relevant to the allegation being investigated, leave it out.
The standard to write toward
Always assume your documentation will be read by someone who wasn't there—a plaintiff's attorney, an EEOC investigator, a judge, or a new HR leader trying to understand what happened two years ago. Your job is to make the record strong enough to stand on its own, with no one around to explain it.
If you need to build an internal documentation template or train your team on investigation writing, that's exactly the kind of infrastructure work that pays off the first time something goes sideways.