10X Writer #109
10xWriter is a newsletter for freelance writers and copywriters who want to build a writing practice that actually pays.
Most freelance writers treat the client brief as a formality. They do a quick back-and-forth to confirm the topic, word count, and deadline.
That works until the fourth revision request lands in your inbox asking for something that was never part of the original conversation.
Scope creep does not start when the client changes their mind. It starts the moment the brief leaves a gap large enough for their expectations and yours to diverge.
A good brief closes those gaps before the work begins.
1. Start with the outcome the client wants, not the deliverable they asked for
The deliverable is a blog post, a sales email, a case study. The outcome is what they expect that deliverable to do.
These are not the same thing.
“I need a 1,500-word article on content marketing” is describing an output.
“I need an article that brings in organic traffic from writers who want to charge more” is describing a result.
Those two briefs will lead to different decisions about the work, and probably different revision conversations too.
Before you agree to write anything, ask: What does success look like for this piece?
Then document the answer.
If the client cannot name it, help them name it and confirm it in the brief.
2. Name every deliverable component, not just the headline piece
Scope creep often lives in the unstated.
If a client hires you to write a landing page, does that include the headline variants? The meta description? The opt-in button copy? The thank-you page?
These feel like small additions in the moment. Across a project, they add up.
The brief should list every deliverable component, one item per line, with a clear note on anything out of scope.
A brief that says “write the landing page for our new enterprise tier” should become:
Headline: one final version, two alternates
Subheadline
Three feature sections, approximately 80 words each
CTA copy
Meta title and description
No FAQ
No pricing copy
No onboarding email
When the client later asks for the FAQ, you have something to return to instead of relying on memory.
3. Define what a revision is, and what it isn’t
A revision is a change within the scope of the original brief.
If the client changes the audience, wants a completely different angle, or asks you to restructure the piece because the strategy has changed, you’re dealing with a new direction.
Make that distinction clear in the brief:
“Two rounds of revisions are included. A revision is defined as changes to existing content. A new direction or restructure is treated as a new brief.”
Also distinguish between a clarification and a revision. If you misunderstood something that was already agreed, that’s different from the client changing what they want.
This isn’t about protecting yourself from the client. It’s about making sure both of you mean the same thing when you say “revision.”
4. Set the input deadline, not just the delivery deadline
Writers track their own deadlines. They don’t always track the client’s.
If the work requires interview transcripts, product specs, brand guidelines, or customer quotes, those inputs are dependencies.
If they arrive late, your delivery date may have to move too.
Write that dependency into the brief:
“Draft delivery by 14 October, depending on receiving interview transcript and product spec sheet by 7 October.”
Now there is a clear connection between the client’s input and your delivery date.
5. Name the single point of contact and the approval chain
A brief that arrives through one person but gets approved by three others can create a very messy revision process.
Those people may have different opinions about the piece, and they may not have been part of the original briefing conversation.
Ask before you start:
Who is the single point of contact?
Who has final approval authority?
Who can request changes?
Are there other stakeholders whose feedback will be incorporated?
Can they consolidate their feedback before sending it to you?
Document the answers.
It is much easier to deal with conflicting feedback before you start than after you’ve already gone through two rounds of revisions.
6. Confirm the tone and audience with one real example
Tone is one of the easiest things to misunderstand.
A client who says they want copy that is “professional but approachable” may have a very different interpretation of that phrase than you do.
Instead, ask for something real:
A piece they’ve published that they like
A competitor’s content they admire
A sample you’ve written that they approved
One real example can do more than three paragraphs of adjectives.
Put the link or sample in the brief. When you deliver the draft, you now have something concrete to refer back to if the client says, “This doesn’t sound like us.”
7. Get the client to confirm the brief before you start
A brief sitting in your inbox is a note to yourself. A brief the client has read and confirmed is a shared record of what you agreed.
It doesn’t need to be elaborate. It can be a shared Google Doc, a simple email with a numbered list, or a one-page PDF.
What matters is that the client has read it and confirmed it in writing before the work starts.
End the brief with: “Please confirm the above by [date] so I can begin work as scheduled.”
That gives you something concrete to return to when a later revision request falls outside the agreed scope.
Before you start the next project
Run through these seven questions:
Outcome: What does the client want this piece to achieve?
Deliverables: What exactly am I delivering, and what is out of scope?
Revisions: What counts as a revision, and what becomes a new direction?
Inputs: What do I need from the client, and by when?
Approval: Who can approve the work and request changes?
Tone: What real example will anchor the voice?
Sign-off: Has the client confirmed the brief in writing?
A good brief isn’t a defensive document. It’s a shared map.
When both sides are reading the same map, the work moves faster, the revisions stay closer to the agreed scope, and there is less room for “I thought that was included.”
Scope creep rarely starts with a bad client, it starts with a brief that left room to disagree later. Writing the acceptance criteria down before touching the keyboard has saved more arguments than any contract clause ever did.