The project is three weeks in. Your client sends a casual message: "Can we also add X?" You say yes — because it seems small, and you want to keep the relationship smooth. Then they ask for Y. Then Z. By the time the project closes, you've delivered 20 hours of extra work and billed for none of it.
This is scope creep, and it costs freelancers and consultants between $7,800 and $15,600 per year on average. Research suggests only 1% of agencies successfully bill for all out-of-scope work they deliver. Knowing how to write a change order is the professional skill that closes that gap.
A change order is a written document that records every scope change — what is being added, how much it costs, and how it shifts the delivery timeline. Both parties sign it before any new work begins. No signature, no work. It is that simple — and that effective.
This guide covers the six sections every change order needs, how to introduce the process without awkward conversations, and how to make your document look polished enough that clients take it seriously.
What Is a Change Order?
A change order is a formal amendment to an existing project contract. It describes a specific modification to the original agreed scope — whether that means adding deliverables, revising requirements, reducing scope, or changing specifications — and documents the updated cost and timeline that reflects the modification.
Change orders apply to any professional services context: web development, design, consulting, marketing, content creation, construction, or managed IT. If you have a signed contract and your client asks for something outside it, a change order is the right response.
The foundational rule: no change takes effect until both parties have signed the document. Verbal agreements, Slack messages, and emails with "sounds good!" are not change orders. A signed document with a clear description, a cost figure, and a timeline adjustment is a change order.
When to Write a Change Order
Any client request that changes what was originally agreed triggers a change order. Common scenarios:
Additional deliverables. The client wants a fifth landing page when the contract specified four. The scope changed. Write a change order.
Revised specifications. The client approved a logo brief and now wants a different direction requiring a full redesign. Write a change order.
Expanded output. The original contract specified five blog posts per month. The client asks for eight. Write a change order.
New stakeholders with new opinions. A new decision-maker joins mid-project and requests revisions that fall outside the agreed revision rounds. Write a change order.
Technology or format changes. The client switches from one platform to another mid-project, requiring rework. Write a change order.
The guiding principle: if it costs you time, it costs the client money. A change order makes that relationship explicit and documented.
The 6 Sections Every Change Order Needs
A solid change order has six components. Each one serves a specific purpose.
1. Project reference information
Open with the project name, the date of the original contract, the change order number (CO-001, CO-002, etc.), and the date the change order is issued. Sequential numbering keeps your paper trail clean across multi-change projects and makes it easy to reference specific amendments in future communications.
2. Party information
Name the client and the service provider. Include company names, contact names, and email addresses. When a project has multiple stakeholders, specify who has the authority to approve changes — limiting this to one named person per side prevents conflicting requests from different contacts.
3. Description of the change
This is the core of the document. Be specific. "Add a fifth page to the website with a contact form, FAQ section (up to 10 questions), and a custom map embed" is a change order description. "Add some extra pages" is an agreement waiting to be disputed.
Break down what is being added, what is being removed if scope is shrinking, and what stays the same. If the change affects named deliverables or milestones from the original contract, reference them by name. Specificity protects both sides.
4. Cost adjustment
State the additional fee clearly, broken into line items if the change has multiple components:
- Additional page design: $600
- FAQ section content: $300
- Map integration: $150
- Total added cost: $1,050
Include the new project total after the adjustment. If the change reduces scope and lowers the price, document the reduction with equal precision.
5. Timeline adjustment
Scope additions take time. If the original completion date was May 20 and the added work pushes delivery to June 1, state the new date. Clients often underestimate how additional work cascades into existing deliverables. A change order makes the timeline impact visible before work begins — and gives the client the opportunity to decide whether the change is worth the wait.
6. Approval signatures
Both parties sign and date. If your client is an organization, get the signature from the decision-maker who authorized the change — not whoever is managing day-to-day communications. A change order signed by the right person holds; one signed by the wrong person creates ambiguity.
How to Introduce the Change Order Process Without Conflict
The hardest part of writing a change order is often initiating it. Many professionals absorb the extra work rather than have the conversation. That avoidance has a direct cost.
The most effective strategy: establish the process before the project starts. A single sentence in your original contract does the work: "Any additions to the agreed scope require a signed change order before work begins." When the client signs the original contract, they agree to this process. The change order conversation never arrives out of nowhere.
When a scope request arrives, respond with this framing:
"Happy to add that. I'll put together a change order covering the cost and timeline impact, and we can move forward once we both sign it."
This positions the change order as a neutral administrative step, not a confrontation. You are agreeing to the client's request — with the appropriate documentation attached.
If a client pushes back, the clearest response: "This falls outside the original scope, so a change order lets us update the agreement. It keeps everything documented so we are both protected." Clients who take their business seriously understand this reasoning. Clients who resist having scope changes documented are giving you useful information about how the rest of the project will go.
Change Order Best Practices for Freelancers and Consultants
Send before starting. The moment you begin work without a signed change order, you lose your leverage. Deliver first, bill later — and clients can dispute after the fact. Send the document, wait for the signature, then start.
Keep the language factual. A change order describes a business transaction. Write it like one. "Additional deliverable: 3 product pages — $750" is cleaner than apologies or qualifications. Specificity reads as professionalism.
Price the actual work. If the change adds two days of work, price it as two days. Scope additions compound — a "small" request often has downstream effects on other deliverables. Price what you see, plus a reasonable buffer for what you cannot see yet.
Store every signed copy. Keep signed change orders alongside the original contract. A complete document trail of what was agreed and when is your primary protection if a project goes sideways.
Number sequentially. CO-001, CO-002, CO-003. When you reference a change order in an email — "as per CO-002" — both parties know exactly which amendment you mean.
What Happens When You Skip the Change Order
The consequences arrive in two forms.
Financial: every hour of out-of-scope work you deliver without a signed document is an hour absorbed into your original fee. The project overruns your time and budget. The client pays the original price regardless of how far the scope expanded.
Relational: without documentation, disputes become your word against the client's. A client who genuinely misremembers what was agreed will believe you underdelivered. A client acting in bad faith has nothing in writing to contradict. Either way, you carry the cost.
A signed change order removes both risks. It records what was agreed, makes the additional cost visible before work begins, and gives the client a clear decision point — proceed with the change at the documented price, or maintain the original scope.
How to Make Your Change Order Look Professional
Content protects you legally. Presentation determines how clients receive the document.
A change order pasted into an email thread reads as an afterthought. A change order that arrives as a formatted document — with your branding, clear section headers, and a clean signature block — reads as a professional business amendment. Clients respond to it differently.
The fastest way to produce a polished change order: draft your content, paste it into DocsAura, and let the AI design it. In under two minutes, your rough text becomes a formatted, branded document ready to send. You spend your time on the business decision — the presentation handles itself.
Every professional services relationship involves scope questions. The difference between the ones that end well and the ones that drain you is documentation. A change order is a short document. Write it before starting the work, get both signatures, and store the result.
That one habit is worth thousands of dollars per year — and takes less than an hour to establish.
Turn voice notes and screenshots into beautiful documents.
Status updates, proposals, case studies, SOPs — generated in minutes, not hours.
Try DocsAura Free