A potential client asked me to prove that my branding work was not AI-generated before signing a contract. I had no idea how to respond. What are people doing to verify and document their creative process these days?
This is rapidly becoming one of the most important questions in creative work, and I have been dealing with it on the agency side for the past year. We had a client contractually require proof of human authorship in Q1, which forced us to actually build a documentation system. Here is what I learned after testing various approaches and tools across about a dozen projects.
Why This Problem Exists Now
The explosion of AI-generated creative work has created a trust deficit. Clients cannot visually distinguish between AI-assisted and fully human-created branding work in many cases, and some have been burned by agencies that charged full rates for AI-generated deliverables. The demand for proof of originality is not paranoia. It is a reasonable response to a market where the production method is no longer visible in the output. We lost a pitch earlier this year because the client suspected our previous work samples included AI-generated elements. They were wrong, everything was human-created, but we had no system in place to demonstrate that. That experience is what pushed me to build a documentation workflow.
The challenge is that proving a negative (“this was not AI-generated”) is fundamentally harder than proving a positive (“here is how this was made”). The most effective approaches focus on demonstrating process rather than disproving AI involvement, because detailed process documentation is something that AI-generated workflows simply do not produce naturally.
Process Documentation Methods I Tested
1. Adobe Content Credentials (C2PA Standard) - Best Technical Solution
Content Credentials is the most promising technical approach. If you create work in Adobe Creative Cloud apps (Photoshop, Illustrator, InDesign), you can enable Content Credentials, which embed tamper-evident metadata showing exactly how the file was created, what tools were used, and whether any generative AI features were involved.
I tested this on five branding projects. The metadata is comprehensive: it logs every edit, every tool used, and whether any AI generation (like Generative Fill) was involved. Clients who understand the technology find it compelling.
- Pros: Industry-backed standard, works with tools designers already use, tamper-evident, increasingly recognized
- Cons: Only works within the Adobe ecosystem currently, clients need to know how to verify, metadata can be stripped if files are exported incorrectly
The verification step is important: clients can inspect Content Credentials at Content Credentials by uploading or dragging the file. This shows them a complete provenance chain including tools used, edit history, and whether any generative AI features were involved. I walk clients through this the first time and it immediately builds confidence. Several have told me they started requesting it from other vendors after seeing how transparent it makes the creative process.
2. Screen Recording the Full Process
This is the brute-force approach, and honestly, it works. I started recording my screen during all creative work using OBS (free) or Loom (if I want easy sharing). A time-lapse of a 12-hour branding project compressed to 15 minutes is hard to argue with. You can see every decision, every iteration, every dead end.
- Pros: Undeniable proof of process, clients love watching the creative journey, doubles as portfolio content
- Cons: Creates massive files, requires remembering to hit record, editing the footage adds overhead
3. Version Control with Timestamps
Using Figma, Abstract, or even just saving incremental versions in a structured folder system creates a paper trail. I save a version at every major decision point with a naming convention that includes dates and descriptions. For vector work, I use git-based version control through Kactus which tracks every change.
- Pros: Creates detailed history, easy to present to clients, integrates with existing workflows
- Cons: Requires discipline, does not prove the work was not AI-generated and then manually recreated, timestamps can be manipulated
For Figma specifically, the version history is excellent because it captures every save point automatically. You can walk a client through the entire evolution of a design from first artboard to final deliverable. The key is labeling your versions meaningfully as you work rather than relying on auto-saves alone. I name versions at every major decision point: “initial concept exploration,” “direction A refined after feedback,” “final type and color lockdown.” This turns the version history into a readable narrative of creative decision-making.
4. Numbers Protocol - Blockchain Provenance
Numbers Protocol takes a different approach by registering your creative assets on a blockchain with creation metadata. It is more focused on establishing ownership than proving process, but the timestamp verification is useful.
- Pros: Immutable record of creation date, decentralized verification, good for establishing precedence
- Cons: Does not prove process, just ownership and timing, adds friction to workflow, blockchain skepticism from some clients
5. Digimarc - Digital Watermarking
Digimarc embeds invisible watermarks in your creative assets that persist through editing, screenshots, and even printing. It is more about protecting work than proving originality, but it establishes ownership chains.
- Pros: Invisible watermarking, survives most transformations, enterprise-grade
- Cons: Primarily about ownership not process, expensive for individual designers, does not prove human authorship
6. Detailed Process Decks
This is low-tech but effective. For every branding project, I now create a process deck that includes: initial research and moodboards (with sources), hand sketches and early concepts (photographed on paper), iterative digital explorations showing progressive refinement, rejected directions with explanations for why they were abandoned, and final deliverables with rationale.
The rejected directions part is key. AI-generated work rarely includes convincing dead ends, because most people using AI only keep the outputs that work. A folder full of terrible ideas that led to the final concept is one of the most human things you can show.
I typically include 8 to 12 rejected concepts in my process decks, organized by exploration phase. Each gets a brief annotation explaining why it was abandoned: “this direction felt too corporate for the brand personality,” or “the client preferred warmer tones so this cool palette was shelved.” The annotations demonstrate the kind of strategic reasoning that AI-assisted workflows rarely document, and that specificity is what convinces skeptical clients.
Comparison Table
| Method | Proves Process | Proves Ownership | Ease of Use | Client Acceptance | Cost |
|---|---|---|---|---|---|
| Content Credentials | Yes (within Adobe) | Yes | Medium | Growing | Included in CC |
| Screen Recording | Yes (definitive) | Indirect | Easy | High | Free (OBS) |
| Version Control | Partial | Yes (with timestamps) | Easy | Medium | Free/Low |
| Numbers Protocol | No (timing only) | Yes | Medium | Low (blockchain) | $$ |
| Digimarc | No | Yes (strong) | Medium | Medium | $$$ |
| Process Decks | Yes (narrative) | Indirect | Labor-intensive | High | Free |
What I Actually Do Now
My current workflow combines three of these approaches:
- Content Credentials enabled on all Adobe work, which happens automatically once you set it up
- Loom screen recordings of key creative sessions, not every minute of work, but enough to demonstrate real human decision-making
- Process decks for major projects, because clients respond to narrative explanations even more than technical proof
This combination covers the technical verification angle, provides visual evidence, and offers a story that clients can actually understand and appreciate.
The time investment is modest once you set up the systems. Content Credentials are a one-time settings toggle. Screen recording is just remembering to hit the record button (I put a sticky note on my monitor for the first month until it became habit). Process decks take about 30 to 45 minutes to assemble after a project wraps, and I now consider that time a non-negotiable part of project closeout, same as archiving files and sending the final invoice.
What to Tell Your Client
For your specific situation, @Willowdusk, I would respond with confidence rather than defensiveness. Something like: “I document my creative process with screen recordings, version history, and embedded content credentials. I am happy to share process documentation for any project.” That positions you as a professional who already has systems in place, not someone scrambling to prove something.
The Bigger Picture
We are in a transitional period where the tools for proving originality are catching up to the tools for generating content. Content Credentials and the C2PA standard are the long-term answer, but widespread adoption will take a few more years. In the meantime, the combination of process documentation, screen recording, and honest communication with clients is the practical path forward.
The designers who build these documentation habits now will have a significant trust advantage as the market continues to grapple with AI-generated content. It is extra work, but it is the kind of extra work that pays off in client relationships and professional reputation.
I also want to note that this is not just about defending against suspicion. The process of documenting your creative journey often surfaces insights about your own methodology that you would not notice otherwise. Several of my team members have told me that the habit of recording and annotating their process has actually improved the quality of their creative decisions, because it forces a level of intentional reflection that is easy to skip when you are just heads-down making things.
honestly this is something I have been worrying about but never actually addressed. The screen recording idea from @voidvibes92 is the most practical starting point for me because it requires zero new tools. I already have OBS installed for streaming. The biggest insight for me is the point about rejected directions being one of the most human things you can show. I have a folder on every project full of terrible early concepts that I used to be embarrassed about. Turns out that is actually my proof of process. Going to start including a “rejected concepts” section in my client presentations.
The technical side of this is worth breaking down a bit more since @CrispestHaze88 and @voidvibes92 covered the creative documentation angle well. From a web design perspective, here is what I actually implement for clients who care about content authenticity.
First, enable Content Credentials in every Adobe app you use. It takes about two minutes in settings and then it runs silently in the background. When you export assets, make sure to include credentials in the export settings because they are sometimes stripped by default in certain formats. For Photoshop, go to File then Content Credentials then enable at the document level.
Second, build a timestamped asset pipeline. I use a combination of git for code assets and Figma version history for design assets. Every meaningful change gets committed with a descriptive message. This creates an immutable timeline that is extremely hard to fake, especially with git because each commit has a cryptographic hash.
Third, consider adding a process journal to your project management setup. I use a simple Notion page per project where I log decisions as I make them: why I chose a particular color palette, what reference materials I studied, which approaches I tried and rejected. This takes maybe five minutes per session and creates documentation that no AI-generated workflow would naturally produce.
For the original question about what to tell a client: frame it as quality assurance rather than defense. You are not proving innocence. You are demonstrating professional process. This reframing matters because it changes the emotional tone of the interaction entirely. Instead of feeling like you are being interrogated, you are presenting evidence of the care and thought you bring to every project.
The clients who ask for proof of originality are actually the clients who value craft the most, and showing them your process is a selling point, not an obligation. I have started including a brief “Authenticity and Process” section in my proposals that outlines how I document and verify my creative process. It covers the commit-based version history, the Content Credentials setup, and the availability of process recordings on request. Not a single client has questioned my work since I started doing this, and several have told me it was a factor in choosing to work with me.
Include a brief process documentation section in your proposals going forward and you will never get caught off guard by this question again. The five minutes it takes to add that section pays dividends in client trust that compound over every project.
Really practical thread. One thing I want to add is that hand sketching early concepts on actual paper and photographing them is still one of the most convincing proof points. There is something about seeing a designer’s messy handwriting and rough thumbnail sketches that no AI workflow can replicate convincingly. The imperfections, the crossed-out ideas, the arrows and annotations in the margins are all deeply human markers that are almost impossible to fabricate.
I have started photographing my sketchbook pages with a timestamp app that embeds the date and GPS coordinates directly into the image metadata. It is overkill, but when a client asks, pulling out a dated photo of a hand-drawn concept that clearly predates the final digital work is an airtight response. I had one client who was initially skeptical about my process, and showing them three pages of rough sketches with timestamps from the first week of the project completely changed the dynamic. They became one of my best referral sources.
The approach @Snaxx_TechGrid outlined for git-based version control is smart too. I might set that up for my own workflow since it adds a technical verification layer on top of the visual documentation.
Late to this thread but glad I found it. I think the market is going to bifurcate into designers who can prove their process and designers who cannot, and the pay gap between those two groups is going to widen significantly. The point @voidvibes92 made about Content Credentials being the long-term answer resonates with me. Once every major creative tool supports C2PA and every platform verifies it, this whole problem mostly goes away. Until then, the screen recording plus process deck combo is the most accessible solution for most of us.