Scope of work
baseline
Defines deliverables, limits, milestones, and acceptance before work starts.
Scope document guide7 min readReviewed 2026-04-30
Use a scope of work to define the deal. Use a change order when the deal changes.
Freelancers often mix up the two documents. A scope of work sets the baseline before delivery starts. A change order protects the project after the client asks for something that changes that baseline.
Change order
delta
Documents an approved change after the original scope is agreed.
EasyScope role
connect both
Keep original scope, requests, approvals, and invoices in one flow.
1
What a scope of work should do
A scope of work should make the initial project clear enough that both sides know what is included and what is excluded.
Define deliverables and milestones in concrete terms.
State revision limits, approval moments, and client responsibilities.
List exclusions that commonly create confusion.
Connect the scope to price, timeline, and acceptance criteria.
2
What a change order should do
A change order should record a client-approved adjustment to the original agreement. It is not a replacement for the original scope; it is an update to it.
Reference the original scope or deliverable.
Describe the requested change and why it matters.
Show added cost, delay, and delivery impact.
Capture approval before the extra work starts.
3
When to update the SOW instead
If a project has not started yet, or the overall plan is being renegotiated, updating the scope of work may be cleaner than adding a change order.
Use a revised SOW before signature or kickoff.
Use a change order after the baseline has been accepted.
Use a new proposal when the request becomes a separate phase.
Keep the client decision explicit in every case.
SOW vs change order decision checklist
Has the original scope already been accepted?
Does the request change deliverables, timeline, or price?
Is this a small clarification or a material change?
Should another deliverable be swapped out instead?
Does the client need to approve before work starts?
Will the decision affect the invoice later?
Frequently asked questions
Can a scope of work include change order rules?
Yes. A strong scope of work should explain how out-of-scope requests are handled, priced, and approved.
Can a change order be informal?
It can be lightweight, but it should still capture the request, impact, and client approval clearly.
Which document matters more?
The scope of work matters most at the start. Change orders matter most once the project begins changing.
EasyScope