Scope Change Request Form Template
A scope change request form template captures every piece of work a client asks for outside the original agreement — what it is, why it's happening, how many hours it adds, what it costs, and who approved it. It turns an informal "can you just add..." into a signed, dated record before any extra work begins.
The template
Copy the fields below into your preferred tool, or rebuild the form in Ascend Forms.
Form instructions (shown to the person filling it out)
Use this form to document any work that falls outside the original agreed scope. Complete all fields before work begins. Unsigned changes are not billable.
Section 1 — Project identification
| Field | Input type | Notes |
|---|---|---|
| Project name | Short text | Required |
| Client name | Short text | Required |
| Original project start date | Date | Required |
| Original scope document / proposal reference | Short text | e.g. "Proposal v2 dated 2026-03-10" |
| Change request number | Short text | Auto-increments if built in Ascend (e.g. SCR-001) |
| Date of request | Date | Required — defaults to today |
Section 2 — What is changing and why
| Field | Input type | Notes |
|---|---|---|
| Description of requested change | Long text | Required. Plain language — "Add a blog section with 5 pages and a CMS" not "expand deliverables". |
| Reason for the change | Long text | Who asked, what triggered it, why it's out of original scope. |
| Which original deliverable(s) does this affect? | Long text | List affected items from the original scope document. |
Section 3 — Impact assessment
| Field | Input type | Notes |
|---|---|---|
| Estimated additional hours | Number | Required |
| Additional fee ($) | Number | Required. Leave 0 only if a genuine no-charge exception. |
| Timeline impact | Multiple choice | "No change" / "Extends by up to 1 week" / "Extends by 1–2 weeks" / "Extends by more than 2 weeks" / "TBD — needs assessment" |
| Does this change affect any dependencies? | Multiple choice | "No" / "Yes — affects another deliverable" / "Yes — affects a third party" |
| Dependency detail | Long text | Shown if previous answer is "Yes". Describe what is affected. |
Section 4 — Approval
| Field | Input type | Notes |
|---|---|---|
| Submitted by (agency/studio) | Short text | Pre-fill with your name in a live form |
| Client approver name | Short text | Required |
| Client approver email | Required — triggers confirmation copy when built in Ascend | |
| Client approval (typed consent) | Short text | Instruction: "Type your full name to confirm approval." |
| Date approved | Date | Required |
| Payment terms for this change | Multiple choice | "Invoiced with next regular invoice" / "Invoiced immediately on approval" / "Deducted from retainer" / "No charge — exception noted" |
Section 5 — Internal record (agency use only)
| Field | Input type | Notes |
|---|---|---|
| Change category | Multiple choice | "Client-requested addition" / "Client-requested revision beyond agreed rounds" / "External dependency" / "Agency error — no charge" / "Regulatory / technical requirement" |
| Assigned to | Short text | Team member responsible for the additional work |
| Time logged against this change (hours) | Number | Filled in after work is complete, not at approval |
| Notes / context | Long text | Internal only — not shared with client |
How to use this template
- Create an Ascend Form for client submissions (Sections 1–4).
- Point form responses to an Ascend Database — each approved change becomes a record you can track.
- Add the internal fields (Section 5) as columns in the database, filled by your team after submission.
- Use an Ascend Page to publish the form link to clients.
Why the verbal agreement is never enough
A client says yes on a call. The work gets done. Two weeks later the invoice arrives and suddenly the extra pages "weren't discussed." With a completed scope change request form, the conversation is on paper: the description of the change, the fee, and the client's typed or signed approval. That record ends the dispute before it starts.
The form also protects the client. It forces both sides to agree on exactly what the change covers — no ambiguity about whether the new feature includes mobile testing or not.
The fields that matter most
Most scope change request form templates online capture the what (description of change) and the cost. That's the minimum. The three fields that separate a useful form from a paper exercise:
Change category — was this a client-requested addition, a revision beyond agreed rounds, or a change caused by a third party? Knowing the pattern across projects tells you whether your quotes are too lean or your revision rounds are too generous.
Timeline impact — most disputes about scope creep are really disputes about deadline slippage. Capturing the timeline effect at approval, not after the fact, keeps expectations aligned.
Dependency detail — the change that looks small in isolation often blocks something else. Getting this on record avoids a client saying "why is the whole project late when we only added one page?"
When to send a scope change request and when to absorb it
Not every out-of-scope item needs a formal change order. A typo fix on a delivered page doesn't warrant one. A new section with custom design, three extra revision rounds, or a CMS migration does. The internal guideline that works for most studios: if the extra work will add more than 30–45 minutes of billable time, document it.
If you're routinely issuing change orders on things that should have been in the original scope, the scope change request form is pointing at a quoting problem — not a client problem.
Connecting approvals to your invoices
The gap most scope change request form processes leave open: the approved changes sit in email or a folder and never connect to the invoice. When billing day arrives, you're reconstructing which changes were approved, for what amount, and whether they were bundled into a previous invoice.
The cleaner path: each approved change request becomes a record in your project database, with the fee attached. When you build the invoice, the approved-but-unbilled changes are already listed. Nothing falls through. See the retainer burn tracker template for tracking how scope changes affect ongoing retainer engagements.
Related templates
Website Discovery Call Checklist
Discovery is where scope is set — use this to cover it thoroughly.
Website Project Handoff Checklist
Reconcile all approved scope changes before the final invoice goes out.
Retainer Burn Tracker Template
Scope changes consume retainer hours — track the impact here.
Client Project Database Template
Store every approved change request alongside the project record.
Frequently asked questions
What is a scope change request form?+
A scope change request form is a document that captures a client-requested addition or change to agreed work — what the change is, the extra hours and cost, the timeline effect, and the client's approval. It creates a written record before the extra work begins.
What's the difference between a scope change request and a change order?+
The terms are used interchangeably in most creative-agency and web-development contexts. A change order sometimes implies a more formal bilateral document with signatures. For most small studios, a completed scope change request form with typed client consent and a date carries the same practical weight.
When should I use a scope change request form template?+
Any time a client asks for work that wasn't in the original agreed scope and the work will take more than 30–45 minutes of your time. Use it before you start the extra work, not after.
Do I need a lawyer to make a scope change request enforceable?+
For small creative-agency work, a signed or typed-consent form with a clear description, agreed fee, and date is a reasonable record. If the engagement involves large fees or high-stakes deliverables, have a solicitor review your standard terms. This template is not legal advice.
How do I handle a client who refuses to fill out a change request form?+
Pausing work until a form is completed is the clearest approach. If the relationship makes that impractical, send a summary email of the agreed change and fee, and ask the client to reply confirming. That reply is your record.
Can I use this template as an Ascend form?+
Yes. Rebuild the sections as an Ascend Form, point responses to an Ascend Database, and each approved change becomes a tracked record. The free tier covers one client end to end.
How do I number scope change requests?+
A simple sequential prefix works: SCR-001, SCR-002. Include a project code if you're managing multiple projects. When built in Ascend, each database record gets an auto-incrementing ID you can use as the reference.
Related template
Website Project Handoff Checklist
Reconcile every approved scope change request against the final invoice before the project closes.
Make it a live form your clients can submit.
A copied template lives in a folder. A live Ascend form goes to a link — clients fill it out, the approval writes directly to your project database, and the fee is ready to pull into an invoice. The free tier covers one client end to end.
Start with Ascend free