Blog

Website change request form template for agencies

Most website projects go over budget one small "while you're in there" at a time. A website change request form template gives those moments a home: one short record of what is changing, why, where on the site, what it does to cost and timeline, and who said yes. Below is a form you can copy, a filled-in version, and a simple test for when to use it.

Website change request form: What changed, why, what it costs, and who approved it.
The short versionA revision adjusts something you already agreed to build. A change request adds something new, or reopens work the client already approved. Only change requests need the form. Keep it to one page: the request, the page and element it affects, the reason, the effect on cost and timeline, and a named person who approves it before work starts. Log every form in one place and link each one to the exact spot on the page.

Why agencies need a change request form

Clients don't set out to blow the budget. They see the site taking shape, have a good idea, and mention it in a call or a comment. You say "sure", because it sounds small. Ten of those later, the launch has slipped two weeks and nobody can remember agreeing to any of it.

A form fixes the memory problem. It turns a passing idea into a decision with a price and a date attached, made by someone who can say yes. Most clients are happy to approve a fair cost when they see it written down. What they dislike is a surprise on the final invoice.

It only works if people use it, and people only use it if it applies to the right things. Send a form for every tweak and the client will stop reading them. So start with the line between a revision and a change request.

Revision or change request?

A revision adjusts something you already agreed to build. It uses the rounds included in your proposal. A change request adds something new, or reopens work the client has already approved. It gets its own cost and timeline, and it needs the form.

The client asksWhich is itWhy
"Can the homepage headline be shorter?" during the design roundRevisionSame page, same element, still in review
"Swap the team photo for the new one we sent"RevisionContent within an agreed section
"Make the buttons a bit darker" before design sign-offRevisionRefining the agreed design
"Add a careers page"Change requestA page that isn't in the agreed sitemap
"Let's go back to the other homepage layout" after it was approvedChange requestReopens a signed-off stage
"Can people book appointments online?"Change requestA new feature, likely a third-party tool
"We've changed our brand colour" after the build startedChange requestAffects every page already built
"The contact form doesn't send"NeitherA bug. Fixing it is part of the job

When you're not sure, ask four questions:

  1. Is it in the agreed scope, sitemap or brief?
  2. Has the stage it touches already been approved?
  3. Does it add a page, a feature, an integration or a new type of content?
  4. Will it take more than an hour or two, or move a deadline?

If the answer to the first is no, or any of the others is yes, it's a change request. Our post on how many revision rounds to include covers how to define a round in the proposal, which makes this line much easier to hold.

The change request form

Copy it into a doc, a spreadsheet row or an email. Swap the parts in curly brackets for your own details. It is deliberately short: if it takes more than five minutes to fill in, it won't get filled in.

Website change request form

One form per change. Approve before work starts.
WEBSITE CHANGE REQUEST Reference: CR-{number} Project: {project name} Date raised: {date} Requested by: {name, role} 1. What should change {one or two sentences describing the change} 2. Where on the site Page: {page name and address} Element: {section or element, or link to the pinned comment} 3. Why {the reason, in the client's words if possible} 4. Why this is a change request, not a revision {new page / new feature / reopens an approved stage / outside the agreed scope} 5. Effect on cost Estimate: {hours} at {rate} = {total}, or {fixed price} Ongoing costs, if any: {plugin, licence or hosting cost} 6. Effect on timeline Adds: {number} working days Launch date moves from {old date} to {new date}, or no change 7. Other effects {other pages, content or work this touches} 8. Decision Approved / Declined / Deferred to {phase or date} Approved by: {name, role} Date: {date} How approved: {email reply / signature / Approve on review link}

A few notes on the fields:

  • Where on the site. "The homepage" is not enough. Name the section, or better, link straight to a comment pinned on the element, so nobody has to guess what "the banner" means.
  • Why. The reason often points to a cheaper fix. "Add a careers page" might really mean "we need one job ad live by Friday", which a single section could handle.
  • Effect on timeline. Clients notice cost and forget time. Say plainly whether the launch date moves.
  • Approved by. Agree at kickoff who can approve spending. A marketing assistant asking for a change is fine; approving the cost may need their manager.

A filled-in version

Here is the same form completed for a fictional dental practice, where the client asked for online booking after the homepage was signed off.

A filled-in version

For reference. Copy the blank form above for your own use.
WEBSITE CHANGE REQUEST Reference: CR-004 Project: the dental practice website Date raised: 18 November 2026 Requested by: Priya Shah, Practice Manager 1. What should change Add an online booking page, and a "Book an appointment" button in the homepage header that links to it. 2. Where on the site Page: New page, /book. Homepage, / Element: Homepage header, next to the phone number (pinned comment on the header in round 2) 3. Why "Most new patients call outside opening hours and we lose them. We want them to book themselves." 4. Why this is a change request, not a revision New page and new feature. The homepage design was approved on 6 November. 5. Effect on cost Estimate: 7 hours at $90 = $630 Ongoing costs, if any: the booking tool's own monthly fee, paid by the practice 6. Effect on timeline Adds: 3 working days Launch date moves from 2 December to 5 December 7. Other effects Header updated on every page. Privacy page needs a line about the booking tool, wording from the practice. 8. Decision Approved Approved by: Tom Reid, Practice Owner Date: 19 November 2026 How approved: Email reply

Notice that the person who asked is not the person who approved. That is normal, and it's exactly why the form names both.

How to run it

Who fills it in

Your project lead, not the client. The client describes what they want, in a comment or a call, and you turn it into a form with the cost and timeline worked out. Asking clients to estimate hours is a good way to make sure the form never comes back.

When to raise it

As soon as you spot it, and before any work starts. A short reply works well: "Happy to do this. It's outside what we agreed, so I've written it up as a change request with the cost and the new launch date. Can you approve it?" Doing the work first and asking later turns a fair conversation into an awkward one.

Getting approval

Send the form to the person who can approve spending, agreed at kickoff. Record the yes in writing. What counts as a valid approval, and whether you need a signature, depends on your contract, so check your own terms. If your contract doesn't mention change requests at all, it's worth asking whoever drafted it to add a short clause before the next project.

Logging every request

Keep one running list per project, in a spreadsheet or your project tool, with one row per form: reference, date, short title, cost, days added and status (waiting, approved, declined, deferred). Declined and deferred rows matter as much as approved ones. At the end of the project they show what was asked for and when, and deferred ideas make a ready-made list for a phase two quote.

Linking it to the page

The hardest part of a change request is often agreeing what it refers to. If the request starts as a comment pinned to the element on the review link, link that comment in the "Where on the site" field. In HTMLAnnotate, a pinned comment records the exact page and element, and you can add a label such as "change request" so these stand out from ordinary revision notes. When the change is built, publish it as a new version on the same link. Earlier versions keep their comments, so the before and after are both on record, and the client can press Approve on the new version to sign it off.

For a wider view of how change requests fit into intake, rounds and sign-off, see our agency client feedback process and the guide to getting client approval on a website.

Change requests after launch

This form is built for projects with a fixed scope. Once a site is live and on a maintenance retainer, most requests are small updates paid from monthly hours, and a full form for each would be overkill. Our guide to handling retainer change requests covers sizing those, what needs a separate quote, and the monthly summary. Keep this form for the larger items a retainer doesn't cover.

To explain the process to a client at the start, add a line to your kickoff email. Our feedback request email templates are a good place to put it.

Questions

What should a website change request form include?

The date and a reference number, who asked, the page and element affected, what should change and why, the effect on cost and on the timeline, and the name of the person who approved it with the date. Anything more tends to stop people filling it in.

What is the difference between a revision and a change request?

A revision adjusts something that is already in the agreed scope, such as rewording a headline during a design round. A change request adds something new, like a page or a feature, or reopens a stage the client has already signed off. Revisions use your included rounds. Change requests get their own price and date.

Who should fill in the change request form?

Usually the agency's project lead fills it in from the client's request, then sends it to the client for approval. Clients rarely know the cost or timeline effect, so asking them to complete the whole form slows things down.

Does a change request need a signature?

It needs a clear, recorded yes from someone with the authority to approve spending. Whether an email reply, a button press or a signature is enough depends on your contract, so check your own terms or ask whoever drafted them.

What if the client says no to the cost?

Mark the request as declined or deferred, note the date, and carry on with the agreed scope. A deferred request is a useful start for a phase two quote or a later retainer.

Pin every change request to the exact spot on the page. Clients click anything to comment, with no account.

Start a free review