Answer
When field conditions differ from the released solar project basis, record the observation, follow the applicable stop-work procedure, route the question to a named decision owner, and send the approved outcome to every team that could act on the old version. A phone call between crew and office is not change control.
Reporting a field difference makes it visible. Resolving it informally can leave other teams acting on an outdated project basis. A roof feature differs from the drawing. The equipment route is narrower than expected. A service detail does not match the available record. A customer asks for a last-minute adjustment. These discoveries are normal in site work; silent changes are not.
This guide helps installers and EPCs set up a communication path for field discoveries. It does not provide safety, engineering, electrical, contractual, authority, or installation instructions. Those require project-specific procedures, qualified judgment, and current requirements. Its focus is the information chain: observation, decision, revision, and distribution.
Last updated: November 2026. SurgePV publishes this post and sells solar design software.
Why Informal Fixes Become Expensive Later
An experienced installer may be able to see a practical way around a site condition. That judgment can be valuable. But a local adjustment may affect the design record, quantities, electrical assumptions, customer scope, access plan, warranty information, or later service work. If the update stays in a phone call, the next team can continue from the old basis.
The issue is not bureaucracy. It is traceability. The US Occupational Safety and Health Administration’s solar electrical-hazard guidance identifies shock and arc-flash hazards. Its scope is US guidance, so other jurisdictions have their own rules. A generic communications article cannot decide whether a crew should proceed in a particular condition. It can require the team to make the observation visible and route it instead of treating it as a minor inconvenience.
Define the Difference Before Naming the Solution
The first message should record facts, not conclusions. State where the condition was observed, what was expected from the released record, what appears different, what evidence is attached, and which activity is affected. “Roof obstruction conflicts with the issued layout at array zone two; photographs and location note attached” is actionable. “Need new design” may be true, but it skips the information that lets the right person decide.
| Record element | Useful wording |
|---|---|
| Project and revision | Identify the current field package or release being used |
| Observation | Describe what was seen without guessing at cause |
| Evidence | Time, photo, drawing reference, measurement or note as appropriate |
| Immediate boundary | State which work is paused, isolated, or awaiting direction under procedure |
| Potential effect | Layout, equipment, access, scope, schedule, document, or customer decision |
| Owner | Name the role responsible for the next answer |
Separating observation from solution is important. The site team may propose an option, but the record should make clear what is observed and what needs review. That protects the crew from being asked to authorize a decision outside its role.
Key Takeaway
Write the observation as a fact (“expected X, found Y, here is the photo”) and keep any proposed fix in a separate line. A record that mixes the two invites approval of a solution nobody reviewed.
Keep site inputs and design revisions connected
Bring a field-change example to a SurgePV demo and ask how revised design outputs and the customer-facing proposal would be handled.
Book a DemoChecking cost first? See the SurgePV pricing page · No commitment required · 20 minutes
Use a Short Triage Path
Not every discrepancy deserves the same response. Triage asks what decision is affected and when it is needed.
- Safety or stop-work question: follow the applicable project and employer procedure immediately; do not use a content workflow as a substitute.
- Release conflict: pause the affected activity and route the condition before the released basis is changed.
- Information gap: collect the missing evidence, identify the decision owner, and set a response time.
- Customer or scope request: record the request separately from the field observation and route commercial approval as needed.
- Minor documented variation: use the organization’s approved process to confirm whether it needs a revision, notation, or no further action.
A safety condition may require a broader stop than the immediately affected task. Follow the applicable safety and project directions; unaffected work may continue only where the responsible process permits. This communication framework does not determine an electrical isolation method or a safe work boundary.
The hazards behind a stop-work call are real. OSHA’s solar guidance sets these reference points for installation work:
Sources: OSHA solar falls guidance and OSHA solar electrical guidance, checked November 2026. Your own procedure and local rules govern the actual stop-work boundary.
Route the Question to the Decision Owner
Field communication is most effective when it names the question rather than broadcasting a problem. “Does this condition require a layout revision before installation continues?” directs the issue to a design owner. “Does the proposed alternative affect the approved customer scope?” directs it toward commercial ownership. “What current documentation governs this electrical question?” identifies the required technical route.
No job title should be presumed to own every answer. The relevant person may be a project manager, designer, procurement owner, qualified reviewer, customer contact, or another role under the project process. The field team’s responsibility is to provide usable evidence and preserve the boundary until direction is received.
For lifecycle context, see NREL’s Best Practices for Operation and Maintenance of Photovoltaic and Energy Storage Systems, 3rd edition (NREL/TP-7A40-73822, December 2018), which aims to improve how PV and storage systems are operated and maintained over their life. A clear change trail serves that same long view. It is not permission to alter an installation.
Make the Decision Specific and Time-Bound
An answer such as “okay to proceed” is weak unless it says what is okay, under which revision, and what remains required. Strong direction names the affected area, the change or decision, the documents to update, the person who authorized the release under the relevant process, and the next communication needed.
For example, a project manager might record that an activity can continue under an identified temporary boundary while a design question is reviewed. Or a design owner might issue a revised record for a named portion of work. The exact form depends on organizational and project controls. Record the authority for that decision and its limits. A project-manager note cannot waive a required qualified review, permit condition, safety procedure, or customer authorization. A later reader should be able to distinguish a temporary restriction from a revised release.
Update Every Artifact That Carries the Old Assumption
Field changes fail when an approved decision reaches the crew but not procurement, or reaches the customer but not the design record. After the decision, scan the affected artifacts.
| Artifact | Change question |
|---|---|
| Field package | Can the crew identify the current instruction and revision? |
| Design record | Does the current project layout or technical output reflect the decision? |
| BOM or order | Did the condition alter components, quantities, or purchasing assumptions? |
| Proposal or scope | Does customer-facing information still match the project basis? |
| Schedule and access plan | Did work sequencing, visit timing, or site coordination change? |
| Closeout record | Will a future owner need to understand this variation? |
Do not assume an updated drawing solves every item. If the customer promise changed, the customer-facing owner needs a controlled communication path. If equipment changed, procurement and field documentation need the same current basis.
When evaluating solar design software, ask how a revised output is identified and handed to the project record. Check document-history and distribution features in the actual workflow, and do not assume automatic field-change control. The responsible team must determine whether the condition is safe, permitted and commercially acceptable.
Pro Tip
Keep a one-line “artifacts to update” checklist on every change record: field package, design record, BOM, proposal, schedule, closeout. Tick each one before closing the item, so nothing is left on the old revision.
See how a revised design reaches the proposal
Ask for a live example: change a layout, then see how the updated output carries into the customer-facing package.
Book a DemoChecking cost first? See the SurgePV pricing page · No commitment required · 20 minutes
Before closing the communication item, record the revision sent, its recipients, and their acknowledgment where the project process requires it. Receipt confirms that an instruction arrived; it does not prove engineering approval or correct execution. If the crew still holds an older package, resolve that mismatch before using the closure status. Link the change to the affected requirement record and revisit the installation-readiness review when the released basis changes.
Keep the Customer Conversation Accurate
A field discovery can create understandable concern. Explain the condition using facts, not assurances that have not been reviewed. State what was observed, what is being assessed, whether the existing scope or schedule is affected at that point, and when the customer can expect the next update. If the scope or price changes, the revised solar proposal is the controlled place to show it.
Avoid telling the customer that an outcome is guaranteed before the appropriate review. Avoid technical detail that creates more confusion than clarity. The aim is a transparent next step: the team has identified a condition, recorded it, and is returning with a controlled answer.
Learn From Repeated Field Differences
Review recurring change categories at a cadence suited to project activity and risk. If access routes are repeatedly missing from early records, improve intake and survey questions. If equipment substitutions arise late, review procurement timing. If roof features routinely conflict with preliminary imagery, change the confidence label and field-verification triggers.
This is not a performance benchmark. It is a feedback loop. Each repeated difference identifies an upstream assumption that can be made more visible or checked earlier. Use the results to improve the project record, not to blame the person who reported a site condition.
Preserve the Original Evidence Alongside the Resolution
Do not overwrite the first observation when the team reaches a decision. Keep the original photo, note, location reference, and date attached to the controlled change record, then add the review outcome and current revision. The before-and-after trail matters when a later person asks why the installed condition differs from an early layout or why an additional customer communication was issued.
Evidence should be proportionate. A clear site photograph and referenced drawing area may be enough for one issue; another may need a specialist report, current manufacturer documentation, or a return visit. The record is not a substitute for that assessment. It makes the assessment request precise and ensures the conclusion can be traced back to the condition that prompted it.
When a proposed answer is rejected, record that outcome as well. It prevents an old workaround from reappearing later as if it were approved. A rejected option can also teach teams which assumptions need earlier validation in future project intake or site-survey planning.
Practical Next Steps
- Give field teams a one-page observation record that distinguishes facts from proposed solutions.
- Require a named decision owner and release boundary for every material field difference.
- After approval, update every document and audience that could act on the old basis.
To see how design revisions and customer-facing outputs connect, book a SurgePV demo and bring a real field-change record. Pricing is on the pricing page.
Frequently Asked Questions
What is a field change in a solar project?
A field change is an observed condition or customer request that differs from the released project basis. It can affect scope, design, equipment, safety planning, schedule, cost, documentation or customer commitments. Record the observation and route the decision, rather than assuming a practical workaround is approved.
Should a solar crew stop work whenever it finds a difference?
It depends on the condition and on the project, employer, safety and technical procedures that apply. Follow required stop-work directions, preserve evidence where it is safe to do so, and get responsible direction before treating the difference as approved. A hazard may need a wider stop than the affected task.
Who needs to receive a field-change decision?
Everyone who may act on the previous basis: the crew, design owner, project manager, procurement owner, customer-facing owner, and the closeout or service record where relevant. The change record should list which documents and audiences were updated.
What should a solar field change record include?
It should include the project and revision, what was expected, what was observed, evidence such as photos and measurements, the work paused under procedure, the potential effect, and the owner of the next answer. Keep facts and proposed solutions on separate lines.
How do you tell a customer about a solar field change?
State what was observed, what is being assessed, whether scope or schedule is affected so far, and when the next update will come. Do not promise an outcome before the review is done. If scope or price changes, issue the revised proposal through your normal approval path.
Can design software handle solar field change control?
Do not assume it does. Ask how a revised output is identified, who receives it, and how the document history is kept. SurgePV supports design outputs and proposal generation, but the responsible team still decides whether a change is safe, permitted and commercially acceptable.
Sources
Primary research and reference material used for this desk-research article.
Where this fits
This article is part of SurgePV's Solar Business & Operations hub, which works through the topic from first principles to the decisions a project team actually has to make.


