ExistBefore
IT

Professional

How to protect a web agency from creative disputes over completed work

"It's not how I imagined it" is one of the most expensive phrases in the creative world. To avoid it, you must turn tastes and opinions into documented elements. If you start tracking well today, the next review will be much more linear.

4 min read

1. How it usually happens

A creative project almost always starts with enthusiasm: moodboard, references, "we like this style", a few examples from other sites. Everything seems aligned.

Then come revisions.

First:

"Beautiful, maybe let's make it a tiny bit more modern."

Then:

"Maybe more minimal."

Finally:

"Actually we expected something completely different."

Meanwhile:

  • team followed received indications
  • client mentally evolved their own idea
  • nobody truly secured what was approved

Typical anecdote: homepage approved in call with great enthusiasm. Three weeks later, new stakeholder in company. Reaction: "Doesn't represent the brand". Approved version exists, but lives only in memories of those in that call.

There is also a less obvious aspect:

creative work is interpretative. Two people can look at same layout and have different expectations on what "finished" means.

Without a clear trail, every feedback becomes a story rewrite.

2. What you need to prove

Here the point is demonstrating what was proposed, what was approved, and in what version.

Concretely:

  • existence of creative proposals
  • exact version of layouts or concepts
  • feedback received from client
  • modifications requested and applied
  • intermediate approvals
  • context they occurred in (call, email, tool)
  • work state at a given moment

The typical question becomes:

"Was this solution already approved or was it changed later?"

3. What to collect

In creative work, evidence is often visual and distributed across multiple tools.

Fundamental materials:

  • design files (Figma, Adobe, Sketch, etc.) exported as PDFs or images
  • layout versions (homepage, inner pages, variants)
  • interface screenshots with visible date
  • comments and feedback left on collaborative platforms
  • emails with revisions or approvals
  • chats with creative indications ("more elegant", "fewer colours", etc.)
  • recordings or notes of review calls
  • brief documents and initial moodboards
  • prototypes or links shared with client

A very useful detail:

save snapshots of approved versions, not just updated files. A "frozen" screen avoids many arguments.

4. How to proceed

You need to turn creative flow into a readable sequence.

When presenting a proposal:

  • export a clear design version
  • assign name and date (e.g., "Homepage_v2_2026-05-01")
  • keep file exactly as shown to client

After presentation:

  • collect received feedback
  • if in call, send brief written summary
  • save or export comments from platforms

When approval arrives:

  • ensure it's explicit (even via email or chat)
  • keep message in its context
  • create a package (design + approval)

For every revision:

  • create new version, without overwriting previous
  • highlight what changed
  • link modification to received feedback

At this point:

  • organise materials by phase (concept, revision 1, revision 2...)
  • timestamp key moments (proposal, approval, final version)

Over time, build clear timeline:

proposal → feedback → revision → approval → development

5. Mistakes to avoid

Errors here are often tied to creative work speed.

  • always working on latest version without saving previous ones
  • approving designs only verbally in calls
  • not distinguishing between "feedback" and "modification request"
  • leaving comments scattered across different tools
  • using unclear file names ("final_def_real2.fig")

There is also a cultural error:

considering taste as something implicit and shared.

In reality, every preference should translate into a concrete, traceable signal.

Useful precautions besides timestamping:

  • ask explicit approvals for each phase
  • always summarise ambiguous feedback
  • maintain visual consistency between archived versions

When everything is documented, confrontation becomes much more objective. Free timestamping adds a precise time reference to versions you collected.

6. After documenting

If a dispute arises:

  • reconstruct version sequence
  • show proposals and relative approvals
  • highlight how feedback guided work

This helps shift conversation from "I don't like it" to "what was decided and when".

If needed:

  • involve client's main referent
  • prepare visual version summary
  • clarify which modifications are new requests

In more complex cases:

  • you can use documentation to support structured confrontation
  • having visual timeline greatly reduces misunderstandings

In the end, advantage is simple:

creative work stops being a perception and becomes a clear sequence of documented decisions.