Change order template

Use this the moment a client asks for something outside the agreed scope. Get it signed before you start the extra work. A change order in writing is how “one small tweak” stops turning into free labor.

CHANGE ORDER

Project: [NAME] Original agreement / SOW dated: [DATE] Change order number: [001] Date: [DATE] Between [CLIENT NAME] (“Client”) and [YOUR NAME / BUSINESS NAME] (“Provider”).

1. Requested change. [DESCRIBE WHAT THE CLIENT ASKED FOR — in plain, specific terms. “Add an online store with 20 products”, not “more stuff”.]

2. Reason. [WHY THE CHANGE — new requirement, changed direction, added deliverable. Optional but useful for the record.]

3. Impact on scope. [WHAT THIS ADDS OR REMOVES from the original deliverables.]

4. Impact on timeline. Original delivery date: [DATE] Revised delivery date: [DATE] [NOTE ANY KNOCK-ON EFFECTS on other milestones.]

5. Impact on price. Additional cost: [$AMOUNT] ([fixed / at your hourly rate of $X for an estimated Y hours]). Payment terms for this change: [e.g. billed on the next invoice / due before work begins]. Revised project total: [$AMOUNT]

6. Terms. All other terms of the original agreement remain in effect. Work on this change begins only after both parties sign below.

Signed:

Client: ______________________ Date: __________

Provider: ______________________ Date: __________

---

How to use this change order

A change order is the cheapest conflict-prevention tool there is: it turns “can you just also…” into a priced, dated, signed decision. Use one every time scope moves, even when the change is small and even when you are not charging for it — an unbilled change recorded in writing still resets expectations.

Generate one with the change order generator, and if you are finding this hard to raise with a client, scope creep scripts has the wording. It amends the contract rather than replacing it.

This template is a starting point, not legal advice.