Why the report matters as much as the investigation

You have interviewed the witnesses, gathered the emails, and weighed the accounts. Now comes the part that often determines whether your careful work actually helps anyone: putting it down on paper in a way that human resources can act on. A well-run investigation that produces a muddled report can leave HR no better informed than they were at the start. A clear report, by contrast, gives them a reliable foundation for difficult decisions about disciplinaries, grievances, or wider cultural change.

The good news is that clarity is a craft, not a talent. It comes from a handful of habits that any investigator can adopt. This article sets out the most useful of them.

Structure everything around the terms of reference

Your terms of reference are the spine of the report. They define what you were asked to look into, and they give the reader a way to check that you stayed within your remit. Before you write a single finding, revisit them. Then organise your report so that each section answers a question the terms of reference actually pose.

A simple structure works well:

• Background: a short, neutral description of how the matter arose.
• Terms of reference: the specific questions you were asked to address.
• Methodology: who you spoke to, what documents you reviewed, and any limitations.
• Findings: your conclusions on each question, with the supporting evidence.
• Appendices: interview notes, relevant documents, and a chronology if helpful.

Resist the temptation to wander. If something important falls outside the terms of reference, note it briefly as an observation and explain why you did not pursue it. HR can then decide whether a separate investigation is warranted.

Separate fact from opinion, and label both

This is the single most common failing in investigation reports. Investigators blend what they observed with what they concluded, and readers cannot tell where the evidence ends and the judgement begins. The fix is discipline: keep them in distinct places.

Facts are things that can be verified. A witness said a specific sentence. A document carries a particular date. An email was sent at 14:20 on a Tuesday. State these plainly, and attribute them. "The line manager stated that..." or "The rota for that week shows..."

Opinions, inferences, and assessments are yours. They belong in a clearly marked section, usually headed "Analysis" or "Assessment". Use language that signals the shift: "In my view...", "The evidence suggests...", "I have concluded that...". Where your conclusion depends on weighing conflicting accounts, say so and explain your reasoning. Did one account align with documentary evidence? Was a witness's recollection consistent over time? HR needs to follow your logic, not just accept your verdict.

Where you cannot reach a firm conclusion, say that too. "The evidence does not allow me to determine whether..." is a perfectly respectable finding. It is far more useful than a confident guess.

Write in plain English, not investigation-speak

Investigation reports are read by busy people who may not be lawyers. They are often read under pressure, sometimes late at night before a meeting. Write for that reader.

Use short sentences. Prefer the active voice. Cut phrases like "it was ascertained that" in favour of "I found that". Avoid jargon such as "the subject of the complaint" when you can say "the employee" or use their name. Titles and role descriptions are fine on first mention; after that, names are clearer.

Be cautious with legal language. You are not delivering a judgment, and using terms like "guilty" or "proven beyond doubt" can create problems later. Stick to your organisation's own vocabulary, and where a term has a specific meaning in your policies, use it consistently.

Finally, keep your tone neutral. Warmth belongs in how you treat people during the investigation, not in the report itself. Avoid adjectives that betray a view: "aggressive", "unreasonable", "clearly dishonest". Describe the behaviour and let the evidence speak. "Raised his voice and interrupted the colleague twice" tells HR far more than "was aggressive".

Make it easy to navigate and verify

A report that is hard to navigate will not be read properly. Add a contents page if the report runs beyond a few pages. Use headings that match the terms of reference so the reader can find the answer to each question quickly.

Number your paragraphs. This makes it far easier for HR, and anyone else who later reads the report, to refer to specific passages in meetings or correspondence. Keep a consistent format for dates, names, and job titles.

Quote directly where wording matters, but do not pad the report with long extracts. Put lengthy documents in the appendices and refer to them in the body. If you include a chronology, keep it factual and brief; it is a navigation aid, not an argument.

Remember that the report may be disclosed in later proceedings. Write every line on the assumption that someone outside your organisation will read it one day. That habit alone will keep your language careful and your conclusions defensible.

Before you send it, do these checks

A short final review catches most problems. Run through this list:

• Does the report answer every question in the terms of reference?
• Are facts and opinions clearly separated and labelled?
• Is every factual claim supported by a source, whether a witness or a document?
• Have you avoided speculation about motives or character?
• Is the language plain enough for a non-specialist to follow?
• Are names, dates, and job titles accurate and consistent?
• Would you be comfortable if the employee concerned read it?

That last question is a good test of fairness as well as clarity. A report that is accurate, balanced, and readable gives HR what they need to make sound decisions, and gives everyone involved confidence that the process was handled properly.