Traceability and compliance
When each side tells a different story
Neither side is lying: each holds a fragment. How to reconstruct what actually happened.
In almost every argument about a delay or a breach, both sides are telling the truth: each describes what they see from their end. You see it never arrived; they see they sent it. Both can be true at once, which is why arguing from memory gets nowhere.
The four usual mismatches
| They say | You see | What usually happened |
|---|---|---|
| "I sent it to you" | No record of anything | It went to another address or a mailbox nobody opens |
| "I already signed" | Still outstanding | They signed an old send, or opened without completing |
| "We warned you about the delay" | No record | It was said by phone and nobody wrote it down |
| "That is not what we agreed" | You remember it differently | It was settled in an email thread with no summary |
Important
All four share a root: **the information existed and did not end up in the shared place**. And all four resolve equally badly afterwards and equally well in the moment — so the work is not winning the argument, it is making the next one impossible.
How to reconstruct what happened
- 1
Start with what has an objective date
Send statuses, deliveries, uploads, signatures. They do not depend on anyone's memory.
- 2
Put both sequences side by side
Yours and theirs, by date. The gap shows itself.
- 3
Ask about specifics, not generalities
"Which address did you send it to and on what day?" moves forward; "are you sure you sent it?" stalls.
- 4
And note the outcome in the file
Even with no blame to assign: next time, that note is the starting point.
Watch out
The nuance that changes the tone: most of these mismatches are not bad faith, they are channel problems. Someone sent to an obsolete address, or replied to an old email, or spoke to a person who no longer handles the matter. Come in accusing and the other side defends itself and you stop learning what happened; come in asking about detail and they tell you.
What prevents the mismatch next time
The first removes the most arguments outright: when the document comes in through the shared route, there are no longer two stories — there is one that both sides can see.
Worth knowing
If the discrepancy is heading for a claim, seal your account along with what supports it before sending. It does not prove you are right, but it fixes what you said and when, which is what gets disputed later.
›What if the other side really is wrong?
Showing the dated sequence convinces far more than insisting.
›Should we show them our record?
Nearly always yes: it turns an argument about perceptions into one about facts.
›What if nothing was recorded at all?
Then the conversation is about how to work from now on, not about who failed.
A real case
The situation
A supplier insists they sent the certificate and the company has nothing.
What you do
- They lay both sequences out by date and ask which address it went to
What you get
It turns out it went to a decommissioned generic mailbox, and submissions move to the link.
The situation
Each party tells a different version of what happened.
What you do
- Checks the recorded sequence with its dates
What you get
The dispute closes by looking.
The situation
There is an argument about who said what and when.
What you do
- Keeps the communications with their dates
What you get
What was said can be read.
The situation
One version rests on an email that no longer exists.
What you do
- Stores what matters outside personal inboxes
What you get
The evidence outlives the people.
The situation
The story is reconstructed from memory.
What you do
- Checks the file's history
What you get
The reconstruction comes from the record.
The situation
What happened must be explained to a third party.
What you do
- Shares the sequence with controlled access
What you get
The third party reads rather than believes.
This article answers
- the supplier says they did send it
- conflicting versions of what happened
- reconstructing what happened in a case
- date discrepancy with a client