Client approval workflow for creative studios: steps, rounds and a template
An approval workflow is a short set of rules: who decides, how many rounds, how long they have, and what counts as a yes. Write it down before the first draft goes out.
The short answer
A client approval workflow has five parts. Name one person who gives the final yes. Set the number of rounds. Give each round a deadline. Define what counts as approved. Record the approval with a name, a version and a date. Put all five in the quote or the kickoff email, so the client agrees before the work starts.
Most disputes at the end of a job are not about taste. They are about a yes that was never recorded, or a round nobody counted.
Step 1Name who approves
Every job has one approver. This is the person whose yes ends the round, even if ten people give opinions.
Ask for the name at kickoff. "Who gives the final yes on the visuals?" is a normal question. If the answer is "the board", ask for the one person who collects the board's notes and speaks for them.
Other people can comment. They do not approve. Say so in writing, for example: "Maria Keller approves. Others can send notes through her."
Some jobs need two approvers, such as a brand manager for the look and a product owner for accuracy. Name both and say what each one signs off. Do not let it grow past two.
Step 2Set the rounds
A round is one full pass: you send a version, the client sends one consolidated set of notes, you apply them. Two rounds is common for a design or a render. A film cut often has two on the rough cut and one on the fine cut.
Put the number in the quote. "Two rounds included, a third billed at the day rate" gives both sides something to count. The wording for the clause is in the revision policy template, and the tactics for keeping the count down are in how to reduce revision rounds.
Rules that keep a round a round:
- One list of notes per round, from one person.
- Notes arrive in one place, not in three email threads.
- Notes on work from an earlier stage count as a new round, not a fix.
Step 3Give each round a deadline
Open feedback has no end. Set a date for each round and say what happens when it passes.
A workable rule: the client has 3 working days to reply to each version. If they do not reply, you send one reminder. If a further 2 working days pass, the version is treated as approved, or the schedule moves by the days lost, whichever the contract says. Pick one and write it down.
Silence is the hard case. Do not treat it as a yes unless the contract says so. Many studios choose to move the schedule, because it avoids an argument and the client still loses the slot.
Step 4Define what counts as approved
Write it as a sentence. "Approved means the named approver clicks Approve on the version, or replies to the version by email with the word approved."
Then list what an approval locks. For a render: composition, camera and materials are locked. Only colour and small cleanup remain. After approval, changes are a new quote.
A phone call is not an approval. "Looks good, thanks" in a chat with no version in it is weak. Ask for the version name back: "Approved: Kitchen_view02_v03".
Step 5Record it
Keep three facts: who approved, which version, and when. Without them, "I never saw that colour" is hard to answer.
In a review tool this is one click. In OIO the client opens the ticket link with no account, pins notes on the image or comments at a timecode on the video, and clicks Approve this version. OIO records who approved which version and when. Without a tool, save the email in the project folder and add the version name to the file name.
For the process on video, see a client approval process for video.
A template to paste
Copy this into your quote or kickoff email and fill in the brackets.
APPROVAL PROCESS Approver: [Name, role]. Only this person gives final approval. Notes: other team members send notes to the approver, who sends one combined list per round. Rounds: [2] rounds of changes are included in the price. Extra rounds are billed at [day rate] per day. Deadlines: we send each version on [date]. You reply within [3] working days. If we hear nothing, we send one reminder. After [2] more working days the delivery date moves by the days lost. What counts as approved: the approver clicks Approve on the version in the review link, or replies "Approved: [file name]" by email. After approval: [composition, camera and materials] are locked. Changes after that are quoted as new work. Record: we keep the approver's name, the version and the date with the project.
Adjust the numbers to the job. A 30-second animation needs longer per round than a logo.
Who should do what
The studio sends the version, with a one-line message saying what to check. "Check the layout and the copy. Colour is not final." This stops notes on things you have not done yet.
The client collects notes internally and sends one list. The tool or the email should make it easy for them to do so.
The studio resolves each note, marks it done, and sends the next version with a short list of what changed. The client approves, or opens the next round.
Where it goes wrong
- The approver changes mid-job. Ask for the new name in writing and note the date.
- Approval of a rough version is read as approval of the final. State what each stage locks.
- Rounds hide inside a long email chain. Move notes to one link per version.
- The studio fixes things nobody asked for, then bills no one. Note what was asked, and do only that.
Doing it in OIO
Create a ticket for each deliverable on the client's project, upload the version, and send the ticket link. A ticket waiting on the client shows a Needs feedback marker, and the client gets one reminder email a day, which you can switch off. A freelancer fixing the notes gets a ticket link with only their brief and files. When the client approves, the quote can become the invoice on the same project. Client review starts on Solo at $19 a month.
Questions
What is a client approval workflow?
It is the agreed set of steps for getting a yes on creative work: who approves, how many rounds, the deadline for each, and how the approval is recorded.
How many approval rounds should I include?
Two is common for a design or a render. Bill extra rounds at your day rate and say so in the quote.
What counts as client approval?
Whatever your contract says. A good rule is a click on Approve on a named version, or an email that repeats the file name with the word approved.
What if the client does not respond?
Send one reminder, then move the delivery date by the days lost. Write that rule into the quote before the work starts.
Who should approve creative work?
One named person per job, or two at most with separate scopes. Everyone else sends notes through them.