Opens in a new tab
  • Services
  • Who We Help
  • Resources
  • AboutStart a Conversation

    Article

    Scope Creep in Service Contracts: Managing Changes Before They Become Billing Disputes

    An extra feature can hold up payment for an entire project if the customer expects it before accepting the work. The statement of work should tell the team which requests it can approve and when it needs to agree on a new price.

    By Dan Liutikas · October 6, 2026 · 5 min read

    Updated November 20, 2026

    Article sections

    A customer asks the project manager to add one more integration before launch. The manager agrees, expecting to bill for it. The customer assumes the original price covered everything needed to get the system running. By the time the invoice arrives, the team has done the work and neither side remembers discussing a fee.

    Three ways scope grows

    A new request
    Another integration, an added location, a revised reportThe provider priced the original integration. The customer expected a working system at every location.
    A changed assumption
    Data needs more cleanup than expected, or a third-party system behaves differentlyThe provider needs more hours to deliver what it already promised.
    An informal accommodation
    The team keeps working on extra tasks to stay helpfulThe customer assumes the team would have asked first if it planned to charge extra.

    These disagreements often start well before the request. A proposal may promise an outcome, while the statement of work (SOW) prices specific tasks. Sales and delivery conversations can give the customer a third understanding. To assess a disputed charge, counsel needs to see what the parties signed, what they later said and did, and how governing law treats the differences.

    Changed assumptions

    A data migration project can grow even when the customer asks for exactly what the provider agreed to deliver.

    The assumptionUsable records from one source system

    What arrivedInconsistent records from several systems

    What the team didReconciled the records to keep the launch on schedule

    The customer still received one migration. The provider spent additional time reconciling the source records.

    Extra hours alone do not establish a right to charge more. Did the SOW specify that the customer would supply usable records from one system? Did either side agree who would pay for cleanup if that assumption proved wrong?

    Informal approvals

    A project lead may take a customer’s request as approval to start and expect to settle the price later. The customer may assume the lead would have quoted a price before starting any billable work.

    A time entry shows that someone did the work. Whether the customer authorized the charge depends on the change provisions, who could approve it, what the parties said and did, and governing law. Delivery staff need to know when they can say yes and when to bring in the person responsible for price.

    Changes that affect more than price

    A firm hired to recommend a system may later be asked to configure and maintain it. That change may require access to customer data, a subcontractor, or a commitment to keep the system running.

    Revisit ownership, security, liability, and exit terms when the work changes. A higher fee for configuration will do little to cover an ongoing support obligation nobody has priced.

    Scope disputes and acceptance

    If a customer refuses to accept completed work because a feature is missing, both the original invoice and the price of the extra feature may be in dispute. While the parties argue, the provider keeps staff on the job and the customer may miss its launch. Check the agreed scope, acceptance criteria, and what each side had to supply. Our article on MSAs and SOWs explains how the two documents work together.

    Setting up a change process

    Project leads rarely need a signed change order to rearrange the week’s tasks. Adding a deliverable or moving a launch date is a different decision. One way to give the team room to act is to distinguish between two kinds of changes.

    Routine adjustment Material change
    Examples Reordering tasks, minor revisions within the existing effort New deliverables, added resources, deadline changes, new obligations
    Approval Project leads, confirmed by email Written change order signed by authorized representatives
    Record Noted in the regular status report Updated scope, price, schedule, and affected terms

    Set the dividing line where a decision starts to affect fees, staffing, deadlines, or a promise to the customer.

    When the same dispute keeps recurring

    If several customers expect the same work at no extra charge, look at the proposal, sales conversations, and what the delivery team usually does. The company may want to include that work in its price, sell it separately, or explain the exclusion earlier. Then make sure the SOW matches what customers hear.

    Responding to a current dispute

    Before demanding payment or stopping work, gather the SOW, the pricing assumptions, the change provisions, and the emails or messages about the request. Those records help establish what the customer approved and what the provider still owes.

    For more on drafting the underlying agreement, see The Provider’s Guide to Master Services Agreements.

    Talk with us about scope and change terms

    If a customer disputes a change or your team keeps doing work it expected to bill, we can review the agreement and correspondence, advise you on the invoice, and help your team decide who can approve future changes.

    Dan Liutikas is the founder and principal of Org Law, outside general counsel to executive teams and boards. He has more than 25 years of experience advising technology and service providers, franchisors, associations, and professional services firms on contracts, transactions, governance, and risk.

    ORG LAW

    Talk with an attorney.

    Tell us what you need help with. We will follow up within one business day.

    Start a conversation