The Slack Message Is Where Scope Actually Dies
Aug 28, 2026
It is 4:47 on a Friday. The account manager drops a message in the campaign channel: "Client wants a 6-second cutdown for paid social. Can we just pull it from the hero? Should be quick."
Three people heart it. A designer replies "on it." You see it eight minutes later.
This is not a process failure. If you have a process, it already says to name the change. You know that. What you do not have, in the next two minutes, is a sentence that names it without sounding like legal, without embarrassing the account manager in front of the client, and without letting a designer start work that is not paid for.
Most writing on this subject stops at the diagnosis. We already published that post. Scope creep in creative work is the slow accumulation of additions that were never acknowledged as changes, and the fix is naming what is happening in the moment it happens. If you want the mechanism, read Scope Creep Is a Creative Industry Epidemic. This post is the language. The actual sentences, for the situations that keep producing unpaid work.
The Template Is Why You Freeze
Search "scope change email" and you will get a change-order template written for construction or software. It has a request ID, a cost impact table, and a line that says "please countersign to proceed." That document is correct. It is also unusable at 4:47pm in a Slack channel where the client is in the thread.
Creative scope does not arrive as a formal request. It arrives as a casual comment, a "quick question" on Zoom, a "while we are in there" from a designer who cares, or a Friday Slack that already has three hearts on it. If your only available language is a change order, you will wait until Monday to send it. By Monday the cutdown is in motion and the naming is a retro.
The language has to work in the channel where the request appeared, in under two minutes, in front of whoever is already watching. That is a different writing problem than "document the change."
Three jobs, in this order:
- Stop the work from starting.
- Name the change as a change, out loud, without a fight.
- Point the decision at a person who can actually make it.
If you reverse that order, you write a careful email while the designer is already in Premiere.
What the Wrong Sentence Does
There are four sentences working creative PMs reach for under pressure. All four fail in a specific way.
"Sure, we can squeeze that in." You just made a delivery commitment the timeline cannot absorb. The account manager is relieved. The designer is now doing a second project inside the first one. You will spend next week explaining a slip that you created in one message.
"That's out of scope." Technically true. Socially radioactive in most client-facing threads. It sounds like a refusal rather than a decision. The client hears no. The account manager has to repair the relationship. You become the person who "isn't commercial."
Silence, then a status update on Monday that quietly includes the extra deliverable. This is the most common version. You absorb it because naming it felt worse than doing it. The absorption is the process. It is also how a six-week campaign becomes an eight-week campaign that nobody agreed to.
A full change-order PDF, twenty minutes later, in a thread that already moved on. Correct artifact, wrong timing. The work started in the gap. The PDF is now a retro.
The usable sentence does something narrower. It pauses the work, names the impact as unknown rather than as a no, and buys the one conversation that has to happen before anyone opens a file.
The core line, which we have used in other posts because it is the one that actually works:
"That sounds like it could affect the timeline. Let me look at it before we proceed."
That line is the start, not the whole job. What follows is the rest of the language, situation by situation.
Seven Situations, and What to Send
Each of these is a real shape. The wrong version is what most people type. The right version does the three jobs above. Copy them. Then change the nouns.
1. The Friday Slack, client in the channel
They send: "Can we also get a 6-second cutdown from the hero? Should be quick."
Do not send: "On it." or "That's extra, we would need a change order."
Send:
"Flagging this before anyone starts. A 6-second cutdown is a new deliverable, not a trim of the hero. I want to check the edit time and whether it lands inside this week or moves us. I'll come back in the morning with the impact so we can decide before files get opened."
Why it works: you named the object (new deliverable), you stopped the work, you gave a time for the answer, and you did not make the account manager look like they overpromised. "I'll come back in the morning" is load-bearing. An open-ended pause is how work starts anyway.
2. The account manager who already said yes
This is the one that produces the most unpaid work in agencies. The client asked in a call. The account manager said "we can look at that." The team heard "yes."
Do not send, in the client thread: "We never agreed to that."
Send, to the account manager, in a private channel, immediately:
"I saw the yes. Before the team starts, I need twenty minutes with you. A cutdown is new scope, and if we run it this week it collides with the hero delivery on Thursday. I can do the impact in a short note we send together. I don't want to walk back your yes in the client thread. I want us to go back with a real answer."
Then the two of you send, together:
"We can do the cutdown. Two options: we add it this week and the hero moves to next Tuesday, or we keep Thursday and schedule the cutdown as a follow-on. Which do you want?"
Why it works: you protected the relationship and the timeline. The account manager does not get hung out to dry. The client gets a choice, not a no. If you want the larger map of who owns what in that relationship, how account managers and creative project managers actually work together is the companion.
3. "While we are in there" from inside the team
A designer, an art director, a copywriter. They are already in the file. They can see a better version. They are not trying to blow the job. They are trying to make it good. That instinct is the asset. It is also how internal scope dies without a client ever asking.
They say: "While I'm in here I want to try a second route on the end card. Won't take long."
Do not send: "We don't have time for that." (They will do it anyway, after hours, and you will still be late.)
Send:
"If the second route is exploration, park it in Working and we can look on Monday. If it is a real option you want in the review, that is a second concept and I need to say so to [approver] before it goes in the deck. I don't want you spending Thursday night on something that is not in the room."
Why it works: you did not kill craft. You sorted exploration from presentation, which is the same cut a good PM makes when AI generates forty concepts. Generate freely. Present on purpose. The project manager owns the cut.
4. The hallway "quick favor" (in-house)
There is no contract. The person asking is a colleague. Nothing about the request costs them anything. That is why agency language fails inside a company.
They say, in Slack or in the hallway: "Can you just add our team's logo lockup to the deck? Super small."
Do not send: "Submit it through the intake form." as the first sentence. You will sound like a help desk. They will ping the designer directly next time.
Send:
"I can get that in. Two things before I assign it: who approves the lockup, and does it need to ship with Thursday's all-hands or can it follow? If it has to ride with Thursday I need to bump [other job], and I want you to know that before I do it."
Why it works: you did not hide behind a form. You manufactured a constraint the requester can see. In-house, the capacity plan is a political document. The sentence has to make the tradeoff visible or the work just lands on the designer. The longer version of that operating model is in Creative Project Management for In-House Creative Teams.
5. Conflicting notes, no named approver
Round two comes back. Brand wants it quieter. The marketing director wants it louder. Both outrank the designer. Neither was named as the person whose yes ends the round.
Do not send, to the designer: "Can you try a version that splits the difference?"
Send, to both stakeholders, copied to the account lead:
"We have two directions in the notes and they do not both fit in this round. I need one decision, in writing, on quieter vs louder before we spend another edit day. [Name], you are the approver on this job. Which one are we making?"
If no approver was ever named, say that:
"We never named a single approver on this one, which is why the notes are pulling in two directions. Before the team revises, I need you two to pick who owns the call. Once that is in writing we will revise against that person, not against the thread."
Why it works: you refused to turn the designer into the tiebreaker. Single-approver routing is not a nicety. It is the only way a revision round has a terminating condition.
6. The client who wants "a few more directions" after AI made forty cheap
The review ran long. Nobody picked. Someone asked to see more. Production got roughly free. Decision-making did not.
Do not send: "We'll generate another round over the weekend."
Send:
"We can generate more. Before we do: another round moves delivery to the twelfth, because the review still has to happen after the generation. We presented three on purpose. If none of the three maps to the brief, tell me which criterion they missed and we will recut the set against that. If the brief is still open, we need to lock the brief before we make more options. More files will not close an unmade decision."
Why it works: you put a visible cost back on regeneration. The cost of going back used to announce itself through the production calendar. Now you have to announce it every time, or the request stays free and therefore infinite. The longer version of that problem is Your Team Can Generate 40 Concepts Overnight.
7. The change you already absorbed, and now have to name late
You missed the window. The work is underway. Naming it now feels like you are picking a fight after the fact. That feeling is why people never name it.
Send, as soon as you notice, not after delivery:
"I should have flagged this when it came in, and I didn't. The cutdown is in motion and it was not in the signed scope. I am putting it on paper now so we are not surprised at invoice. Impact is [X hours / Y days]. Two options: we formally add it and adjust the date, or we stop it and finish the original delivery. I need a call from [approver] today, not a vibe."
Why it works: you did not pretend you caught it in time. You still named it. Late naming is better than silent absorption. Silent absorption trains everyone that the next request will also go unnamed.
What You Are Actually Protecting
The language is not for you. It is for the people making the work.
A designer who starts a cutdown on Friday night because three people hearted a Slack is not going to bring that up in the retro. They are going to stop trusting that anyone is watching the edge of the job. The next time you ask them to hold a line, they will not, because last time the line was a performance.
The PM who can send the Friday sentence, and then actually come back in the morning with an impact, is doing the judgment part of the job. The administrative part, chasing assets and updating the board, is the part that is getting cheaper. This part is not.
That is also the part generic project management training does not teach. A change-request form assumes the request arrives as a request. Creative work disguises it as collaboration, as craft, as responsiveness, as "being easy to work with." The sentence has to unmask it without punishing the people who were trying to be those things.
What This Looks Like Across Environments
At an advertising agency, most of these messages run through the account manager first. Do not name the change in the client thread until you have aligned internally. The private-channel version in situation 2 is the default, not the exception.
In-house, there is no invoice to point at. The tradeoff has to be another job, another date, or a named person going without. If you cannot name the thing that gets bumped, you have not named the change. You have only named your discomfort.
In film and production, the language is often already better because call sheets and locked-versus-open decision points exist as formal artifacts. Steal that. "Is this locked, or is it open?" is a production sentence that belongs in agency reviews. If it is open, it is not a small add. It is a reopening.
A Note on Tone
None of these scripts work if you send them as a lecture. They work if you send them as logistics.
The difference is one beat. Logistics names an impact and a next step. A lecture names a principle. "We have a scope process" is a lecture. "I'll come back in the morning with the impact" is logistics. People can agree to logistics in a thread. They fight with principles.
Write short. Write in the channel where the request appeared. Do not move a Slack ask into an email in order to make it feel more official. The work will start in Slack while you are formatting the email.
And do not apologize for naming it. You can be warm. You cannot be sorry that a new deliverable is a new deliverable. "Sorry to be a stickler" trains the room to treat the next naming as optional.
Frequently Asked Questions
How do you tell a client something is out of scope without damaging the relationship?
Do not lead with "out of scope." Lead with the impact and a choice. "We can do this. It moves Thursday, or it follows as a second job. Which do you want?" The relationship is damaged by a surprise slip, not by an honest option set. The account manager and the project manager should send that choice together.
What do you say when a client asks for extra work in Slack?
Pause the work first. "Flagging this before anyone starts" is the line that matters. Then name the object as a new deliverable, give a time you will return with impact, and keep the client in the loop. Do not let a designer reply "on it" while you draft a longer response.
Is a change order enough to stop creative scope creep?
A change order is the record. It is not the intervention. Creative scope arrives in conversation, not in a form. If the only tool you have is the form, the work starts in the gap. Use a two-minute message in the channel, then the change order once the decision is made.
How do you handle scope creep from your own creative team?
Do not treat craft as the enemy. Sort exploration from presentation. Internal experiments can live in a Working folder. Anything that will be shown to a stakeholder is a scoped option and needs to be named before it is made. The PM owns that cut, in partnership with the creative director.
What if I already let the extra work start?
Name it late. "I should have flagged this when it came in" plus the impact plus a decision still recovers more than silence. Late naming is a process failure you can survive. Silent absorption becomes the process.
Do I need a certification to get better at this?
No. You need a habit, and you need language you can send under pressure. A creative-specific credential helps if you want the surrounding disciplines, brief writing, single-approver routing, decision closure, taught as one system rather than collected as scars. It is not required to send the Friday sentence.
Closing
If your team keeps absorbing extra work, the problem is probably not that you lack a scope process. It is that the process has no sentences that work in the channel where the request actually appears.
The CPMA Creative PM AI Kit is built for that gap. It includes a swipe file with ready-to-use language for 24 real situations, including scope pushback, plus a master system prompt so ChatGPT, Claude, or Gemini drafts in this register instead of in generic PM-speak. One-time purchase, $97, instant download, 5-day money-back guarantee. Get the Creative PM AI Kit here.
If you want the surrounding system, briefs, revision discipline, stakeholder routing, not only the sentences, Level I is $147, self-paced, typically 10 to 15 hours, unlimited exam retakes, certificate that never expires. Start with Level I. The Bundle at $297 includes Level I, Level II, the Resume Kit, and the AI Kit if you are going to do the whole path anyway.
Who should skip this: if you already have language that pauses work in under two minutes and a named approver on every job, you do not need a post to tell you that. Send the sentence. Come back in the morning with the impact.
The Only Certification Built for Creative Project Managers
Designed by veterans from Disney, Google, Sony Pictures, Paramount Pictures, Red Bull, Snap Inc., and Accenture. Start for $147 or download the free eBook first.