A simple change-order process for fixed-fee web projects

Scope creep rarely arrives as a big new project. It arrives as “can you also…” after the scope was agreed.

You say yes to avoid friction. Then the extra work accumulates, the deadline stays fixed, and the project becomes less profitable with every “quick” request.

I kept seeing the same pattern in freelance threads: the change order is supposed to go out, but it never does. The relationship pressure wins, the work gets done anyway, and the loss only shows up at project close.

Here is the process that keeps coming up as the one that actually works.

1. Write down what “done” means before the project starts

A change order only works if there is a written scope to compare it against. The proposal does not need to be long, but it needs to be countable.

At minimum, write down:

  • the deliverables, in countable terms;
  • what is explicitly not included;
  • the number of revision rounds;
  • who provides assets, access, and decisions;
  • how new requests are handled.

“Five pages, responsive build, contact form, two revision rounds, one training call” is countable. “A professional website” is not.

2. When the request arrives, do not answer yes on the spot

The most useful sentence is some version of:

“Let me check how that fits the current scope and come back with the price and timeline impact.”

This buys you time, signals that the request is being taken seriously, and avoids the trap of saying yes before you know what it costs.

3. Price the change, not the relationship

A change order does not have to be a legal document. It needs four things:

  1. what is being added;
  2. the additional hours or fixed fee;
  3. the timeline impact;
  4. a written approval.

Options are useful. You can offer:

  • approve the change at $X and the new date;
  • defer it to a later phase;
  • cancel it and keep the original scope.

That gives the client a decision instead of a surprise.

4. Get written approval before starting

“Sounds good” in a call is not approval. A reply that says “approved, go ahead” is.

If the client will not put it in writing, that is information about the project, not a reason to start the work.

5. Log it and invoice it

A simple log with date, request, hours/fee, approval status, and invoice status is enough. The point is not bureaucracy. The point is that at the end of the project you can answer: what changed, what was approved, and what was billed?

A worked example

A five-page website project is fixed at $4,800, with a 50% deposit and 50% on acceptance. The timeline is four weeks.

In week three, the client writes:

“The new hygienist starts in January. Can you also add online booking and a sixth service page? It should be quick because you already have the design.”

This sounds small, but it adds an integration, a page, testing, and coordination with a third-party vendor.

The response:

“Thanks for the update. The booking integration and sixth page are outside the five-page scope we signed, so I want to handle them properly rather than quietly absorbing the work. I can add them as a change order: integration and page build, 9 hours at $75/hour = $675, plus a five-business-day timeline shift. The new delivery date would be December 12. If that works, reply with approval and I’ll schedule it.”

The client approves. The revised total is $5,475.

The important part is not the exact numbers. It is that the client got a clear choice before the work started, and the freelancer got a written record.

What to put in the proposal

A useful scope section has five parts:

  1. Deliverables — files, pages, features, formats.
  2. Acceptance criteria — how the client will know it is done.
  3. Not included — the things people assume are included.
  4. Client responsibilities — feedback deadlines, access, decision-maker.
  5. Change control — any request outside the scope goes through a change order.

The “not included” section is the one that saves the most arguments. It is also the one most proposals skip.

Five red flags

  • “Can you also…” arrives after the scope was agreed.
  • The request is called “small” but nobody can estimate the time.
  • The direction changes, not just the wording.
  • Feedback is verbal and never written down.
  • The deadline stays fixed while the scope grows.

If two or more are true, write the change order before starting.

What not to do

  • Do not silently absorb repeated extra work.
  • Do not send a surprise invoice after the work is finished.
  • Do not promise an outcome you cannot control.
  • Do not treat a template as legal advice.

Honest limitations

This is a practical process, not legal, tax, or financial advice. Adapt the documents to your contract and jurisdiction. A template cannot guarantee that a client will behave well; it can only make the agreement easier to see.

If you want the editable version

I packaged the proposal, change-order form, XLSX log, client scripts, and worked example into a 19-file kit for solo web developers:

ScopeGuard: Freelance Proposal & Change-Order Template Pack

It is $12, one ZIP, no subscription. The process above is free to use whether you buy it or not.

Disclosure: I used AI assistance to draft and format this article and the templates; I reviewed and edited them before publication. Not legal advice.