A design change is any modification to the intended configuration, materials, or performance criteria of a building element after the design has been developed to a given stage, whether that’s a small clarification or a substantial revision affecting cost and schedule. It’s the underlying design event that bulletins, RFIs, and eventually change orders exist to formalize and track.
Design changes originate from several distinct directions, and knowing which one you’re dealing with usually shapes how it should be handled. Owner-driven changes come from a shift in program or preference; the owner decides they want a different finish or adds a room. Design-team-driven changes often come from the architect or engineer catching a coordination issue or code conflict during their own quality review process. Field-driven changes surface when actual site conditions don’t match what the design assumed, which happens more often on renovation and adaptive reuse work than on ground-up new construction.
Timing shapes cost impact more than almost any other factor. A design change made during schematic design costs essentially nothing beyond the design team’s time. The same conceptual change made after construction documents are issued for permit can trigger re-permitting delays. Made after construction has started, it can mean demolishing installed work, and each of those scenarios represents a roughly order-of-magnitude jump in cost from the one before it, which is the whole logic behind investing in thorough design review and constructability checks earlier rather than later.
Not every design change is bad news for the project; some genuinely improve the building, whether through value engineering that reduces cost without sacrificing performance, or through a late-stage refinement that the owner is happy to pay for because it solves a real problem. The distinction that matters for project health isn’t whether changes happen, but whether they’re caught and priced fairly, at the right stage, with clear documentation of why.
Documentation discipline around design changes matters just as much as the technical evaluation of cost and schedule impact. A design change that’s agreed to verbally in a design meeting, without a follow-up bulletin or written confirmation, tends to resurface later as a disagreement about what was actually decided, not because anyone acted in bad faith, but because memory of a verbal agreement degrades and diverges between parties in ways that a contemporaneous written record simply doesn’t.
