Skip to main content
Hybrid App Logo

Scope Change Order Template

A free change-order structure for freelancers to document new scope, pricing, approvals, and timeline impact before extra work starts.

Starter Resource

Starter text template

Plain-text scope change starter. Copy the plain-text starter now, then replace the fields below and review it before using it.

Save drafts in workspace
Open change order generator

Fields to customize

Original scope
Requested change
Timeline impact
Price impact
Approval deadline

SCOPE CHANGE ORDER STARTER

Project: [Project name]
Client: [Client name]
Original agreement: [Name of the agreement or proposal this changes]
Original approval date: [Date]
Change order date: [Date]

1. Original Scope
The approved scope included:
- [Original deliverable 1]
- [Original deliverable 2]
- [Original deliverable 3]

2. Requested Change
The client requested:
[Describe the new work, revision, timing change, or added responsibility.]

3. Added Deliverables
This change adds:
- [Added deliverable 1]
- [Added deliverable 2]

4. Timeline Impact
Original milestone or delivery date: [Date]
Updated milestone or delivery date: [Date or no change]
Dependencies: [Client input, approval, access, vendor, or payment dependency]

5. Price Impact
Added fee: [Amount]
Payment timing: [Due before work starts / milestone / next invoice]
Invoice or payment link: [Link, if ready]

6. Assumptions and Exclusions
- [Assumption]
- [Assumption]
- This change does not include [excluded item] unless approved separately.
- All other terms of the agreement or proposal named above stay the same.

7. Approval
To approve this change, reply with written approval by [date] and complete [payment step, if required]. Extra work begins after approval and required payment or materials are received.

Approved by client: ________________________ Date: __________
Approved by freelancer: ____________________ Date: __________

Change-order outline

Use this when a client asks for work that was not included in the original agreement. The goal is to protect the relationship while making the business impact explicit.

  • Original scope: what was approved before this change

  • Requested change: what the client is asking to add or alter

  • Impact: added effort, schedule movement, dependency changes, and risks

  • Approval: price, payment timing, and written authorization before work begins

Starter wording

This change order adds [new work] to the approved scope for [project name]. The added work requires [hours/days] and changes the project total by [amount]. Work begins after written approval and any required payment step.

  • Added deliverables: [deliverable 1], [deliverable 2]

  • Timeline impact: [new date or no change]

  • Client approval needed by: [date]

Use it inside Hybrid

Run the change through the change-order generator when you want the scope language, pricing logic, and invoice handoff to stay connected.

  • Estimate the cost of the extra work

  • Generate client-ready change-order copy

  • Create or update the invoice after approval

Key Takeaways

  • Extra scope should be approved before delivery starts

  • A change order should name price, timeline, and approval deadline

  • Clear change-order habits protect margin and reduce client confusion