A fiduciary sends a trust report to a beneficiary in March. In November, the beneficiary's lawyer claims they received a different version, one that did not disclose a specific transaction. The firm still has the file on its own server, dated March, but the beneficiary's lawyer points out that a file's internal date is set by whoever holds the file, and in this case that is the fiduciary itself. The report is very likely genuine and unchanged. It just is not provable on its own terms, and the firm is left arguing from memory against a document.
Law firms and fiduciaries produce a steady stream of documents that carry weight later: engagement letters, legal opinions, valuation reports, board resolutions, closing sets, trust accountings. Most of them are delivered by email, saved as a PDF, and never touched again, until somebody asks when a deliverable was finalized, whether it was the exact version the client received, or whether anything in it changed after the fact. At that point the delivery method matters as much as the content did on the day it was sent.
Why the usual delivery trail falls short
An email with an attachment shows a send date, but that date sits inside a mail server the sender controls, and the attached file can be swapped into the same thread later without much friction. A PDF can carry a "last modified" timestamp in its own metadata, but that metadata is written by the same software that produced the file in the first place. None of this makes a delivery dishonest. It means the record depends on trusting the party that produced it, and that is exactly the party a dispute puts under scrutiny.
For a fiduciary or a law firm this gap shows up in a specific, recurring way. A client, a regulator, or opposing counsel asks for proof that one particular deliverable, unchanged, existed at one particular point in time, and the honest answer sitting in most files today is "we believe so," not "here is how you check."
What it means for a deliverable to carry its own evidence
A sealed deliverable is built differently. At the point it is finalized, the file is hashed, a value derived from its exact contents that changes completely the moment a single character changes afterward. That hash is timestamped by a Qualified Trust Service Provider rather than by the sender's own system, and the identity behind the deliverable is tied to a verified signer rather than a name typed into a signature block. The result is a certificate that bundles the file, the date, and the identity into one record, with a link that resolves to a public verification page.
The test that matters here is simple. Can the client, an auditor, opposing counsel, or a court check the deliverable without asking the firm anything first. If yes, the record stands on its own. If checking it requires a phone call to confirm what was actually sent and when, the firm is still the only witness to its own work, and a firm cannot be a neutral witness to itself.
The legal weight behind it
Under eIDAS Article 41, a qualified electronic timestamp carries a legal presumption as to the accuracy of the date and time it indicates and the integrity of the data it is bound to. That shifts the practical burden in a dispute: the side disputing the date has to show the timestamp is wrong, rather than the firm having to prove from scratch that it is right.
In Switzerland, a qualified electronic signature combined with a qualified timestamp is deemed equivalent to a handwritten signature under Article 14 paragraph 2bis of the Code of Obligations. The certification framework behind that signature, who is permitted to issue one and under what controls, is set out separately in the Federal Act on Electronic Signatures (ZertES). Together, these two provisions are what separate a signed PDF sitting in a folder from a signature that carries the same standing in a courtroom as ink on paper.
Where this matters most in practice
An engagement letter sealed at the point it is sent settles what was agreed, and when, which matters if the scope of a matter becomes disputed a year into the relationship. A legal opinion delivered to a client fixes the exact advice given on a given date, which matters if the client's position later shifts and the opinion gets reread with different eyes, sometimes inside a malpractice claim. A valuation report handed to a fiduciary's beneficiaries or filed with a court proves the figures were not adjusted after the fact. A board resolution signed by several trustees needs every signer's identity checked independently, not just a stack of names collected on one page and trusted as a set.
Consider a closing set on a mid-size transaction. The final signature pages go out by email on a Friday afternoon, and by the following Monday one party's counsel is asking whether a specific clause in their copy matches what everyone actually signed. Without a sealed record, the firm is reconstructing the answer from sent-mail folders and whoever happens to remember the call. With a sealed record, the firm sends the verification link and the question closes itself.
None of these situations are rare or exceptional. They are the ordinary paperwork of running a practice or administering an estate. The difference is whether that paperwork can defend itself six months, or six years, later, once the person who remembers exactly how it was sent has left the firm.
Deliverables that travel across a border
Client work rarely stays inside one jurisdiction. A Swiss fiduciary reports to beneficiaries living abroad. A law firm's opinion gets forwarded to a counterparty's counsel in another country entirely. An internal file date, trusted only inside the office that set it, does not travel well once it leaves that office's own walls. A qualified timestamp does, because it is checkable evidence rather than an internal record: eIDAS requires a qualified timestamp issued in one EU member state to be recognised as qualified in every other member state, and the underlying intellectual property in most legal work product carries automatic copyright protection in the 181 countries bound by the Berne Convention, with no registration required anywhere. Proof that stands up the same way wherever it is opened is a different kind of proof from a record that only your own office is in a position to vouch for.
Building it into the delivery workflow
The practical shift is small. Instead of exporting a final PDF and attaching it to an email, the file is sealed at the moment it is finalized, before it leaves the firm. The certificate travels alongside the deliverable, or sits behind a link inside the same email. Nothing about how the client receives the document changes. What changes is what happens if that document is ever questioned. The firm can point to a verification page instead of piecing a story back together from memory and server logs, months or years after the fact.
For firms handling prior art, manuscripts, designs, or invention disclosures on behalf of IP clients specifically, the same logic applies to proof of creation. Swiss Trust Layer's setup for IP law practices covers how a qualified timestamp fixes existence and integrity for that kind of work product, which sits close to what a general legal opinion or a fiduciary report needs from a sealing workflow.
A short check before you send
Before a deliverable leaves the firm, three questions are worth asking. Is there a hash tied to this exact file, not a description of it. Is the date attached to it set by somebody other than the firm. And can the client, or anyone the client hands it to later, check both of those without calling the office first. A deliverable that answers yes to all three can defend itself on its own terms. One that does not is only as strong as the memory of whoever sent it.
Ready to seal a deliverable before it leaves your desk. See how it works for IP law practices, or start with the next report, opinion, or resolution due to go out this week.
