revisions-and-approvals
How we handle client feedback, revision rounds, and sign-off. Clear process here protects the team and sets honest expectations with clients from the start.
The revision model
Standard project scope includes two review rounds. This is communicated at brief stage, not after the first round of feedback arrives.
Round 1
First draft presented. Client consolidates all feedback before responding.
Round 2
Revisions actioned. Second and final draft presented for sign-off.
Additional rounds
Estimated separately. Agreed before work begins, not after
Rules of the revision process
Consolidated feedback only
We do not accept feedback drip-fed across multiple emails or messages. The client sends one consolidated response per round. This is set at kick-off.
Feedback is not a new brief
If client feedback changes the objective, audience, or core message of the work, that is a scope change, not a revision. We flag it, pause, and requote if needed.
Written approval before delivery
Nothing is finalised, published, or printed without written client approval. A reply email saying "approved" is sufficient. We keep a record.
Internal review first
Work is reviewed internally before every client-facing send. We do not let unreviewed work leave the building.
Version naming
Files are named clearly: ClientName_ProjectDescription_v1, v2, FINAL. Final means approved — it is never applied to a work in progress.
What 'approved' means
Approval is not silence. It is a positive written confirmation from the client that the work is complete and ready for delivery, print, or publication. If we have not received explicit approval, the project is not approved.