Change Events vs. Change Orders: Why the Difference Matters
Not every project change becomes a change order. Separating the two keeps potential changes visible while your team decides what to price and submit.
4 min read
A change event is something that happened
A change event records something on the project that may have commercial impact: a drawing revision, a field direction, an unexpected site condition, added work, rework, or a delay.
At this stage nobody has decided whether it is billable. The goal is to capture it with its evidence while the details are still fresh.
A change order is the commercial request
A change order is the formal document your team prepares after reviewing a change and pricing its impact. It is what gets submitted, negotiated, approved, or rejected.
One change order can cover one change event or bundle several related ones.
Why keeping them separate helps
When teams only track change orders, anything that has not been priced yet is easy to forget. Potential changes sit in email threads and notebooks until the notice window has passed.
Tracking change events first gives you a complete list of what might be recoverable, with a clear status for each: under review, confirmed, priced, or dismissed.
Human review sits in between
Software can help spot potential changes, but whether a change is compensable depends on the contract, the facts, and the relationship. A project manager should review each change event before it becomes a change order.
