1. How it usually happens
Everything goes smoothly until someone says: "It wasn't like that".
And that is where the problems begin.
In the professional world, many dynamics play out on informal channels: quick chats, voice notes, hastily shared screenshots. A promise made in a group chat, an edit agreed upon via WhatsApp, a delivery delayed by a message at 11:47 PM.
When a dispute arises, you often end up with:
- fragmented conversations across multiple apps
- randomly saved screenshots
- files renamed a thousand times
- different versions of the same document
A typical anecdote: a project manager is convinced they received written confirmation for an urgent change. They scroll through chats... finding pieces, but the context is missing. The client remembers differently. The truth lies somewhere in the middle, but without a timeline, proving it becomes hard.
There's also a curious viewpoint: sometimes the issue isn't a lack of evidence, but disorganised excess. Too much information, zero structure.
2. What you need to prove
You need simplicity here: you don't need to prove everything, just something precise.
With chats and screenshots, the point is usually proving:
- that a communication took place
- when it took place
- what exactly it contained
- in what context (before/after other events)
- any subsequent confirmations or changes
In concrete terms:
- existence of a message or exchange
- content of a conversation
- chronological sequence across multiple communications
- version of a piece of information at a specific moment
- promise, agreement, or instruction received
The clearer you are on this point, the less useless material you will collect.
3. What to collect
This is where smart selection comes in. You don't need to save everything, you need to save well.
Useful material:
- full chat screenshots (including visible date and time)
- full conversation exports when possible
- original voice notes
- emails linked to the same situation
- documents shared during the conversation
- any attachments (PDFs, images, tech files)
- different versions of the same file
- internal notes or chronological memos
A frequently undervalued detail: a long, complete screenshot is better than three out-of-context crops.
Real-world example: a screenshot showing only "Ok, go ahead" holds little value. One showing the whole conversation before and after tells a story.
4. How to proceed
Now you take action. The goal is to build a timeline readable even by someone unfamiliar with the case.
Start by gathering all material into a single space. Don't work across five different folders.
Then:
- order files by date (not name)
- rename files descriptively (e.g., 2026-03-12_client_chat_confirmation)
- place screenshots and original files from the same phase side-by-side
- create a logical sequence: before → during → after
- briefly annotate what each element represents
At this point, build a simple narrative:
"At 10:12 request made → at 10:15 confirmation arrives → at 11:00 file sent → at 14:00 complaint arrives"
A little consultant's trick: assume the reader has zero patience. If they grasp everything in 2 minutes, you've done a good job.
Finally, lock the key files of the sequence in time, always keeping the original versions intact.
5. Mistakes to avoid
This is where people often stumble, even with good intentions.
Common mistakes:
- taking cropped screenshots without dates/times
- altering original files (even just opening and re-saving them)
- mixing different versions without distinguishing them
- saving only excerpts instead of full context
- relying on memory to "fill the gaps"
- naming files generically like screenshot1_final_def
Helpful tips:
- always keep originals separate from working copies
- avoid sending files via apps that compress them
- maintain consistency in names and dates
- if something is missing, point it out instead of reconstructing it from memory
Tidy documentation cuts down the work for whoever must analyse it and makes the whole sequence more credible. Free certification helps lock key steps in time without complicating the process.
6. After the documentation
Once the timeline is built, the strategic part begins.
Depending on the case, you can:
- share the reconstruction with your internal team
- present it to a technical consultant
- use it in a negotiation with the counterparty
- attach it to formal communication
- prepare it for potential use in legal contexts
Practical advice: don't send everything in one massive dump. Prepare a summary version hitting the key points and keep the rest as backup.
The reader must orient themselves instantly, without digging through dozens of files.
When the timeline is clear, the tone of the conversation shifts. And often the outcome, too.