Why approvals get lost
It is a Thursday morning at a small marketing agency that runs social posts, emails, and ads for a dozen local businesses. A client calls, unhappy: the holiday promotion that went live overnight shows last week's offer wording. The account manager is sure the client approved it. The designer remembers two versions, one sent by email and one shared in a chat thread. The client's office manager said "looks good" on one of them, but the owner asked for a change in a separate text message that never reached the designer. Nobody can show which file was approved, who approved it, or when.
That scene is an original illustration, not a TwoQM client and not a measured result. It shows a common gap in agencies of every size: the creative work is careful, but the approval itself lives in scattered emails, chats, and phone calls.
TwoQM has already written about client asset libraries with version labels (where finished files live), retainer hours burn reports clients can read (time and budget visibility), and AI-drafted follow-ups with human send approval (internal review of AI drafts). This article is different. It covers one question before anything goes out under a client's name: which exact version did the client approve, who approved it, and is that the version scheduled to go live?
The usual gaps look like this:
Approvals arrive in many channels. Email replies, chat messages, text messages, comments in a shared file, and phone calls all count as "yes" to someone.
The approver is not always the decision maker. An assistant says it looks fine, while the owner, who has the final word, has not seen it.
Versions multiply quietly. A small wording fix creates a new file, but the approval sits on the old one.
Scheduled posts are set up before the final yes. A draft gets scheduled to hold the slot, and nobody swaps in the approved version.
Change requests after approval are not tied back. The client asks for one more change after saying yes, and it is unclear whether the earlier approval still stands.
What the approval log should show
Keep one line per piece of content, linked to the client and the campaign:
Client, campaign, and channel. For example, a holiday promotion post for two social channels, or a single email.
Version identifier. A version number or label on the exact file or text, matching the one in your asset library.
Who may approve for this client. Named in advance, with a backup, so a "yes" from someone else is flagged for confirmation.
Approval status. Draft, sent for review, changes requested, approved, scheduled, or live.
Approved by, when, and how. The person, the date and time, and the channel, with a copy or screenshot of the approval message attached.
Scheduled version check. Confirmation that the version scheduled in the posting or email tool matches the approved version.
Changes after approval. Any later request creates a new version and a new approval line. Nothing is overwritten.
Write the rules before building anything
Write one page per client, and one agency-wide page, before you automate. Who may approve on the client's side? What counts as approval: a reply to a specific review link, a written message, or a recorded call note? How long do you wait before following up on a pending approval, and who follows up? Can anything be scheduled before approval, and if so, how is it marked so it cannot go live by accident? What happens when an approved piece needs an urgent change, such as a sold-out offer?
Share the client page with the client and ask them to confirm it. That page is what the log should mirror. When the rules change, change the page first.
Make approving easy for clients
A process that makes clients log into something complicated will push approvals back into texts. Keep it simple:
One review link per version. The client sees the exact text, image, and channel, with an approve button and a box for change notes.
Plain, bilingual review screens. If your client's team works in Spanish, the review page and notes can be in Spanish, while the content stays in the language it will publish in.
Forwarded approvals land in the log. If a client still replies by email, a named person attaches that reply to the version line the same day.
Reminders go to the right person. Pending items remind the named approver, not everyone on the client's team.
A last check before go-live. Before a scheduled item publishes, someone confirms that the scheduled version matches the approved one.
Where software and AI help
Custom software fits when approvals are scattered and your posting tools do not record who approved which version. A small client review portal can show each version, capture the approval with name and time, and keep the history for the account manager and the client. Connected systems work can link that portal to your asset library and your scheduling tools, so the scheduled item carries the approved version label. Business automation can send reminders to the named approver and flag any scheduled item that has no matching approval.
AI automation can draft a short summary of each client's pending and changed items, in English or Spanish, for the account manager to review. AI does not approve content, schedule or publish posts, change client files, or send messages to clients without a person reviewing and sending.
Where to start this week
Pick your three busiest clients. For each one, write down who may approve and how approvals arrive today. For the next two weeks, record every approval on a shared sheet with version, approver, date, time, and channel, and attach the approval message. Before anything publishes, check it against the sheet. At the end, look at how many approvals came from someone other than the named approver, or arrived after scheduling. That record will show whether you need a small portal or just a firmer habit.
TwoQM builds custom software, connected systems, and automation for professional services firms, including marketing agencies. This article describes agency operations for tracking client approvals; it is not legal or contract advice for your specific business. Pricing explains how custom software and business systems are scoped.
Discuss Your Client Approval Portal · Explore custom software