What good investigative work actually looks like

Investigations

Investigative work is badly served by how it is portrayed. The reality is far less dramatic and far more procedural — and the procedure is exactly what separates findings that hold up from findings that fall apart the moment they are challenged.

It starts with the question

Most weak investigations are weak because the brief was never tightened. “Find out what is going on” is not a question anyone can answer or close out. “Establish whether this person was working during the period they claimed to be unable to” is.

Getting to that sentence with a client is the first real piece of work, and it is worth the time it takes. It defines what evidence would settle the matter, and just as importantly, what would not.

Evidence has to survive someone hostile reading it

The standard we work to is simple: assume every note, timestamp and image will be examined by someone whose job is to discredit it. That assumption changes daily habits.

  • Contemporaneous notes, not reconstructions written up later.
  • Continuity that can be demonstrated, not asserted.
  • A clear line between what was observed and what was inferred.

A finding you cannot show your working for is an opinion. Clients are not paying for opinions.

Knowing when to stop

There is a point where further surveillance stops adding weight to a conclusion and starts adding cost. Recognising it — and saying so — is part of the job. So is reporting an inconclusive result plainly, rather than dressing it up.

Clients remember the case where they were told the honest answer far longer than the one where they were told what they wanted to hear.

Why the technology matters

None of the above scales on memory and goodwill. It scales on a system that logs every step as it happens, keeps the case file consistent between investigators, and produces reporting in the same shape every time.

That is the reason our investigative businesses run on platforms built inside the group rather than generic tools. The method is the product, and the software exists to make the method repeatable.