How to Write a Change Order for Agency Work: A Practical Template and Process

A client asks for “one small addition” to a website, campaign, or brand project. The request sounds manageable, but it changes the workload, affects a review date, or depends on information the team has not received. If the agency simply absorbs it, the project can quietly become less profitable—and the client may not realize anything changed.

A change order makes the adjustment explicit. It records what is changing, what it will cost, and how it affects delivery. The goal is not to make every conversation bureaucratic. It is to give both sides a shared decision before the team commits time.

This guide explains when to use an agency change order template, what to include, and how to get approval without turning a practical conversation into a dispute. It is operational guidance, not legal advice; contract requirements vary by jurisdiction and by the agreement you already have in place.

What is a change order in agency work?

A change order is a written record of an agreed change to an existing project or service agreement. It usually covers a change in scope, fee, timing, assumptions, or some combination of those. You may also call it a scope change, project amendment, or change request. Use the term your contract uses, and make sure the document connects clearly to the original agreement.

A request is not necessarily an approved change. A client can ask for a new landing page; the agency can estimate it; and the client can decide whether to proceed. Until the right client contact approves the revised terms, the team should not treat the additional work as committed—unless the original agreement says otherwise.

Change orders work best alongside a clear initial proposal. If your scope and assumptions are vague, it may be difficult to tell a genuine change from work that was already included. See this guide to what to include in an agency proposal beyond scope, timeline, and price.

When should an agency write one?

Use a change order when a client-requested adjustment meaningfully changes the agreed work, effort, cost, schedule, or risk. Common examples include:

  • Adding deliverables, such as extra pages, ad variations, or a second concept route.
  • Changing an approved direction in a way that requires substantial rework.
  • Adding a new stakeholder review round beyond the agreed process.
  • Changing a technical requirement, integration, platform, or content responsibility.
  • Requesting a faster delivery date that requires reprioritizing work or adding capacity.

Not every small correction needs a formal document. Fixing a typo or clarifying an existing deliverable may be covered by the original scope. Set a sensible threshold: for example, document any request that adds a deliverable, pushes a milestone, or is expected to take more than a defined number of hours. The right threshold depends on project size and how frequently scope shifts.

Internal agency rework is different. If the team made an error against the approved brief, charging the client for correcting it is usually not an appropriate change order. First establish whether the request is new work or a correction to work already promised.

What an agency change order template should include

A useful change order is specific enough to approve without a meeting to interpret it. Keep it short, but include the decision-making details.

1. Identify the original project

Include the client and agency names, project title, original agreement or proposal date, and change order number. This makes the document easy to trace if there are several changes. State that the change order modifies the identified agreement, rather than replacing the whole agreement unintentionally.

2. Describe the requested change

Describe the new or revised work in concrete terms. “Improve the website” is not clear. “Design and build one additional campaign landing page using the approved page template, including one desktop and one mobile layout” gives both sides something they can check.

Also state what is not included. For instance, the extra page might not include new copywriting, photography, translation, or a new integration. Exclusions prevent a narrow approval from being interpreted as an open-ended commitment.

3. State the fee and billing terms

Give the added fee and explain how it was calculated when helpful: fixed fee, estimated hours at agreed rates, or another method. If time and materials are used, state an estimate or not-to-exceed amount, how often you will update the client, and what happens if the work is likely to exceed the limit. A change in billing method may need to be agreed explicitly. This comparison of fixed-fee and time-and-materials pricing can help frame the choice.

Include taxes or expenses if relevant, and say whether the fee is invoiced immediately, at a milestone, or on the next regular invoice. Avoid writing “additional fees may apply” without a number or a clear way to calculate the amount.

4. Explain schedule and dependencies

Show which milestone or delivery date changes. If the original launch date stays in place, explain what needs to happen to protect it—for example, client content must arrive by a stated date, or another deliverable must be deferred. Name any client approvals, access, or materials the new work depends on.

5. Set approval and start conditions

Identify who can approve on the client’s behalf, how they approve, and whether work begins only after written authorization. Include an approval date or expiry for the estimate if capacity or costs may change. If the project agreement specifies an approval method, follow it.

Copy-and-adapt agency change order template

CHANGE ORDER [number]

Client:
Agency:
Project:
Original agreement/proposal and date:
Date of change order:

Requested change:
[Describe the new or revised work and the reason for it.]

Included deliverables:
[List specific outputs, quantities, formats, and review rounds.]

Not included:
[List exclusions, such as copy, assets, additional revisions, or integrations.]

Fee and billing:
[Added fee or rate, estimate/cap if applicable, expenses/taxes, and invoice timing.]

Schedule impact:
[Revised dates or confirmation that dates are unchanged, plus dependencies.]

Assumptions and client responsibilities:
[Required access, content, feedback, or approvals and due dates.]

Approval:
By approving, the parties agree to the change described above. All other terms
of the original agreement remain unchanged unless expressly amended here.

Client approver, title, and date:
Agency representative and date:

Adapt that language to your signed agreement and local requirements. In particular, do not rely on the sentence about other terms remaining unchanged if the change also affects payment rights, ownership, liability, or another contractual term without checking the agreement.

A practical change-order process

  1. Log the request. Record who asked, when, and what outcome they want. A quick request log helps prevent verbal instructions from disappearing into email or chat.
  2. Check the baseline. Compare the request with the signed scope, assumptions, and included revision rounds. For a website, a work breakdown can make it easier to spot whether a new page or functionality was included; see this website project work-breakdown method.
  3. Estimate the impact. Ask the delivery lead for effort, dependencies, and schedule effects before giving the client a price. Consider coordination, quality assurance, and project management—not only production hours.
  4. Offer a clear choice. Present the added work and its cost, or explain a reasonable alternative: replace another deliverable, defer the request to a later phase, or keep the existing scope.
  5. Get approval, then update delivery records. Save the accepted change order with the original agreement. Update the project plan, budget or time allowance, and client-facing status so the team works from the same version.

For government contracts, the Federal Acquisition Regulation emphasizes that only authorized contracting officers can execute contract modifications on behalf of the government. That rule does not govern ordinary private agency engagements, but it illustrates why an agency should verify that an approver has authority rather than relying on any stakeholder’s informal request. See FAR 43.102 on contract modifications.

Common mistakes to avoid

  • Starting first and pricing later. This turns a change into a negotiation over work already delivered. If speed matters, send a short written estimate and get approval before starting.
  • Describing only the fee. A number without deliverables, exclusions, and schedule impact leaves room for different expectations.
  • Ignoring client delays. Added work may not be the only schedule risk. Record how late feedback or missing content affects dates.
  • Using a change order to mask an unclear scope. If the same category of request keeps recurring, clarify the base scope or revise how future work is priced.
  • Letting the document conflict with the master agreement. Check that payment terms, approval procedures, and any change-control clause are consistent.

If you use electronic signatures, U.S. federal law generally provides that a signature or contract may not be denied legal effect solely because it is electronic, subject to the law’s conditions and exceptions. That does not mean every click or email is automatically sufficient in every situation; use an approval method that fits your agreement and applicable law. See the U.S. E-SIGN Act, 15 U.S.C. § 7001.

FAQ

Is a change order legally binding?

It can form part of a binding agreement, but the result depends on the original contract, the approval process, and applicable law. Make sure the document is accepted by authorized representatives and does not conflict with existing terms.

Can a change order be approved by email?

Often, an email can document approval, but check the signed agreement for required procedures. Make the approval unambiguous: identify the change order, price, and schedule, and have an authorized client contact confirm acceptance.

Should agencies charge for estimating a change?

For a small, straightforward request, a brief estimate may be part of normal client service. For a complex change requiring discovery, technical investigation, or design exploration, explain whether that assessment is paid work before doing it.

What if the client refuses to sign?

Do not proceed with the added work on the assumption that approval will come later. Continue the original scope if it remains practical, or pause the affected work and discuss a replacement, deferral, or revised schedule.

How detailed should the template be?

Detailed enough to define the work, price, timing, assumptions, and approval. A small adjustment may need only a one-page record; a change involving technical risk, several deliverables, or multiple dependencies deserves more detail.

Similar Posts