A website change request is anything added or altered after the scope was agreed: a new page, a new feature, a redesign of an approved section. It costs extra because it adds work and can delay launch. Agree a written process: describe the change, get a quote and new date, approve in writing, then build, with 1 small contingency budget.
Key Takeaways
- Changes are normal; unmanaged changes are what cause disputes.
- Fixed prices cover the agreed scope only; new work needs its own quote.
- Changes after design approval or build often cost more than the same change earlier.
- A simple written change process protects both owner and developer.
- Group small changes into a single request where possible.
What Counts as a Website Change Request?
Every project changes a little as it takes shape. You see the design and realise a page is missing, a competitor launches a feature you want too, or a partner asks for a booking form. A website change request is any addition or alteration to the agreed scope after it was signed off. Changes are normal and often sensible. The trouble starts when they are added informally, through WhatsApp messages and phone calls, without anyone agreeing what they cost or how they affect the launch date. That slow drift is called scope creep.
Scope is easier to protect when you start with the right partner; see our guide to choosing a developer.
Which Changes Usually Cost Extra?
| Usually included | Usually a change request |
|---|---|
| Fixing errors against the agreed scope | Adding new pages or sections |
| Text edits within agreed revision rounds | New features such as booking, payments or login areas |
| Small layout fixes during agreed revisions | Redesigning a section already approved |
| Bugs found during testing | Switching to a different platform or theme mid-project |
| Agreed content placed on agreed pages | New integrations with other systems |
Exactly what is included depends on your contract; our contract checklist explains how to word it.
Why Do Changes Cost More Later?
A change costs least before design starts, more after design approval and most after building, because finished work must be undone, redone and retested. Adding a page during planning is a line on a list. Adding the same page after launch preparation may mean new design, new content, navigation changes, new testing and an updated launch plan.
What Does a Worked Example Look Like?
An illustrative case: a clinic agrees a six-page business website. After design approval, the owner asks for an online appointment form linked to doctors' calendars. The developer explains this is a new feature: it needs design for the form, calendar logic, email and WhatsApp notifications and testing. They quote the extra work separately and estimate the launch moves by about a week. The owner can approve it now, or launch on time and add booking in a second phase. Either choice is fine; what matters is that it is a decision, not an assumption. The figures and timings are invented to show the process.
What Is a Fair Change Process?
- Describe the change in writing: what, where and why.
- Estimate: the developer replies with cost and effect on the timeline.
- Decide: approve, defer to a later phase or drop it.
- Record: keep approved changes in one list with dates and prices.
- Build only after written approval.
Fixed-price and hourly projects handle changes differently; our comparison of fixed price vs hourly explains the trade-offs.
How Can Owners Reduce Change Requests?
- Spend more time on the brief and discovery meeting.
- Agree a full page list and feature list before design.
- Involve every decision-maker early, not after design.
- Keep a "phase two" list for ideas that can wait.
- Hold a small contingency budget for genuine surprises.
- Review the scope document once more, line by line, before signing it.
- Ask the developer which parts of the scope they see as most likely to change.
What Should a Developer Do?
Flag a change as soon as it is requested, before doing the work, and never surprise a client with charges at the end. Our design feedback guide explains how revision rounds differ from changes.
Do Changes Affect Data or Privacy?
New features that collect personal data, such as booking forms or logins, also need privacy policy updates and security checks. Include these in the change estimate.
How We Price Changes
Our packages, from Rs 40,500, list exactly what is included, and we quote any change in writing before starting it. See our pricing page.
See also Your First Website Discovery Meeting.
Frequently Asked Questions
- W3C WAI — WCAG overview
- ICO — UK GDPR guidance and resources
- OWASP — Top 10 web application security risks
How we researched this: The clinic example is invented and labelled illustrative, as the plan requires. The included-versus-change table and change process are editorial, based on common contract practice. Our prices come from the published list.
Project scope getting out of hand?
Message us on WhatsApp for a fixed quote, or see our published pricing first.