A change order is one page nobody wants to sign and everyone ends up glad exists.
It says what changed, what that adds to the timeline, and what it adds to the invoice. Nothing on the new item moves until both sides sign it.
Skip it, and the fight happens at delivery instead of at the request.
What Locks Before Work Starts
Every Full Visibility Package starts with a locked baseline. Scope, milestones, and a payment schedule get set before the first camera comes out or the first line of code gets written.
That baseline is not a suggestion. It is what the finished work gets checked against later, when someone asks whether the project delivered what it promised. The post on what a baseline is actually for covers the record that gets taken before any of this starts.
A locked scope only works if it stays locked. The moment new pages, new shoot days, or new features get added without a record, the baseline stops meaning anything.
This protects the client as much as it protects me. A quoted price and a quoted date only hold if the scope behind them holds too. Once the ask changes, the number attached to the old scope is not honest anymore for either side.
Where the Ask Usually Grows
The request that blows up a timeline is rarely one big ask. It is five small ones, each reasonable on its own.
A client wants one more page. Then a second location added to the shoot. Then a feature that was never in the original brief. None of these feel like scope changes in the moment. Together, they are a different project than the one that got quoted.
I have watched a build run weeks past its date this way, with nobody able to point to the single decision that caused it.
Saying yes in the room is easy. The client is happy, the meeting ends well, and the new idea genuinely does make the project better. What is missing in that moment is the arithmetic: what the addition costs in hours, in a shoot day, in a week added to the schedule. That arithmetic has to happen somewhere, and a change order is where it happens on the record instead of getting absorbed and resented later.
What a Change Order Actually Says
A change order is short. It names the new item, what it adds to the schedule, and what it adds to the invoice.
Nothing starts until both sides sign it. That is the entire point. The client sees the real cost of the new ask before it becomes work, not after.
A change order usually gets written for:
- A page, section, or feature that was not in the locked scope.
- An added shoot day, location, or deliverable.
- A deadline moved earlier than the schedule allows.
- A feature request that needs new access, a new integration, or new content.
The Cost of Guessing Instead
Without a change order, the new work still happens. It just happens without anyone agreeing on what it costs or when it pushes the date.
That is the expensive version of the same conversation. The disagreement does not disappear. It moves to delivery, when the client is looking at an invoice or a deadline that does not match what they remember agreeing to.
Nobody wins that conversation.
It also costs the parts of the project that are not on the invoice at all. A Full Visibility Package only works because positioning, production, web, and search get built against the same plan. An untracked change to one piece, a new page here, a new shoot angle there, can quietly push the other three out of sync with it. The system stops moving as one thing and starts drifting into four separate ones.
When a Small Ask Is Free
Not every request needs paperwork. A typo fix, a clarifying question, a color swapped for one already in the brand system. None of that touches the baseline, and none of it gets billed.
The test is simple. Does it add a page, a day, a feature, or a deadline that was not already locked. If yes, it is a change order. If no, it gets fixed on the spot.
Most clients relax once they see the line drawn this clearly. The paperwork is not there to slow anyone down or to nickel and dime a fair request. It exists so the good idea that comes up in week three gets the same honest treatment the original scope got in week one.
What I Would Not Waste Money On
I would not waste a client's money building a system with no record of what changed and why. That is not accountability. That is a guess dressed up as a memory.
A locked baseline and a short paper trail cost nothing extra. What they buy is a project where the timeline, the invoice, and the finished work all agree with each other.
That discipline is what keeps positioning, production, web, and search moving as one system instead of drifting apart the moment the first real request comes in.
If you want a Full Visibility Package that stays honest when the plan meets a real business with real changes in mind, that paperwork is built into every one I run.