Change Management for Project Engineers (RFIs, Change Orders, and Cost Control)

Change Management, RFIs, and Change Orders: The System That Protects Everyone on the Project

Change is inevitable on every commercial construction project. The owner requests a modification. The design has a gap that the field cannot resolve without a drawing revision. An unforeseen condition requires a scope adjustment. None of these events are failures they are the natural reality of building complex structures in an imperfect world. What determines whether change events damage a project or get absorbed cleanly is not whether they happen. It is whether the team has a system for managing them.

The project engineer sits at the center of that system. RFIs, potential change orders, executed change orders, documentation, posting to drawings, trade partner notification all of it flows through the PE. A PE with a disciplined change management process protects the project’s budget, the schedule, the trade partners who need to be paid for extra work, and the contractual integrity that governs every decision. A PE without one finds themselves six months into a project with untracked exposures, unpriced changes, trade partners doing work outside their contract without financial approval, and a change order reconciliation that will take months to untangle.

What an RFI Actually Is

An RFI request for information is the formal mechanism for modifying the contract documents when something is unclear, missing, or inconsistent. That definition matters because it shapes how the PE should think about the RFI process. You do not design through submittals. You do not design through field sketches, verbal agreements, or email conversations. If something on the drawings or specs needs to change, it changes through an RFI a formal, documented, traceable request that produces an official answer tied to the contract.

This matters for two reasons. First, because the contract documents govern the project, and any deviation from them that is not formally documented creates risk for the party who deviated. A trade partner who installs to a verbal instruction rather than a posted RFI response has installed outside the contract documents, and their protection in a dispute is thin. Second, because the fewer RFIs on a project, the better the design. RFIs are, in a very real sense, rework for information they represent gaps that should have been resolved in the design phase rather than pushed into the construction phase for the field team to navigate. A streamlined RFI process simple, clear, frictionless, with only the information actually needed honors that reality rather than creating administrative overhead that obscures it.

The goal for any RFI is the same: propose a clear solution, describe the issue with enough specificity that the designer can answer it correctly on the first response, and submit it early enough that the answer arrives before the construction sequence needs it. A well-written RFI with a recommended solution gets answered faster and more accurately than a vague question that leaves interpretation to the reviewer. The PE who writes RFIs with that discipline is protecting the schedule as much as they are resolving a design gap.

The Trigger Rule: Log It the Moment You Know

Here is the rule that protects more projects from financial surprises than almost anything else in change management. The moment any event occurs that might cost money or time, it becomes a potential change order with an assigned number. Not when the price is confirmed. Not when the owner approves it. Not when the work is complete and someone asks what it cost. The moment the trigger happens.

This principle keeps nothing forgotten. A potential change order log that is current in real time with every triggered event numbered, described, and tracked is the difference between a project whose financial projections reflect reality and a project where half the exposures are invisible until they surface as disputes at closeout. If an event is triggered on a Tuesday morning, it is on the log by Tuesday afternoon. If it eventually gets resolved without a cost impact, it gets closed off the log. If it becomes an executed change order, the log tracks that evolution.

The downstream effect of this discipline is also significant. When the PM is reviewing financial projections and contingency exposure, the potential change order log is what makes those projections honest. A project that appears to have consumed only a third of its contingency budget might actually have consumed 75% once every tracked potential change order is accounted for. Without the log, that reality is invisible until it is too late to take corrective action. With the log, the picture is clear every week at the strategic planning meeting, and corrective action is available when it is still relatively cheap.

The Phase Gate Process: Do Not Proceed Without Financial Approval

The single most important rule in change order management is this: do not authorize work outside the contract scope until financial approval has been obtained. Not tentative approval, not a verbal from the owner, not a hand wave in a meeting that someone interprets as a go-ahead. A documented approval written confirmation that the rough order of magnitude cost, or the final lump-sum cost, has been accepted by the owner and the work can proceed.

This sounds obvious. In practice, schedule pressure and relationship dynamics push teams across this line constantly. A change is needed urgently. The owner says “just go, we’ll work out the price later.” The team proceeds, the work gets done, and then the price conversation becomes a negotiation over work that has already been installed. The leverage has shifted entirely to the owner’s favor. The trade partner who did the work may or may not get paid for it at what it actually cost them. And the PE who authorized the work without written approval is holding a difficult conversation with very little documentation to support the project’s position.

The phase gate model prevents this. Each step in the change order process the RFI, the design response, the rough order of magnitude pricing, the owner’s written approval, the final pricing, the executed change order has a clear gate. Work at the next step does not begin until the gate is cleared. It feels slower. It is actually faster, because it eliminates the disputes, the reconciliation effort, and the relationship damage that unauthorized work creates.

Posting to Drawings Only After Approval

Once an RFI is answered and the change is approved, the updated information needs to be posted to the drawings in the field. This step is as important as the approval itself, because a trade partner who is still working from a superseded drawing after an approved RFI has been answered is working from wrong information and the quality consequences of that belong to the change management system, not to the trade.

The PE’s discipline here is simple: post the bulletin or the RFI response to the current drawing set immediately after approval, before releasing the trade to act on the change. Current, relevant, accurately marked drawings are the protection. Unmarked drawings with verbal instructions are a dispute waiting to happen.

When changes are concentrated in a specific scope or area, they should be handled by a dedicated resource a separate engineer or office PE focused on pricing and processing the change orders rather than diverting the main project team from contract work. A project team that gets overwhelmed by change order processing and loses focus on the contract scope will deliver neither the contract work nor the change work at an acceptable standard. Keeping those tracks separate when volume demands it is a management decision the PE and PM need to make proactively, not reactively when both tracks are already behind.

Warning Signs That Change Management Is Breaking Down

Before the financial exposure becomes unmanageable, watch for these signals that the change management system needs a reset:

• Potential change order events are being tracked in someone’s memory or a personal spreadsheet rather than in the formal log with assigned numbers.
• Work outside the contract scope is being performed based on verbal approvals because the formal process feels too slow for the schedule pressure.
• Updated RFI responses have been answered but not posted to the field drawing set, meaning some trades are still working from superseded information.
• The contingency budget appears healthy on the cost report, but the potential change order log if it exists shows exposures that have not yet been moved to the contingency calculation.
• Change orders from months ago are sitting unexecuted because the pricing and documentation were never finalized.

Every one of those signals is a financial exposure that is growing invisibly. The system, run correctly, makes every exposure visible from the moment it is triggered. That visibility is what allows the PM and owner to make informed decisions rather than being surprised.

The Eight-Point Summary That Protects Every Project

The complete change management framework distills to eight disciplines that every PE should treat as non-negotiable:

• Log every triggered change immediately with an assigned number.
• Process the RFI correctly clear, descriptive, with a recommended solution.
• Obtain pricing, negotiation, and written approval before executing any work.
• Track both time and cost impacts for every potential change from the moment it is triggered.
• Document properly to protect the project backup, vendor pricing, owner authorization.
• Avoid scope gaps by closing every interface between contract scope and change scope before either progresses.
• Track changes systematically using phase gates so no step proceeds without the required approval.
• Prevent change order overload from derailing contract work by separating the tracks when volume demands it.

We are building people who build things. The PE who masters change management is building the financial integrity of the project ensuring that every extra dollar spent is authorized, every trade partner gets paid for their work, and every change is traceable from trigger to execution. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow including the change management discipline that protects the project’s budget and the people who build it.

A Challenge for Builders

Open your current project’s potential change order log this week or create one if it does not exist and account for every event that has been triggered since the project started that might have a cost or time impact. For each one: has it been numbered? Has it been priced? Has written approval been obtained before any work proceeded? Has the approved change been posted to the drawings? If any of those steps are missing for any item, close the gap this week. The longer a potential change order sits untracked, the harder it becomes to reconstruct and the more it costs in reconciliation effort and relationship damage at closeout.

As W. Edwards Deming said, “Manage the cause, not the result.”

On we go.

Frequently Asked Questions

When should a potential change order be logged?

The moment any event is triggered that might have a cost or time impact not when the price is confirmed, not when the work is done, but at the moment the trigger occurs. Immediate logging with an assigned number ensures nothing gets forgotten and every exposure is visible in the financial projections from day one.

Why is written financial approval required before proceeding with change order work?

Because performing work outside the contract scope without written approval shifts all negotiating leverage to the owner after the work is already installed. Written approval whether a rough order of magnitude or a final lump-sum protects the project, the trade partner who performs the work, and the GC who authorized it. Verbal approvals are disputes waiting to happen.

What does “phase gates” mean in change management?

Each step in the change order process RFI submission, design response, pricing, owner approval, execution, drawing posting has a clear gate that must be cleared before the next step begins. No work proceeds to the field without passing through the approval gate. This structure prevents the unauthorized work and unresolved pricing that create the most expensive change order disputes.