Website Change Request Form: Free Template, Change Log and Process
By GiveFeedback.ioUpdated 9 min read
A website change request form is how a client asks for something different from what was agreed (a new page, a moved section, a new feature) in a way you can estimate, approve and schedule. Without one, changes arrive as quick favors in calls and chats, get done for free or forgotten, and the price is discussed after the work is finished. The free Word form and Excel change log below give every request the same fields, an estimate and a clear yes or no from the client before anything starts.
What is a website change request form?
A website change request form is a short document in which a client asks for a change to their website and the agency answers with the scope, an estimate and a delivery date, so the change is approved before any work starts. It records three decisions in one place: what exactly will change, whether it's already paid for, and what it costs if it isn't.
Before launch, it's what you use when a client wants to reopen a stage they already approved: once the design or the staging site has been through client website approval, anything that changes it is a change request. After launch, the same form is often called a website update request form, and most requests are content updates or small improvements under a maintenance plan. The handover document is the right place to explain to the client how bugs and changes are told apart from then on.
Is it a change request or a bug?
It's a bug if the site doesn't do what was agreed, and a change if the client wants something different from what was agreed. The approved design, the scope and the sign-off are the reference: if the site matches them, the request is a change, however small it is.
| Request | Example | Usually covered by | How it should arrive |
|---|---|---|---|
| Bug | "The contact form doesn't send on iPhone" | The warranty or the maintenance plan | A bug report with steps and a screenshot |
| Content update | "Change the opening hours for winter" | The maintenance plan's hours | An update request, often without a quote |
| Change request | "Add a page for our new service" | A quote, unless the plan's hours cover it | The change request form |
| New project | "We'd like to add an online shop" | A new proposal | A brief and a proposal |
The grey areas are where it gets awkward. The menu works, but the client expected it to stay on screen while scrolling: if the approved design showed a sticky menu, it's a bug; if it didn't, it's a change. Our bug report guide draws the same line: "the menu doesn't open on iPhone" is a bug, "I'd like the menu to be green" is a change.
When it's unclear, say so in the assessment and agree it with the client before doing the work. Doing it first and arguing about it afterwards is how a one-off favor becomes the rule.
What should a website change request form include?
Four parts: the request, filled in by the client; the assessment, filled in by the agency; the approval, signed or confirmed in writing by the client; and the completion, which records when the change was checked and went live. These are the fields in the Word template:
| Field | Who fills it in | Why it's there |
|---|---|---|
| Request ID, date, requester, pages | Client (the ID by the agency) | One reference across emails, the log and the invoice |
| Type of change | Client | Separates content updates from new pages and features |
| What is there now / what you would like instead | Client | Turns "make it pop" into something you can estimate |
| Why: the goal or the problem it solves | Client | Often points to a simpler way to get the same result |
| Done when | Client | Defines finished before the work starts |
| Attachments | Client | Marked-up screenshots, final texts, images |
| Priority and wanted-by date | Client | Lets you schedule it; "urgent" needs a reason |
| Scope | Agency | Included in the contract, covered by the maintenance plan, or quoted |
| Estimate, cost, impact, risks, delivery date | Agency | What the client is approving |
| Decision and signatures | Client and agency | The approval, in writing |
| Done, checked and live dates | Agency | Closes the request in the log |
Two fields do most of the work. Why catches requests where the client has already designed a solution ("add a pop-up on every page") for a problem that has an easier fix ("people can't find the phone number"). Done when settles the end of the job before it starts: "the page is live at this address, appears in the menu on phones and computers, and a test message from the form arrives at sales@" leaves nothing to argue about at review time. The template's second page has a filled-in example, a new service page from request to go-live.
Change request template to copy and paste
For requests that arrive by email, paste this into your reply and ask the client to fill it in, or fill it in yourself from what they said and ask them to confirm it. It has the same fields as the Word form.
Change request: [short title]
ID: CR-___
Date:
Requested by (name, role):
Page(s):
Type: [text or image update / design or layout change / new page
or section / new feature / integration / SEO or technical / other]
What is there now:
What you would like instead:
Why (the goal or the problem it solves):
Done when:
Priority: [low / normal / high / urgent: why]
Wanted by (date and reason):
Attachments:
--- Filled in by us ---
Scope: [included in the contract / covered by the maintenance plan /
out of scope: quoted]
Estimate (hours):
Cost:
Impact on the timeline:
Proposed delivery date:
Approved by (name, date):
How does the website change request process work?
Receive, log, assess, estimate, approve, deliver, report. The form covers the first five steps; the change log keeps the history of all of them.
- Receive the request. If it comes by phone or in a chat, write it on the form yourself and send it back for the client to confirm.
- Log it in the change log with an ID and the status New.
- Assess it: bug or change, in scope or not, how long it takes, what else it affects.
- Send the estimate with a delivery date and set the status to Waiting for approval.
- Get the approval in writing, as a signature on the form or a reply to the estimate. Nothing starts before it.
- Make the change on staging, ask the client to check it against "Done when", then release it and record the date.
- Report once a month: the log's summary with the hours used and the requests still waiting for a decision.
Batch small approved changes into regular releases instead of shipping each one the day it's approved. Each release then gets one round of testing and one email to the client, and a fix in one place is less likely to break something next to it unnoticed.
How do you keep a website change log?
One row per request, never deleted, with the scope, the estimate, the client's decision and the status. When a request is turned down, set it to Rejected instead of removing it: the log is the record you'll need when a client says "we asked for that months ago" or "we never approved that".
The Excel template has one row per request with these columns: ID, date received, requested by, page URL, the change in one sentence, type, scope, priority, estimate in hours, quote, client decision, decision date, assigned to, status, live date and notes. Type, scope, priority, decision and status are dropdowns, so the sheet can be filtered by any of them. The shaded rows are examples to replace.
A second sheet adds it up: requests logged, requests waiting for the client, approved hours, approved quotes, hours covered by the maintenance plan and a count by status. That summary doubles as the monthly report to the client, and it's the conversation you need when a maintenance plan comes up for renewal: here is what you asked for, here is what it took.
What should the contract say about change requests?
Define what counts as a change, how it is requested, how fast you answer with an estimate, who approves on the client's side and the rate. A small-change rule keeps minor updates from needing a quote each time. Here is an example clause to adapt; it's an example, not legal advice, so have it reviewed for your jurisdiction.
Changes. Any request that differs from the approved scope, design or
content, or that reaches us after sign-off, is a change request. The
Client submits change requests in writing, using the change request
form. We reply with an estimate within [two (2)] working days. Work
starts only after the Client's designated contact approves the
estimate in writing, and is billed at the agreed rate of [rate] per
hour. Changes estimated at under [one (1)] hour may be made without a
separate estimate and are listed in the monthly change log. Defects in
the delivered work are not change requests and are fixed under the
warranty.
The clause pairs with a revision limit during the project; the approval guide has one for review rounds.
How do you collect change requests from clients without the chaos?
Give clients one place to send them, and make it easier than a chat message. Change requests often start as a remark about a specific spot on a page, so the easiest place to collect them is the page itself.
With GiveFeedback.io, a "Give Feedback" button sits on the client's site. The client clicks it, marks the spot on a screenshot with arrows, boxes, text or numbered markers, writes what they want and picks a type. The default types are Bug, Feature, Proposal and Recommendation, so a broken form and a request for a new section arrive already sorted. No account is needed, and it works from a computer, a phone or a tablet.
Each report includes the page URL, the browser and version, the operating system, the screen resolution and a log of the page's console messages, errors and failed requests, so the bugs arrive ready to reproduce. Bugs go to the fix list. Feature and Proposal reports become rows in the change log, with the form for anything that needs a quote. Reports can be created automatically in Jira, Trello, ClickUp, Asana, monday.com, Wrike or Notion, or posted to Slack, Discord or email (all integrations), and you can invite the client to a read-only view of the project's feedback so they see what's open and what's resolved.
The Free plan covers 5 projects and 50 feedback reports; see pricing for the rest.
Put the form in the handover pack, the clause in the contract and the log in a shared folder. The first "quick change" after launch then becomes a two-line estimate and a yes or no, instead of a favor nobody wrote down.
Frequently asked questions
What is the difference between a change request and a bug?
A bug is when the site doesn't do what was agreed: a form that doesn't send, a layout that breaks on a phone. A change request asks for something different from what was agreed: a new page, a moved section, another color. Check the approved design and scope: if the site matches them, the request is a change, however small it is.
Who fills in a website change request form?
The client fills in the request: what they want, why, which pages, a priority and a date. The agency or freelancer fills in the assessment: whether it's in scope, the estimate, the cost and a delivery date. The client then approves or rejects the estimate in writing, and the agency records when the change was checked and went live.
Should small website changes go through a change request?
Log all of them, but don't quote all of them. A small-change rule in the contract keeps minor updates moving: for example, changes estimated at under an hour are done without a separate estimate, or come out of a monthly block of maintenance hours. The log still lists every change, so the client can see where the hours went.
What is a website update request form?
It's the same document used after launch, usually under a maintenance plan: the client asks for a content update or a small change, and the agency confirms whether the plan's hours cover it or it needs a quote. The form and the log on this page work for both; set the scope to "Covered by the maintenance plan" when it applies.
Can I use the change log in Google Sheets?
Yes. Download the Excel file and open it in Google Sheets with File, then Import, then Upload. The dropdowns for type, scope, priority, client decision and status are kept, and so is the summary sheet that adds up approved hours and quotes. Share it with the client as view-only so they can follow each request without asking.
How quickly should an agency answer a change request?
Set a response time for the estimate in the contract, not for the change itself, for example two working days. Urgent requests can get a faster estimate if the client explains why. What matters is that the client knows when to expect an answer, and that no work starts before they approve the estimate in writing.
Keep reading
Guides
Jira Bug Report Template: Free CSV Import and Field Guide
A Jira bug report template you can import: a free CSV with four example bugs, a field guide, a description to paste and how to write a bug report in Jira.
- 9 min read
Guides
Website Feedback Form Questions: 45 Examples by Goal (Free Template)
Website feedback form questions for visitors, customers and clients: 45 examples grouped by goal, three ready-made forms and a free Excel question bank.
- 11 min read
Guides
Bug Severity vs Priority: Differences, Examples and a Free Matrix
Bug severity vs priority: what each one measures, severity levels, website examples where they disagree and a free Excel matrix that suggests priority.
- 10 min read
Collect visual feedback on your next website
Visual website feedback for agencies, freelancers and their clients.
Free plan - No credit card - Set up in minutes
