Generating Code-Compliant Solar Designs With Automatic Engineering Calculations

What Code-Compliant Actually Means for a PV Design

A plan examiner does not look at a solar design the way a salesperson does. The render that sells the homeowner, panels tucked neatly across the south face, means nothing to the city. The examiner opens the single-line diagram and starts checking numbers. Is the conductor between the modules and the combiner sized for the corrected ampacity? Does the overcurrent device protect that conductor and sit below the busbar limit? Is the rapid-shutdown method called out and labeled? Does the structural page show how the array load reaches the roof framing? Each of those is a line in the National Electrical Code, published as NFPA 70, and a design is code-compliant only when every one of them holds.

So code-compliant is not a style or a finish. It is a stack of specific engineering results that the drawings have to prove. The NEC, maintained by the National Fire Protection Association as NFPA 70, carries the rules that govern a PV system in Article 690 and the interconnection rules in Article 705, and the jurisdiction adopts a particular edition of it. A design that passes in a city on the 2020 code can fail in the next county on the 2023 edition because a rule changed. The calculations are the product. The pretty layout is the wrapper.

Why Plan Sets Come Back Rejected

Ask any installer where their projects lose time and the plan-check loop comes up fast. A set goes in, sits in a queue, comes back with correction notices, gets fixed, and goes back into the queue. Each round can add a week or more, and it happens before a single panel is mounted. The frustrating part is that the corrections are rarely exotic. They are small, repeatable errors in the same handful of places.

A conductor sized for its base ampacity without the temperature correction for a hot rooftop. An overcurrent device that protects the wire but exceeds the inverter busbar rating under the interconnection rule. A voltage-drop figure copied from a prior job that does not match this run length. A rapid-shutdown label missing from the set, or placed but not specified on the diagram. A structural detail that names a standoff but never shows the load reaching a rafter. None of these require a redesign. They require someone to catch the math before the examiner does, and on a manually drafted set, under deadline, that someone is the same engineer who is already stretched across six other jobs. The errors that trigger rejections are precisely the ones a computer is good at and a tired human is not.

Conductor and Overcurrent Device Sizing

Conductor sizing is where the most rejections start, because it is a chain of dependent steps and getting any one wrong invalidates the rest. The NEC requires PV source and output circuit conductors to be sized for continuous duty, which means the maximum current is multiplied by 125 percent before the conductor is chosen. For a PV source circuit that maximum current is itself 125 percent of the module short-circuit rating, so two stacked factors already apply before any environmental correction.

Then the ampacity has to be derated for conditions. Conductors on a hot roof run well above the ambient design temperature, and the NEC temperature-correction factors cut the allowable ampacity sharply once a raceway sits close to the roof surface. Fill matters too, because more than three current-carrying conductors in a raceway triggers an adjustment factor. The conductor has to clear both the corrected-ampacity check and the continuous-duty check, and the larger result wins.

The overcurrent device is the next link. It protects the conductor, so its rating cannot exceed the conductor's corrected ampacity, and on the interconnection side it has to satisfy the busbar loading rule in Article 705 so the combination of utility and solar backfeed does not overload the panel. Change the module, the inverter, the wire run, or the raceway and all of this shifts. Done by hand, that is a worksheet rebuilt every time. Done in software, the model holds the equipment and re-runs the chain the moment anything changes.

Voltage Drop and Ampacity Corrections

Voltage drop is not strictly a safety limit in most of the NEC, but plan examiners and utilities expect it documented, and an array that loses too much voltage on long runs also loses production the homeowner was promised. The calculation depends on the conductor material, its size, the one-way distance, and the current, and on a commercial roof with a combiner far from the inverter those runs get long enough to matter. A design that holds drop under a sensible target on the DC side and again on the AC side reads as engineered. One that ignores it reads as guessed.

The ampacity corrections feed straight back into this. A conductor upsized to hold voltage drop changes the overcurrent coordination, and a conductor chosen only for voltage drop still has to pass the corrected-ampacity and continuous-duty checks from the previous section. These calculations are coupled, which is exactly why doing them in isolated spreadsheets drifts. The Department of Energy's guidance on solar performance and efficiency is a reminder that wiring losses are real losses, not a paperwork formality, so the voltage-drop number on the plan set should match the number behind the production estimate the customer signed. When one model carries both, they cannot diverge.

Rapid Shutdown and Module-Level Electronics

Rapid shutdown is one of the most-cited parts of a modern PV plan set because it changed how arrays are wired. NEC 690.12 requires that conductors inside the array boundary and leaving it can be brought to a safe voltage quickly so firefighters are not working around an energized roof. In practice this pushes most residential and many commercial designs toward module-level electronics, either microinverters or DC optimizers, that reduce conductor voltage at each module when the system is shut down.

For the plan set, that means several things have to line up. The single-line diagram has to show the rapid-shutdown equipment and the initiation device. The labels have to state that the system has rapid shutdown and where the control is. The equipment selected has to actually be listed for the function claimed. A design that specifies a string inverter with no module-level device, then claims rapid-shutdown compliance, is an immediate correction. Because the requirement is tied to the specific equipment in the system, a platform that knows which inverter and which module-level device the design uses can flag the mismatch before submittal rather than leaving it for the examiner to find. This is also where equipment libraries earn their value, since the listed function travels with the part instead of living in someone's memory.

Labeling, Placarding, and the Single-Line Diagram

Labeling looks like the trivial part of a PV design and generates a surprising share of corrections. The NEC requires a set of placards and markings, including disconnect labeling, warnings about energized conductors on both line and load sides, the rapid-shutdown placard, and markings that identify the power sources at the service. Each has required wording and placement, and the adopted code edition can change the exact language. A set that is electrically perfect but short a label still comes back.

The single-line diagram is where the whole electrical story has to be legible in one page. It shows the modules, the strings, the combiner if present, the inverter, the disconnects, the overcurrent devices with their ratings, the conductor sizes and types, the grounding and bonding, and the point of interconnection. An examiner reads the diagram against the calculations and against the site plan, and any disagreement among the three is a correction. When those three documents are generated from one model, they agree by construction. When they are drawn separately, the diagram is where a stale number hides. PVComplete's engineering tools generate the single-line diagram and the equipment schedule from the same design that produced the layout, so the ratings on the diagram are the ratings the calculations used.

Structural Attachment and Load Paths

The electrical code is only half of code-compliant. The array also has to stay on the roof through wind and snow, and the structural page has to show it. That means the attachment method, the standoff or flashing used, the fastener into the structural member, the spacing of the attachments, and a load path that carries the dead load of the array plus the environmental loads into the framing and down to the foundation. On a commercial roof the governing loads come from the building code and the referenced load standard, and a structural engineer often has to confirm the existing roof can carry the addition.

For software, the useful contribution is keeping the attachment plan consistent with the layout and the loads. If the array moves, the attachment points move, and the spacing that satisfied the uplift calculation has to be rechecked. A platform that produces attachment plans and details alongside the electrical set keeps the structural story attached to the same geometry, so the detail on the plan matches the panel positions on the roof. The stamp still belongs to a licensed engineer, and the software does not replace that judgment. It makes sure the drawing the engineer stamps is internally consistent with everything else in the set.

How Software Automates the Calculations and Checks the Set

The difference between a drawing tool and an engineering platform is whether the software understands what the lines mean. A generic CAD program will let you draw a conductor of any size next to an overcurrent device of any rating and never object, because to the program they are just lines and text. An engineering platform knows the conductor carries current, knows the device protects it, knows the module's electrical ratings, and can therefore run the NEC calculation and tell you when the two do not agree.

PVComplete's PVCAD is built inside AutoCAD for exactly this reason. It carries an equipment library so the module, inverter, and balance-of-system parts bring their real electrical ratings into the model, it places the array and the electrical components as objects that know their own properties, and it generates the electrical diagrams and the permit and construction sets from that single model. Because the calculation is tied to the equipment, changing a part re-runs the affected math instead of leaving an old number behind, and the error-checking catches the mismatches that otherwise ride through to plan check. The honest caveat is that PVCAD is desktop software and needs an AutoCAD license, which is a real cost, and the trade is that you get full engineering control rather than a simplified estimate. For the earlier sales stage, PVSketch produces a fast layout and a one-click permit package, and the layout hands off to PVCAD when detailed engineering takes over.

What to Require From a Code-Compliance Platform

Not every tool that claims permit-ready output actually runs the engineering. When you evaluate a platform for code-compliant design, look past the sample plan set and test whether the calculations are real, tied to equipment, and traceable. This checklist separates software that computes from software that merely draws.

• It runs NEC conductor and overcurrent sizing with the continuous-duty factor, not a fixed wire-size lookup.
• It applies temperature correction and conduit-fill adjustment to ampacity for the actual raceway and climate.
• It computes voltage drop on both the DC and AC runs from the real conductor lengths in the design.
• It enforces rapid-shutdown requirements against the specific inverter and module-level device selected.
• It generates the single-line diagram, equipment schedule, and labels from the same model as the layout.
• It carries an equipment library so module, inverter, and balance-of-system ratings come from listed parts.
• It lets you set the adopted NEC edition and interconnection rules for the jurisdiction.
• It produces attachment plans and structural details that stay consistent with the panel geometry.
• It error-checks the set and reports mismatches before submittal rather than at plan check.
• It keeps a licensed engineer in the loop for review and stamp instead of implying the software is the authority.

Manual, Spreadsheet, and Software-Automated Engineering Compared

There are three common ways teams produce the engineering behind a plan set, and they are not equally reliable as volume grows. The table lines them up on the dimensions that decide whether a set clears plan check on the first pass.

Hand calculation is defensible on a one-off and indispensable for judgment, but it does not hold accuracy across a pipeline of jobs. Spreadsheets speed the arithmetic and still leave the diagram and the assembly manual, which is where drift creeps in. Automated engineering trades a license cost for calculations that stay tied to the design.

SolarAPP+ and the Shift to Automated Permitting

Automated engineering on the design side meets a matching shift on the government side. The Department of Energy's SolarAPP+, the Solar Automated Permit Processing platform, performs an automated code compliance check on a residential PV submission and, when the design passes, issues the permit instantly instead of routing it through a human plan-review queue. It works because the compliance rules are explicit enough to be checked by software, which is the same reason a design platform can check them before submittal.

The U.S. Department of Energy describes SolarAPP+ as an online platform that automates the permit review for code-compliant residential solar systems, running an instant compliance check so jurisdictions can issue permits immediately rather than through manual plan review, which cuts the delays that add to a project's soft costs.

U.S. Department of Energy, Streamlining Solar Permitting With SolarAPP+

Adoption is real and growing. The DOE has reported that more than 160 communities are automating solar permitting with SolarAPP+, which means a meaningful and rising share of residential projects can skip the plan-review wait entirely when the design is clean. The catch is that the automated check only rewards designs that are genuinely compliant, so the value of a platform that runs the engineering up front compounds here. A design that already satisfies the conductor, overcurrent, rapid-shutdown, and labeling rules is the design that clears an automated permit on the first try. Not every jurisdiction participates, and commercial projects still route through conventional review, so the practical play is to produce a compliant set regardless and let SolarAPP+ accelerate the jobs where it is available.

Compliance Mistakes That Trigger Extra Plan-Check Cycles

The same handful of mistakes drive most of the rework, and each traces back to a calculation done loosely or a document that drifted from the model. Catch these and the first-pass approval rate climbs.

Sizing conductors without the corrections. Choosing a wire from base ampacity and skipping the temperature and fill derate is the classic rooftop error, and it fails the moment the examiner applies the correction factor you left out.

Overcurrent devices that break the busbar rule. A breaker that protects the conductor but violates the Article 705 interconnection limit on the panel busbar is a frequent and avoidable rejection.

Stale numbers on the single-line diagram. When the diagram is drawn separately from the calculations, a mid-design equipment swap updates one and not the other, and the examiner catches the disagreement.

Claiming rapid shutdown the equipment does not provide. Specifying a plain string inverter and then asserting 690.12 compliance without a module-level device is an instant correction.

Missing or misworded labels. An electrically sound set that is short a required placard, or uses wording from an older code edition, still goes back for the label alone.

Designing to the wrong code edition. Using the NEC edition you are used to instead of the one the jurisdiction adopted puts correct-looking work on the wrong rulebook.

A structural detail with no load path. Naming an attachment product without showing the fastener reaching a structural member leaves the reviewer unable to confirm the array stays put.

The common thread is that every one of these is a calculation or a consistency check a platform can run before submittal. PVComplete's PVCAD builds the electrical engineering and the permit set from one model so the diagram, the schedule, and the labels agree, and the broader Enact platform carries that engineered design through proposal, permitting, and the handoff to install, so the set a reviewer stamps is the set the crew builds. The engineer's stamp is still the authority. The software's job is to make sure the numbers under it are right the first time.

Frequently asked questions

What makes a solar design code-compliant?

A design is code-compliant when it satisfies the National Electrical Code, published as NFPA 70, across conductor and overcurrent sizing, voltage drop, rapid shutdown, labeling, and structural attachment, for the code edition the jurisdiction has adopted. The pretty layout does not matter to a plan examiner. The calculations and the documents that prove them do. The NFPA 70 standard carries the PV rules in Article 690 and interconnection rules in Article 705.

Can software really generate code-compliant engineering calculations?

Yes, when the software understands the equipment rather than just drawing lines. An engineering platform carries the module and inverter ratings, runs the NEC conductor, overcurrent, and voltage-drop math against them, and re-runs it when a part changes. PVComplete's PVCAD does this inside AutoCAD and generates the single-line diagram and permit set from the same model. See PVComplete for the engineering tools. A licensed engineer still reviews and stamps the result.

What is SolarAPP+ and how does it relate to code compliance?

SolarAPP+ is the DOE's automated permit platform that runs an instant code-compliance check on residential solar submissions and issues the permit immediately when the design passes. It works because the compliance rules are explicit enough for software to check, which is the same logic a design platform uses up front. The DOE reports it is in use across more than 160 communities, though not every jurisdiction participates and commercial projects still use conventional review.

Why do solar plan sets get rejected at plan check?

Mostly for small, repeatable calculation and documentation errors, not design flaws. Conductors sized without temperature correction, overcurrent devices that break the busbar rule, stale numbers on the single-line diagram, missing rapid-shutdown labels, and structural details with no load path are the usual culprits. These are exactly the mismatches software can catch before submittal. Automated permitting through SolarAPP+ only clears designs that are already clean.

Does automating the calculations replace a licensed engineer?

No. The software removes the arithmetic errors and keeps the drawings consistent with the model, but a licensed engineer still reviews the design and provides the stamp the jurisdiction requires. The useful division is that the platform handles the repeatable NEC calculations and consistency checks while the engineer applies judgment, especially on structural load paths and unusual sites. The DOE's Solar Energy Technologies Office tracks how tools and standards shape project outcomes.

How does automatic engineering reduce permitting delays and soft costs?

By catching compliance errors before submittal, so sets clear plan check on the first pass instead of cycling through corrections. Every rejection adds a week or more to a project before anything is built, and that time is pure soft cost. A platform that runs the NEC math and error-checks the drawings, then feeds a clean design into automated permitting where available, compresses the loop. Enact carries the engineered design through proposal and permitting in one workflow (Enact).

Sources

1. NFPA 70 - National Electrical Code
2. DOE - Streamlining Solar Permitting With SolarAPP+
3. DOE - 160 Communities Now Automating Solar Permitting With SolarAPP+
4. DOE - Solar Performance and Efficiency
5. DOE - Solar Energy Technologies Office
6. DOE - Homeowner's Guide to Going Solar
7. PVComplete - PVCAD and PVSketch engineering tools
8. Enact - Solar design and proposal platform
9. SEIA - Solar industry research data