Scope changes are normal; scope chaos is not
Every real project changes, you learn things mid-build, the market moves, a stakeholder has a thought. The projects that die are not the ones with changes; they are the ones where changes were handled by conversation alone: agreed verbally, remembered differently, billed by surprise. The working method fixes this with one artifact: the change note, one paragraph, always the same shape.
The change note, exactly
"Change: replace the contact form with a two-step booking flow. Cost: $600 (8 hours). Moves: launch by 3 business days. Accepted by: [client], [date]." What it changes, what it costs, what it moves, who accepted. Before it is written, the developer's job is to state the tradeoff plainly, including "this is free and small" when it genuinely is, and "this is bigger than it sounds" when a client's innocent request touches the database, the checkout, or three templates. The note is not bureaucracy; it is the shared memory that prevents the month-five argument about what was agreed in week two.
The micro-change allowance, the pressure valve
Rigid scope enforcement breeds resentment over trivia ("can we swap two words?"). The honest mechanics include a small allowance: minor copy tweaks, small styling adjustments, handled within the engagement up to a stated allowance, no notes required. The line is stated in the quote so nobody discovers it mid-project. What never rides free: new features, new pages, integrations, design overhauls, those are change notes, because they move dates and budgets.
The freeze that protects launch
From code-freeze to launch, change requests queue for the post-launch cycle, by agreement made at kickoff, not invoked in a crisis. The reason is mechanical: changes near launch are untested against a deadline, and the QA pass cannot cover what keeps moving. Post-launch, the queue is processed as a scoped mini-project. Clients who accept the freeze get launches that hold; clients who insist on changes mid-freeze get the honest restatement of the risk and a new date. The contract guide places the change-note clause; the payments page covers how the costs are invoiced.