Exterior Construction – Change Orders
Nothing Gets Built Until
It’s Written & Signed
Verbal agreements about added scope are the single largest source of end-of-project construction disputes. The contractor expected to be paid. The client expected it to be included. Neither party was dishonest — both are accurately describing a conversation that produced different expectations. A RainFire Builders change order is a written document with defined scope, stated cost, schedule impact, and both party signatures — required before any work on the changed scope begins. No exceptions.
START A PROJECT CONVERSATION
SEE WHAT’S INSIDE
OUR CHANGE ORDER SERVICES
Written Change Orders
Scope Change Management
Field Condition Change Orders
Change Order Pricing
Schedule Impact Assessment
Change Order Log & Tracking
Client-Initiated Changes
Code-Required Changes
Verbal vs. Written Agreements
Change Order Disputes
Licensed & Insured
THE CORE ISSUE
Verbal Agreement Protect the Contractor –
Written Change Order Protect Everyone
The construction industry’s most pervasive bad practice — the verbal scope agreement — persists because it is convenient for contractors and invisible to clients until the final invoice arrives. Here is a direct comparison of what each approach produces.
⚠ VERBAL AGREEMENT — WHAT ACTUALLY HAPPENS
✓ WRITTEN CHANGE ORDER — WHAT IT PRODUCES
THE 15-MINUTE RULE
A written change order takes approximately 15 minutes to prepare and 5 minutes to review and sign. This 20-minute documentation step is what separates a project that ends in mutual satisfaction from one that ends in a billing dispute. A contractor who refuses to document changes in writing before proceeding is protecting themselves at the client’s expense. RainFire Builders applies the written change order requirement uniformly — on a $200 lighting upgrade and a $45,000 structural modification alike. The amount does not determine the requirement; the requirement is absolute.

OUR CHANGE ORDER SERVICES
Every element of RainFire Builders’ change order management — from the first identification of a scope change through pricing, approval, execution, and log tracking — is applied with the same written discipline on every project.
Every scope modification to the original contract — regardless of size — is documented as a written change order before work proceeds. The change order identifies the specific scope being added, removed, or modified; the cost impact with a labor-and-material breakdown; the schedule impact in calendar days; the reason for the change; and the updated contract total. Both parties sign before work proceeds. A $150 scope addition and a $40,000 scope addition receive the same documentation discipline — because the amount does not change the requirement for mutual written agreement.
When construction reveals an existing condition materially different from what was visible at estimate time — hidden rot, rock in excavation, unknown utilities, asbestos-containing material, structural deficiencies in existing framing — RainFire Builders stops work, documents the condition with photographs, prepares a written change order describing the additional scope required, and presents it to the client before proceeding. The client decides how to respond — proceed with the proposed additional scope, choose a different approach, or make another decision. The discovery is never used as a license to spend money without authorization. On cost-plus projects, the same process applies; the change order documents the reason for the unplanned scope addition.
Change orders are priced using three methods depending on the scope definition: lump sum (fixed price for well-defined additional work — preferred for client cost certainty); unit price (agreed rate per unit of measure multiplied by actual quantity — used for work where type is known but quantity will be field-determined, such as rock excavation at $X per cubic yard); or time-and-material at the contracted markup rate (labor actual hours at contracted rates plus materials at invoice cost, plus the overhead and profit markup stated in the original contract). The markup rate for T&M change orders is defined in every RainFire Builders contract — never negotiated after the fact.
Every change order states the schedule impact in calendar days — whether the change adds to the project completion date, reduces it (scope deletion), or has no impact. This is not a formality: scope additions that extend duration without updating the project schedule produce unexplained schedule slippage that the client cannot trace to a specific decision. When multiple change orders have each added “just a few days,” the cumulative schedule impact can add weeks to the project completion date. RainFire Builders states and tracks cumulative schedule impact through the change order log — so the client always knows what the current projected completion date is and which change order decisions drove any difference from the original.
A running change order log maintained throughout the project — showing every change order by number, date, description, cost impact, schedule impact, status (pending, approved, rejected), and cumulative running contract total. The log is the document that answers the question “why is this project costing more than the original contract?” with a specific, itemized list of every change that was authorized. The log is included in the monthly project documentation provided to the client. At project closeout, the final change order log becomes part of the project record — a complete history of every scope decision made from contract through completion.
When the building department requires scope not included in the original permitted design — additional shear wall per the plan checker, SDC D seismic reinforcing upgrade identified at framing inspection, egress window added at plan check — RainFire Builders prepares a written change order citing the specific code section requiring the additional scope. The cost responsibility determination depends on the reason for the deficiency: code requirements that arise from an inspector’s interpretation of a valid design are typically the client’s cost; code deficiencies that result from a design error in the licensed architect or engineer’s documents may be the designer’s professional liability responsibility. RainFire Builders documents the code basis for every code-required change order so cost responsibility is clear from the beginning.
HOW WE HANDLE CHANGES
The RainFire Builders Change Order Process
From the first identification of a scope change to the update of the project records, every change follows the same five-step process — the same for a $200 upgrade and a $50,000 scope addition.
Change Identification & Documentation Trigger
A scope change can be identified by the client (a request to add, remove, or modify something), by the project manager (a field condition discovered during construction that requires additional scope to address), by the design team (a drawing conflict or missing detail resolved through the RFI process that requires additional work), or by the building department (a code requirement or plan check comment that adds scope not in the original design). Regardless of the source, the identification of any change to the contract scope immediately triggers the written change order process. The affected work stops until the change order is executed — or in genuine emergencies, a Construction Change Directive is issued, and the cost is documented and agreed afterward.
Scope Description & Reason Documentation
The change order scope description must be specific enough that both parties — reading it independently — would understand exactly what work is being added, removed, or modified. Vague scope descriptions (“additional electrical work”) are as bad as no change order at all because they permit contradictory interpretations. The description specifies the physical location, the trade performing the work, the materials being used, and the boundaries of the change — what is included and what is explicitly excluded. The reason for the change is documented simultaneously (client request, field condition, code requirement) because it determines cost responsibility and is used in the change order log as the historical explanation for why the scope changed.
Cost Pricing & Schedule Impact Calculation
The cost of the changed scope is calculated using lump sum, unit price, or time-and-materials methodology — with the labor-and-materials breakdown shown separately, and the overhead-and-profit markup applied at the rate stated in the original contract. The schedule impact is calculated by assessing whether the changed scope affects any critical path task. A scope addition that adds work to a non-critical path phase may have zero schedule impact; the same amount of work added to a critical path phase extends the project completion date by the duration of the addition. Both cost and schedule impact are stated on the face of the change order — not relegated to footnotes.
Client Review, Questions & Execution
The completed change order is presented to the client for review — with a clear explanation of the scope, the cost basis, and the schedule impact. The client has the opportunity to ask questions, request pricing alternatives, or negotiate before signing. No pressure is applied to execute quickly based on “we need to keep moving” — the schedule consequence of a delay in approving the change order is stated honestly (if the work is on the critical path, delay in the change order approval delays the project; if it is not, there is no schedule urgency). The client signs when they are satisfied with the change order contents. Work on the changed scope begins after both signatures are obtained.
Log Update, Budget Update & Record Filing
After execution, the change order is entered in the change order log — updating the running contract total, the schedule impact cumulative total, and the log status for this CO from “pending” to “approved.” The approved budget in the job cost system is updated to reflect the change order’s cost impact on the relevant cost code. The executed change order document is filed in the project records — accessible throughout the project and provided to the client in the project closeout documentation package. The client’s monthly project update for the period in which the change order was executed includes the change order summary in the project report, so the client has a written record of every change decision that affected their project’s cost and schedule.
The Most Common Change Order Triggers On Wasatch Front Projects
Utah’s most frequent field-condition change orders arise from the same site conditions that affect estimates: expansive Lake Bonneville clay that requires more engineered fill replacement than visible at the surface; rock or caliche hardpan encountered at depths where the estimate projected clear excavation; moisture or rot behind siding or in wall cavities opened during renovation; and existing MEP configurations that conflict with the planned new work routes. Every one of these is a legitimate field condition — not a contractor error and not a client failure. The written change order is the mechanism that handles each discovery honestly: work stops, conditions are documented with photographs, the response scope is priced, and the client makes an informed decision.
Code-required changes are more common on the Wasatch Front than in many markets because Utah’s seismic environment (Seismic Design Category D in most Wasatch Front jurisdictions per ASCE 7-22) and WUI fire zone designations in foothill communities create code requirements that sometimes change between design and construction. SDC D shear wall and hold-down requirements that are tightened at plan check, additional egress windows identified during framing inspection, and IECC energy code provisions that are interpreted differently by different plan checkers all generate code-required change orders that are the result of legitimate regulatory requirements, not contractor or design errors.
The most preventable Utah change order — and the most expensive — is the undocumented verbal scope agreement that accumulates over a long project. A custom home project of 14 months with weekly site visits creates hundreds of casual conversations that each potentially generates a scope change. On a properly managed project, each one that results in actual changed work produces a written change order. On an improperly managed project, they accumulate verbally until the final invoice reveals $85,000 of “extras” that the client cannot specifically recall authorizing. RainFire Builders eliminates this outcome structurally: the written change order is required before work proceeds, without exception, on every project we manage.
No work on the changed scope begins before a written change order is signed by both parties. A $200 lighting upgrade receives the same documentation discipline as a $40,000 addition. The amount does not determine the requirement. The requirement is absolute because the amount at which verbal agreements produce disputes is impossible to predict in advance.
When construction reveals a condition that requires additional scope, work stops, and the condition is photographed and documented before the response scope is determined. The change order includes the photograph reference. Documentation at the moment of discovery — not reconstructed from memory later — is the standard that makes field condition change orders supportable if ever disputed.
The overhead-and-profit markup for time-and-material change orders is defined in every RainFire Builders contract (typically 15% on labor and materials). This rate is agreed to at contract execution — not negotiated after work has been performed, and the client has no leverage. Change order pricing should never be a surprise; the rate that will be applied is a contract term visible from day one.
The change order log maintains a running contract total — original contract value plus all executed change orders — updated after every execution. The client knows the current authorized project cost at all times, not just at the beginning and the end. There is no financial surprise at the final invoice because the final invoice reflects a running total the client has been watching throughout the project.
CHANGE ORDER FUNDAMENTALS
A Change Order Is A Contract Modification. Treat It Like One
Every construction project begins with a contract — an agreement between the client and the contractor about what will be built, what it will cost, and when it will be complete. A change order is the document that modifies the contract when the project’s scope, cost, or schedule needs to change after the original contract is signed. It is not a request, a suggestion, or a conversation — it is a formal amendment to a legal agreement, and it carries the same weight as the original contract.
The residential construction industry treats change orders informally — a text message, a conversation on-site, a nod of agreement — and this informality is the direct cause of the most common and most expensive construction disputes. When the final invoice includes $32,000 in “extras” that the client doesn’t remember authorizing, both parties are typically telling the truth: the contractor performed work they believe they were asked to do; the client never consciously authorized $32,000 of additional spending. The written change order — signed by both parties before work proceeds — makes this dispute impossible because the mutual understanding is documented in writing at the moment of agreement, not reconstructed afterward from memory.
On a RainFire Builders project, every modification to the original contract scope — whether initiated by the client, discovered in the field, or required by the building department — is documented as a written change order. The change order identifies the scope being added, removed, or modified; the cost impact broken into labor and materials; the schedule impact in calendar days; and the reason for the change. Work on the changed scope does not begin until the change order is executed by both parties. This is not slow or burdensome — it is a 15-minute documentation step that prevents a multi-week dispute at the end of the project.
The running total of all executed change orders, added to the original contract value, equals the current approved contract value. This running total is updated in the change order log after every execution and is included in the monthly project update provided to the client. You should always know what the current authorized value of your project is — not because we send you one number at the beginning and another at the end, but because both numbers are available to you throughout the project.
COMMON QUESTIONS
CONSTRUCTION CHANGE ORDERS FAQs
The questions every construction client should ask about scope changes — answered honestly, with no contractor-protective hedging.
A change order is a written document that modifies the original construction contract — changing the scope, the price, the schedule, or some combination. Change orders are required whenever the work deviates from what was defined in the original contract, whether through additions, deletions, or substitutions. On a properly managed project, every change is documented as a written change order before work on the changed scope begins. The running total of all executed change orders, added to the original contract value, equals the current approved contract value at any point in the project. Change orders are the mechanism that keeps the contract current and prevents the accumulation of undocumented scope additions that cause end-of-project financial surprises.
Verbal agreements fail as change order documentation because they are unenforceable (no written record means no reliable evidence if parties disagree), imprecise (verbal descriptions are ambiguous and produce different interpretations), and invisible (costs accumulate without the client ever seeing a running total). The most common and expensive construction dispute is the verbal scope addition: the contractor performed work they believe they were asked to do; the client never consciously authorized additional spending. Neither party is dishonest — both are accurately describing their understanding of a conversation that produced different expectations. A written change order, signed before work proceeds, makes this dispute structurally impossible. RainFire Builders requires written change orders on all scope changes without exception — not because it’s burdensome, but because the 20 minutes it takes is the single best investment in project outcome available.
Change orders can be initiated by the client (adding, removing, or modifying scope after contract execution), the contractor (field conditions discovered during construction, or drawing ambiguities requiring field resolution through the RFI process), or the building department (code requirements not addressed in the original design). Regardless of who initiates the change, the process is the same: scope is documented, cost and schedule impact are calculated, the change order is presented to the client, and work proceeds only after both parties sign. The reason for the change is documented because it determines cost responsibility — client-initiated changes are paid by the client; estimating errors or omissions are the contractor’s cost; unforeseeable field conditions are typically the client’s cost; design errors may be the designer’s professional liability.
A complete change order includes: a sequential change order number for tracking; the date issued; the project and contract reference; a specific scope description (what work is being added, removed, or modified, specific enough that both parties reading it independently would understand the same thing); the cost impact — lump sum or T&M with labor and material broken out separately; the overhead-and-profit markup at the contracted rate; the schedule impact in calendar days; the reason for the change; the updated contract total (original plus previous COs plus this CO); and both party signatures. Missing any element makes the change order incomplete and its enforceability weaker. The running contract total update is particularly important — without it, the client cannot track the current authorized project cost.
When construction reveals a condition materially different from what was known at estimate time — hidden rot, unexpected rock, asbestos, unknown utilities, structural deficiency in existing framing — the correct process is: stop work on the affected scope, document the condition with photographs before any removal or remediation, prepare a written change order describing the condition, the additional scope required, the cost impact, and the schedule impact, and present it to the client before proceeding. The client decides how to respond. What should not happen: the contractor proceeding with additional work and informing the client at billing time. Field condition discoveries are decision points for the client, not licenses for the contractor to spend money without authorization. RainFire Builders has an internal policy: no additional work on a discovered condition before the client has seen the photograph and signed the change order.
Change orders are priced three ways: lump sum (fixed price for well-defined changes — preferred for client cost certainty); unit price (agreed rate per unit of measure times actual quantity — for changes where type is known but quantity is field-determined, like rock excavation at $X per cubic yard); or time-and-material at the contracted markup rate (actual labor hours at contracted rates plus materials at invoice cost, plus the overhead-and-profit markup stated in the original contract — typically 15–25% on labor and materials). The T&M markup rate is defined in every RainFire Builders contract at execution — never negotiated after work is performed when the client has no leverage. RainFire Builders uses lump sum pricing wherever the scope is defined to give clients cost certainty on the change order amount.
A change order log is a running register of all change orders on a project — showing CO number, date, description, cost impact, schedule impact, status (pending/approved/rejected), and cumulative running contract total for every change order. The log is the document that explains why the project cost differs from the original contract value. If a project started at $450,000 and the current authorized value is $518,000, the change order log itemizes the $68,000 difference through every specific scope decision that was made and authorized. RainFire Builders maintains a current change order log on every project and includes it in the monthly project documentation — so the client always knows what the current authorized project cost is and what decisions produced that number.
A change order (CO) is bilateral — both contractor and client agree on scope and cost before work proceeds. A Construction Change Directive (CCD) is unilateral — the client instructs the contractor to proceed with a scope change before the cost is agreed upon, typically because the change is urgent and waiting would cause unacceptable delay. Under a CCD, the contractor proceeds and the cost is determined afterward by negotiation or the contract’s dispute resolution mechanism. CCDs are appropriate for genuine emergencies; they should not be used routinely to avoid the pricing process. A contractor who regularly receives CCDs — because the client directs work before agreeing to cost — is in a situation where their cost recovery is at risk. RainFire Builders uses standard change orders on all non-emergency changes and reserves CCD-equivalent procedures for genuine urgencies where documented urgency justifies proceeding before pricing is complete.
The RainFire Standard
WHY CHOOSE RAINFIRE BUILDERS FOR CHANGE ORDER DISCIPLINE?
Written Before Work — Always
No work on changed scope begins before both parties sign a written change order. This requirement is not waived for urgency, small amounts, trusted relationships, or project phase. The consistency of the requirement is the requirement — a policy that has exceptions is not a policy.
Cost AND Schedule, Every Time
Every change order states both the cost impact and the schedule impact in calendar days. Scope additions that add cost without adding documented schedule days produce unexplained schedule slippage. We track cumulative schedule impact through the change order log — the client always knows the current projected completion date and which decisions drove any change from the original.
Field Conditions Stop Work
When construction reveals an unforeseeable condition, work stops, and the condition is photographed before any response scope is determined. The client sees the photograph and approves the change order before work proceeds. Discoveries are never used as a license to spend money — they are decision points that belong to the client.
Log Current, Total Visible
The change order log — with running contract total — is updated after every execution and included in the monthly project report. The client knows the current authorized project cost at all times. There is no financial surprise at the final invoice because the final number is a running total the client has been watching throughout the project.
CONTINUE THE PROCESS:
RELATED PROJECT MANAGEMENT SERVICES
Scheduling
Every change order states its schedule impact in calendar days. The change order log’s cumulative schedule impact column drives the current projected completion date – keeping the production schedule current and honest throughout the project. | Explore More About Scheduling
Job Costing
Every change order updates the approved budget in the job cost system. The monthly job cost report and the change order log together show the client both the current authorized cost and how the project is performing against it. | Explore Job Costing
Estimates
The best change order is the one that never happens because the estimate was complete. A line-item estimate with stated exclusions prevents the most common class of change orders – items the client assumed were included that weren’t. | Explore Estimates
Inspections
Building department plan check and field inspections are the most common source of code-required change orders. Understanding the inspection process – and what inspectors require in Utah’s SDC seismic environment – reduces unexpected code-required changes. | Explore Inspections
Start Your Project
Ready to work with a contractor who documents every scope change in writing before it happens? Contact RainFire Builders to start the conversation about your Utah construction project. | Get Your Free Estimate
All Project Management
Return to the complete project management overview – estimates, scheduling, job costing, change orders, inspections, and quality assurance. | Go Back to the Beginning
Written. Priced. Signed. Before Work Proceeds.
Never Get Surprised by a Construction Invoice Again.
The difference between a project that ends in a billing dispute and one that ends in mutual satisfaction is not the quality of the work — it’s whether every scope change was documented in writing before it was built. A RainFire Builders project has a written change order for every scope modification, a running contract total visible at all times, and no final invoice that exceeds the sum of what was explicitly authorized. Every change you approved. Every dollar you authorized. Documented before work starts, visible in the monthly report, and in the project record when it’s done.
Call us now at (385) 336-7246 or request an estimate online. We’ll start on your property’s project and your future with care.
We Make It Happen –
Request an Estimate
Schedule your in-person consultation. Let’s get your project started


