Solar Permitting Automation for Installers

What is solar permitting automation?

It covers two layers. The first is on your side: generating plan sets, filling AHJ forms and utility applications from design data, and tracking where each submission stands. The second is on the jurisdiction side, where platforms such as NREL's SolarAPP+ run an automated code check and issue the permit instantly for eligible residential systems.

In the SolarAPP+ pilot, NREL found projects were installed and inspected on average 12 business days faster than on the traditional process. In Tucson, Arizona review dropped from 24 days to under 1 day, and in Menifee, California from 8 days to under 1 day. Where your jurisdiction does not use an instant platform, the time is lost in resubmissions, and that is where installer-side software helps.

Not every project qualifies for an instant path. Commercial systems, ground mounts and unusual roof structures usually go through ordinary plan review, so a realistic setup treats instant permitting as one route among several and lets the software choose per project based on the jurisdiction profile and system type.

• Packet generation from design data
• Jurisdiction-specific checklists
• Submission and correction tracking
• Utility interconnection and net metering application status

Where do permits get rejected?

Rejections come from the same short list: a single-line diagram that does not match the equipment on the spec sheet, a missing structural note for roof attachments, a wrong rapid shutdown label, or a form revision the AHJ retired. These are checkable. A rules layer can compare the inverter model on the diagram with the datasheet on file, confirm the module count matches the string layout, and verify required labels appear.

Corrections are also a data problem. When a reviewer emails comments, the response often lives in an inbox. Software can log each comment against the project, assign it to a designer and show the revision history.

Keep a library of past rejections by jurisdiction. After a few dozen projects it shows which reviewers ask for roof load calculations, which want a site photo with the plan, and which reject unlabeled disconnects. Feeding that history back into the pre-submission checks is the cheapest accuracy gain available.

How do you handle interconnection and net metering?

Utility applications run on separate timelines and portals from the building permit. Some utilities accept web portal submissions, some use email and PDF forms, and tariff rules differ by state. Automation here means a status board per project with a due date for each pending application, reminders when approval is overdue, and a record of the permission-to-operate date, which usually gates final invoicing.

Net metering rules change by utility and state, so the system keeps a tariff table that a person updates and the software references, instead of embedding rules in code.

What can software read from a jurisdiction?

Portals vary. Some AHJs offer permit APIs or standard portal products, many offer only a login and an upload form, and others still take email. Vascoh builds to what each one offers: API calls where they exist, structured email parsing where they do not, and a manual confirmation step for portals that block automated access. Respecting a portal's terms of use is part of the design.

How do you keep it maintainable?

Jurisdiction requirements are data. Each AHJ gets a profile listing required documents, form versions, fees and typical review time. When a form changes, a person edits the profile instead of a developer editing code, and the packet generator picks up the change on the next project.

Fees and deadlines belong in the same profile. Permit fees feed the project budget, and typical review times let the tracker raise a flag when a submission has waited longer than usual, so someone calls the office before the schedule slips.