You write it after the work has started
Once the client thinks the change is underway, approval becomes awkward.
Change order template
A change order template is useful. A change order workflow is safer.
A good template gives you the right fields. EasyScope helps you fill them from the real project: the original scope, the client request, the effort estimate, the timeline impact, and the approval record.
Template fields
request + price + approval
The essentials are simple. The hard part is keeping them connected.
Change order sections
Live project1
Requested change2
Not included in original scope3
Cost and timeline impact4
Client authorizationDocument anatomy
The fields matter. The timing matters more.
1
Requested change
2
Not included in original scope
3
Cost and timeline impact
4
Client authorization
Why it matters
Why static templates break down
Most freelancers do not struggle because they lack a document. They struggle because the document is disconnected from the moment the client asks for the change.
Numbers are copied manually
Budget, rate, effort, VAT, and timeline data can drift between the project and the document.
Approval is not tied to delivery
A signed PDF is useful, but the team still needs to know what became approved work.
The EasyScope way
What every freelance change order should include
Use this structure as a practical checklist, whether you start with a document or generate it from EasyScope.
01
Describe the requested change
State what the client asked for, what deliverable it affects, and why it is outside the agreed scope.
02
Show effort, price, and delay
Add estimated hours or days, price, VAT or tax handling where relevant, and delivery impact.
03
Capture explicit authorization
Include client approval, signature or acceptance, date, and any payment or invoicing terms.
Proof points
Template plus workflow
EasyScope takes the template idea and attaches it to the project data that makes it defensible.
Original scope
Compare new work against approved deliverables.
Impact simulator
Calculate cost and timeline before sending.
Document generator
Create change-order drafts from approved context.
Client portal
Send the change for review, approval, or signature.
No awkward surprises
Template questions
Can I copy this structure into my own document?
Yes. The sections above are a useful baseline. EasyScope exists for when you want the structure connected to live project data.
Should a change order mention the original contract?
Usually yes. It should clearly say that the new work amends or extends the previously agreed scope.
Should I include timeline impact?
Yes. Extra work often changes delivery dates. Showing that impact prevents a client from approving budget while expecting the old deadline.
Do not let your template sit outside the project.
Use EasyScope to turn extra requests into priced, approved, invoice-ready changes.
Build a change order