Most approval problems don't start in the piece: they start in what was never said. With each client, in writing and before you start:
02
Ask for approval in a way that can be given
“Looks OK?” in a voice note is not an approval request. A request carries everything the person needs to decide without asking:
03
When they ask for changes
Endless changes are rarely the client's fault: they come from changes that arrive loose, half-finished and unconfirmed.
04
When they don't reply
Chasing isn't about insisting harder: it's about having decided in advance when to remind, who to escalate to and what happens if there's still no answer.
05
Keep a record of every approval
What isn't written down wasn't approved. And what isn't measured can't be fixed.
What you can do this week, without changing tools
If you'd rather it just happened
Everything above can be done with email and a spreadsheet. PortaliaFlow does it for you, in a portal with your brand:
Each piece goes out with a deadline and the client answers on the piece itself: “Approved” or “Changes”. Asking for changes requires a note.
Three automatic reminders (next day, after three days and after a week, configurable) and escalation to the account manager and to you.
Every delivery is a version and every round of corrections is numbered.
Who approved, which version and when is recorded, with no separate table.
Emails go out with your agency's sender, from your domain.