1. How it usually happens
"I already have something in mind, I'll send two references."
Everything starts there: moodboard, examples taken online, some phrases thrown in call. Then you step in. You structure, improve, connect pieces, turn hint into usable asset.
Problem arises later:
client sees that output as natural evolution of their initial idea. You see it as creative work built step by step.
Typical situation:
- client proposes "a simple landing like this one"
- you build copy, structure, flow, visual
- project stops
- months later something very similar appears, developed elsewhere
From client's perspective, they just "carried forward idea".
From your perspective, someone used already developed work.
An art director told of receiving brief with three reference images. A week later delivers complete campaign. Client pauses it. Three months later, same campaign online, with small tweaks. "We followed initial concept", they tell him.
2. What you need to prove
Here the issue is clearly distinguishing between initial input and creative development.
You must be able to prove that:
- initial idea was generic or incomplete
- your intervention added structure, content, and form
- final assets already existed in defined version
- result is not a simple copy of initial references
- any reuses derive from your development
In practice:
"This is not just initial hint. It's the result of already built creative work."
3. What to collect
Your position's strength lies in showing process, not just final result.
Collect:
- client brief (email, chat, documents)
- initial received references (links, images, examples)
- intermediate work versions (drafts, iterations)
- source file (Figma, PSD, copy documents)
- complete asset exports (PDF, images, mockup)
- communications where you present or explain work
- any client feedback and revisions
- collaborative platform screenshots
A detail often making difference: showing "before and after". Jump between input and output makes added value evident.
4. How to proceed
Effective strategy is building clear trace of creative evolution.
When receiving client hint:
- save it as is (without reworking immediately)
- keep original references
During development:
- create saved intermediate versions
- keep input and output separate
- document creative choices (even with short notes)
When reaching significant version:
- export complete, stable version
- assign clear file name
- timestamp material with ExistBefore
After delivery:
- keep sending communications
- avoid retroactively modifying already shared files
- if updating, create new tracked versions
A useful approach is thinking of project as timeline: every important step deserves a documented "snapshot".
5. Mistakes to avoid
Some behaviours make it hard distinguishing your creative contribution:
- working directly on client materials without keeping them separate
- not saving intermediate versions
- delivering only final result without context
- mixing client input and creative development in same file
- losing track of initial communications
Useful precautions:
- always keep a "raw" copy of received inputs
- make process visible, not just result
- avoid overly generic files reusable without context
Free timestamping allows you to secure key development moments, making sequence between initial idea and realised work clearer.
6. After documenting
Once you have documented creative path, you can use it concretely.
You can:
- clarify with client what was developed compared to initial hint
- use material as base for more precise contract proposal
- reuse work parts in other contexts more safely
- address any reuses with concrete examples
If ambiguous situations emerge:
- compare initial inputs and developed assets
- collect any subsequent uses
- evaluate direct confrontation based on documented elements
When process is visible and orderly, it becomes much easier explaining where idea ends and work begins.