Designers Should Create Evidence Before Client Review

Why Should Designers Create Evidence Before Client Review?

A designer spends three weeks on a brand identity. Logo variations, a color system, type pairings, mockups on packaging and signage. The files go out to the client for the first round of feedback, and from that point on, the designer has no real control over where they travel next. Maybe the client loves the direction and quietly hands it to an in-house team to "finish." Maybe a stakeholder who never signed the contract claims the concept was theirs to begin with. Maybe, months later, a dispute over scope or ownership ends up in front of a lawyer, and the only thing anyone can point to is an email thread with vague timestamps and no record of what the original files actually looked like.

None of this is rare. It's one of the quieter risks of creative work, and a dated file record can help document what existed before it was shared. It does not prevent copying, replace a contract or guarantee that a dispute will be resolved.

The moment of maximum exposure

Client review is the point where a designer's control over their own work is lowest and the potential for dispute is highest. Files get forwarded. Screenshots get shared in Slack channels the designer isn't part of. A client's internal team sees the concept and, whether through carelessness or intent, treats it as a starting point for their own version. When that happens, the designer's only leverage is being able to show, with hard evidence, what existed and when.

Timestamping and copyright registration serve different purposes. A file fingerprint and blockchain record support prior existence of a matching file. They do not register copyright or assign ownership. Preserve contracts, communications and version history alongside the proof.

What a pre-review timestamp actually proves

A blockchain-anchored timestamp doesn't store or expose the design itself. It takes a cryptographic hash a unique fingerprint generated from the file's exact contents via SHA-256 hashing and anchors that fingerprint to a public blockchain ledger. Change a single pixel, a single layer, a single character of code in the file, and the hash changes completely. The ledger entry becomes an immutable file verification record: proof that a specific, unaltered version of the design existed at a specific moment, verifiable by anyone, without needing to trust Certelo, the designer, or the client's word for it.

For freelancers and agencies, this creates a reference for an exact saved design. It is evidence of prior existence and file integrity, with limits: it does not prove authorship or ownership and does not guarantee acceptance by a court, arbitrator or insurer.

Why "before review" matters more than "eventually"

Designers who do think about protecting their work often do it reactively after a dispute has already started, or after a client has already gone quiet on payment. By then, the useful window has usually closed. A timestamp created after the fact only proves the file existed as of that later date; it says nothing about what was shown to the client, or when.

Create the record before sharing if you want evidence that a matching file existed by that earlier time. Keep the actual sent message, attachment and client feedback as well. A timestamp alone does not prove what was delivered, who developed the concept or who is entitled to payment.

A workflow that doesn't slow anyone down

At a meaningful checkpoint, preserve the final export or project file and create its proof through Certelo before sharing it. The file is hashed locally without upload. Check the confirmation status and keep the original and proof references together; processing and network times can vary.

Preserve files at meaningful milestones, such as an initial concept, a reviewed version and final delivery. Their timestamps can support a chronology, while the related communications explain the context and decisions.

Common questions

Does this replace a contract or an NDA?

No. A timestamp is evidence of what existed and when — it doesn't set terms, ownership splits, or payment obligations. It works alongside a contract, not instead of one, and tends to matter most when a contract's terms are being disputed rather than absent.

Can a client tell I've timestamped a file?

No. The process doesn't touch the file the client receives or leave any visible trace in it. The hash and the blockchain record exist entirely separately from the deliverable itself.

Is this only useful if something goes wrong?

It can be useful when someone needs to compare versions or examine a timeline. The value depends on preserving the original files and supporting records; a timestamp does not promise a quick resolution or a successful claim.

Designers can add dated references to important saved versions before sharing them. Certelo hashes the selected file in the browser without uploading it. Preserve the original, proof references and project records for a later comparison.proof-of-existence platform that lets creators generate this kind of verifiable record without uploading their files or trusting a third party to keep the record honest.