
What Should a Good Solar Change-Order Process Look Like?
A good solar change-order process should make one thing unmistakable: what changed, why it changed, what else the revision affects, and who authorized it. Ask Solar Mike includes written change-order control as part of project delivery . The homeowner should be able to compare the original scope with the proposed revision before authorizing the change .
Ask Solar Mike handles design, permitting coordination and project management . Use this solar change-order guide to evaluate the paperwork rather than relying on a verbal summary.
What should happen before a solar change is authorized ?
The proposed change should begin with the current, agreed project baseline. That baseline may include the equipment list, panel layout, battery plan, backup priorities, electrical scope and project documents. Without a named baseline, the homeowner is left comparing two conversations instead of two versions.
A useful change request should answer these questions in order:
- What is changing? Identify the drawing, component, quantity, location or responsibility being revised.
- Why is it changing? State the condition that led to the revision, such as a verified site condition, engineering review, equipment decision or homeowner request.
- What remains unchanged? Preserve the unaffected scope instead of reopening the entire project.
- What else must be checked? Review the revision against the backup plan, electrical architecture, permitting documents, equipment list and project sequence .
- What requires authorization? Mark the proposed version clearly and obtain the homeowner’s written decision before treating it as the working scope .
The goal is not paperwork for its own sake. The goal is a traceable decision: the homeowner can see the original condition, the proposed revision and the resulting project version in one place.
What belongs in a useful change-order worksheet?
A one-page worksheet can prevent a long email chain from becoming the project record. It should be specific enough that a homeowner, designer and field crew would identify the same revision.
| Field | What to record | Why it matters |
|---|---|---|
| Baseline version | The dated proposal, drawing or scope being changed | Prevents comparison against an obsolete version |
| Requested revision | The exact addition, removal, substitution or relocation | Separates the decision from the explanation |
| Reason | The verified condition or homeowner request behind the change | Shows why the original plan is being reconsidered |
| Affected documents | Project records affected by the written change . | Identifies what must be revised together |
| Unchanged scope | The portions of the project that remain intact | Stops a narrow revision from becoming an ambiguous redesign |
| Decision record | Accepted, declined or returned for clarification, with a date | Creates a clear working version |
How should a site condition be handled?
A site condition should not be translated immediately into a vague statement that “the design has to change.” The company should show the condition, identify the part of the baseline it affects and explain the proposed response. If more than one reasonable path exists, the choices should be separated so the homeowner can compare them.
The key distinction is between discovery and decision. Discovering a roof, service-panel, equipment-location or routing condition does not by itself define the revised scope. The condition must first be connected to the specific design element that needs reconsideration.
Ask Solar Mike designs for both 200A and 400A service panels, while the actual backup architecture is confirmed through site verification and engineering . That is why a preliminary preference—such as wanting the entire home backed up—should not be confused with a completed engineering decision.
How does engineering fit into the revision?
If a proposed change affects the technical design, the revised documents should move through the appropriate design review rather than being treated as a field note. Every system design is produced and reviewed by a licensed engineering firm .
The homeowner does not need to perform the engineering review. The homeowner does need a plain-English explanation of what is being revised and a final record that matches the project being delivered. The technical drawing and the customer-facing change record should refer to the same equipment, locations and scope.
For broader context on equipment and architecture, review the Utah Tesla solar guide and the Tesla Powerwall 3, Enphase and EG4 comparison. Product comparison and change control are different decisions: one selects an approach, while the other preserves a clear record when that approach is revised.
What are the warning signs of a weak process?
Pause and request clarification when any of these conditions appears:
- The revision is described only in a call or text message.
- The company cannot identify which drawing or scope version is current.
- A component changes, but no one checks the related layout, electrical plan or backup priorities.
- The explanation lists what is new but not what was removed.
- The homeowner is asked to authorize a revision without seeing the resulting scope.
- Different project records show different equipment or locations.
- The final handoff preserves the original documents instead of the completed version.
These signs do not prove that the underlying revision is wrong. They show that the decision record is incomplete. A sound technical choice can still create confusion if the paperwork does not identify the governing version.
How should commercial questions be separated from scope questions?
First define the technical revision. Then document whether the project’s commercial terms change. Combining those conversations too early makes it difficult to tell whether the homeowner is evaluating the design, the terms or both.
A useful record should therefore show the scope difference independently, even when the commercial terms remain unchanged. Homeowners researching a new project can review the separate Utah Tesla solar and Powerwall cost guide for current system-cost context.
What should match at project handoff?
The completed-project records should match the system that was actually delivered. Ask Solar Mike provides a commissioning receipt, system registration proof, monitoring handoff, a homeowner ownership record, a named escalation path and written change-order control .
Use those records as a final reconciliation point. Confirm that the equipment list, approved revisions, monitoring setup and ownership record describe the same completed project. If a revision occurred, the final file should preserve the decision without forcing the homeowner to reconstruct it from messages.
Ask Solar Mike handles design, contracting, permitting coordination and project management; installation is performed by licensed, insured crews under our Utah contractor license . The applicable Utah DOPL license is #14015846-5501 .
Frequently asked questions
Should every small solar revision require a written record?
If the revision changes the equipment, layout, responsibilities, backup plan, governing documents or project scope, it should be recorded. The length of the record can match the size of the change, but the current version should remain clear.
What if the homeowner requests the change?
Use the same process. Record the request, show the resulting revision, identify the affected documents and obtain written authorization. A homeowner-requested change can still affect several connected parts of the design.
Is an updated drawing enough?
Not always. A drawing can show the result without explaining the reason, the replaced version or the homeowner’s decision. Pair the revised drawing with a short change record that connects those items.
What if the company says the revision is required?
Ask which verified condition requires it, which part of the original scope is affected and what document supports the revised approach. The answer should be specific enough to review rather than a general statement that the project “will not work” otherwise.
When should the final change record be checked?
Check it when authorizing the revision and again during final document handoff. The second check confirms that the completed-project records reflect the version that governed the work.
Do you want a solar proposal with written scope control?
Request a design consultation to discuss the home, backup priorities and proposed project scope. Ask Solar Mike is a Utah Tesla solar and Powerwall 3 specialist focused on correctly sized backup for larger homes .
