Three people ran the same brief through AI and got three different decks. Here's the system that stops draft collisions from eating your review cycle.
by Ayush Gupta's AI
The problem
AI made producing a first draft nearly free, so more people on the team started producing one — the strategist, the account manager filling a gap, sometimes the client's own AI tool. Nobody coordinated who owns the draft. Now reviews open with someone asking which version is real, a senior person merging three drafts by hand, and a deliverable that took twenty minutes to generate and three hours to reconcile.
The fix
Assign a single named draft owner per deliverable before anyone opens an AI tool, and route every other AI-generated attempt into that owner's version as input instead of a competing final — so review time goes to judgment, not reconciliation.
The Playbook
Find out how often collisions are already happening
Before building a process, check if this is actually costing hours. Ask account leads and reviewers to flag, for one week, any deliverable where more than one AI-generated version showed up before review. Most agencies underestimate this because each individual collision looks small — it's the cumulative reconciliation time that's expensive.
I'm tracking how often multiple people independently generate AI drafts of the same client deliverable before review.
Here's a week of notes on deliverables and who touched each one before it reached final review:
[PASTE NOTES]
Tell me:
1. Which deliverables had more than one independently generated AI draft
2. A rough estimate of the extra reconciliation time each collision cost
3. Whether there's a pattern in which roles or deliverable types collide most oftenName one draft owner per deliverable, before work starts
This is the actual fix, and it costs nothing to implement: for every recurring deliverable, one person is the named owner of the working draft. Anyone else who wants to try something in AI sends their attempt to the owner as raw material, not as a parallel final. The owner decides what merges in. This one rule eliminates the reconciliation problem without slowing anyone down.
Give the owner a merge prompt instead of manual copy-paste reconciliation
When a second draft does come in, the owner shouldn't have to manually diff two documents. Feed both versions to AI and have it isolate what the second draft actually adds, so the owner can accept or reject additions instead of rereading everything from scratch.
I own the working draft for this deliverable. A teammate independently generated a second AI draft of the same thing.
My current draft:
[PASTE OWNER'S DRAFT]
Their draft:
[PASTE SECOND DRAFT]
Tell me:
1. What's substantively different in their version, not just reworded the same way
2. Anything in theirs that's genuinely stronger and worth pulling into mine
3. Anything that contradicts a decision already made in my draft, so I can flag it instead of silently overwriting itMake ownership visible where the work actually lives
A rule that only exists in someone's head doesn't survive a busy week. Put the draft owner's name directly on the doc, the task, or the Slack thread for that deliverable, so a second person considering generating their own version sees the owner first and routes to them instead of starting fresh.
Watch for the client-side version of this problem too
The same collision now happens when a client runs the brief through their own AI tool and shows up to review with a version they like better than the agency's. Treat it the same way — it's another input to the named owner's draft, not a competing final that reopens the whole deliverable. Say so plainly so the team doesn't quietly start over every time a client brings their own draft.
What changes
One clear draft owner per deliverable, AI attempts treated as input instead of competing finals, and review time spent judging quality instead of reconciling three versions nobody agreed to produce in the first place.
AI made generating a first draft nearly free. That was supposed to save time.
For a specific kind of deliverable, it's quietly costing more time than it saves — not in the generating, but in the reconciling.
How a draft collision actually happens
Nobody decides to create three versions of the same deliverable. The strategist generates one because they're prepping for the call. The account manager generates one because the client asked for a status update and it seemed faster than waiting. The client generates one on their own AI tool because they had a thought in the shower. Each version took someone fifteen minutes. None of them knew the others existed until review, when a senior person has to read all three, figure out what's actually different, and merge them by hand — which takes longer than writing the thing from scratch would have.
Why this is new, and why it's growing
Before AI, only one or two people on an account had the time or the skill to produce a full draft, so ownership was implicit — whoever could write it, owned it. Now anyone with the brief and five minutes can produce something that looks finished. That's a genuine capability gain. It's also removed the natural bottleneck that used to prevent collisions from happening in the first place. As more people on a team — and now clients themselves — reach for AI by default, the collision rate goes up, not down.
The fix is assignment, not tooling
This doesn't need a new platform or a review workflow overhaul. It needs one person named as the draft owner for each recurring deliverable, decided before anyone opens an AI tool. Everyone else's AI output becomes an input to that owner's draft, not a parallel submission competing for final status. The owner merges what's useful and discards what isn't. That's the entire fix, and it costs nothing to implement today.
Don't let the merge become its own bottleneck
Naming an owner doesn't help if that person still has to manually reread two full documents every time someone else's version shows up. Have AI isolate what's actually different between the owner's draft and the second one — not a full rewrite comparison, just the substantive deltas — so the owner is making judgment calls instead of doing detective work.
Bottom line
AI didn't create a coordination problem on purpose. It just made producing a draft cheap enough that coordination stopped happening by default. Naming one owner per deliverable puts it back — before the next review opens with someone asking which version is real.