Use the template right away
Change request — web project
1. Request
- Project / website: ____________________________
- Requested by (name, role): ____________________________
- Date: ____________________________
- Request no.: ____________________________
2. The change
- What should change? ____________________________
- Where exactly (page, section, element): ____________________________
- Desired outcome / goal of the change: ____________________________
3. Classification
- ☐ Defect — deviates from what was agreed (fixed at no charge)
- ☐ New request — beyond the agreed scope (billable, needs a quote)
- Reference to the agreed scope (proposal / brief section): ____________________________
4. Impact
- Estimated effort (hours): ____________________________
- Cost: ____________________________
- Effect on the timeline / launch date: ____________________________
- Priority: ☐ high ☐ medium ☐ low
5. Decision
- ☐ Approved — proceed as quoted
- ☐ Declined
- ☐ Deferred until after launch
- Decided by (approver): ____________________________
- Date / signature: ____________________________
Why block 3 pays for the whole form
Most scope conflicts in web projects aren’t about money — they’re about the missing moment of decision. The client believes the wish is part of the deal; the agency knows it isn’t; nobody says it out loud, and the resentment compounds. Block 3 forces the classification while the wish is fresh:
- Defect: the site deviates from what was agreed — fixed at no charge, no discussion.
- New request: beyond the agreed scope — welcome, and billable. The form turns it into a small, clean quote instead of a favor that erodes the margin.
The reference line to the proposal or brief makes the decision checkable: scope isn’t what anyone remembers, it’s what was written down.
In bepeq, the form fills itself
Every client note in bepeq already carries what this form asks for: the exact element, the wish, the round, the status. Wishes beyond scope stay documented instead of drowning in email — and the sign-off record lists what was agreed.
Start bepeq for freeRound 1 closed
14 notes · all done
Round 2 running
Deadline: 4 days left · 3 open points
Then: sign-off with a record
Related templates and guides
All templates
Checklists and templates for the agency workflow, in one place.
Design brief template
The 8-block brief that fixes scope before the project starts.
Website Feedback
The complete guide from the first comment to a binding sign-off.
Website redesign checklist
40 points across 5 phases, from planning to post-launch.
About this template
Created by David Malewski, founder of bepeq (DAMA Solutions GmbH), based on real web projects with agencies and web designers. The template is free to use and adapt. Last updated July 9, 2026.
Common questions about change requests
What is a change request in a web project?
A change request is any wish that goes beyond the agreed scope after the proposal is signed: a new section, a different layout, an extra feature. The form documents what is wanted, what it costs and who approved it — so the change becomes a normal, billable event instead of a silent scope creep.
What’s the difference between a defect and a change request?
A defect deviates from what was agreed and gets fixed at no charge. A change request asks for something new and is billable. Block 3 of this form forces that decision early — it is the single most conflict-preventing line in the whole document.
Do I really need a form for every small change?
Not for typo-level fixes inside an agreed feedback round. The form is for changes that touch scope, budget or timeline. A good rule: if it takes more than an hour or changes what was quoted, it gets a change request.
How do change requests relate to feedback rounds?
Feedback rounds collect corrections on the agreed scope. Change requests capture wishes beyond it. Keeping the two separate is what keeps rounds finite: the round closes on schedule, and new wishes queue up as documented, billable requests instead of reopening the round.