Solar Design Change Orders: How Scope Changes Get Priced and Approved

A design contract is signed, the deposit clears, and work starts on schedule. Six weeks in, the geotechnical report comes back with soil bearing capacity 30% lower than the assumption used at bid stage. The foundation design has to change. Nobody did anything wrong. The site is just different from what the drawings assumed. Now someone has to decide who pays for the redesign, how much it costs, and who signs off before work resumes.

This is a change order. It is one of the most common friction points in an active solar design engagement, and it is also one of the most avoidable, if the contract sets clear rules before the first change ever happens.

Direct answer. A solar design change order is a documented, priced, and mutually signed modification to an existing design contract’s scope, cost, or timeline. It typically gets triggered by differing site conditions, an AHJ (Authority Having Jurisdiction) redesign requirement beyond the contract’s included revision rounds, a customer-initiated scope change, or a utility interconnection requirement change discovered during technical review. Pricing usually follows one of three models: a fixed quote for the specific added work, a rate card applied to estimated hours, or a percentage markup on the original design fee. Formal written approval before work resumes, not verbal agreement, is what prevents the change from turning into a payment dispute.

This guide is for the EPC (engineering, procurement, and construction) or developer managing an active design contract who just got a change order request and needs to know if the price is fair, and for the design vendor who wants change-order terms that hold up without a fight every time a project hits an unplanned turn.

What a Change Order Actually Is

A change order is a formal amendment to a signed contract. It is not a new contract, and it is not a verbal understanding. In the American Institute of Architects (AIA) standard construction contract system, the change order form is AIA G701, which records the project details, a description of the change referencing specific drawings or specifications, the adjustment to contract price, the adjustment to contract time, and signature blocks for both parties. The change is not binding until everyone signs.

Engineering-specific contracts use an equivalent structure. The Engineers Joint Contract Documents Committee (EJCDC) C-941 Change Order is built for design and engineering work specifically, usually initiated by the engineer rather than the owner or contractor, and it covers changes to both contract price and contract time. It pairs with a Work Change Directive, a field order that lets work proceed before the formal change order paperwork is finished, for situations where waiting for signatures would stall the project.

ConsensusDocs 202 is the equivalent bilateral form used in the ConsensusDocs contract family, alongside ConsensusDocs 203, a unilateral interim directive an owner can issue to keep work moving before a price is agreed.

Solar design contracts rarely reference these forms by name, but the underlying structure they establish, description, cost, schedule, signatures, is the standard that any solar design change order should meet. A one-line email that says “go ahead and redesign the racking layout, we’ll figure out cost later” is not a change order. It is an invitation to a dispute.

The Four Triggers That Cause Most Solar Design Change Orders

1. Differing site conditions

The site survey, geotechnical report, or existing structural drawings the design was based on turn out to be wrong, incomplete, or not representative of actual conditions. Common examples in solar design work: soil bearing capacity lower than the geotech assumption, an existing roof structure that does not match the as-built drawings provided by the client, buried utilities or rock discovered during pile installation that were not on the survey, or a shading obstruction that was not visible in the site photos used for preliminary design.

This is a well-established concept in construction law, not something unique to solar. A “differing site conditions” (DSC) clause is standard in federal contracts and most AIA, EJCDC, and ConsensusDocs forms. It comes in two recognized types, according to AIA Contract Documents’ guidance on differing site conditions: Type I is when actual conditions differ materially from what the contract documents represented, and Type II is when conditions differ materially from what is ordinarily encountered for that type of work, even if nothing in the documents specifically claimed otherwise. The clause exists so the party doing the work does not have to price blind contingency into every bid for conditions nobody could have verified in advance.

For a solar design vendor, this means the original fixed-price quote was built on the information available at bid stage. When that information turns out to be wrong through no fault of either party, redesigning the foundation, structural system, or racking layout is legitimately outside the original scope.

2. AHJ-mandated redesign beyond the included revision scope

Every solar design contract should specify a number of included revision rounds, typically two to three rounds covering normal plan check comments. An AHJ redline asking for a corrected label or an updated wire size falls inside that included scope. A redline that requires re-running the structural calculations because the AHJ wants a different code edition applied, or a request to add a completely new fire setback layout the jurisdiction did not flag during pre-application review, goes beyond it.

The distinction matters because AHJ review timelines are already a major source of project delay independent of redesign work. The National Renewable Energy Laboratory (NREL) tracks this at scale through its SolarTRACE dataset, which covers median permitting, inspection, and interconnection cycle times across more than 1,500 jurisdictions and 140 utilities built from over 200,000 project records. A 2021 NREL soft-cost analysis found permitting, inspection, and interconnection soft costs of $0.23 per watt DC for small installers and $0.25 per watt DC for national integrators, according to NREL’s technical report on solar soft costs. When an AHJ redesign adds a review cycle on top of that baseline, both the redesign cost and the schedule slip need to be captured in a change order, not absorbed silently by the vendor.

3. Customer scope changes

The client decides to add a battery energy storage system (BESS) mid-design, change the module or inverter selection after the electrical design is already drafted, expand the system size, or add a carport structure to what was originally a ground-mount-only scope. These are the most straightforward change orders because nobody disputes the cause. The client wants something different from what was signed. The negotiation is entirely about price and schedule impact.

The most common failure mode here is scope drift without a change order at all. A client asks “can you also check if we could fit a few more rows,” the design team says sure and spends four hours on it, and three more of these requests happen before anyone notices the project is running behind on a fixed-price contract that never accounted for the extra work. Every scope addition needs a change order, even a small one, or the vendor absorbs unlimited scope creep for free.

4. Utility interconnection requirement changes

Interconnection utilities evaluate grid capacity, transformer loading, protection and backfeed risk, and export limits during their technical review, and the outcome is not always known at the time the design contract is signed. A system designed for a specific export capacity can come back from utility review capped lower, requiring active power control hardware, a different inverter configuration, or a redesigned electrical single-line diagram to comply.

This is not a hypothetical edge case. The Solar Energy Industries Association’s 2025 Year in Review reports that median duration from interconnection request to commercial operation date now exceeds five years for projects built in 2025, with interconnection queue congestion limiting commercial solar deployment in mature markets. A design that sat in an interconnection queue for months before technical review results come back is a design that may need mid-project changes the original contract could not have anticipated. The AHJ and the interconnecting utility are two separate reviewing authorities, and a change triggered by one does not automatically excuse a delay caused by the other, so change order documentation should specify which authority drove the change.

How Change Orders Get Priced

Three pricing models cover most solar design change orders. Each has a different dispute profile.

Fixed quote for the specific added work. The vendor scopes the change (for example, “redesign pile foundation layout for updated geotech report, re-run structural calculations, revise civil drawings”) and quotes a fixed number for that defined package. This is the most dispute-resistant model because both sides agree on the price before work starts. It works best when the change has a clear, boundable scope, which is true of most site-condition and AHJ-driven changes.

Hourly rate against an estimate. The vendor states an hourly rate, typically the same rate used in the base contract if one exists, and gives a good-faith estimate of hours for the change. Work is billed against actual hours with the estimate serving as a not-to-exceed ceiling or a check-in trigger. This model fits changes where the full scope is not knowable up front, such as an open-ended request to “explore options” for a BESS addition before the client commits to a specific configuration.

Percentage markup on the base design fee. Less common in solar-specific practice but used in some fixed-price EPC-adjacent contracts, where the change order value is calculated as a percentage of the original contract sum tied to the change’s proportional scope. This model is the hardest to defend in a dispute because the percentage rarely maps cleanly to actual engineering hours, and clients tend to push back on it more than a scoped fixed quote.

There is no single industry-standard markup percentage that a credible source publishes for change order pricing in solar or general construction. Figures circulating online claiming a specific “standard” markup are not traceable to a primary source such as AACE International, and should be treated as informal contractor practice rather than a benchmark. What matters more than hitting a specific percentage is that the pricing method is stated in the base contract before any change order is needed, not negotiated from scratch mid-dispute.

The Approval Workflow That Prevents Disputes

A workable change order approval workflow has five steps, and skipping any of them is what turns a routine scope change into a payment fight.

1. Identify and document the trigger. The party that discovers the issue, whether it is the design team finding a soil report discrepancy or the client requesting a BESS addition, documents it in writing with enough specificity that the other party can evaluate it without a meeting. A photo, a geotech report excerpt, or the AHJ redline itself should accompany the notice, not a paraphrase of it.
2. Scope and price the change. The vendor defines exactly what work the change requires, using one of the three pricing models above, and states the schedule impact in business days, not “a little longer.”
3. Submit a written change order for approval. This is the AIA G701 or EJCDC C-941 style document: description, cost, schedule impact, and a place for both parties to sign. Email approval with a clear cost and scope stated is acceptable if the base contract says so, but a verbal “go ahead” is not.
4. Get signed approval before resuming work on the changed scope. This is the single most important step and the one most often skipped under schedule pressure. If the client needs work to start before formal sign-off, some contracts use an interim work directive, similar to ConsensusDocs 203, that lets work proceed under agreed terms while final paperwork catches up. This still requires written authorization, just a lighter-weight version of it.
5. Track the change order against the master contract. Every approved change order should be logged against the original scope of work so both parties can see cumulative changes to price and schedule at any point in the project, not just discover it at final invoice.

Most solar design change order disputes trace back to step 4. Work continues on a verbal go-ahead, the change turns out to be more involved than either side expected, and now there is no signed document establishing what was agreed before the work started. By the time the invoice arrives, the two sides remember the conversation differently.

What Most EPCs Get Wrong About Change Orders

The most common mistake is treating every change order request as adversarial, when the majority are not. A differing site condition is nobody’s fault. Delaying approval of the change order to negotiate price while the schedule keeps slipping costs the EPC more in carrying costs than the disputed change order amount usually would have.

The second most common mistake runs the other direction: approving change orders informally and quickly to keep the project moving, without capturing scope or price in writing, which is exactly how scope creep accumulates unnoticed until a final invoice arrives 20% over the original contract with no paper trail explaining why.

The fix for both is the same. Set the change order process, the pricing method, and the revision count in the base contract, before either side needs it. A design vendor that includes clear change order terms in its standard agreement, rather than leaving the topic for an awkward mid-project conversation, is signaling that it has run this process enough times to know where it usually breaks down.

Change Orders vs. RFP Scope and Milestone Payments

It helps to place change orders correctly in the project lifecycle. The RFP response process defines scope, deliverables, and pricing before a contract is signed, when both sides still have full flexibility to negotiate terms. A well-structured RFP response reduces the number of change orders a project generates later, because ambiguous scope at RFP stage is the single biggest source of “was this included or not” disputes mid-project.

Milestone billing governs how payment for the already-agreed scope gets released across the project timeline, tied to delivered documents like a stamped plan set rather than external events like AHJ approval. A change order sits between these two: it modifies the scope and price that milestone billing then tracks against. If a change order adds a new deliverable, it should also specify which milestone payment it attaches to, so the payment schedule does not silently fall out of sync with the actual scope of work.

How Heaven Designs Handles Change Orders

Every Heaven Designs engagement states the included revision count and the change order pricing method in the proposal, before the contract is signed. When a differing site condition, AHJ redesign request, or interconnection change comes up mid-project, our engineering team documents the trigger, scopes the specific work with a fixed quote where the scope is boundable, and sends a written change order for sign-off before resuming design work on the changed scope. If you are structuring change-order terms for an active solar permit design or detailed engineering contract and want a second read on the language, our team can review it. Reach out through our contact page or request sample design deliverables to see how our change order documentation is structured in practice.

Conclusion

Three things reduce change order friction on an active solar design contract. First, state the included revision count, the pricing method, and the approval process in the base contract, not after the first change is needed. Second, treat every scope change, however small, as a documented change order rather than an informal favor, because undocumented small changes are what accumulate into disputed final invoices. Third, never resume work on a changed scope without a signed change order, even under schedule pressure, because verbal agreements are what create the “we remember this differently” conversation at invoice time.

Frequently Asked Questions

What is a change order in solar design?

A change order is a written, signed amendment to a solar design contract that modifies scope, cost, or schedule after the original agreement is in place. It documents what changed, why, the added cost, and the schedule impact, and it requires approval from both the client and the design vendor before the changed work begins.

Who pays for a change order caused by differing site conditions?

Under standard construction contract practice, differing site conditions are typically the responsibility of whichever party the contract’s DSC clause assigns the risk to, usually the owner or client, since neither party could have priced for conditions that were not knowable at bid stage. The design vendor’s original quote assumed the site data provided was accurate, so redesign work triggered by inaccurate site data is standard change order territory, not something the vendor should absorb for free.

How many revision rounds are normal before a change order applies?

Two to three included revision rounds is typical for a solar design contract, covering routine AHJ plan check comments and minor client feedback. A revision that requires re-running structural or electrical calculations, or that responds to a jurisdiction requiring a materially different design approach, usually falls outside included revisions and into change order territory.

Can a design vendor refuse to start a change without a signed change order?

Yes, and a vendor with clear contract language is within its rights to do so. Vendors that proceed on verbal approval to avoid delaying the client are the ones most likely to end up in a payment dispute later, because there is no written record establishing the agreed scope and price before the work happened.

Does a utility interconnection requirement change count as a change order?

Yes, if it requires design rework beyond what the original contract scoped, such as adding active power control hardware or revising the single-line diagram to meet a lower export cap than assumed. Since interconnection technical review outcomes are outside either party’s control, this is typically treated similarly to a differing site condition trigger.

What is the difference between a change order and scope creep?

A change order is a documented, priced, and approved scope change. Scope creep is the same kind of change happening informally, through email requests and verbal agreements, without ever being captured as a change order. Scope creep is what a disciplined change order process is designed to prevent.

Should change order pricing use a fixed quote or hourly billing?

A fixed quote works best when the added scope is clearly boundable, such as a specific redesign task. Hourly billing against a not-to-exceed estimate works better for open-ended requests where the full scope is not knowable until exploratory work is done. Both are more dispute-resistant than an undefined percentage markup, provided the method is agreed in the base contract before any change order is needed.

How does a change order affect milestone billing?

A change order that adds deliverables or shifts the schedule should specify which milestone payment it attaches to, so the milestone payment schedule stays in sync with the actual scope of work. Without that update, a client can end up disputing a milestone invoice that reflects scope the change order already modified.