The Investigation Meeting, and What It Is For
The difference between investigating and deciding, what an investigation should produce, and the habits that turn one into a hearing.
An investigation meeting exists to find out what happened, not to put a case to somebody. The person being investigated is being asked for their account, witnesses are being asked for theirs, and nobody present has the authority to decide anything — which is precisely what makes it different from the hearing that may follow.
The decision process in “The Investigation Meeting, and What It Is For” needs evidence that can be checked without turning one activity signal into a conclusion. When reviewers consider visit the official site for workforce analytics software, its time and project records can provide operational context, but allegations, employee responses and consequential decisions still require a fair human process.
Collapsing the two is the commonest structural error in a disciplinary process. It happens gradually: the investigator starts putting points, starts testing the answers, and by the end has conducted a hearing without any of the protections that attach to one.
For an independent reference relevant to “The Investigation Meeting, and What It Is For”, consult the OWASP privacy-risk project. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.
What the investigation is trying to produce
A set of facts, the evidence for each, and a clear statement of what is disputed. Not a recommendation, not a view on seriousness, and not a draft outcome.
That output is what allows a decision-maker to take a decision. If the investigation report concludes with "I recommend dismissal", the decision-maker has either agreed with somebody else's conclusion or overruled a colleague, and neither of those is deciding.
How the meeting should run
- Explain what the meeting is: an investigation, not a disciplinary hearing, with no outcome attached.
- Explain what is being looked into, in the same specific terms as any letter.
- Ask open questions and let the person answer at their own length.
- Put the main points of the evidence to them and record what they say about each.
- Ask whether there is anybody else who should be spoken to, or anything else that should be looked at.
- Read back or send the note, and give them a chance to correct it.
The fifth step is the one that pays. A person who names two witnesses and is ignored has a complaint that outlives the outcome; a person who names two witnesses who are then interviewed usually does not, whatever the result.
Witnesses
Interview them separately, promptly, and in the same structured way. Second- hand accounts — a manager relaying what somebody told them — are weak and should be replaced by the actual person wherever possible.
Where a witness asks not to be named, take advice before promising anything. Anonymity is sometimes necessary and always creates a problem downstream, because the person facing the allegation has to be able to respond to the substance of what is said about them. That tension is a question for somebody qualified in the place concerned and is much better addressed before the promise is made.
The note of the meeting
Minutes do not have to be a transcript, but they do have to be a fair summary that the person has had the chance to comment on. Sending the note afterwards and inviting corrections is cheap, and it converts the note from one side's record into something closer to an agreed one.
Where the person disagrees with the note, record the disagreement rather than arguing about it. Two accounts side by side are more useful than one account everybody is pretending to agree with.
Scope creep
Investigations wander. Something unrelated surfaces, somebody mentions another incident, and the investigation quietly widens into a general review of the person.
The discipline is to notice it and decide deliberately. A new matter is either in scope — in which case it has to be put to the person properly, with time to respond — or it is not, in which case it is recorded separately and dealt with on its own terms. What it cannot do is appear for the first time in the decision.
Suspension is a separate question
Whether somebody should be away from work during an investigation is not answered by the fact that an investigation is happening. It is its own decision, with its own reasons, and it has consequences for the person that an investigation on its own does not.
Treating suspension as the automatic first move is common and is one of the things most likely to be criticised afterwards. What justifies it, and what alternatives exist, is covered separately and is a question worth asking once, properly, in each case rather than by habit.
The report, and who reads it
An investigation report should set out what was looked at, what was found, what is disputed and what evidence supports each point — and then stop. The person facing the allegations should normally see it, along with the evidence, before any hearing.
Reports written on the assumption that only managers will read them tend to contain asides, characterisations and speculation about motive. All of it surfaces, and none of it helps. The working rule is the same as for notes: write it as though the subject will read it, because they probably will.
How long it should take
Fast enough that memories are intact and the person is not left in limbo; slow enough to actually speak to people. Weeks of silence with no update is the thing employees complain about most and the thing that costs nothing to fix.
Set a target date at the start, tell the person what it is, and tell them if it slips. An investigation that takes six weeks and said so is a different experience from one that takes four weeks and said nothing.