Client approval workflow: how work actually gets signed off (and how to stop the version churn)
Ask any studio what eats their margin and the answer is rarely creative work — it's approvals. Feedback scattered across email, WhatsApp and calls; versions named "final_final_v7"; a stakeholder appearing at round four. A good approval workflow fixes the system, not the people.
The five-stage workflow
- Agree the rounds up front. Contract for two rounds of revisions, in writing, before work starts. Unlimited rounds don't protect the client; they guarantee drift.
- Name one approver. Their yes is the only yes. Commenters feed them; they don't feed the studio directly. (See the design brief template, question 8.)
- Collect feedback in one channel, per round. Consolidated notes, one list, no contradictions between three inboxes.
- Version everything visibly. Each round is a distinct, labelled version — and the response to each note is visible (done / discussed / declined with reason). Declined-with-reason is the underrated one: it stops the same note returning in round three.
- Capture sign-off as an event. Not "we emailed on Tuesday" — a dated, attached-to-a-version record of who approved what.
Where teams run this today — honestly
Most small teams run approvals on a patchwork: email for sign-off, a shared drive for files, chat for the urgent nudges, maybe a project tool for tasks. It works until volume or client count grows, then the seams show: feedback fragments, and the approval trail becomes archaeology.
Dedicated options exist at several weights — project management tools (Trello, Asana, Monday), proofing platforms, and all-in-one agency systems. They differ in price model, learning curve, and how much process they impose on a five-person team. We're deliberately not rating competitors here; the right question is simpler: does your current setup let you answer "which version did the client approve, and when?" in under a minute? If not, the workflow above will help regardless of tooling.
CreativeBoard takes the narrow slice of this problem that causes the most churn — brief, versions and approvals held together in one shareable object per item — and is priced for small teams rather than per client or per seat. Early access is free:
Common failure modes (and the one-line fix)
- The phantom approver: a senior stakeholder reopens round three. Fix: approver named in the brief, before work starts.
- Feedback in five channels: fix: one consolidated round per cycle; everything else is context, not feedback.
- "Approved" that isn't recorded: fix: sign-off is a dated event attached to a version, not a feeling.
- Scope creep disguised as feedback: fix: each note is mapped to the brief; notes that change scope are priced, not absorbed.