SmartCheck
What certifying does not solve
Four things people expect from a seal that it does not provide, and what to use instead.
Certifying does one thing and does it very well: it fixes that a specific file existed on a date and has not changed since. Almost all misunderstandings come from expecting four further things that are not included — worth knowing before resting a claim on it.
The four it does not give
| What many people expect | The reality | What actually helps |
|---|---|---|
| That it proves the content is true | It proves the file said that, not that it was true | The source document and whoever answers for it |
| That it proves who created it | It proves possession on a date, not authorship | Contracts, intermediate versions and the trail of work |
| That it proves the other side read it | That is outside the seal | The record of sending, delivery and opening |
| That it keeps a copy safe | It keeps a fingerprint, not the file | Keeping the document in its file, plus a copy of what is critical |
Important
The first row causes the most confusion in commercial conversations. A sealed delivery note proves that note, with that text, existed on the 4th — it does not prove the goods were delivered. The seal protects the document's **integrity and date**; what the document asserts is still worth whatever whoever signed it is worth.
Where it does change the outcome
In those four cases it adds something no other measure provides as cheaply, which is why it is worth having in the right places rather than everywhere.
Watch out
The nuance nobody deduces: verification is done on the **exact** file. If someone opens the PDF and saves it again, or compresses it, or prints and scans it, it is already another file and will stop verifying even though it reads identically. When you send evidence to a third party, send the file as it is, without touching it "to make it smaller".
How it works alongside the rest
- 1
Sign when what matters is that someone accepts something
A signature adds identity and consent; a seal adds integrity and date.
- 2
Record the send when what matters is that it arrived
Delivery and opening are separate evidence.
- 3
And certify when what matters is that it has not changed
The three complement each other and none replaces the other two.
Worth knowing
That a third party can verify it without asking you for anything is half the value: if verifying requires trusting you, you have added little to simply keeping the file.
›Does it stand up in court?
It provides date and integrity, which is a lot. Final weight is for the court, alongside the rest of the evidence.
›What if the file is lost?
The check has nothing to work on: the fingerprint does not reconstruct content.
›Should I certify everything just in case?
It does not pay: sealing what nobody will dispute consumes and adds noise.
A real case
The situation
A company seals every delivery note believing it proves the deliveries.
What you do
- Understands the seal proves the document, not the event
- Adds the recipient's signature at delivery
What you get
It can now evidence the delivery, not merely that the note existed.
The situation
A seal is expected to stop somebody copying an idea.
What you do
- Understands it proves existence, not exclusivity
What you get
Expectations are set before they are needed.
The situation
A seal is expected to bind the other party.
What you do
- Signs whatever must bind
What you get
Each tool does its own job.
The situation
It is expected to validate the document's content.
What you do
- Understands it proves what it said, not whether it was true
What you get
It is not credited with a verification it does not perform.
The situation
It is expected to replace an official register.
What you do
- Checks with the adviser what each case requires
What you get
The seal complements rather than replaces.
The situation
It is expected to organise the archive.
What you do
- Organises before sealing
What you get
The seal rests on something ordered.
This article answers
- what does certifying a document actually prove
- does a seal prove it is true
- limits of evidence certification
- does certifying prove authorship