About BuildChangeOrder

I built BuildChangeOrder after getting burned by scope creep twice in the same year. The first time, a client added two extra features mid-project and then acted surprised when the final invoice was higher than the original quote. The second time, I added the features without documenting it — and then couldn't justify why the bill was higher. Both situations were my fault for not having the conversation in writing.

A change order solves that. It's not about being difficult — it's about making sure both sides know exactly what changed, what it costs, and that they agreed to it. When both parties sign, there's no ambiguity. The "I thought that was included" conversation never happens.

What's built in: Running contract totals so your client can see the cumulative impact of all changes, not just this one. Dual signature blocks — contractor and client. Optional schedule impact tracking. A reason-for-change field that forces you to articulate why the scope changed, which is useful when revisiting the project later.

For developers, the BuildChangeOrder REST API lets you generate change orders programmatically from your own project management data.

Part of the Build ecosystem: BuildQuotes, BuildInvoice, BuildPDF, and BuildCertificates.

Contact

Questions or bugs? buildpdf.help@gmail.com