How to Price a Change Request: Formula + Example

To price a change request, add up three things: the new work itself, the knock-on rework the change causes in work that's already done, and the cost of the timeline impact (rush effort, rescheduling, or delayed payments). The formula is: change request price = (new work hours + rework hours) × hourly rate + timeline cost. Then send the price and the new timeline to the client and start only after they approve. Most freelancers and agencies only price the first part — which is why "approved" changes still lose money.

Why most change requests are underpriced

Here's the usual pattern. A client asks to add a feature mid-project. You think, "That's about four hours," quote four hours, and get a quick yes. Then you discover:

• Two pages you already built need layout changes to fit the new feature.

• The QA you finished last week has to be repeated.

• The launch date slips, so the final milestone payment slips with it.

• To keep other clients on schedule, you work a weekend.

You were paid for four hours. The change actually cost twelve, plus a delayed invoice.

The fix isn't charging more for the sake of it. It's pricing the whole change, not just the visible part. A change request is honest when it reflects the real effect on the project.

If you haven't used one before, a change request form is a short document that describes extra work, what it costs, how it affects the timeline, and records the client's approval before work starts. This article is about getting the "what it costs" part right.

The change request pricing formula

Change request price = (new work hours + knock-on rework hours) × hourly rate + timeline cost

Let's break down each part.

1. New work: the change itself

This is what the client actually asked for: the new page, the extra integration, the additional ad set. Estimate it the way you'd estimate any task:

• Break it into steps (design, build, content, review, deploy).

• Estimate hours for each.

• Include one revision round for the new work, and say so in the request.

• Add the small stuff: a call to clarify, project-management time, handover notes.

If you price on fixed fees rather than hours, still estimate the hours first, then convert to a fixed price. It keeps the number grounded.

2. Knock-on rework: what the change breaks or touches

This is the part that's almost always missed. Ask: what already-finished work has to change because of this request?

Common sources of knock-on rework:

• Design: other pages or components that need adjusting for consistency.

• Development: refactoring, updating shared components, re-testing.

• Content: copy that references the old structure, navigation, SEO metadata.

• QA and approvals: re-testing and re-approving things that were already signed off.

• Marketing: updating creatives, landing pages, or tracking when an offer or product changes.

Walk through the project quickly and list every deliverable the change touches. If something was already approved by the client, reworking it is chargeable — that's part of the cost of the change, not a favour.

3. Timeline impact: the cost of time

A change almost always moves something. That movement has a cost, even if it's not hours of work. Common ones:

• Rush effort. If the client wants the change and the original deadline, you may need overtime, contractors, or to push other clients. A rush premium covers this. Many agencies use a percentage on top of the work cost; pick a number you'd be happy to defend.

• Rescheduling cost. If the change delays the project, the slot you'd booked for the next client may be affected, or team members sit partly idle waiting on approvals.

• Delayed payments. If your final invoice is tied to launch, a later launch means later cash. You don't have to bill for this, but you should know it, and you can adjust milestone timing in the change request.

Sometimes the timeline cost is $0 and the right answer is simply: "This adds 3 business days; launch moves from [date] to [date]." That's still worth writing down. The client is approving the delay as well as the price.

Worked example: pricing a mid-project change request (HYPOTHETICAL)

All numbers and names below are fictional and only illustrate the method.

A two-person web agency is building a 6-page website on a fixed fee. Their hourly rate is $85. Halfway through, the client asks to add a pricing page with three plan cards and an FAQ, and still wants the original launch date.

Step 1 — New work

Step 2 — Knock-on rework

Step 3 — Timeline impact

Keeping the original launch date means about 19 extra hours have to fit into the existing schedule. The agency would need to shift another client's work and add evening hours. They apply a 20% rush premium to the work cost. (The percentage is a hypothetical business choice, not a standard.)

The math

• Work cost: (14 + 5) × $85 = 19 × $85 = $1,615

• Rush premium: 20% × $1,615 = $323

• Change request price (keep launch date): $1,938

Offer the client a choice. This is often the most useful step. Alongside the rush option, give a standard option:

• Option A — keep launch date: $1,938

• Option B — move launch by 3 business days: $1,615, launch moves from [date] to [date]

If they had only quoted the new page, they'd have charged 14 × $85 = $1,190 and absorbed the rest. The gap ($425 of rework alone, more with the rush) is the money most teams leave on the table on "approved" changes.

The approve-before-work workflow

A well-priced change request only protects you if the client agrees before you start. Here's a simple process:

1. Check the request against the scope

Is it included, extra, or unclear? Open your scope of work and look for the deliverables list and the "not included" section. If it's unclear, ask what "done" looks like before you estimate.

2. Price it the same day

Use the formula: new work + knock-on rework + timeline cost. A fast reply with a clear price feels professional. A price that shows up a week later feels like a penalty.

3. Send the change request with a short, friendly note

Something like:

Happy to add this. It's outside the current scope, so here's a quick change request with the price and what it does to the timeline. Two options: keep the launch date with a rush fee, or move launch by 3 days at the standard price. Just reply with A or B.

For general wording on out-of-scope conversations, see how to tell a client it's out of scope.

4. Start only after a written yes

An email saying "approved, option B" is enough for most changes. For larger ones, use the signature block on the change request form template. Make sure the person approving can actually approve spending. To make this approval step part of your contract terms, add a scope creep clause.

5. Log it and update the plan

Record the approved change, the price, and the new dates. Update the project timeline and your invoice schedule. Over a few months, that log tells you whether a client's base package or retainer is the right size.

What if you've been doing changes for free?

Most people start pricing change requests after realising how much they've given away. If you want a rough sense of the ongoing cost across your clients, the free scope creep calculator estimates monthly and yearly unbilled work from three inputs: active clients, unbilled extra hours per client per month, and hourly rate. It won't price a specific change request for you — use the formula above for that — but it's a quick reality check on the bigger picture.

From there, you don't need to suddenly charge for everything. Start with the next request: price it fully, offer a choice on timing, and ask for approval before you start.

Doing this without the paperwork

I built Creepless because pricing and chasing approvals for every extra request was the part that always slipped in a busy week. Clients send requests through their own private link, each one is checked against the plan you set, and extras get a suggested price and a drafted reply. The client approves the quote before work starts.

You can click through the demo to see the flow — the sample clients and numbers there are fictional. The free plan covers 2 clients and 20 AI checks, no card needed, and setup takes a few minutes.

FAQ: pricing change requests

How do you calculate the cost of a change request?

Add the hours for the new work and the hours for any rework it causes in already-finished work, multiply by your hourly rate, then add any timeline cost such as a rush premium. Formula: (new work hours + rework hours) × rate + timeline cost.

Should I charge a rush fee for change requests?

Only if the client wants the change without moving the deadline and that forces overtime, contractors, or rescheduling other work. A good approach is to offer two options: the standard price with a later date, or a rush price that keeps the original date.

Can I charge for changes to work the client already approved?

Yes. Once a deliverable is approved, changing it is new work. Include that rework in the change request price and say so in your scope of work upfront.

Do small changes need a formal change request?

Every extra needs a price and a yes before work starts, but not always a full form. For a small change, a one-line reply with the price and the client's "go ahead" does the same job.