How I build permit-ready plan sets with a solar CAD offline workflow
The array is the easy part. The plan set is where residential solar jobs stall. A crew can lay out 24 modules on a roof in an afternoon, then wait two weeks because the permit office kicked the drawings back for a missing setback dimension or an unclear label callout. I got tired of that loop, so I moved my whole submittal process to a solar CAD offline workflow that runs on my laptop with no cloud login. If you want to follow along, you can download the offline editor and open a blank sheet while you read.
This piece is not about panel placement — I wrote about that in my solar array design workflow. This is about the paperwork the array becomes: the site plan, the roof plan, the single-line diagram, and the label schedule that an authority having jurisdiction (AHJ) actually approves.
Why the plan set, not the array, is where solar jobs stall
Most residential PV permits are rejected for documentation, not engineering. The panels are fine. The problem is a plan set that a plans examiner cannot read in one pass: a roof plan with no fire-access pathways, a single-line that omits the rapid-shutdown device, or a label list that does not match NEC 690.56(C) and 705.12. Each of those is a resubmit, and each resubmit is another 5 to 15 business days on the calendar.
The 2023 National Electrical Code raised the bar again. Rapid shutdown under NEC 690.12, the labelling in 690.13, and the interconnection rules in 705.12 all have to be shown, not implied. An examiner wants a drawing that spells them out. When your design tool lives in a browser tab and only exports a rendering, you end up redrawing the whole thing in generic CAD anyway to get a compliant sheet.
There is a second cost that nobody prints on the invoice: connectivity. Cloud design tools assume a live session. On a rooftop in a new-build subdivision, or in a basement main-panel photo shoot, the signal drops and the tool logs you out. A solar CAD offline setup removes that failure mode entirely. The file is on the disk, the symbol library is on the disk, and the export runs on the disk. I tested this on a job with no service at all and produced the full sheet set on the tailgate before I drove back.
The solar CAD offline workflow I use for AHJ submittals
I built my submittal process around five sheets, and the whole point of a solar CAD offline tool is that all five come out of one file with one coordinate system. No re-scaling between apps, no re-keying dimensions.
The five sheets every AHJ wants
- Cover / site plan. Property lines, the structure, the array footprint, and the point of interconnection. Setbacks dimensioned, north arrow, scale bar.
- Roof plan. Module rows, fire-access pathways and setbacks per the local fire code, attachment spacing, and the conduit run to the inverter.
- PV single-line diagram. Strings, combiner if used, the rapid-shutdown device, inverter, AC disconnect, and the connection to the service. Wire sizes and OCPD ratings called out.
- Placard / label schedule. Every NEC label with its text and location, so the inspector checks a list instead of hunting the roof.
- Attachment / structural detail. The rafter attachment, flashing, and spacing that the structural reviewer signs off.
In the editor I keep each sheet as a viewport into the same drawing, so a change to the array on the roof plan updates the counts I reference on the single-line. When I add the rapid-shutdown device, it drops in as an IEC 60617 symbol with the callout attached, and it stays snapped to the wire. The label schedule reads from the same objects, which is how I stop the classic mismatch where the roof shows eight modules per string and the single-line still says ten.
For the electrical rules themselves I check the array configuration against IEC 62548 photovoltaic array design rules and the NEC references above, then freeze the sheet. When the drawing is done it exports straight to a dimensioned, multi-page PDF ready for upload — no watermark, no "upgrade to export" wall. If you want the same setup, the one-time lifetime licence covers the offline editor with no monthly fee attached.
A real submittal: an 8.4 kW rooftop in under a day
Here is a job that looks like most of my week. A composition-shingle roof, 24 modules at 350 W for 8.4 kW DC, two strings of 12, a single 7.6 kW string inverter, and rapid shutdown at the module level. The homeowner wanted the permit filed the same week.
I laid out the two string rows with a 0.9 m fire-access pathway to the ridge, dimensioned the setbacks, and dropped the conduit run down to the inverter on the side of the house. The single-line came together in maybe twenty minutes because the string count and the module wattage were already in the file — the same discipline a New York solar installer lays out a roof with, and close to the Chicago rooftop workflow I have written up for tighter city lots.
The label schedule was the part that used to eat an hour. This time it wrote itself from the placed devices: rapid-shutdown labels at the array and the service, the sign for the AC disconnect, and the interconnection placard. Total time from blank file to a five-sheet PDF was about four hours, most of it measuring the roof, not drawing. The permit came back approved on the first pass. That first-pass approval is the number that actually pays — every avoided resubmit is roughly two weeks I keep on the schedule.
How solar CAD offline compares to Aurora, PVsketch and AutoCAD
I want to be fair about the alternatives, because they are good tools for different jobs.
Aurora Solar and PVsketch are strong at sales design and shading yield. Aurora in particular does LIDAR-based shade analysis that a local tool cannot match, and it plugs into proposals. The trade-offs are that they are cloud-only and subscription-priced — plans that are billed every month, and the bill runs on before you have filed a single permit. If the signal drops, so does the session. For plan-set production specifically, you are often exporting and finishing the sheet elsewhere.
AutoCAD (and LT) will absolutely produce a compliant sheet, and plenty of shops run on it. It is also a general drafting package: AutoCAD LT costs $540 a year (Autodesk list price, July 2026) and full AutoCAD several times that and no solar-specific symbols out of the box — you build or buy the block library yourself.
A solar CAD offline tool sits in the gap: it runs on the laptop, it ships the PV and NEC symbol set, and it produces the permit PDF without a login. The one-time lifetime licence means the cost is paid once, which for a small install shop changes the maths against a bill that returns every year. For yield and shading I still reach for NREL's modelling, and I pair the design with NREL's SolarAPP+ automated permitting where the jurisdiction supports it — SolarAPP+ has processed well over 100,000 residential solar permits since it launched, which tells you where standardised plan sets are heading.
FAQ
Is a solar CAD offline tool accurate enough for a stamped permit set?
Yes, for the drawing. The geometry, dimensions, and NEC labels are all produced to scale and export to a clean PDF. Structural and electrical stamps still come from a licensed engineer where your AHJ requires them — the tool produces the sheet the engineer reviews, it does not replace the stamp.
Can I work with no internet at all?
That is the entire point. The file, the symbol library, and the PDF export all run locally. I have produced full five-sheet submittals on a rooftop with no service. Nothing phones home, which also means your client's address and roof data stay on your machine.
How is this different from your array design article?
The solar array design workflow covers laying panels on the roof, string routing, and setbacks. This article covers turning that array into the permit plan set — site plan, single-line, and the label schedule an inspector signs. Same file, later stage.
Does it handle the 2023 NEC rapid-shutdown and labelling rules?
The rapid-shutdown device, the 690.13 disconnect labelling, and the 705.12 interconnection callouts are all placeable symbols with attached text. Because the label schedule reads from the placed devices, the roof plan and the single-line stay in agreement instead of drifting apart on a manual list.
What does it cost compared to a subscription?
It is a one-time payment rather than a monthly plan. A cloud design subscription is billed every month; the offline editor is bought once. Check the current tiers on the pricing page before you buy.
Where this leaves your permit pipeline
The array was never the bottleneck. The plan set is, and a solar CAD offline workflow puts every sheet in one file that an examiner can approve on the first pass. That is fewer resubmits, no dropped cloud sessions on the roof, and design data that never leaves your laptop. I run my whole submittal process this way now, and the first-pass approval rate is the reason I have not gone back.
If you install solar and you file your own permits, try it on your next job — download the offline editor, rebuild your last approved plan set in it, and see how long the five sheets take. When you want to know what is landing next, the public roadmap shows what I am shipping into the solar workflow this quarter.