Every fixed-price software project reaches the same moment. Three weeks in, you see the first screens, and you think of something. "Can we also let customers upload a photo?" A change order is what happens next, and whether your budget survives depends on how it is handled.
Key Takeaways
- A change order is a short written agreement to change the scope, price, or timeline of a project.
- It protects both sides: you see the cost before agreeing, and the builder is not stuck absorbing extra work.
- A good one names the change, the price, the new date, and what it pushes out.
- Many budget blowouts start with changes that were agreed out loud and never written down.
What It Actually Is
A fixed price only works if both sides agree what the price covers. That agreement is the scope, usually a list of features and the tests each one must pass. A change order is a small document that says "we are changing that list, and here is what it costs."
It can be one paragraph. It should never be zero paragraphs.
Without change orders, a fixed-price project has two bad endings. Either the builder quietly absorbs every request and starts cutting corners to stay profitable, or the builder bills for everything at the end, and you get an invoice you did not expect. Both endings are common. Both are avoidable.
What a Good Change Order Contains
| Field | Example |
|---|---|
| What is changing | Customers can attach one photo to a booking request |
| Why | Groomers need to see the dog's coat before quoting |
| Price impact | +$900 |
| Timeline impact | +4 working days to milestone 3 |
| What it affects | Booking form, booking detail screen, storage costs |
| What it replaces, if anything | Nothing |
| Approval | Your signature or written OK, and date |
The "what it affects" line is the one people skip, and it matters. A photo upload looks like one button. It also means storing files, limiting their size, showing them on another screen, and deciding who can see them.
How Change Orders Keep a Fixed Price Fixed
On our own software factory projects, this is the process: you submit a change request, we assess the effect on timeline and cost, and you approve the updated scope and price before any work on it starts. No approval, no work, no bill.
That rule does two things. It removes surprise invoices, because nothing is billed that you did not approve in writing. And it makes you pause. When a change has a price next to it, you decide whether you really need it now. Plenty of the "small" ideas that come up mid-project belong on the list for version two, and a price tag is what makes that obvious.
Swaps Are Often Better Than Additions
A change order does not always add money. Often the smart version is a swap: "add photo upload, remove the review stars from this version." If the two are similar in effort, the price and date do not move at all. Ask for this option. A good builder will tell you honestly whether the swap is even.
A Concrete Version
A home-cleaning booking app, fixed at $18,000 across four milestones. During milestone two, the owner asks for three things:
1. Photo upload on the booking form.
2. A discount code field.
3. Changing the button color.
The builder replies with one change order:
- Button color: no charge, under ten minutes of work, done.
- Discount codes: +$1,200 and 5 working days, because codes need rules (expiry, one use per customer) and have to be checked at payment.
- Photo upload: +$900 and 4 working days, or a swap for the "reschedule booking" screen, which is similar effort.
The owner approves the discount codes, swaps the photo upload for the reschedule screen (customers can call to reschedule for now), and signs. New total: $19,200. New date: five working days later. Nobody is surprised at the end.
The Honest Counterpoint
Change orders can be abused from the other side. Some builders write a thin scope on purpose, win the job with a low price, and make their money on change orders. The defense is a detailed scope before you sign, and a look at how the builder has handled changes before. Ask a past client. If every project of theirs ended 50% over the original price, the fixed price was never really fixed. Our post on what a good software quote looks like shows how detailed a scope should be.
Frequently Asked Questions
Is every small change a change order?
Tiny adjustments, like wording or colors, are usually handled without one. Anything that adds a screen, a rule, a kind of user, or an integration should be written down, however small it sounds.
What if the builder built something wrong?
That is a fix, not a change. If the work does not match the agreed acceptance criteria, it gets corrected at no extra cost. See how to review a software milestone before you pay.
Can I refuse a change order price?
Yes. You can drop the change, swap something out, or move it to a later phase. You should never be forced to accept one.
How do I stop scope creep before it starts?
Keep a written "later" list from day one. Our guide on how to manage scope creep in software projects covers the habits that help.
The Bottom Line
A change order is a short, written "yes, at this price, by this date." Insist on it for anything beyond tiny tweaks, ask for swaps, and nobody gets a surprise invoice. If you are still at the scoping stage, the honest read helps you decide what belongs in the first version before any price is set.
Roberto Espinoza is CEO of Ruzora, which builds custom software for business owners at a fixed price and places pre-vetted senior LATAM engineers with US teams. Get a free honest read on your idea.
