Change Order Template: Charge for Scope Changes

Executive Summary

A change order template is a short, reusable document that records a change to an already-agreed project: what is changing, why, how it shifts the timeline and the cost, and the revised total both sides sign. Most search results for the term are built for construction sites, but the same instrument is what protects consultants, designers, and developers from unpaid scope changes.

For knowledge work, the change order is the mechanism that turns an offhand “can you just add one more thing” into documented, billable work. This guide covers what a change order is, when to issue one instead of absorbing the request, the seven fields every change order must capture, a fill-in template to copy, and a worked example. It closes on the part that worries people most: how to charge for a scope change without losing the client.

What is a change order template?

A change order template is a pre-built form that documents an agreed change to a project’s scope, timeline, or price after the original contract is signed. It captures the change in writing, ties it to a cost and a schedule impact, and gets both parties to approve the new total before the extra work starts.

The term has a construction problem. Nearly every top result treats a change order as a contractor document for materials and labor on a build site. The underlying tool is identical for professional services, where the “extra work” is another design round, a new integration, or a fresh analysis the client asked for after kickoff.

A change order sits downstream of the original agreement. The proposal sells the work, the scope of work or statement of work defines it, and the change order amends it when reality moves. For the upstream documents, the FlowEdge guides on scope of work and the SOW template cover how to set the baseline a change order later references.

When should a change order be issued instead of absorbed?

A change order should be issued whenever a request falls outside the signed scope and costs meaningful time or money. The rough line: if honoring the request adds more than an hour or two, or pushes a deadline, it warrants a change order rather than a quiet absorption.

Absorbing small favors can be a deliberate relationship choice. A five-minute tweak handled for free buys goodwill. The danger is that unbilled favors compound. One added page becomes a redesign, and the original fixed fee slowly stops covering the real work.

The data shows how common this drift is. Scope creep, the uncontrolled expansion of work beyond the agreement, affected 52 percent of projects in PMI’s 2018 research, up from 43 percent five years earlier. Organizations with mature delivery practices held it to 28 percent. The difference is rarely talent. It is a documented change process that everyone agreed to in advance.

What should a change order template include?

A change order template should include seven fields: a reference to the original agreement, a description of the change, the reason for it, the impact on the timeline, the impact on cost, the revised contract total, and a sign-off block. Drop any of these and the document loses the precision that makes it billable.

Here is what each field does and why it matters:

• Original agreement reference: The contract or SOW name, date, and the specific clause being amended. This anchors the change to the signed baseline so there is no argument about what was already covered.
• Description of the change: A plain-language summary of the new or modified work. Specific enough that a third party could tell what is being added.
• Reason for the change: Who requested it and why. A new requirement, a client decision, or a discovery made during the work. This keeps the record neutral rather than accusatory.
• Impact on timeline: The revised dates or added days. Many scope changes cost schedule even when the fee barely moves.
• Impact on cost: The added fee, broken into hours or a fixed amount. Showing the math reduces pushback.
• Revised contract total: Original value, plus this change, plus any prior change orders, equals the new total. One running number both sides track.
• Sign-off: Dated signature lines for both parties. The extra work should not begin until both names are on the form.

These fields map directly to why projects derail. PMI research found that changing priorities, shifting objectives, and inaccurate requirements rank among the top causes of project failure, each one a scope change that went unmanaged.

A fill-in change order template to copy

The structure below works as a simple change order template for most professional engagements. Replace the bracketed prompts with project-specific detail and number each change order in sequence so the running total stays clear.

Rebuilding this form on every request is where billable hours quietly disappear. FlowEdge was founded after its own founder spent three to four hours per document on proposals, SOWs, and contracts. A reusable structure removes most of that, and an AI document generator can re-scope a project from a few plain-language inputs instead of manual editing.

What does a change order example look like?

A change order example pairs each field with specific commitments instead of bracketed prompts. The condensed sample below covers a website project where the client added a feature after the build started.

The example shows why a separate document beats an email thread. The Spanish-language site was never in the original scope, so without a change order the developer either eats two weeks of unpaid work or starts an awkward argument mid-project. The form makes the addition routine instead of personal.

How do you charge for scope changes without losing the client?

The way to charge for a scope change without losing the client is to make the change order feel like good service rather than a penalty. Frame it as protecting the agreed scope, budget, and deadline that the client signed up for, not as a fee grab.

Three habits make that framing land. First, mention the change process at signing, so the first change order is never a surprise. Second, present the request neutrally, in writing, with the cost math shown. Third, give the client a clear choice: approve the addition, defer it to a later phase, or trade it for something already in scope.

This works because clients rarely object to paying for value. They object to feeling ambushed. Most professional projects involve change, so handling it cleanly is a sign of competence. PMI’s research on what derails projects shows how often the trigger is a scope or objective shift rather than poor execution.

Pricing the change is simpler than it feels. For hourly work, the math is the hours times the rate. For fixed-fee work, the cleanest approach is to estimate the added hours, apply the same effective rate as the original engagement, and round to a flat amount. A consistent method signals fairness more than any single number does.

Speed matters as much as price. A change order sent within a day of the request keeps momentum and looks professional. The same logic that wins proposals applies here: a fast, clear document is a trust signal. For the engagement-level document this amends, the SOW guide covers the baseline that makes change pricing defensible.

Try FlowEdge Free

What is the difference between a change order form and a change request?

A change request asks for a change, while a change order authorizes and prices it. The request is the conversation starter, and the change order is the signed document that makes the new scope and fee binding. Many teams use a change order form to capture both steps on one page.

The naming varies by context. A change order form template and a project change order template describe the same instrument with different labels. A change order request template usually refers to the intake step, where the client or team member writes down what they want before anyone prices it.

For most solo consultants and small agencies, one combined form is enough. It records the request, the impact, and the approval in a single place. Larger or regulated engagements sometimes split the request and the order into two documents, but the seven fields above still carry the weight in either format. A change order template in Word or a shared doc both work, as long as the running total and the sign-off survive every revision.

Frequently Asked Questions

What is a change order?

A change order is a written, signed document that amends an existing contract to account for work outside the original scope. It records what is changing, the effect on the timeline and cost, and the revised total. Once both parties sign, the new scope and fee become binding, which is what separates it from an informal email request.

How do you write a change order?

Start from a template with the seven core fields: original agreement reference, description of the change, reason, timeline impact, cost impact, revised total, and sign-off. Fill each field with specific detail, number the change order in sequence, and send it for signature before the extra work begins. Showing the cost math reduces back-and-forth.

What is the difference between a change order and a change request?

A change request is the ask, and a change order is the authorization. The request describes a desired change, while the change order prices it, sets the new timeline, and becomes binding once signed. Smaller teams often combine both into a single change order form rather than tracking two separate documents.

Who prepares a change order?

For professional services, the service provider usually prepares the change order because they can estimate the time and cost of the added work. The client then reviews and signs to approve it. In larger projects, a project manager or contract owner may draft it, but both parties must sign before the work proceeds.

Should a change order be signed?

Yes. The signature is what makes the revised scope and fee enforceable, the same way it does on the original contract. Starting the extra work before both parties sign is the most common way a change order fails to get paid. For high-value or complex changes, a brief legal review before signing is a sensible precaution.

Can a change order be used for any project type?

Yes. While most change order templates are written for construction, the same structure works for consulting, design, software, and agency projects. The fields stay the same: reference the original agreement, describe the change, show the timeline and cost impact, and capture sign-off. Only the description of the work differs by field.