Website change request form
By The Onbo team · Updated
Short answer
A website change request form captures what the client wants changed, why, how urgent it is and which pages it affects, then records your price and timeline impact and the client's approval. Use it for anything outside the approved sitemap or scope, and start the work only once the client has accepted the change in writing.
Every website project gets new ideas halfway through: a careers page, a booking feature, a second language. Those ideas are often good, and clients should be able to suggest them. The trouble comes when they’re added informally, by email or in passing on a call, and the scope, price and launch date quietly drift. A short change request form turns each idea into a clear decision for both sides.
How to use this form
Introduce it at kickoff as the normal route for new ideas, alongside the approved sitemap. When the client asks for something outside the agreed scope, send the form or fill it in together. Add your estimate, send it back, and start only after the client approves. Keep every completed form with the project record.
The change request form
Client and project: [client] - [project]
Request number and date: [CR-01] · [date]
Part 1: completed by the client
| Field | Answer |
|---|---|
| What would you like to add or change? | [e.g. a careers page with job listings] |
| Why? What should it achieve? | [goal] |
| Which pages or features does it affect? | [pages] |
| How urgent is it? | Before launch / soon after / later phase |
| What will you supply? | [content, images, details] and by when |
Part 2: completed by you
| Field | Answer |
|---|---|
| Is it within the current scope? | Yes (no charge) / No (change) |
| Work involved | [design, build, content, testing] |
| Price | [amount] |
| Effect on the timeline | [new launch date or “none”] |
| Effect on other work | [anything delayed or replaced] |
Part 3: approval
| Approved by | [name, with final say] |
| Date | [date] |
| Payment | [added to the next milestone / separate invoice] |
When should you use it?
Use the form for anything outside the approved sitemap, the agreed features or the included revision rounds. Don’t use it for small corrections within an included round, such as fixing a typo or adjusting a colour; asking for a form there feels bureaucratic. The test is simple: if the request adds work you didn’t plan or price, it’s a change.
For example, a web studio might receive a request for an events calendar during design. The client fills in part 1 in five minutes, the studio adds a price and a one-week extension in part 2, and the client’s managing director approves it the same afternoon. The calendar is added to the timeline, invoiced with the launch payment, and nobody argues about it later.
How do you keep change requests friendly?
Present them as a way to say yes, not a barrier. Thank the client for the idea, respond quickly, and offer options: add it now with a new date, add it after launch as a second phase, or swap it for something of similar size that’s no longer needed. Many clients are relieved to see the cost and timing before deciding, rather than discovering them at the final invoice.
The form works best when the original scope is clear. If you haven’t got a signed-off sitemap, start there: see how to get sitemap approval from a website client. Your agreement should describe the change process too; the web design contract checklist lists the clause, and the website project kickoff is the moment to explain it.
How do you price a change?
Estimate the change the same way you priced the original project: the design, build, content and testing it adds, plus any effect on work already done. Small additions are often simplest as a fixed price; larger ones may need a short scope of their own. Say clearly whether the change moves the launch date, because that matters to clients as much as the price. If several small requests arrive together, bundle them into one change so the client makes one decision rather than five.
A change request checklist
- Change process explained at kickoff
- Approved sitemap and scope as the reference
- Client describes the change and the reason
- Affected pages and inputs listed
- Price and timeline impact estimated
- Options offered: now, later phase, or swap
- Approval from the person with final say
- Work starts only after approval
- Payment route agreed
- Completed form kept with the project record
Where Onbo fits
Onbo sets up the reference point change requests depend on. At the start of each project, your client accepts the agreement with your scope and change terms, pays the deposit and answers your website questionnaire, so the approved pages and features are on record before design begins. Try it free for 30 days; see pricing.
Questions
What should a website change request include?
What's changing, why, which pages are affected, priority, any content or files needed, and then the price, timeline impact and the client's approval.
When should I use a change request?
For anything outside the approved sitemap, agreed features or included revision rounds. Small fixes within an included round don't need one.
How do I introduce change requests without annoying the client?
Mention them at kickoff as the normal way new ideas get added, so the first request feels routine rather than a reaction to the client.