How to Respond to Out-of-Scope Brand Deal Requests

Respond to an out-of-scope request by identifying the original requirement, describing what changed, and offering a revised fee, date, or deliverable tradeoff. Do not begin the extra work while arguing about whether it is “small.” The practical question is whether the request changes the work you agreed to perform.

Compare the request with the accepted scope

Open the signed agreement, accepted brief, approved concept, and later written changes. Find the language covering deliverables, included revisions, reshoots, raw footage, usage, and deadlines. A request is not out of scope merely because it is inconvenient, and it is not automatically included because it sounds quick.

Use a side-by-side note:

| Agreed scope | New request | Effect | |---|---|---| | One 30-second edited video | Three new 15-second cutdowns | Two additional exports and checks | | One revision round | New product introduced after v2 | New shots and revised claims | | Organic posting only | Brand wants paid ads for six months | New usage permission and price | | Creator supplies final edit | Brand asks for raw footage | Additional files and rights questions |

If the original language is genuinely ambiguous, say so. A neutral clarification is more credible than declaring a breach after both sides used an undefined phrase.

Separate corrections from changed scope

The cleanest distinction is the source of the change. If your draft missed a requirement that was clear in the accepted brief, correcting it may fall within the included revision process. If the brand adds a talking point, scene, format, product, or use after approval, that may be a scope change depending on the agreement.

Common categories include:

• Correction: fix the wrong code, omitted required disclosure, or misspelled product name from the accepted brief.
• Preference: adjust pacing, color, or phrasing within the same concept.
• Scope change: add a new deliverable, product, location, hook, or platform.
• Rights change: expand paid media, territory, term, editing, or sublicensing.
• Schedule change: move a deadline or require rush work because an input arrived late.

Do not rely on these labels alone. Quote the controlling term and explain the actual production effect. The first-draft email guide helps establish which requirements and files were in the submitted version.

Reply with impact and options

A strong response is factual, short, and easy to approve:

Thanks for the update. The accepted scope includes one 30-second Reel and one consolidated revision round. Adding two hooks requires two additional edits, exports, and review checks. I can add them for $X and deliver all three versions by [date], or I can replace the existing hook within the current scope and keep the original date. Please confirm which option you want before I begin.

That structure has four parts: what was agreed, what is new, what it changes, and what decision is needed. It avoids moral language such as “unfair” when a practical amendment can resolve the issue.

If the brand wants a call, take it, then confirm the result in writing. A verbal “yes, that should be fine” is easy to interpret differently once an invoice or launch date is involved.

Price or trade the change deliberately

Additional money is one response, not the only response. You can also extend the deadline, replace one deliverable with another, reduce included revisions, limit usage, or decline the addition. Choose an option based on the real constraint.

Before quoting, count:

• Preparation, filming, editing, and administrative time
• Additional people, locations, props, shipping, or travel
• New music, talent, or third-party permissions
• Review and export work for each version
• Opportunity cost created by exclusivity or a changed date
• Added usage value, if the request expands the license

Do not describe a rights expansion as free production work. Paid-ad permission can require little editing while still changing how and where the content is used. The creator usage-rights guide provides a media, territory, and term framework.

Know when to pause or decline

Pause when the request introduces an unapproved product claim, asks you to remove a required disclosure, conflicts with another agreement, requires uncleared material, or cannot fit the safe production window. A deadline does not turn an unresolved compliance or rights question into approval.

You can decline without escalating the tone:

I cannot add that claim or publish it until the brand confirms the approved wording and review decision. I can keep the current approved language, or hold the post while your team resolves it.

For a material dispute, repeated nonpayment, or a demand that may affect legal rights, seek qualified advice in the relevant jurisdiction. This workflow is practical contract management, not a conclusion about what a court would enforce.

Prevent the same dispute next time

After the campaign, update your scope language. Define the number of posts and files, what one revision round means, when a reshoot is included, how late inputs affect dates, and how new usage is approved. Include a written change process with a named decision owner.

The pre-acceptance questions in what to ask before accepting a creator brief can catch most of these issues before the shoot. The first-try approval guide then helps distinguish a creator miss from a requirement that changed after production began.

Keep the original request, your response, and the approved change with the campaign record. That history makes the next submission and invoice understandable to someone who was not on the call.