Change requests your client signs before you start
Keep scope and revision rounds in locked terms, and send each change as a revised version with its price and time.
- 5/5 on G2
- 4.2 on Capterra
- Building QuoteCloud since 2013
In QuoteCloud a studio keeps its scope and revision-round terms in a locked content block (content locking, Business). When a client asks for more, you revise the signed proposal into a new version with each change, its price and the effect on the launch date; the client signs it before work starts, and earlier versions stay in the document's history (version history, Business).
Change request CR-02 to a sample website proposal, GS-2611, from a fictional studio, Glasswing Studio, shown as the difference between version 1 and version 2, like a code review. Removed lines are struck through in red and added lines are in green: gift cards in the shop were not in scope, now gift cards from $25 emailed to the recipient, plus $1,200; five page templates become six with a weddings gallery page, plus $320. The project fee including tax goes from $21,098.00 to $22,770.00, plus $1,672.00, and the launch moves from week 14 to week 15. At the foot, version 2 is signed by Ella Mancini on Friday 11 December at 9:40 am, with version 1 kept in the document's history.
Revise the signed proposal, get version 2 signed
At the week-7 design review Ella asks for gift cards before Mother's Day and a page for wedding work. Neither is in the signed scope, so Sam doesn't start them. He opens the signed proposal and uses Revise Last Version.
Version 2 sets each change beside what was agreed, its price, the new project fee and the extra week. Ella signs it the next morning; Ravi starts the gift cards that afternoon. The extra $1,672.00 goes on the launch invoice.
- Revise Last Version keeps version 1
- Each change: was, now, price and time
- Signed before the extra work starts
Version history: Business plan · eSignatures: every plan
Deposits, milestones & sign-offAsked for at the design review: sell gift cards before Mother's Day, and show wedding work on its own gallery page.
| Change | Agreed scope | Now | Price ex tax |
|---|---|---|---|
| Gift cards in the shop | Not in scope | Gift cards from $25, emailed to the recipient | +$1,200.00 |
| Weddings gallery page | 5 page templates | 6 page templates | +$320.00 |
- Agreed project fee version 1
- $21,098.00
- This change inc. tax
- +$1,672.00
- Revised project fee inc. tax
- $22,770.00
- Time
- +1 week: launch moves from week 14 to week 15
Signing this version replaces the scope and fee in version 1. Version 1 stays in the document's history. The extra fee is added to the launch invoice.
Accept and sign
Ella Mancini · Owner, Sparrow & Pine
Signed online · Fri 11 Dec 2026, 9:40 am
Change request summary
- Change
- +$1,672.00 inc. tax
- Project fee
- $22,770.00 inc. tax
- Launch
- Week 15
- Version
- 2 of GS-2611
Certificate of authenticity and audit trail attached
Activity
- Version 2 sentRevise Last Version · CR-02
- Signed by EllaVersion 1 kept in history
Scope and revision rounds, written once and locked
Most change-request arguments start with a scope that was worded differently in every proposal. Glasswing keeps its scope, revision-round and change wording in the content library and locks it.
- About GlasswingTeam and process
- What's includedScope wording per site type Locked
- Revision roundsTwo on designs, one on the build Locked
- How changes workChange requests as new versions Locked
- Payment milestonesDeposit, design, launch Locked
- Recent workCase study with photos
- 1CoverElla & Luca Mancini · valid 30 days
- 2About us From library
- 3Your sitemap12 pages from 5 templates
- 4Price by phasePrice table with options
- 5Project phasesGantt chart, 14 weeks
- 6Scope Locked block
- 7Revisions Locked block
- 8Changes Locked block
- 9Payment milestones Locked block
- 10Recent work From library
- 11Sign & payTwo signers, 40% deposit
Write it once
Save scope, revision and change wording as content library blocks every project manager reuses.
Content library: Essentials and up
Lock what must not change
Locked blocks go out exactly as written; only permitted roles can unlock and edit them.
Content locking: Business
Point to it in the change
Each change request quotes the agreed scope, so the client sees why it's extra.
What counts as a change, and what doesn't
Agree it in the locked terms, then apply it the same way on every project.
New pages or templates
A page outside the sitemap, or a new page template, is a change with its own price.
New features
Gift cards, a members' area, a new integration: priced as a change, with any effect on the launch date.
Another revision round
Rounds beyond those in the scope are a change, or an add-on the client ticked up front.
Swaps of equal size
Swapping one page for another of the same kind can be agreed in a comment, with no new version.
Fixing what was agreed
Bugs and things that don't match the signed designs aren't changes: they're your work.
Late client content
Content that arrives after the agreed date can move the launch: say so in the terms.
Price the next change in minutes, not a new proposal
Free for 14 days, no credit card required. Version history and content locking are on the Business plan.
Sample change request · CR-02
Agreed in writing before a line of code
Two changes, one new version, signed the morning after the design review. The extra fee is on the launch invoice, and nobody has to remember what was said on the call.
Change orders in QuoteCloudSend a change request in five steps
From the client's request to a signed version 2, before the extra work starts.
Hear the request
The client asks in a call, an email or a comment on the proposal.
Revise the proposal
Open the signed proposal and choose Revise Last Version.
Price each change
Set each change beside the agreed scope, with its price and its effect on the launch date.
Send version 2
The client reads what changed and asks in comments if anything's unclear.
Signed, then start
Once it's signed, start the work. Version 1 stays in the history (Business plan).
Change requests: your questions
How do I handle a change request on a website project?
Open the signed proposal and use Revise Last Version. In the new version, set each change beside the agreed scope with its price and its effect on the launch date, then send it. The client signs version 2 before you start the extra work, and version 1 stays in the document's history on the Business plan.
How do I stop scope creep?
Write your scope, exclusions, revision rounds and change process once, save them in the content library and lock them (content locking, Business plan), so every proposal says the same thing. When something falls outside, send a change request the client signs, rather than agreeing it on a call.
Can the client edit the proposal or suggest changes in it?
The client can comment on the proposal and you can reply, so a request can start there. They can't edit your document: you make the changes in a revised version and send it for signature. There's no live co-editing in QuoteCloud.
Is the change paid when the client signs it?
Only if you set a deposit or payment on that version. Many studios add the change to the next milestone invoice instead, and say so in the change request. QuoteCloud takes payment only on signing; it doesn't invoice later.
Can a Zap create a revised version for me?
Zapier's Duplicate or Revise Document action can create the new version from Essentials (document creation fees apply). You still add the changes and prices and send it; automations don't tick options or choose content blocks.
More for web studios
Every page of the QuoteCloud web developers & SEO microsite.
-
Deposits, milestones & client sign-offA deposit on signing, later milestones set out in the contract and a separate sign-off document for each milestone.Explore
-
Website build proposalsDiscovery, design, build and launch as phases on a Gantt, pages as quantities and a deposit paid when the client signs.Explore
-
Discovery questionnairesThe questions you ask before you quote, answered inside a document with the Forms block, then carried into the proposal.Explore
- App & software development proposalsiOS, Android and web app estimates by feature and sprint, with the hours, the options and the client's sign-off in one document.
- Optional features & add-onsE-commerce, bookings, a second language and integrations as optional items the client ticks, with the total and deposit following.
- Fixed fee or time & materials estimatesOffer a fixed fee and a time-and-materials estimate side by side, so the client chooses how they'd rather pay.
- Portfolio & case studiesYour best work, team bios and process as content library blocks, dropped into every proposal and kept up to date in one place.
- SEO proposals & retainersAudit, technical fixes, content and link building as monthly charges in the agreement, with results only ever your own estimate.
- Hosting, maintenance & support plansCare plan tiers as packages, monthly or annual charges in the agreement, expiry dates and renewals bulk-sent for signing.
- Project tools, CRM & accounting connectionsSigned proposals to Jira, Asana, monday.com or Trello through Zapier or the API, Pipedrive directly, and Xero or QuickBooks.
- Web, SEO & app templatesReal QuoteCloud templates for website development, redesigns, SEO, maintenance and app projects, ready to make your own.
- QuoteCloud implementation for studiosYour proposal templates converted, your rates in the catalogue, Stripe connected and your project tools linked.
- FAQAnswers to the questions web studios, developers and SEO specialists ask most.
Say yes to changes, in writing
Free for 14 days. No credit card required.