Online Work & Freelancing
Freelance Change Request Pricing: A Fair Way to Quote Extra Work
Freelance Change Request Pricing: A Fair Way to Quote Extra Work

☰ Table of Contents
Freelance change request pricing gets uncomfortable when a client says, “Could we just add one more thing?” The work may sound small, but it can add research, design, testing, approvals, and a new delivery date. A fair quote makes those costs visible without turning a friendly project into an argument.
The useful distinction is not whether the client is being difficult. It is whether the request changes an agreed deliverable, assumption, or deadline. If it does, pause the original scope, estimate the new work, and get written approval before starting. This guide gives you a repeatable way to do that, including a simple estimate and a message you can adapt.
The moment a request stops being a revision
A revision improves a deliverable within the agreed direction: correcting a typo, adjusting a color, or refining a headline in the included review round. A change request alters what you are making or how much work it takes: adding a new page, connecting another payment provider, writing extra copy, or changing an approved design direction.
Use the original brief as the test, not the client’s wording. “Quick” describes how the request feels to the client, not how long implementation and quality checks will take. If you need to revisit a decision, redo completed work, or test a new path, treat it as a scope change. Your scope of work should already state deliverables, review rounds, and what is excluded.

Price the work, not the awkwardness
Start with a small task breakdown. Include the visible work, the less visible work, and the coordination required to deliver it. Do not add a vague “scope creep fee.” Explain the actual tasks and the rate or fixed price that applies.
| Estimate component | What to count | Example |
|---|---|---|
| Production | Design, writing, coding, research, or configuration | 2.0 hours |
| Review and testing | QA, browser/device checks, edits, or deployment checks | 0.75 hour |
| Project coordination | Clarifying requirements, handoff, and approval notes | 0.25 hour |
| Schedule impact | Time displaced from other work or a changed milestone | Revised delivery by 2 days |
If you bill hourly, multiply realistic hours by your established project rate. If you quote fixed-price work, use your internal hourly target to check the estimate, then present a fixed amount for the defined result. For example, 3 hours at $75/hour gives a $225 baseline. Add no arbitrary surcharge; if uncertainty is real, state a range and what would make it move.
A quick change-request estimate
For a small request, use this four-step calculation:
- List the new deliverable or changed assumption in one sentence.
- Break the work into production, review/testing, and coordination.
- Estimate each part separately, then total the hours or fixed fee.
- State the fee, what is included, what is not, and the revised delivery date.
Keep the estimate proportional. A tiny copy edit that is outside the included rounds may be a one-hour minimum; a new integration needs discovery and a proper estimate. Never imply that an uncertain estimate is guaranteed. Mark it as a range or request a short paid discovery step when the unknowns could change the price materially.

| Request | Likely estimate approach | Approval detail |
|---|---|---|
| One new page using an existing layout | Fixed fee after counting content and QA | Page content, responsive checks, one review round |
| New payment or CRM integration | Paid discovery, then fixed quote or capped hourly work | Systems, access, test cases, third-party fees excluded |
| Extra design revision after sign-off | Hourly or a defined revision bundle | Specific screens and number of rounds |
| Urgent delivery ahead of schedule | Quote the work and confirm availability first | New delivery date and any rush premium agreed in writing |
Quote options clients can actually choose
When there is a genuine trade-off, offer two sensible paths rather than one take-it-or-leave-it number. One can preserve the original deadline by moving another deliverable out; the other can add the work and move the date. Or offer a smaller first phase before the full enhancement. Do not manufacture a “cheap” option that cannot meet the client’s stated need.
Show the difference in outcome, fee, and timeline. That makes approval a business decision instead of a negotiation about whether your time is worth paying for. For recurring extra requests, compare the cumulative workload against a retainer-versus-project break-even test; the right answer may be a new monthly scope, not repeated mini-quotes.

Protect the schedule and approval trail
Pause only the affected work while the client decides. Keep the original deliverables moving where practical, but do not silently start the extra work. A written approval should confirm the requested change, price or billing method, payment milestone if relevant, and delivery date. A brief email reply is enough for a small project; a formal change order may be appropriate for a larger contract.
Make the consequence clear without sounding punitive: “Once you approve, I’ll schedule the additional page and send the updated delivery date.” If the new request replaces an earlier item, document the swap. Keep the original scope and the approved change together so nobody has to reconstruct the agreement later.
When to say no or re-scope
Decline or propose a fresh scope when the request is outside your expertise, depends on access the client cannot provide, creates a compliance or security risk, or cannot fit the timeline honestly. You can also say no when repeated changes make the original fixed price unworkable. A clear boundary protects the relationship better than accepting work you already know you cannot deliver well.
Be specific and offer a next step: remove another deliverable, extend the deadline, bring in a specialist, or schedule a separate project. If a client disputes whether something was included, compare the request against the actual written scope and discuss the ambiguity before assigning blame.
A ready-to-send change request template
Thanks for flagging this. The request to [specific change] is outside the deliverables currently listed in [scope/proposal]. I can add it for [fixed fee / estimated X–Y hours at rate], including [included work and review], with delivery moving from [old date] to [new date]. It does not include [exclusions]. I’ll keep the agreed work moving and schedule this addition once you reply “Approved.” Would you prefer this option, or should we keep the original scope as-is?
Adapt the language to your contract and local rules. Do not begin billable additional work based only on a call or an ambiguous “sounds good.” A clear approval prevents misunderstandings and lets you deliver confidently.
Frequently Asked Questions
How much should a freelancer charge for a change request?
There is no universal fee. Estimate the work using your usual rate or fixed-price method, include testing and coordination, and quote the specific result. A small well-defined request can be fixed-price; uncertain work may need paid discovery or a clearly capped estimate.
Is a change request the same as a revision?
Usually not. A revision refines an agreed deliverable within the included review limits. A change request adds a deliverable, changes an approved direction, or alters an assumption that affects the work. Your contract should define the distinction.
Should I charge extra for a client’s “small” request?
Charge when the request is outside the agreed scope, not because the client used the word “small.” Estimate the actual effort fairly. If it is covered by your included revisions, honor that commitment.
Can I charge a rush fee for a change?
Only if you can meet the accelerated date and the client agrees to the price before you start. State what moves in the schedule and whether the rush fee applies to the added work or the whole project.
What if the client says the work was already included?
Compare the request with the signed scope, proposal, and prior approvals. If the wording is ambiguous, resolve that in good faith before billing. Revise future proposals so the deliverable, exclusions, and review rounds are easier to interpret.
Do I need a formal change-order document?
For small changes, a clear written approval by email may be sufficient under your agreement. Larger or higher-risk changes deserve a signed amendment that records price, deliverables, dates, and any changed terms. Follow the contract and applicable local law.

