6 Changes That Require a Solar SLD Review

A single-line diagram can remain visually tidy after the project beneath it has changed. That is what makes stale SLDs dangerous to workflow control. A substituted module, moved inverter, new battery, revised service point, or authority comment may alter only a few marks on the page, yet those marks can govern equipment schedules, labels, conductor information, protection, and field instructions.

This guide is for solar designers, project engineers, installation managers, and operations leaders deciding when a solar SLD must return to review. It covers change control, not jurisdiction-specific electrical design. The adopted code, authority requirements, utility rules, manufacturer instructions, engineering judgment, and verified field conditions remain controlling.

The six triggers below are deliberately broader than “the drawing changed.” Review begins when the technical basis changes, even if nobody has edited the drawing yet. That distinction catches revisions while they are still manageable.

Define review by consequence, not by drawing appearance

An SLD review is a documented decision about whether the current electrical representation still matches the project. It asks whether the source inputs are current, the equipment and connections are consistent, and the package is suitable for a named purpose. It does not mean reopening every settled choice after a spelling correction.

The National Fire Protection Association’s NFPA 70 development page identifies the National Electrical Code as the benchmark for safe electrical design, installation, and inspection in the United States. A project must still establish which edition and local amendments its authority has adopted. A generic reference to “the NEC” does not answer that project question.

Use a consequence screen before deciding the review depth. Ask whether the change can affect any of the following:

• electrical ratings, operating ranges, or equipment compatibility;
• conductor, overcurrent protection, disconnect, grounding, or labeling information;
• the point of interconnection or the way generation interacts with the service;
• an approved equipment list, permit package, utility submission, procurement release, or field set;
• an assumption used by a calculation or a note relied on by another discipline.

If every answer is no and the evidence is recorded, a limited document-control check may be enough. If any answer is yes or uncertain, route the SLD through technical review. “It looks almost the same” is not a technical finding.

That table is a routing aid rather than an approval matrix. The party authorized to accept a change depends on the project. Internal quality control should never be presented as engineering or authority approval.

What should an SLD change-impact screen contain?

An SLD change-impact screen should identify the trigger, current and proposed source values, affected equipment or relationships, governing evidence, decision owner, diagram elements, calculations and schedules, downstream documents, submissions, field work, and release status. It should distinguish a proposed change from an accepted one, so drafting, procurement, sales, or installation cannot treat an unresolved request as the new project basis.

Use one screen before choosing review depth. The purpose is not to answer the technical question. It tells the team which questions exist, who may answer them, and where the former decision appears. A small visual edit can have a wide impact; a large redraw can sometimes represent a narrow documentation correction.

Use this impact table:

Use this copy-ready change screen:

Trigger and date:
Active SLD and project revisions:
Current approved basis:
Proposed or corrected basis:
Authorization state:
Affected electrical relationships:
Affected diagram elements and references:
Downstream records and submissions:
Work allowed before decision:
Qualified reviewers and external notifications:
Closure evidence and release effect:

Do not mark “no impact” without a reviewer and basis. The value of the screen comes from explicit nonimpacts as well as changes. If a qualified role decides that an artifact needs no visible revision, record why and whether its review status remains current.

Keep the screen connected to one accepted change record. If several requests arrive together, list them separately before combining compatible work into a release. Otherwise a rejected substitution can accidentally ride inside an approved site correction.

1. The array configuration or selected module changes

Changing the array can alter more than module count. A new module may have different voltage, current, temperature coefficients, dimensions, connector information, and listing or installation conditions. A revised roof layout may move modules between orientations or shade conditions. An added row may push a string beyond a design boundary even though the total DC capacity changes only modestly.

Start the review with the current manufacturer documentation and the actual proposed string map. Do not compare products by nameplate wattage alone. Check whether the new array description on the SLD agrees with the layout, equipment schedule, stringing record, and analysis file. If a planning model and a released drawing describe different counts, stop and reconcile them before choosing which one is “right.”

The U.S. Department of Energy explains that PV system design involves modules, mounting structures, inverters, storage where used, and connections among system components in its solar photovoltaic system design overview. That overview supports the system-level point: one component choice sits inside a connected design. It does not validate a project-specific string length or equipment pairing.

An array change should prompt these checks:

1. Compare the proposed module’s current documentation with the module identified in the design basis.
2. Rebuild or verify each affected string rather than editing only the displayed module total.
3. Confirm that the inverter inputs shown on the SLD match the layout and string schedule.
4. Revisit conductor, protection, connector, and labeling information wherever the change can affect them.
5. Reconcile the bill of materials, proposal, permit set, and procurement status with the accepted design.

The practical test is whether another person could install, inspect, purchase, or explain the system from the current records without guessing which array version controls. If not, the SLD review is unfinished.

2. The inverter, optimizer, or power-conversion equipment changes

An inverter substitution is a topology and ratings question, not a catalog swap. The proposed unit can differ in input channels, operating windows, current limits, output rating, integrated disconnects, protection functions, communications, and installation conditions. Module-level power electronics can add their own compatibility and rapid-shutdown considerations. The SLD must describe the equipment actually intended for the site.

Read the new product documentation alongside the current drawing. Check the AC and DC sides separately. On the DC side, trace every string to the input arrangement and confirm that the design assumptions still apply. On the AC side, revisit output conductors, protection, disconnecting means, panel or switchboard connection, and any control or monitoring relationships that appear in the package.

Product certification also has a defined scope. UL describes its work for photovoltaic and solar system testing and certification, including components such as modules, inverters, and other solar equipment. A certification mark is not permission to ignore the product’s conditions of use or the project’s adopted requirements. Reviewers need the exact model and current documentation.

Procurement pressure can make this trigger easy to mishandle. A distributor may offer an available inverter after the specified model becomes difficult to obtain. Operations sees a schedule fix; design sees a different electrical device. Both views are legitimate, which is why the substitution request should include the proposed model, supporting documents, requested decision date, and affected purchase order before approval.

Do not let “approved equal” become a silent category. Equal for what purpose? Mechanical fit, electrical ratings, listing scope, communications, warranty, and customer contract are separate questions. The SLD reviewer owns only the electrical and documentation questions within their authority, while other owners close the rest.

3. Storage, backup, or operating mode is added or revised

Storage changes the system story. A grid-following PV system, a PV-plus-storage system, and a system intended to serve selected loads during an outage do not share the same connections or operating assumptions. Adding a battery late in the sales process can introduce new power-conversion equipment, disconnects, protection, load selection, control logic, labels, and emergency information.

The review should begin with the intended operating modes written in plain language. State what is expected to happen when the grid is present, when it is absent, during charging, and during any maintenance or emergency isolation. Then compare that narrative with the SLD. A line on a drawing cannot carry an operating concept that the project team has never agreed upon.

Use the manufacturer’s current instructions for every proposed component and combination. Identify which loads, if any, are intended to remain energized, how that load set was established, and which questions require field or qualified electrical review. Do not infer whole-building backup from a battery icon in a proposal. Likewise, do not treat an early sales option as an accepted construction configuration.

The relevant interconnection framework may also change. IEEE describes IEEE 1547-2018 as establishing criteria and requirements for interconnection of distributed energy resources with electric power systems interfaces and associated interoperability. The project’s applicable utility process and adopted requirements still decide what must be submitted and accepted.

Storage revisions deserve an explicit cross-document check:

A team should not issue the updated proposal while leaving the electrical revision “for later.” That sequence lets a customer-facing promise outrun the design evidence.

4. The service, point of interconnection, or utility direction changes

A service change can invalidate a large part of the prior electrical reasoning while leaving the array untouched. New service information may reveal a different rating or configuration. A utility response may require a different connection approach. A field visit may show that the assumed equipment location or routing is impractical. Each case sends the SLD back to the evidence.

Separate observed facts from proposed design. A photograph can show a label or physical condition, but the reviewer must confirm that it belongs to the correct site and date. A customer statement can flag a service upgrade, but it does not establish the completed condition. A utility email may address one revision and not another. Record provenance beside each important input.

The revised review should compare:

• current service and distribution information;
• the proposed point and method of interconnection;
• equipment ratings and protection shown in the SLD;
• utility comments, application version, and response date;
• any site or routing constraint that changed after survey;
• permit, drawing, and label sets already released.

Avoid universal language about what a utility “always allows.” Interconnection rules, tariffs, forms, and engineering practices differ by service territory and can change. Use the serving utility’s current documents for the actual project. IEEE 1547 provides a standards framework, while the local process supplies the project-specific path.

For a scoped U.S. utility example, PG&E’s interconnection handbook index separates technical requirements, supporting addenda, equipment information and single-line drawing examples. Its base manual and supplementary records have different dates. Retrieve the documents that govern the actual application and ask the serving utility how an equipment or topology change affects the current approval. These materials apply to PG&E’s process; they are not a worldwide substitution rule.

Field access and installation planning belong in the same conversation. OSHA’s construction standard for fall protection duties sets requirements for walking and working surfaces in covered construction activities. The SLD is not a safety plan, but a changed equipment location or route should not be accepted from a desk drawing when safe access, working space, or field feasibility remains unresolved.

When service evidence is incomplete, label the design stage. An indicative SLD may support a feasibility discussion if its assumptions are visible. It should not be issued as a final field instruction. The release status must travel with the sheet, not live in one person’s memory.

5. Conductors, protection, disconnects, or equipment locations change

Some changes arrive as field questions rather than formal redesign requests: the intended raceway route is blocked, a disconnect cannot be mounted where shown, a conductor length or pathway changes, or available equipment differs from the schedule. Treat these as design inputs, not invitations to improvise an undocumented final condition.

The first task is to capture what was found. Use dated photographs, marked plans, measurements where appropriate, the proposed response, and the name of the person reporting it. Then identify which documents and calculations rely on the former condition. The SLD may need a revised equipment location, conductor description, protection scheme, or note. The site plan, elevation, schedule, labels, and installation instructions may also move.

Review boundaries matter here. A project manager can document the request and stop affected work. A designer can evaluate the drawing and coordination impact within their role. A qualified electrical professional may need to decide technical adequacy. The authority or utility may need a revision. Good change control routes the question to the right person instead of pretending one signature covers every concern.

Use a field-change ticket with seven entries:

1. exact location and current drawing revision;
2. observed conflict, supported by a photograph or measurement;
3. proposed change and reason;
4. equipment or material affected;
5. work paused, protected, or allowed to continue;
6. required reviewers and external notifications;
7. accepted revision and confirmation that superseded instructions were removed.

The ticket preserves the observed conflict and proposed response while crews are waiting. It tells the reviewer what must be answered now and which decisions can wait; it does not establish a particular turnaround or rework saving.

6. The governing requirement, authority comment, or release purpose changes

The same electrical design can face a different review question when its governing context changes. An authority comment may request clarification. A utility may issue a new direction for the application. A project paused across a code-adoption date may need a requirements check. A concept sheet may be promoted into a permit or construction package. Each event changes what the SLD must demonstrate.

Never update a note from memory after a requirements comment. Attach the actual comment, identify the issuing organization, record the date and application or permit reference, and show how the response appears in the revised package. If the comment is ambiguous, ask the issuer or responsible reviewer rather than filling the gap with a confident interpretation.

Release purpose deserves equal attention. A preliminary drawing may contain open dimensions, provisional equipment, or assumptions suitable for discussion. When that file becomes part of a permit, procurement, or field package, those conditions need resolution or controlled exceptions. The drawing did not become more reliable because its filename changed.

A requirements review should answer four separate questions:

• Which code edition, amendment, utility document, manufacturer instruction, or contract requirement applies?
• What exactly changed from the prior accepted basis?
• Which SLD elements and related records does that change touch?
• Who has authority to accept the response for the intended release?

The NFPA, OSHA and DOE references provide U.S. context; IEEE and UL references describe their stated standards or certification scope. None can identify every requirement at a particular address. Local adoption, site conditions, product instructions, and the responsible reviewers complete the record.

How should the team choose the depth of SLD rereview?

Choose SLD rereview depth by finding the earliest accepted input or decision the change can invalidate, then mapping every dependent relationship and release. Use document-control review for proven nontechnical edits, targeted technical review for bounded source changes, and broader coordination when topology, service, operating mode, requirements, or several disciplines change. Uncertainty itself triggers escalation rather than a guessed limited review.

Use this sequence:

1. Preserve the last issued SLD and the evidence that supported it.
2. Run the change-impact screen against the proposed or corrected source.
3. Identify the earliest project input or qualified decision that may no longer hold.
4. Map dependent calculations, schedules, diagram relationships, notes, and labels.
5. Map layout, stringing, BOM, model, proposal, submission, procurement, and field consumers.
6. Assign each reopened question to the role with authority to decide it.
7. Define work that may continue and work that must stop.
8. Repeat the necessary technical, parity, and release checks.
9. Compare the new issue with the prior release for unintended differences.
10. Notify recipients and record which former use is superseded.

Illustrative workflow example, not an electrical design approval: A module substitution request arrives after the SLD has been released for a named package. The replacement has a similar nameplate power, and the roof layout appears unchanged. Procurement asks whether document control can update the equipment name without reopening technical review.

The team screens the change rather than assuming equivalence. It routes current product documentation, stringing implications, displayed electrical relationships, schedules, model, bill of materials, proposal, and active submissions to their responsible owners. The SLD remains on its former approved equipment basis until those decisions are complete. Similar wattage does not determine review scope.

If qualified review establishes that some relationships remain valid, the record preserves those nonimpacts. If another input or document changes, it enters the new issue. The depth follows the evidence, not a rule that every substitution requires a complete restart or only a text edit.

Keep review scope separate from urgency. A field or customer deadline can change priority and escalation, but it cannot create missing evidence or transfer authority to the drafter. Where safe and permitted, the team may narrow the interim use while the decision remains open.

Teams lose control when a change moves through private messages, marked-up PDFs, and verbal approvals with no common status. A workable path can be short, but every step needs an owner and an output.

1. Capture the trigger. Record the request, field observation, substitution, comment, or changed project objective against the current revision.
2. Screen the consequence. Identify affected ratings, topology, calculations, documents, submissions, purchases, and field work.
3. Collect controlling evidence. Attach current product documents, site records, authority or utility communications, and the accepted design basis.
4. Assign review authority. Name the internal and external parties needed for this class of decision.
5. Revise connected records. Update the SLD and every schedule, drawing, model, proposal, or instruction that depends on it.
6. Issue for a named purpose. State whether the new set is for discussion, permit, procurement, construction, or another defined use.
7. Retire superseded versions. Keep history, but make the current set unmistakable where people work.

The review record should be readable by somebody who missed the original conversation. “Rev B per comments” fails that test. “Changed inverter model following approved substitution request SR-014; revised DC inputs, AC output schedule, disconnect note, BOM, and proposal equipment description” gives the next reviewer a path. The example is illustrative, not a claim about a customer project.

Keep the SLD, BOM, and proposal on the same revision

Electrical review does not end at the drawing border. A current SLD paired with an old equipment schedule can send the wrong item to purchasing. A revised array paired with an old production scenario can put a stale figure in front of the customer. A field set paired with a newer utility application can leave installers working from an abandoned connection concept.

Create a release register with the current SLD, layout, equipment schedule, bill of materials, analysis file, proposal, permit set, utility application, and field package. Record the revision and date for each. A mismatch is not automatically an error, since some records may be intentionally provisional, but the reason and allowed use should be visible.

Electrical design supports electrical workflow documentation, while Solar Proposals connects customer-facing output to project work. PV shade analysis and the Generation and Financial Tool support modeled scenarios. These tools can keep related work closer together, but they cannot decide which source is correct or approve an engineering change.

Results depend on source data, assumptions, equipment models, configuration, and review. Outputs support design and documentation workflows but do not replace approval by the responsible engineer, authority, lender, insurer, or utility.

When can a prior SLD review remain valid after a change?

A prior SLD review can remain valid only for decisions unaffected by the change. The impact record should identify the evidence, changed input, dependency path, qualified reviewer, and reason each retained decision still applies. The package still needs revision and parity control where displayed facts changed. Never preserve approval because the drawing looks similar or the prior reviewer is unavailable.

Treat retained decisions as scoped carryovers, not blanket approval. A reviewer may conclude that a label correction does not reopen technical calculations, while the issue set and revision note still need document-control review. A layout change may leave one equipment decision intact while reopening string membership and every dependent representation.

Use a carryover record:

Prior review and release purpose:
Changed input:
Prior decision considered for carryover:
Dependency check performed:
Evidence still current:
Qualified reviewer and disposition:
Artifacts still requiring update:
Condition that would reopen this carryover:

Do not copy an old approval mark onto a new sheet. The release package should show which review applies to the current revision and how any prior decision was carried forward. If the organization requires a new signature or formal act for the new issue, follow that requirement even when technical content is unchanged.

After distribution, watch for a mixed-revision field set. A current SLD beside an older layout, equipment schedule, or installation instruction can defeat careful carryover reasoning. Recipient acknowledgment should identify the package they received and the records it supersedes.

Once the revised set is issued, ask whether the process exposed the affected records early enough. Do not measure success by the absence of comments alone. A reviewer can miss something. Better operational questions examine traceability: Was the trigger connected to evidence? Did the right person decide? Were downstream records reconciled? Could the field and customer-facing teams identify the current version?

Track returned packages by reason without turning internal data into an unsupported industry benchmark. Useful categories include incomplete substitution evidence, stale site information, missed cross-document updates, unclear authority response, and uncontrolled field change. The pattern tells your team which intake form, review prompt, or release check needs attention.

The SLD should return to review whenever a change can alter the electrical story another person will rely upon. Six triggers make that rule operational: array configuration, power-conversion equipment, storage or operating mode, service or interconnection, conductors or locations, and governing requirements or release purpose. The discipline is simple to state and difficult to fake. Evidence changes, the review changes.

Frequently Asked Questions

Does every module substitution require an SLD review?

A module substitution deserves screening, and it requires SLD review when electrical ratings, string lengths, conductor choices, protection, labels, equipment compatibility, or the approved equipment schedule could change. A reviewer should compare the proposed module data with the current design basis instead of treating equal wattage as electrical equivalence.

Who should review a revised solar single-line diagram?

The required reviewer depends on jurisdiction, project stage, contract, and company authority. Internal design review can catch coordination problems, but it does not replace a licensed engineer, authority, utility, manufacturer, or other qualified reviewer when that party’s approval or judgment controls the project.

Can a field redline replace an updated SLD?

A field redline can preserve an observed change, but it is not automatically the final controlled drawing. The team should route the redline through its change process, test every affected calculation and document, obtain required review, and issue a clearly identified revision before relying on it as the current record.

Should a battery added after permit approval trigger review?

Yes. Adding storage can change equipment, operating modes, protection, disconnects, conductor paths, labels, service interaction, and emergency information. The revised design must follow current product instructions and the rules adopted for the site, with authority, utility, and engineering review handled where required.

What should an SLD revision note contain?

Record the change request, reason, source evidence, affected sheets and schedules, reviewer, decision, date, and release purpose. A useful note also identifies superseded versions and open conditions. Writing only ‘revised per comments’ hides the technical question and makes later reconstruction needlessly difficult.