Revisions & Scope

Revisions

How we count revisions, what does and does not qualify as a revision, and how to respond to revision feedback without sounding defensive or letting scope quietly expand.

Every round turns around in 24-72h with each note itemized.

The core decision when feedback lands: is it a normal revision, or new-project territory - and have the included rounds run out?

#Revision Policy & Process

#Standard Revision Counts

3rounds included on video editing

2rounds included on voiceover

3rounds included on thumbnails (first round = initial design, not a revision)

#What Counts as a Revision

What Counts as a Revision

Pacing tweaks
Trims
Title/caption adjustments
Color adjustments
Audio mixing adjustments
Small structural changes
Font/text changes
B-roll swaps

#What Does NOT Count as a Revision (New Project Territory)

What Does NOT Count (New Project Territory)

Complete concept change or heavy restructure
Changing the style entirely after agreeing on a direction
Adding significant new footage not in the original scope
Changing the runtime significantly (e.g., "make it 15 min instead of 8")
Changing the script after voiceover is generated
Adding new deliverables not in the original offer

#Extra Revisions

Extra revision pricing varies by project complexity, scope, and situation. It can range from free (minor tweaks on a good client relationship) to $15, $50, or significantly more for complex projects. Use your judgment - there is no single flat rate. Always inform the client before starting the extra revision:

Always inform the client about the extra charge BEFORE starting the extra revision - never surprise them with it after.

#Extra Revision Heads-Up

Template

Got it. Usually these orders only cover 3 revisions, and we already did [X], so this would be an additional $[amount based on project]. Do you want to move forward with this extra revision?

#Handling Revision Feedback

Ask for consolidated feedbackDon't let clients drip-feed notes one message at a time.

If feedback is vagueAsk for specifics. "Can you point me to a timestamp?" or "Can you send a reference for what you mean?"

If feedback contradicts previous direction"You initially asked for X, and now it sounds like you want Y - just want to confirm before I make changes since that would reverse the previous direction."

#Revisions Language

"You're over your revision count"
"That's outside the scope"
"I can't do that without additional payment"

"I want to go the extra mile for you - send me one consolidated list and I'll do a final refinement pass"
"I'd love to make that happen - since it's a different direction from the original scope, let me put together a quick quote so we can keep moving"
"Great idea - that would be a separate project, but I can definitely help with that next"

#Handling Revision Feedback - The Response Framework

#The 6-Step Revision Reply (For Difficult Situations)

1
Thank them for the feedbackone line, no superlatives
2
Provide relevant contextif any; keep it brief, context not excuses
3
Reframe the situation positivelyif applicable
4
Remind them of the established processgently reference the revision timeline
5
List every revision point back to themmirror their feedback as a bulleted list
6
Close warmly but realisticallyno predictions

#When to Keep It Simple vs. Full Framework

KEEP IT SIMPLE when...	USE THE FULL FRAMEWORK when...
Client is happy with minor tweaks	Client is frustrated or says "this is not correct"
Feedback is clear, you have everything	Missing critical info (fonts, colors, source files)
You're within the agreed timeline	Delays or broken promises on your end
Scope hasn't changed	Client asking for work outside original offer
Repeat client who trusts you	New client forming their opinion of you

#The Simple Response (Most Common)

1
Thank them for the feedbackone line, genuine
2
Briefly acknowledge what they said
3
Confirm you're on it
4
Offer continued support

Example: "Hey [Name]! Thanks for the feedback - glad to hear you're happy with the direction! I see the notes on [brief acknowledgment], I'll get those updated and send over a new version as soon as I can. If you need anything else in the meantime, just let me know!"

Things to avoid even in simple replies:

Avoid Even in Simple Replies

Don't just say "got it" - feels cold
Don't repeat their entire list back - they just wrote it
Don't add timeline estimates unless asked
Don't say "no problem" - implies their feedback was a burden

#Difficult Revision Scenarios

Client says "this is still not correct"Don't get defensive. Don't over-apologize. Acknowledge, list specific fixes, remind of timeline, ask for anything missing.

Client frustrated about timingAcknowledge urgency without new promises. Remind of agreed timeline. Never compress without charging expedited.

Client asks for work outside scope"The current order includes X. What you're describing would be Y, which I'm happy to do as a separate order." Minor additions - use judgment.

Vague feedbackDo NOT guess. Ask targeted questions and for reference examples.

Client genuinely upsetStay calm, don't match energy, acknowledge frustration, refocus on solution. If abusive, escalate to Mark.

#Revision Response Template

Template

Hey [Client Name]! Thank you for the feedback [and screenshots/examples if applicable].

[Optional: Brief personal context - 1-2 sentences max]

[Optional: Positive reframe]

As I mentioned at the start of the project, each revision round typically takes 24-72 hours. I'm prioritizing your project, but wanted to make sure we're on the same page with that timeline.

Here's what I'm working on:
- [Point 1 mirrored from their feedback]
- [Point 2]
- [Point 3]

[Question if needed: "Do you happen to know the exact font name / hex code / etc.?"]

[Warm close - no predictions, no over-promising]

#Tone Guide for Revisions

Quality	What it looks like	What it does NOT look like
Warm	"Thank you for the feedback"	"OMG your notes are amazing!!"
Confident	"I'll work through each point"	"I'm so sorry, let me try again"
Honest	"Each round takes 24-72 hours"	"I'll have this back in a few hours"
Professional	"Revisions are part of the process"	"I guess I misunderstood what you wanted"
Proactive	"Do you have the exact font name?"	Guessing and hoping for the best

#Revision Handling in Practice

#Normal revisions (within scope)

1
Acknowledge warmly and immediatelyconfirm you understand each note, give a turnaround expectation (24-72h)
2
Ask for the right kind of notestimestamped notes on video work and consolidated feedback (especially from clients gathering team input) to keep revisions efficient
3
Deliver the revisionitemize every change against their notes

#Post-completion goodwill revisions

If the order is already closed and the client asks for a small tweak, deliver via chat with NO official-delivery/approve/auto-complete/review language. Just the revised file + an invitation to flag preferences next time. Builds goodwill without re-opening formal machinery.

Goodwill = revised file in chat only. No delivery/approve/auto-complete/review language - that re-opens formal machinery you don't want to re-open.

#Scope creep to paid overage (the Pedro pattern)

When revision rounds exceed the included count, hold the line warmly. Frame it around the relationship, then convert to paid:

#Pedro Pattern - Converting Excess Revisions to Paid

Template

You're never a hassle - I appreciate you being respectful about it. But I do need to flag something: this order included [X] revision rounds, and we're now well past that. I've been happy to go above and beyond because you're a great client. Going forward, each additional revision round will be $[X]. If that works, I'll send a quick offer and get it done within 24-48 hours.

This preserves the relationship AND gets you compensated. Clients who value you will pay happily.

#Major structural pivots

Photo-level / pacing tweaksNormal revisions. Handle them within the included count without flagging scope.

Complete format / structure rebuildsBigger lifts. Absorb as goodwill on personal/milestone projects and high-LTV relationships when the changes are coherent (not scattered).

Only flag scope if a client pivots structurally AGAIN after you've already rebuilt.

#The two-version / two-format delivery

On ambiguous notes or format uncertainty, deliver both interpretations and let the client pick. Revisions then apply to the chosen version only. Flag extra formats as goodwill (normally a paid add-on) to protect the precedent.