How to keep internal comments out of client feedback
Your team needs somewhere candid to discuss a post before the client sees it. Here is how to keep internal comments and client feedback on the same content without mixing them.
Most agencies have a story about an internal note the client was never meant to read. Moving the debate to Slack stops the leak but splits the discussion from the post it is about. A better pattern keeps both conversations on the same content, with a clear line between them.
Why internal comments end up in client feedback
Most review tools give each post one comment thread. Your team uses it to work things out, and your client uses it to give feedback. Both are reasonable uses. The trouble is that one thread is doing two jobs for two different audiences.
The internal half of that conversation is often the most useful part. A strategist flags that the hook is weak. An editor asks whether a third revision is still inside scope. A producer notes that the client's favourite clip has a licensing problem. None of it is secret, but none of it was written for the client either.
So teams move the candid part somewhere else: a Slack thread, a direct message, a shared doc. That stops the leak and creates a new problem. The discussion is no longer attached to the version it is about, newer teammates miss it, and nobody can find it when the client asks why something changed.
Decide what counts as internal before you need to
Agree on one rule with your team: if you would be comfortable with the client reading it in a meeting, it can go where the client sees it. Everything else stays internal. These are the conversations that come up most in social content reviews.
| Conversation | Where it belongs |
|---|---|
| Critique of a first cut or draft caption | Internal |
| Effort, budget or scope concerns | Internal |
| Reminders and hand-offs between teammates | Internal |
| Questions only the client can answer | Client |
| The revised version for sign-off | Client |
| Answers to the client's questions | Client |
The rule covers tone as well. Internal comments can be short and blunt. Client comments should read as if they were written for the client, because they were.
Private and public comments in Sequence
Sequence now gives every comment on a post one of two settings. Private comments are for your workspace team. Public comments are also visible to brand-only members, such as a client you have invited to a single brand.
- A Private and Public filter sits above the comments on a post, in Media review, on Plan comments and in the approvals pop-up, with a count for each.
- Your team opens on Private, so a new comment stays internal unless someone chooses Public.
- Clients only see the Public thread. Nothing tells them a private one exists.
- On Private, @mentions only suggest workspace members, so a client cannot be tagged into an internal note.
- Replies always follow their thread, so a private discussion never picks up a public reply by accident.
Who counts as your team comes from membership, not from a setting on each person. Anyone in your workspace sees Private comments; anyone you have only added to a brand does not. If a freelancer needs the internal thread, add them to the workspace.
Move a thread when the conversation changes
Internal discussions often end with something the client should see. The team agrees on a new caption, or realises a decision needs the client's input. Rather than retyping the conclusion as a new comment, move the thread to Public from its first comment. The whole thread moves together, and brand-only members are notified once.
Moving the other way is limited on purpose. Once a client has commented in a thread, it stays Public, so nobody's own words disappear from their view. If you need to talk about their comment internally, start a private thread beside it.
Share links and notifications follow the same rule
Review links work the same way. If you share a post with Show comments turned on, the link only shows Public comments. Private comments never appear on a share link, whoever opens it.
Notifications respect the line too. A private comment only notifies people in your workspace, mentions included, while a public comment reaches the client as it always has.
A simple routine for your next client review
- Debate the draft in Private until the team is happy with it.
- Switch to Public to ask the client one specific question, with the version attached.
- Keep notes about effort, scope or timing in Private, even once the client is involved.
- Move an internal thread to Public when its conclusion is something the client should read.
- Resolve the public thread once the client signs off, so the next review starts clean.
For the approval side of the same workflow, our social media approval process template covers stages, deadlines and revision rounds.
If your team reviews social content with clients, try running the next review this way in Sequence. The candid discussion stays next to the work it is about, and client feedback stays clean.
