Change Order & Scope Creep Checklist

The paperwork that stops small teams from donating hours: every new deliverable gets a written change order before the work starts — one page, one price delta, one date. Scope creep is not a client personality flaw; it is the absence of a form.

1. The one-line rule

Anything not in the signed quote is a change, and a change is written down before work starts. Not after. Not "we'll sort it out at invoice time." The rule has three words that do all the work: "that's a change." Said pleasantly, they end ninety percent of renegotiation before it starts. A client who hears "sure, no problem" learns that your quote was an opening bid; a client who hears "that's a change — here's the one-page form" learns that your quote was a contract.

Two clarifications that make the rule survivable:

• Clarification is not a change. Explaining how the thing you already sold works, or fixing a defect, is delivery — it ships free and fast. Creep is new output: a new page, a new report, a new integration, a new "while you're in there."
• The test is one sentence. "Would I have priced this differently if it had been on the original quote?" If yes, it's a change order. If no, it's a clarification. Write that test on your team channel so juniors don't guess.

2. What goes on the face of the change order

One page, five fields, no legal prose. A change order that takes an hour to draft will never get drafted.

• Number and parent. CO-04, quoting job 2026-017. Change orders chain to a signed document; a free-floating change order is a suggestion.
• The delta, in client words. One sentence: "Adds a sixth report to the monthly pack, same format as the others." If you can't write it in one sentence, you haven't understood the request — go back to the discovery call checklist and ask the two questions you skipped.
• Price delta and time delta. "+$1,800 and +6 working days." Clients accept price more readily when they see the time it buys; a price with no days reads as a penalty.
• The knock-on line. What else moves because of this: "Project completion moves from 14 Mar to 24 Mar." Silent knock-ons are how one small change becomes three late ones.
• Reply-by date. "If we don't hear back by Friday, the current scope and dates stand." A change order without a reply-by date dies in a client's inbox and takes the schedule with it.

3. Price the delta from a rate card, not a mood

The moment of the ask is the worst moment to invent a price. Keep a small rate card — hourly rates by role, a day-rate floor, and a minimum change fee (one hour, even for "tiny" asks). The minimum fee exists for economics, not spite: it prices out the tenth fifteen-minute favor and keeps the form worth signing.

• Use the rate card's published rate, not a discount rate. A change order is a premium product: unplanned, unbudgeted, charged against a schedule the client already approved. Charging the same as the original quote teaches clients to skip the planning step.
• Never backfill hours. If work already happened, the change order records it as "completed — invoiced this cycle," at full rate. Retroactive paperwork at apology prices is how the next twelve changes arrive free.
• Bundle, don't trickle. If three small asks land in one week, issue one change order with three line items. One signature a week is administrative; four is nagging.

4. The two-minute script

Deliver the change order like an airport announcement, not a negotiation. Boredom is the tone that works:

"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."

Three things make this script hold: it is said immediately (same message thread as the request), it names the number before the client names a feeling, and it always offers 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 the pushback comes — and it will, once per client until the pattern teaches itself — the answer is the same three beats: what's in the quote, what the change costs, what the choice is. "The current quote covers the five pages we agreed. This is a sixth page, so it's +$600 and two days — or we keep the five-page plan. Your call, and both are fine." No apology, no exception-making in the moment. Exceptions get decided in writing, after a night's sleep, never in the thread.

5. When to eat a change on purpose

Rigid is not the goal; profitable is. Keep a small, deliberate goodwill budget — say $200 per client per project — and spend it consciously:

• Eat it when it's a defect. If the request exists because something in your original scope was ambiguous, that's rework, not a change — it ships free and the template gets a clarifying line so it never recurs.
• Eat it when the client just paid on time. A small unquoted favor after a clean payment buys more goodwill than a discount ever will — and it lands at the exact moment the referral ask is cheapest.
• Charge for anything with recurring cost. A one-off hour is a gift; a forever-hour (a new report every week) is a subscription the client must sign for, because subscriptions compound quietly into every future quote.

The budget line matters more than the individual decision: a team that knows it has $200 of "yes" available stops resenting the small asks and stops giving away the big ones.

6. The stop-work boundary

One clause in every quote and every change order: work outside signed scope stops when the change order is unsigned. Not as a threat — as arithmetic. The team has a fixed number of hours and a signed scope that fills them.

• Deliver the signed scope on time, to the letter. The cleanest proof of the boundary is a project where everything promised arrives exactly as promised — and everything extra waits politely on a form.
• Never stop mid-milestone. Finish the current milestone, then hold. Stopping mid-delivery reads as hostage-taking; finishing a milestone and pausing reads as a system.
• If a client refuses to sign and keeps requesting: send the outstanding change orders as a summary invoice estimate — "here's what the last six requests would total if approved." Some clients sign the moment they see the accumulated number; others go quiet, which is also an answer.
• The exit ramp. If unsigned scope keeps arriving after two summary invoices, the price-increase letter becomes a new engagement letter: same services, repriced to match how the client actually behaves. Clients who pay for creep are often excellent clients — they just need a price list that admits it.

7. Worked example: the studio that stopped bleeding hours

A three-person web studio tracks hours against quotes for one month and finds the honest number: 22% of all project hours are spent on work no quote ever mentioned — "quick tweaks," an extra landing page, one new integration, a second round of "final" revisions. The invoices are clean; the margin is gone.

Six weeks after installing the one-page change order — same clients, same team:

• Unquoted hours fall from 22% to 4% — and the 4% is the deliberate goodwill budget, not an accident.
• Eleven change orders signed, averaging $540 each — roughly $5,900 of previously invisible revenue, from work the team was already doing for free.
• Two clients push back hard and stay — one signs after the summary-invoice email; the studio later raises that client's retainer at renewal and keeps them.
• Delivery gets faster, not slower: the schedule stops absorbing silent extras, so promised dates become believable again.

The revenue was always there. It was priced at zero because there was no form.

8. Five weekly numbers

• Change orders issued (target: roughly one per active project per fortnight — zero means the form is being avoided, not that creep stopped).
• Signed within reply-by window (target: 70%+ — below that, your reply-by dates are decorative or your prices are scary).
• Unbilled delta hours (target: under 5% of logged hours — this is the one number that shows whether the system is real).
• Average delta size (drifting down over time means the client is learning to ask inside scope; drifting up means you're under-quoting originals).
• Goodwill budget spent (target: under $200/client/project, spent on purpose — zero spent means you're rigid; over means the budget isn't a budget).

9. The mistakes that turn forms into fights

• The change order as punishment. If the tone is gotcha, clients route future requests around you — through juniors, through "small favors." The script's bored-administrative tone is the defense.
• Pricing from memory. No rate card means every delta is improvised under pressure, and improvised prices are either guilt-low or hostility-high.
• Trickling. Fifteen one-line change orders teach a client that your paperwork is noise. Bundle weekly; sign once.
• No reply-by date. Open-ended change orders sit unsigned for weeks while the team silently absorbs the work "temporarily."
• Eating changes without a budget. Free favors with no ledger feel generous in the moment and read as margin leak at quarter-end. Name the budget, then spend it kindly.
• Stopping mid-delivery. The boundary lands only when the signed scope is flawless. A milestone hold proves the system; a stalled build proves the grievance.
• Never updating the original template. Every eaten defect should end with one added line in the next quote, so the same ambiguity is never sold twice.

Scope creep is a paperwork problem, not a people problem. One sentence — "that's a change" — plus a one-page form with a delta price, delta days, and a reply-by date converts donated hours into signed invoices. Price from a rate card, bundle the small stuff, keep a named goodwill budget, hold the stop-work boundary at milestone edges, and track unbilled delta hours like the profit line it is. The upstream fix is a quote that's hard to outgrow: scope the original with the discovery call checklist, put the clock on closing with the quote follow-up sequence, and when the pattern of creep reveals a systematically under-priced service, correct it calmly with the price increase announcement template — while vendor-side creep gets the same medicine from the other chair with the vendor contract checklist.

This checklist is part of the Hive80 Lab ops kit line — field-tested, instantly downloadable: And the sequence that funds the scope: the upfront deposit checklist puts the money before the calendar slot, so every change order negotiates against a funded project.

• The First 30 Minutes — free incident quick-start
• Ops Field Cards — 12 printable incident checklists — $4
• Ops Starter Kit — full incident-response kit for small teams — $14
• Ops Mega Bundle — all 5 kits in one download — $29