Does a qualified timestamp replace a signed contract?

No. A qualified timestamp and a signed contract serve different purposes. The contract defines what both parties agreed to: scope, price, and ownership terms. The timestamp proves that specific files existed at a specific moment in time, before any dispute starts. Agencies should have both. The timestamp protects your creation record; the contract protects the agreed terms. If you have to choose which comes first, seal the files before they leave your system, then chase the contract signature.

What if I already sent the files to the client without sealing them first?

A timestamp applied after delivery proves the file existed at that later moment, not at the original moment of creation. It is still better than no record at all, but it is not the strongest position. The most defensible record is one created before the client receives any files. For active disputes, consult a legal professional. For all future projects, seal before you send. The two-minute process takes less time than a single follow-up email.

Can a client or their legal team dispute a ZertES or eIDAS qualified timestamp?

The timestamp is issued by an independent, accredited trust service provider under a regulated legal framework. The hash is computed from the exact file at the exact moment of sealing. Altering the file after the fact produces a different hash, which invalidates the certificate. A client cannot credibly dispute the record without challenging the accreditation of the issuing authority, which is a significantly harder legal argument. Swiss courts confirmed this standard in BGE 144 III 97 (2018), and the EU standard is confirmed under ECJ C-507/17 (2019).

Does this apply to all creative deliverable types, or only certain file formats?

Any file can be sealed: PDF presentations, ZIP archives of brand files, layered Photoshop or Illustrator documents, InDesign packages, video exports, motion graphics source files, UX prototypes, code repositories, and contract drafts. The platform hashes whatever file you upload. The format does not affect the legal validity of the timestamp. The common practice is to compress all deliverables into a single ZIP archive before uploading, so one certificate covers the entire project handover.

How long does a ZertES or eIDAS timestamp certificate remain valid as evidence in court?

Both ZertES and eIDAS qualified timestamps use RFC 3161 cryptographic standards, which are designed for long-term archival use. The standard supports renewed timestamping to extend cryptographic validity as algorithms evolve. For most agency disputes, which typically arise within two to three years of project delivery, the original certificate is fully sufficient. Swiss Trust Layer issues certificates that support long-term archival (LTA) signatures under ETSI EN 319 422 for longer-term needs.

Proof of Creative Work Ownership

Sharing creative deliverables before a contract is countersigned leaves a gap in your ownership evidence. One qualified timestamp, applied before the files leave your system, closes it.

A Geneva-based brand studio delivered a complete visual identity to a Series A startup in March. The files went over. The invoice followed. The contract stayed unsigned. Four months later, the startup's new management claimed the designs were created internally. The studio had email threads, mood boards, and draft invoices. What they lacked was a single tamper-proof record proving the work existed before any dispute began.

Direct answer: Sharing creative work before a contract is countersigned leaves a gap in ownership evidence. If a client disputes authorship, you must prove your work predates any competing claim. A qualified timestamp, issued under ZertES (Switzerland) or eIDAS (EU), cryptographically records the exact moment a file existed. That record is court-admissible in Switzerland (BGE 144 III 97) and across all 27 EU states (ECJ C-507/17), with no lawyer or registry required.

The Gap Between "Delivered" and "Legally Protected"

Most creative agencies operate on trust. A client brief arrives. Work begins. Deliverables go out before the contract is countersigned, because that is how client relationships move in practice. The formal agreement catches up later, or sometimes not at all.

This gap is not a legal technicality. It is a real exposure point. Under Swiss law and across the EU, copyright exists automatically from the moment of creation. But "moment of creation" is a claim, not a fact, until it is supported by dated evidence that a court will accept. Email timestamps from your own server, version numbers in your project management tool, and internal cloud storage logs all share a common weakness: you control them. That means an opposing party can argue they are not independent records.

If a client later says your logo concept was derived from their brief, or that the UX flows were developed by their internal team, the dispute is no longer about who is right. It is about who can prove a verifiable timeline.

What an IP Dispute Actually Costs

Swiss arbitration data is direct on this point. The Swiss Arbitration Association estimates the average IP dispute cost at CHF 150,000 to CHF 400,000, including legal representation, expert fees, and lost billable time. For a mid-sized agency, a single contested project can equal an entire year of profit margin.

Most of those costs accumulate before any finding on the merits. Correspondence, hearings, and document requests all accumulate costs before any ruling on the merits. Agencies lose money in the process even when they ultimately win. Preventing the dispute entirely, or resolving it quickly with clear dated evidence, is worth far more than those figures suggest.

What Changes with a Qualified Timestamp

A qualified timestamp is not a registration. It is not a contract. It is a cryptographic record, signed by an accredited trust service provider, stating: this exact file existed at this exact moment. The hash is the fingerprint of the file. The timestamp is the clock. Neither can be altered after the fact.

Under ZertES Article 2, qualified timestamps issued by Swiss-accredited providers carry a legal presumption of accuracy. The Swiss Federal Court confirmed court-admissibility in BGE 144 III 97 (2018). Across the EU, the European Court of Justice ruled in ECJ C-507/17 (2019) that eIDAS-qualified timestamps are legally binding in all 27 member states.

This is not a software feature. It is a legal instrument. And it is available from CHF 5 per document.

How the Scenario Would Have Resolved

Return to the Geneva studio. Before sending the identity files to the client, the studio uploads the archive to Swiss Trust Layer. The platform applies a ZertES-qualified timestamp to the package. A verifiable certificate is generated and stored. The studio then sends the files.

Four months later, when the dispute begins, the studio retrieves the certificate. The timestamp shows the completed identity package existed, was hashed, and was recorded in March, before any internal work by the startup's new management team could have produced the same designs. The arbitration panel has an independent, dated record. The studio has clear evidence of prior creation. The dispute resolves faster, at lower cost, and with the studio's authorship confirmed.

None of that required a lawyer in March. It required CHF 5 and two minutes.

Swiss Trust Layer has processed more than 47,000 sealed works since launch. A significant portion comes from creative professionals who treat sealing as a standard step in client handover, alongside watermarking proofs or version-tracking deliverables.

Three Steps to Seal Work Before Client Handover

The process is the same for a solo freelancer and a 40-person brand studio. Make it part of your standard handover checklist.

Compress your final deliverable files into a single archive. Gather all final files as they will be delivered, not working drafts or source files you are still revising. Include what the client will receive. This ensures the timestamp covers exactly what is in dispute if a challenge ever starts.
Upload and seal with a qualified timestamp. Upload the archive to Swiss Trust Layer. The platform hashes the file and applies a ZertES (Switzerland) or eIDAS (EU) qualified timestamp from an accredited trust service provider. A verifiable certificate is generated in under two minutes. Cost: from CHF 5 per document.
Store the certificate first, send the files second. The sequence matters. Save the certificate in your project records before the files leave your system. The certificate is your dated, tamper-proof proof of prior creation. If a dispute starts next month or in three years, it is the first document your legal contact will ask for.

Why "I Have the Files" Is Not Enough

Agencies often believe that email timestamps, cloud storage metadata, or version control logs will protect them in a dispute. These records are useful context. They are not qualified legal evidence in the way a ZertES or eIDAS timestamp is.

Email timestamps can be questioned. Cloud metadata is editable by the account holder. Internal file versioning reflects your own system's clock, which you control. A qualified timestamp is issued by an independent, accredited third party, under a regulated legal framework. That independence is exactly what gives it legal weight that your own records cannot match.

Protect the Work You Have Already Done

The studio in our opening could have paid CHF 5 before sending the March identity files. That one record would have pre-empted four months of dispute, removed the legal cost exposure of CHF 150,000 to CHF 400,000, and protected a client relationship that had started well.

The work was theirs. The question was never talent or effort. The question was evidence.

Seal your next deliverable before it leaves your system. Start here, from CHF 5 per document.

You Sent the Work. Now Prove You Made It.