Why Each Writer Rebuilding Client Instructions Breaks Down
- Published
- November 20, 2026
- Reading
- 7 min read
- Share
In This Piece
A writer opens a chat for a dental client and pastes in the paragraph she wrote in June. It says "warm and friendly." Another writer on the same account has his own paragraph, which says "no exclamation marks" and mentions the new Eastside office. In August the client told him they never want to see the word "journey" again. On Tuesday, the first writer's draft uses it twice. (The writers and the dentist are made up. The Tuesday may not be.)
Client instructions for AI writing are whatever a writer gives a chat tool so the draft sounds like that client: tone, rules, facts, and examples. When each writer keeps their own copy, the client ends up with several versions of itself, and the quality of a draft depends on who happened to get the assignment.
In our view, those instructions belong to the client, in one place, with someone responsible for them. The writer's job is the brief.
The Short Version
- Every writer's copy starts out sensible, then drifts, because each person fixes only what went wrong for them.
- A client's comment reaches the person who received it, and stays there.
- A shared project per client in a chat tool fixes a lot of this, and for some agencies it's enough.
- Whichever tool you use, keep two things apart: what's true of the client, and what this post is for.
- A person still reads for tone, coverage, flow, and intent.
Four Writers, Twelve Clients, and Up to 48 Copies
Nobody sets out to build this. A writer gets a decent draft after some fiddling, saves the paragraph, and reuses it. Some teams end up with a folder they call the library, which is usually a shared drive where old paragraphs go to retire.
The arithmetic is unkind. Four writers on twelve clients, a roster we've made up, can mean up to 48 copies. Most agencies won't reach the full count, but the trouble starts at two. Four things go wrong, in roughly this order:
- The copies drift. One writer adds the new office and another doesn't, because the old office never caused her a problem.
- Comments stop with whoever got them. A client says something once and reasonably assumes the agency heard it. Only one person did.
- A copy can leave with its writer. When a freelancer rolls off, the best version of the client may be in their personal account.
- Results follow the operator. One writer is good at instructing a chat tool and gets good drafts. Another isn't. Your client is paying for the account, and they're getting the luck of the assignment.
That last one is why we don't think more coaching solves it. You can teach everyone to write better instructions, and it does help. You'd still have a dozen careful versions of each client, and no way to know which one is right.
A shared project per client in a chat tool is the first fix to try, and OpenAI says ChatGPT projects can keep tone and style consistent across contributors. With someone disciplined owning each one, it ends the drift between writers, and a departing freelancer no longer takes the good version with them. Carrying each client's comments in, and tracking what the client said yes to, still stay with you. We've set out what a project per client fixes, and what it leaves, and if your shared copies are custom GPTs, read what's happening to them before you build another.
Move the Writer Back to the Brief
Here's the test we'd use on any instruction. Would it still be true on a different post for this client? If yes, it belongs with the client. If it's only true today, it belongs in the brief.
A made-up example shows how much of a writer's paragraph doesn't belong to them. This is what often gets typed:
You are a senior healthcare copywriter. Write warmly, with no exclamation marks. We have offices in Midtown and Eastside. Never say journey. Write a LinkedIn post about our new evening hours for working parents.
Only the last sentence is about this post. Everything else is true of the client, and it has been retyped by someone who may have an old version. Move it, and the brief becomes something a writer can think about:
Evening hours at Eastside, starting in January. For working parents who keep postponing a checkup. One point: you can come after pickup. LinkedIn post.
That's closer to the work you hired them for: who it's for, and what they should come away knowing. Getting the setup right shouldn't be a skill that decides which client gets the good draft.
Merge the Copies for One Client First
You can start this week, with no new software. Pick the client whose drafts come back most often and work through the wider content process one step at a time.
- Collect every copy. Ask each writer for what they actually paste, including what's in their personal accounts.
- Lay them side by side. Where they disagree, ask the client, not the team.
- Sort each line. Keep what's true of the client. Move post-specific lines to the brief. Drop the tricks aimed at the tool.
- Name one owner. They approve changes, and everyone else suggests them.
- Give comments a route. When a client says something that should hold next time, it goes on the sheet the same day, with who said it and when.
When you've done that for three clients, check that they still differ. Keeping client voices apart has a way to test it, with the names covered.
What Your Team Still Reads For
We've led a content team through the move from freelance writing to AI-assisted writing, with editorial review kept in place. In our view, software can check the routine items, and a person judges tone, topic coverage, flow, and intent.
Tidy instructions won't tell you that the post makes a promise the client can't keep, or that a line reads as cold the week after a layoff. That's where we'd want a writer's attention.
The Writer Brings the Brief
Instructions belong on the client. The writer brings the brief.
Where GoMimic Fits
Create client content. Get it approved. Deliver it.
In GoMimic, the voice, rules, examples, and Business Facts sit on the client, so a writer starts from the client and brings the source. If your best instructions live in a custom GPT, a Claude Project, a Claude Skill, or a Gemini Gem, Bring In reads them and offers suggestions for you to add or skip. Things Never to Say holds the word "journey" for every writer on the account.
GoMimic learns from your client's real writing, and from the work your client approves. When a client's comment should hold for next time, someone presses Keep This for Next Time, and it becomes a rule for that voice, with who said it, on which post, and when. Your team signs off, the client answers post by post on their review page, and GoMimic never posts.
It creates from what you give it, and a blog post or bylined article only from your client's own take. It won't pick a topic or plan your content strategy for you. To see it on your own work, send one real client post to the Taste Test.
Put real client work to the test.
Questions People Ask
Should you teach writers to write client instructions for AI writing?+
Teach the basics, because writers should understand what they're working with. Just don't let it decide draft quality. Keep each client's instructions in one owned place, so a new writer gets the same client as your best one.
Is one shared project per client enough?+
Often, yes, when each project has a named owner who keeps it up. It ends the drift between writers. Client comments and the record of what was approved still have to be handled separately.
Who should own a client's instructions?+
Whoever answers for that account, usually the account lead or the senior editor. Writers can suggest changes. One person approves them, and they check the facts with the client when copies disagree.
What if one writer gets better results with their own version?+
Find out why. If their version holds something true about the client, move it to the shared copy so everyone gets it. If it's a habit of their own writing, it may belong to them, and it shouldn't change how the client sounds.
Can we move instructions out of a custom GPT?+
Yes. Copy them out while you can still open them, along with any files. GoMimic's Bring In takes them as suggestions, and nothing is saved until you save it.
Written by the GoMimic team
GoMimic helps you create client content, get it approved, and deliver it, in each client’s voice.
Why It WorksMore from GoMimic
Editing Checklist for Agency Content (With the AI-Tell Pass)
An editing checklist in the order an editor reads: the point, the reader, the client's voice, an AI-tell pass, and the facts. Copy it for any draft.
Software Break-Even: A Sum With Your Own Numbers
Software break even, worked out with your own numbers: what the tool really costs, what an hour costs you, and how to test the hours on real work.