Table of Contents
A freelance scope change request should show what the client asked to change, why it is outside or different from the agreed scope, the added fee, the schedule effect, and the approval needed before the changed work begins. Copy the template below, replace every bracketed field, and attach it to the original project record.
This is an original SignQuick template you can use without an account. SignQuick also sells an e-signature service, but the template is useful on its own.
Is this a revision or a scope change?
Do not label every difficult comment as “scope creep.” Compare the request with the signed contract, statement of work, quote, approved brief, and revision allowance first.
| Client request | Usually treat it as | What to check |
|---|---|---|
| Correct work that does not meet an agreed requirement | Correction within the existing scope | Acceptance criteria and the freelancer's responsibility for the mismatch |
| Adjust an in-scope concept during an included feedback round | Included revision | Number of rounds, review deadlines, and what “revision” means |
| Add a page, feature, format, integration, or deliverable | Scope change | New work, dependencies, fee, and delivery impact |
| Replace an approved direction or redo accepted work | Scope change | Work already completed, work that can be reused, and revised milestones |
| Remove one item to make room for another | Scope swap or change | Whether effort, risk, price, and timing really remain equivalent |
| Ask for work unrelated to the original outcome | New project or separate phase | Whether a clean new agreement will be clearer than an amendment |
If the original agreement defines a change process, use it. A friendly chat message can capture the initial request, but it should not be the only place where the final scope, price, and date are recorded.
Copy the freelance scope change request template
Scope change request: [short change title]
- Change request ID: [CR-001]
- Status: Proposed — not approved
- Project: [project name]
- Original agreement: [contract, statement of work, or quote title, version, and date]
- Request date: [written date]
- Effective date if approved: [written date or approval date]
- Requested by: [client name and role]
- Prepared by: [freelancer or business name]
- Decision requested by: [written date and time zone]
1. Requested change
[Describe what the client asked to add, remove, replace, or accelerate. Use observable deliverables rather than “make it better” or “add a few changes.”]
2. Original scope reference
The original agreement includes: [quote the short relevant scope, deliverable, revision limit, or assumption].
This request changes that baseline because: [explain the difference without blaming the client].
3. Deliverables in this change
- Added or revised deliverable: [specific output, quantity, format, and acceptance criterion]
- Included work: [tasks, meetings, review rounds, testing, or handoff]
- Client inputs: [content, access, feedback, approvals, and due dates]
- Excluded: [adjacent work that is not part of this change]
4. Fee impact
| Work item | Basis | Amount |
|---|---|---|
| [Work item] | [hours × rate or fixed amount] | [currency and amount] |
| [Work item] | [hours × rate or fixed amount] | [currency and amount] |
| Additional fee | [currency and amount] |
- Taxes or third-party costs: [treatment and amount, or state that they are excluded]
- Payment timing: [deposit, milestone, invoice date, and due date]
- Updated project total, if useful: [original total + approved changes]
5. Schedule impact
- Original milestone or delivery date: [date]
- Added time: [number of business days or weeks]
- Revised milestone or delivery date: [date]
- Schedule assumptions: [approval and client inputs received by a stated date]
- Effect on work already underway: [continues, pauses, or must be replaced]
If approval or required inputs arrive after [date], the freelancer will confirm a new delivery date before beginning the changed work.
6. Terms that do not change
Except for the scope, fee, schedule, and payment details stated above, all other terms of [original agreement title and version] remain unchanged. If this request conflicts with the original agreement, [state which document controls or ask for legal review].
7. Client decision
Choose one:
- [ ] Approve this scope change, additional fee, and revised schedule.
- [ ] Request a revision to this proposal; changed work remains pending.
- [ ] Decline this change; the original scope and schedule continue, subject to existing dependencies.
Keep the status as Proposed — not approved until the required decision is recorded. Delete drafting notes, resolve every bracket, and make the “Excluded” line as specific as the added deliverable.
Worked example: adding a booking page to a website project
The names, dates, hours, and prices below are fictional. They show the calculation and schedule logic; they are not recommended freelance rates.
Starting agreement
North Loop Design and Cedar & Clay Studio signed a fixed-fee agreement for a five-page marketing website. The USD 3,600 scope includes one homepage, three service pages, one contact page, responsive layouts, and two consolidated review rounds. The agreed design handoff is November 27, 2026.
After approving the wireframes, the client asks for a sixth page where customers can choose a service and open the client's existing scheduling tool.
Change request CR-003
- Requested change: Add one responsive booking page and embed the client's existing scheduling link.
- Why it changes the scope: The signed list contains five pages and no booking workflow. The new page adds information architecture, responsive design, integration instructions, and testing.
- Included: One booking-page layout for desktop and mobile, embed placement for the existing scheduling tool, one review round, and link testing in the delivered prototype.
- Client inputs: Final service names, scheduling URL, account access needed for testing, and approved booking instructions by November 6.
- Excluded: Custom scheduling software, payment collection, automated email setup, calendar-account support, development of the full website, and more than one review round for the added page.
| Added work | Calculation | Fee |
|---|---|---|
| Page structure and user flow | 4 hours × USD 75 | USD 300 |
| Desktop and mobile design | 5 hours × USD 75 | USD 375 |
| Embed specification and prototype testing | 3 hours × USD 75 | USD 225 |
| Additional fee | 12 hours × USD 75 | USD 900 |
- Payment: USD 450 when the change is approved and USD 450 with the revised design handoff.
- Updated project total: USD 4,500 before any applicable taxes or external costs.
- Schedule: Four business days are added. If approval and all client inputs arrive by November 6, the design handoff moves from November 27 to December 3, 2026.
- Work already underway: The approved five-page wireframes remain valid. Only the new page waits for approval.
- Unchanged terms: The original ownership, confidentiality, cancellation, and general payment terms continue.
This example makes the tradeoff visible. The client can approve USD 900 and four business days, ask to simplify the page, swap another deliverable after the freelancer re-estimates the effect, or decline and keep the five-page project.
A practical approval workflow
The Project Management Institute's scope-management reference connects a change with its cost and schedule impact and recommends authorization before changed work begins. For a small freelance project, that can be a lean six-step process:
- Capture the request. Restate the client's desired outcome in plain language.
- Compare it with the baseline. Point to the exact deliverable, revision limit, assumption, or exclusion that applies.
- Estimate the whole impact. Include the work itself, rework, meetings, dependencies, testing, third-party costs, and delivery effect.
- Offer a decision. Let the client approve, request a revision, decline, or discuss a genuine scope swap.
- Wait for the right approver. A project contact may not have authority to change price or dates.
- Update the working plan. Put the approved amount on the invoice schedule, revise milestones, and store the decision with the original agreement.
The Australian government's contractor guidance on contract variations likewise recommends putting changes in writing and having both parties sign, while emphasizing that the contract's variation clause can govern how changes are made. That guidance is Australian, not a universal legal rule; follow the agreement and law that apply to your project.
How to send the change request for signature
First, settle the wording. A signature does not repair a vague description or an unresolved price. Export the final request as a PDF and give it a filename that connects it to the project, such as cedar-clay-CR-003-booking-page.pdf.
In SignQuick:
- Open New Document, choose Upload PDF, and check the document title.
- Add the client representative who is authorized to approve the change. Choose the language for their signing emails and signing page.
- Review the signature and date fields placed for the first signer. Add fields for any other required signer and confirm that each signer has a signature field.
- Send the request, then keep the completed PDF and audit trail with the original contract, quote, and project records.
The live help center has the exact steps for sending a PDF for signature. If the client asks for another change before signing, revise the source file, increase its version, and send the corrected PDF clearly. Do not silently substitute new terms after approval.
For the starting document, use the free freelance contract template. If the project is still in the quote stage rather than already underway, the service quote template is the better fit. When the change request is ready, create a free SignQuick account to send it for review and signature.
Research and SignQuick's released workflow checked November 2, 2026. This is a general business template, not legal, tax, or accounting advice.
Frequently asked questions
What is a freelance scope change request?
It is a written proposal for changing an agreed project after work has started. It identifies the original scope, the requested addition or replacement, the fee and schedule impact, what remains unchanged, and the decision required before the changed work begins.
When is client feedback a scope change instead of a revision?
Compare the request with the signed agreement, statement of work, and included revision allowance. Correcting work that misses an agreed requirement may be included; adding a deliverable, replacing an approved direction, exceeding revision limits, or changing a dependency may require a scope change.
Should a freelancer start extra work before approval?
Usually, keep the added work pending until the authorized client representative accepts its scope, price, and schedule impact. Continue unaffected original work when practical, unless the requested change makes that work wasteful or the agreement requires a pause.
Does a change request replace the original freelance contract?
Not normally. A focused request should identify the original agreement and state which terms change and which remain in effect. Whether acceptance modifies the contract depends on the agreement, the wording, and applicable law.
Can a scope change request be signed electronically?
You can export the final request as a PDF and send it for electronic signature. Confirm who has authority to approve the change, follow the variation process in the original agreement, and check any legal or industry-specific requirements that apply.
