DEV Community

Hive80-lab
Hive80-lab

Posted on Originally published at hive80-lab.github.io

Change Order & Scope Creep Checklist for Small Teams (Stop Working for Free)

Scope creep is not a client personality flaw — it is the absence of a form. A three-person studio I worked with recently tracked one month of hours against quotes and found that 22% of all project hours went to work no quote ever mentioned: "quick tweaks," an extra landing page, a second round of "final" revisions. Clean invoices, gone margin.

The one-line rule

Anything not in the signed quote is a change, and a change is written down before work starts. Three words do all the work: "that's a change." Said pleasantly, they end ninety percent of renegotiation before it starts.

  • Clarification is not a change: explaining how the thing you sold works, or fixing a defect, is delivery.
  • The test: "Would I have priced this differently if it had been on the original quote?" Yes → change order. No → clarification.

What goes on the face of a change order

One page, five fields:

  1. Number + parent — CO-04, quoting job 2026-017. A free-floating change order is a suggestion.
  2. The delta in client words — one sentence: "Adds a sixth report to the monthly pack."
  3. Price delta + time delta — "+$1,800 and +6 working days." A price with no days reads as a penalty.
  4. The knock-on line — what else moves: completion goes 14 Mar → 24 Mar.
  5. Reply-by date — "if we don't hear back by Friday, current scope and dates stand."

The two-minute script

"Happy to add that. It's outside the current scope, so I'll send a one-page change order — it adds two days and $600. Reply by Friday and we'll slot it in; otherwise the current plan stands."

Immediate, number-first, and always offering the path of not doing it. A change order that feels like the only option reads as a trap; one with a visible "or not" reads as a service.

When to eat a change on purpose

Keep a named goodwill budget — say $200/client/project — and spend it consciously: eat rework caused by your own ambiguity, eat a small favor right after a clean payment (that's the cheapest moment goodwill ever gets), but charge for anything with recurring cost — a forever-hour is a subscription the client must sign for.

The stop-work boundary

Work outside signed scope stops when the change order is unsigned — at milestone edges, never mid-delivery. If unsigned scope keeps arriving, send the outstanding change orders as a summary invoice estimate. Some clients sign the moment they see the accumulated number; others go quiet, which is also an answer.

Six weeks later

Same clients, same team: unquoted hours 22% → 4% (the 4% is the deliberate budget), eleven change orders signed averaging $540 — roughly $5,900 of previously invisible revenue from work the team was already doing free.


The full checklist — the five fields, the rate-card pricing rules, the three-beat pushback answer, the five weekly numbers led by unbilled delta hours — lives on the ops notes site: Change Order & Scope Creep Checklist.

If you want the incident-response half of small-team ops handled too, the kits this checklist belongs to:

Top comments (0)