Skip to content
Guide

A simple design approval process

An approval process does not need software or paperwork. It needs five clear stages, one person who decides, and a record of what was agreed. Here is a version that works for a freelancer or a small studio.

The five stages

1. Brief. Write down the goal, the audience, the deliverables, the number of change rounds and the deadline. Get the client to confirm it. Everything later is measured against this page.

2. Concepts. Show a small number of directions. Ask the client to choose one, or to say what to combine. Do not move on until one direction is chosen.

3. Refinement. Work on the chosen direction through the agreed number of rounds. At the end of each round, send a short list of what you changed and what you did not, so the client can confirm it.

4. Final approval. The person with the final say approves one numbered version. Record the date and the version. This is the moment the project is agreed.

5. Handover. Release the final files, in the formats you agreed, after the final invoice is paid. Keep a copy of the approved version and the record of the approval.

Who decides what

Separate people who give feedback from the one person who approves. A committee can comment freely, but one named person says yes. If two people disagree, the approver decides, or asks the client to settle it before the next round.

What to record at each stage

With Roundfy most of this is recorded for you: each version is numbered and dated, comments are pinned to the spot and attributed, and every approval is kept with its date. Boards also produce a round report you can send to the client.

How to avoid scope creep

Scope creep is usually a missing line in the brief rather than a difficult client. State what is included, state what a new round costs, and compare any new request with the brief. Say it kindly and early: “That sounds like a new direction, which would be an extra round. Shall I quote it?”

Common questions

Who should have the final say on a design?
One named person on the client side who has the authority to approve and to pay. Agree who that is in the brief. Other people can comment, but they do not approve.
What should a sign-off record include?
The name of the approver, the exact version approved, the date and time, and any conditions, such as “approved subject to the colour change in comment 4”.
How do I handle feedback from many people?
Collect it in one place, tied to the exact spot it refers to, then merge it into one list of changes for the client to confirm. Do not work from separate emails and messages.
Do I need special software for this?
No. A shared document and a clear brief will do for a small project. Software helps when you run several projects at once, when reviewers are many, or when you want a dated record without keeping it by hand.

See how a full round looks in the live demo, or read how to get a client to sign off a logo. All guides.