It's the 24th, 11:40 p.m. A client's WhatsApp group holds fourteen screenshots from three days ago and two replies: "These look good" and "Let's make the coffee one pop a bit more." Which coffee one, version two or three? Does "these" mean all fourteen? The team spends the next morning asking, and approval week gets longer again.
This post shows how to move approvals from screenshots and attachments to a single link, following a fictional agency, Pera Digital. Most of it works with any tool: the rules of a good approval process, how to introduce it to clients, and a setup checklist.
What actually breaks during approval week?
Approval week drags because of the process, not because clients don't care. The trouble gathers in three places.
1. Nobody knows which version was approved
Every screenshot is a copy of the post, and every revision adds another. The client doesn't remember which one they said yes to, and you scroll through chat history to work out which should go live. Publishing the wrong version is the most expensive mistake here, because the client remembers it as carelessness.
2. The feedback is vague
"Make it pop." "It doesn't feel like us." These are clear to the client and opaque to the designer. Color? A shorter caption? A bigger product? Vague feedback gets fixed by guessing, and when the guess misses, the same visual comes back a second and third time.
3. Approval restarts the work
An approved post isn't a scheduled post. Someone has to find the approved version, upload it, paste the caption and enter the date and time. Across six clients and about eighty posts a month, that step eats hours and invites mistakes: the wrong day, a missing hashtag, an old image.
Six rules for a good approval process
These rules work with a shared folder as well as a project management app. What matters is writing them into the contract or kickoff email and agreeing on them up front.
Pick a single source of truth
Content awaiting approval should live in one place, and the client should look only there. Use WhatsApp, email and a shared folder at once and you'll have three "final versions." Wherever feedback arrives, record the decision in that one place.
Set an approval deadline
Don't say "whenever you get a chance." Send the calendar on the 20th, say, and make the 25th the last day for approvals. Decide in advance what happens if there's no reply: do posts wait, or does the first week stay unpublished? Put it in the contract.
Limit revision rounds
Two revision rounds per post is a reasonable start for most agencies; a third is extra work. The limit isn't a penalty. It encourages considered feedback in the first round.
Give feedback a structure
Ask the client for what should change (image, caption or both), which direction it should go, and where. The table translates common vague comments.
| What the client says | What changes? | Which direction? | Where? |
|---|---|---|---|
| "Make it pop" | Image | Color | Background |
| "It's too long" | Caption | Shorter | First two sentences |
| "It doesn't sound like us" | Caption | Warmer | Opening line |
| "I can't see the logo" | Image | Composition | Bottom right corner |
| "The offer is wrong" | Caption | Fix information | Dates and terms |
Keep versions apart
The client should only ever see the current version. Keep older ones on the team's side, away from where approvals happen. If you work with files, name them consistently (for example brand-nov-07-v2) and move approved files to a separate folder.
Remove the manual step between approval and publishing
A copy-and-paste step between the approved post and the published one is where mistakes happen. Ideally, clients approve in the same place you schedule. If not, give whoever schedules a single approved list, and have a second person check the result.
The new flow: four steps from calendar to approval
Pera Digital applies these rules with the VonaHub client approval portal:
- 1
Share the calendar
Click "Share" on the calendar, optionally set a PIN and copy the link. You can still send it over WhatsApp; now WhatsApp carries the link, not the content.
- 2
The client reviews on their phone
No account needed. The client sees the month's posts as a feed, calendar, grid or list, in Instagram, Facebook and LinkedIn phone previews. Reels play inside the portal.
- 3
Approve or request changes
Each post has "Approve" and "Request changes"; "Approve all" clears every pending post in one tap.
- 4
Approved posts schedule themselves
A post with a future date and a connected account is scheduled the moment it's approved. Nobody has to schedule it again.
A change request gives the client the structure from the table above, ready-made. They choose the scope (image, caption or both), then tick up to two of ten preset directions such as color, composition, shorter, warmer or fix information. They can also drop up to three markers on the image, each with a short note like "logo gets lost here." The request lands on the team's approvals screen, and the post can be regenerated from the feedback in one click.
When "make it pop" arrives as "Image · Color · background too pale," Pera Digital's designer no longer has to guess, and most first rounds close without a second.
How do you introduce the new process to clients?
A WhatsApp group feels fast and familiar, so present the change as something that makes the client's job easier, not as a new rule. Three suggestions:
- Announce the change at the start of the month; don't switch methods in the middle of approval week.
- In the first month, approve one post together with the client on a short video call or screen share.
- Keep the WhatsApp group for urgent matters, but accept approvals and change requests only through the link.
A sample email for the first month
Adapt the text below to your agency and your client.
Subject: Your November posts are ready for review: here's your approval link
Hi Selin, starting this month we'll collect content approvals through a single link. It shows all of November's posts exactly as they'll appear on Instagram. There's no account to create, and it works on your phone.
Tap "Approve" on any post you're happy with and it will go out on its planned day. To change something, tap "Request changes," choose what should change and, if it helps, leave a note on the image. Please approve by November 25; our contract includes two rounds of changes per post.
The link is below. It's protected with a PIN, which I'll send separately. If anything is unclear, call me; happy to do the first approval together.
Open the portal under your agency's brand
The page your client opens should feel like part of your agency. On the Enterprise and Agency plans, the portal shows your logo, colors, typeface, welcome message and contact details, and the PIN screen is branded too. See the white-label client portal and managing 10 brands with a small team.
White label portalOpen the approval portal with your agency's logo and colorsApproval process setup checklist
- Choose one place for content awaiting approval and show the client only that place.
- Write the calendar delivery date and the approval deadline into the contract.
- Agree with the client on what happens if there's no reply by the deadline.
- Set the number of revision rounds per post and note how extra rounds are billed.
- Show the client how to give feedback as "what, which direction, where."
- Show the client only the current version.
- Protect the approval link with a PIN and send the PIN through a separate channel.
- Check daily for approved posts with a past date or a disconnected account.
- Approve one post together with the client in the first month.