Web Design Change Orders: Billing Scope Creep Without Losing Clients

On this page 8 sections

1. How Scope Creep Quietly Kills Agency Margins
2. Writing a Scope Clause That Defines a "Change"
3. What Every Web Design Change Order Should Include
4. Pay Before Work, Add to the Next Milestone, or Bill Hourly?
5. Collecting Change Order Payments by Card or ACH
6. Using Change Order Records as Chargeback Evidence
7. Scripts for Telling Clients a Request Is Out of Scope
8. Next Steps

Key takeaways

• Define what counts as a "change" in your original contract so out-of-scope requests trigger a process, not an argument.
• Never start extra work without a signed change order and either payment, a deposit or a documented addition to the next milestone.
• Use secure payment links, a virtual terminal or ACH to collect change order fees instead of handling card numbers over email.
• A clean paper trail of signed approvals, dated deliverables and matching invoices is your best defense if a client later disputes the charges.

Most web projects don't blow up in one dramatic request. They drift, one "quick tweak" at a time, until the hours you've worked far exceed what the client paid for. A web design change order turns that drift into a documented, billable event. This guide explains how to define a change in your contract, what a change order form should include, how and when to collect payment, and how to keep records that hold up if a client disputes the charge later. It also includes scripts for saying "that's out of scope" without damaging the relationship.

How Scope Creep Quietly Kills Agency Margins

Scope creep in web design rarely looks like a new project. It looks like this:

• "Can we add a blog? It's just one more page."
• A third and fourth round of homepage revisions after the client approved the mockup in Figma.
• A booking plugin, a membership area or a CRM integration requested after the build is already on staging.
• Content that arrives late and in pieces, forcing you to rebuild layouts you already finished.
• A launch date that slips because of client delays, while your team keeps the project open.

Each request seems too small to fight over. Together they can wipe out the profit on a fixed-fee project. The bigger problem is cash flow. If you do the extra work first and invoice at the end, you're extending unsecured credit to a client who may already be stretching your patience.

The fix is a process that puts payment and approval before the work, not after. That process starts in your original contract.

Writing a Scope Clause That Defines a "Change"

You can't bill for out-of-scope work if the scope was never clearly written down. Your proposal or statement of work should list deliverables specifically enough that both sides can tell when a request falls outside them.

What Counts as a Change

Spell out the categories that trigger a change order. Common ones include:

• New page templates or sections beyond the agreed sitemap
• New functionality, such as ecommerce, booking, memberships, multilingual support or third-party integrations
• Revisions beyond the included rounds at any phase
• Changes to approved work, such as redesigning a page after the client signed off on the mockup
• Rework caused by late or changed content from the client
• Timeline extensions that the client requested or caused

What Doesn't Count

Be equally clear about what you'll fix at no charge. That usually includes bugs in your own code, items already listed in the scope, and corrections needed to meet the approved design. Clients are more willing to accept change fees when they can see you're not nickel-and-diming them for your own mistakes.

Charging for Extra Revisions

Revision limits only work if you define a "round." One practical definition is a single consolidated set of feedback delivered together, rather than a stream of emails over several days. State how many rounds each phase includes (discovery, wireframes, design, development) and what each extra round costs, either as a flat fee or at your hourly rate.

Add a phase-approval clause too. Once a client approves wireframes or a design, changes to that phase become change orders. That one sentence prevents most "let's rethink the homepage" requests during development.

For the payment side of your contract, pair this clause with clear web design deposit and milestone payment terms so change orders slot into a structure the client has already agreed to.

What Every Web Design Change Order Should Include

A change request form for web design work doesn't need to be long. It does need to be specific enough that a third party, such as a card issuer reviewing a dispute, could read it and understand exactly what the client asked for and agreed to pay.

Include these fields:

1. Change order number and a reference to the original contract or proposal
2. Date of the request and date of approval
3. Description of the change in plain language, such as "Add a three-page blog section with category filtering," not "blog stuff"
4. Reason for the change, for example a client request, late content or a new feature
5. Cost, whether as a flat fee, an hourly estimate with a cap, or a not-to-exceed amount
6. Payment terms, including when payment is due, how much is required upfront and the accepted payment methods
7. Timeline impact, meaning how many days the change adds to launch
8. Effect on other deliverables, if anything else shifts or gets removed
9. Client signature or electronic approval, with name, title and timestamp
10. Statement that work begins after approval and payment (or deposit) is received

Many agencies build this into their project management or e-signature tool so the client can approve and pay in one step. If you're choosing a platform, compare options in our guide to invoicing software for web design agencies.

Pay Before Work, Add to the Next Milestone, or Bill Hourly?

There are three common ways to handle scope creep in web design billing. Each fits a different kind of request.

Illustrative example: A client on a fixed-fee site build asks for a new online booking feature mid-project. You quote it as a flat fee, collect half when the change order is signed, and add the other half to the launch milestone invoice with the change order number listed on the line item. If the client later questions the launch invoice, the signed change order and the deposit receipt show they approved the cost in advance.

Whichever approach you choose, follow one rule: no signature, no work. Verbal approvals on a call are easy to forget and hard to prove.

Collecting Change Order Payments by Card or ACH

Change orders are usually remote, card-not-present transactions. How you collect payment affects your costs, your security and your evidence if there's a dispute.

Secure Payment Links and Hosted Invoices

The cleanest option is an invoice or payment link the client pays online. The client enters their own card details, so you never handle the number. The payment record also ties directly to the invoice and change order. A payment gateway can support address and security-code checks, which help confirm that the person paying is the cardholder.

Keyed Payments Through a Virtual Terminal

Some clients want to read a card number over the phone. A virtual terminal for keyed card payments lets you enter it securely in a browser instead of writing it down. Keyed transactions often cost more than other payment types and carry more fraud risk, so use them as the exception. Never ask clients to email card numbers, and never store card details in your project files. Our article on PCI responsibilities for web developers covers why.

Card on File for Ongoing Changes

For clients who request frequent small changes, a stored card can speed things up. Get written permission explaining when and how you'll charge the card, and send a receipt for each charge that references the change order.

ACH Bank Payments

For larger change orders, ACH payments typically cost less than cards. You'll need the client's authorization to debit their account, and you should keep that authorization on file. Confirm current authorization requirements with your processor.

Passing on Card Fees

Some agencies offset card costs on large change orders through surcharging or dual pricing. Rules vary by state and card brand, and they come with disclosure requirements, so read our guide to passing card fees to clients on large invoices and confirm current requirements before you add a fee.

MannyPay offers payment processing for web design agencies, including virtual terminals, online gateways such as Authorize.net and NMI, and a QuickBooks integration for agencies that reconcile invoices there.

Using Change Order Records as Chargeback Evidence

Disputes over out-of-scope web design charges usually come after launch. The client remembers the original price, sees a larger total and calls their card issuer. If that happens, your response depends almost entirely on what you documented at the time.

Build an evidence file for every change order:

• The signed change order, including the e-signature audit trail (timestamp, email address and, if your tool records it, IP address)
• The original contract showing the scope clause and revision limits
• Email or project-tool threads where the client requested the change
• Proof of delivery, such as dated screenshots, staging URLs, version history or commit logs showing the work was completed
• The invoice and receipt, with the change order number on the line item
• Any client approval of the finished work, including "looks great" messages

Response deadlines for disputes are strict and vary by card brand and processor, so check your processor's timelines and keep these files organized enough to pull together quickly. For a full walkthrough, see our guide to winning web design chargebacks after a site launches.

Good records also matter beyond individual disputes. Agencies with frequent chargebacks can draw extra scrutiny from processors, a risk explained in why processors flag web design agencies.

Scripts for Telling Clients a Request Is Out of Scope

How you say it matters as much as what you charge. Aim to be friendly, quick and specific, and always offer a path forward.

When a client asks for a new feature:

"Love this idea. A booking system wasn't part of our original scope, so I'll put together a short change order with the cost and how it affects the launch date. Once you approve it and the deposit comes through, we'll get started."

When revisions go past the included rounds:

"We've used both included design rounds for the homepage. I'm happy to keep refining it. Additional rounds are billed at the rate in our agreement, and I can send a change order for one more round now."

When late content forces rework:

"Since the new copy changes the page structure we built, we'll need to rework two layouts. I'll send a change order covering the extra time so we can keep the project moving."

When a client pushes back on the cost:

"I understand. If budget is tight, we could launch with the current scope and schedule this as a phase two after launch. That keeps your launch date and spreads out the cost."

Offering a phase two is often the move that saves both the margin and the relationship.

Next Steps

Start with three changes to how you work:

1. Update your contract template with a clear definition of a change, revision limits and a phase-approval clause.
2. Create a one-page change order form that requires a signature and payment terms before work begins.
3. Set up payment links, a virtual terminal and ACH so clients can pay change orders quickly without sharing card numbers by email.

This article is general information, not legal or tax advice. Have a qualified attorney review your contract language, and confirm current card brand and state rules on fees with your processor.

If you want to review how your agency collects project and change order payments, request a free processing quote. A MannyPay specialist will respond within one business day.

ME

About the author

MannyPay Editorial Team

Beyond the Swipe's editorial desk researches the publication's guides and news and cites its sources in every article. Articles reviewed by a named MannyPay editor carry that editor's byline.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.