A client approves a three-post social package, then asks for two more posts, new product photos, and a revised caption direction. The work may sound small in a message, but it is no longer the package you priced. A clear rate card scope change example gives you a practical way to name the added work, price it, and get approval before your timeline slips.
This is not about being difficult. It is about giving the client a clean decision: keep the original scope, add the requested work at the stated rate, or adjust the delivery plan. When the options are visible, most reasonable clients can decide quickly.
Why scope changes need a rate-card rule
A rate card tells a prospect what your common services cost. Scope language tells an existing client what happens when a project changes after approval. You need both because a package price only works when the deliverables, revision rounds, timeline, and responsibilities stay close to the original agreement.
Without a scope-change rule, freelancers often absorb additions to preserve the relationship. That creates a worse problem than one unpaid task. Your client begins to see extra work as included, your calendar fills with unplanned production, and your effective hourly rate falls.
A useful policy does not have to read like a contract. It can be a short section in your proposal, rate card, project brief, or approval email. The key is to separate a revision from a new deliverable.
For example, changing a headline on an approved carousel may fit within one revision round. Asking for a second carousel with a different audience, visual direction, and caption is a new deliverable. Replacing one approved product image with another might be a revision. Requesting a new product shoot, retouching, and three alternate crops is added scope.
The rate card scope change example to adapt
Start with an original scope that is specific enough to measure. Here is a fictional example for a freelance creator working with a small business. The prices illustrate the calculation; they are not market benchmarks or recommended rates:
> Original package: $900 > Includes three Instagram feed posts, one campaign concept, captions for each post, one consolidated revision round, and delivery within 10 business days. Client supplies approved product details, brand assets, and feedback in one document. > > Scope-change policy: Requests that add deliverables, require a new concept direction after approval, add revision rounds, change the agreed deadline, or require new source materials are quoted separately. Work begins after written approval of the updated scope and fee.
Now imagine the client asks for two additional posts after the campaign concept is approved. Your change notice can stay direct:
> Requested change: Add two Instagram feed posts using the approved campaign concept. > Added fee: $240, based on $120 per additional post. > Timeline impact: Delivery moves from June 14 to June 17. > What remains unchanged: The original three posts, one revision round, and existing caption direction. > Approval needed: Reply “approved” to add this work to the project.
That is a rate-card scope change example because it connects an extra request to a published unit price, explains the schedule effect, and creates an approval checkpoint. It avoids vague wording such as “I can probably fit that in” or “there may be an additional charge.”
If the added request is less predictable, do not force it into a unit price. Quote a fixed add-on or an hourly estimate with a not-to-exceed amount. A new concept direction, a rush turnaround, or a set of assets with unknown cleanup needs may take more discovery than an extra post.
Build rates around work you can define
Your rate card does not need a price for every possible request. It needs a consistent way to price the requests you see most often. Use the Creator Rate Card Calculator to work through supported rate, revision, rush, and usage inputs, then check the result against your actual scope. Verified members share three weekly core uses across eight tools; after that allowance, a core calculator use requires confirmation before one Creator Tools credit is used. For creators and marketers, that often means defining add-ons such as extra social assets, additional caption sets, alternate aspect ratios, extra revision rounds, rush delivery, additional platform adaptation, or new campaign concepts.
Use per-item rates when the task is repeatable and the inputs are clear. An additional edited product image or another caption variation can work well as a per-item add-on. Use a project add-on when the request changes several parts of the workflow at once. A new launch angle may require new research, messaging, visual direction, review, and production.
Hourly pricing is useful for open-ended work, but clients need a boundary. Instead of saying, “This will be billed hourly,” say, “I estimate two to three hours at $95 per hour and will check with you before exceeding $285.” That protects you from surprise work while giving the client a decision point.
Your listed price should account for more than the minutes spent making the final file. Include planning, source review, communication, setup, revision handling, exports, and quality checks. A low add-on rate can look easy to approve, but it becomes expensive for you if it repeatedly ignores that supporting work.
Send the change notice before you start
The timing matters as much as the wording. A scope change should be identified when the request arrives, not after you have already completed it. If you begin first, the client may reasonably assume the work was included.
Use a short response that acknowledges the request and pauses the work without sounding rigid:
> Yes, I can add that. It sits outside the approved package because it adds two new deliverables. I’ll send the added fee and revised delivery date for approval before I begin.
Then send the change notice in the same place the client already uses to approve work, such as the project email thread or your client portal. Keep the original scope and the change notice together when possible. You want both sides to see what changed and what did not.
Do not bury the new fee in a long message. Put the requested addition, fee, delivery effect, and approval action where a busy client can scan them. If an invoice deposit is part of your process, state that clearly before scheduling the new work.
A client may ask whether the request can be included “this one time.” That depends on the relationship and the size of the request. You can choose to waive a minor addition as a goodwill gesture, but label it as a one-time courtesy and still record it. Otherwise, a favor becomes an invisible update to your package terms.
Handle common gray areas without overcharging
Not every request deserves a change order. Small corrections caused by your own error should be fixed without a fee. If a typo remained after your review, correct it. If you used the wrong brand color despite receiving the approved guide, that is not a client scope change.
Client-caused delays are more nuanced. If feedback arrives late, you may be able to keep the original delivery date when your schedule allows. If the delay pushes work into a reserved period or requires rush production, explain the new date or rush fee before committing. The point is not to penalize a client. It is to make capacity visible.
Revisions also need a clear definition. “One round” should mean one consolidated set of feedback on the same deliverables. It should not mean separate feedback from four stakeholders over three days. Ask the client to collect comments, then review the combined notes against the approved direction.
Make approval easy to track
A change notice only works if you can find the approval later. Save the approved message with the project files, update your task list, and revise the invoice or statement of work if needed. Before you start, compare the approved change against your production checklist so the team, if you have one, does not work from an outdated brief.
If you need a client-ready starting document, you can draft the structure in AI Business Document Studio. Treat any generated draft as a working document, then review every deliverable, rate, date, and approval term before sharing it. A document tool can speed up formatting, but it cannot decide whether a client request belongs inside your agreement.
For recurring clients, review your change requests every few months. If clients routinely add short-form videos to a social package, consider adding a video option to the next version of your rate card. If a certain add-on causes repeated back-and-forth, tighten the inputs required before you quote it.
A good scope-change process protects your time without turning every request into a negotiation. State what changed, show the cost and timing, wait for approval, and then deliver work you can stand behind.