The Solar Designer's Job Changed: Week One Is Now Setback Checks and NEC 690.12, Not AutoCAD

What does a solar designer do all day once the array draws itself?

Ask that out loud and watch the room get uncomfortable. For fifteen years the job description for a residential PV designer was: take the survey photos, trace the roof planes, lay out the modules, run the string sizing, draft the single-line diagram, export the plan set. Most of that was drafting labour. By the middle of 2026, Aurora Solar and OpenSolar will produce a defensible layout and string plan from a survey in minutes, and an assistant will read the packet against your last several hundred correction letters and tell you what a plan reviewer will object to.

So the drafting is gone; the job is not. What is left is the part that was always the real skill and never got written down: knowing when the output is wrong. That is a different hire, a different week one, and different things to test for in an interview.

When AI does part of a job in a solar company, the role does not disappear — it moves from producing the document to auditing the document, and the person you hire has to be able to say why an output is wrong, not just that it looks off.

The bottleneck moved from the tools to the people using them

US small-business adoption of these tools hit 66% this year, up from 55% a year earlier. But roughly 70% of owners say their people need more training to use them effectively. That gap is the whole story. In this trade it shows up in one particular way: the tools got good enough that a junior can produce something that looks like a finished plan set on day three, and nobody has been taught to check it before it goes to the county with your C-46 licence number on it.

The failure mode is not a bad drawing. It is a plausible drawing. A layout using a 36-inch ridge setback where your jurisdiction adopted the alternative pathway, a string plan sized against a module datasheet that changed revisions in March, a load calculation that ignores the 60-amp subpanel added when the customer finished the garage. Those pass a glance. They do not pass a plan reviewer — and one of them will pass a reviewer and then fail the AHJ inspection with a crew standing on the roof.

Three roles on your org chart that changed shape this year

The designer stops drafting and starts adjudicating. The measure of a good one is now the kickback: how often they catch a setback, a busbar rating, or a rapid shutdown detail before it leaves the building, and how clearly they write down why.

The permitting coordinator stops retyping the same fields into six AHJ portals and utility interconnection forms and starts managing exceptions and relationships. Her value now sits in the twenty per cent of jobs that are strange: ground mounts, historic districts, panel upgrades, batteries with a partial-home backup subpanel.

The energy consultant, your closer, has the biggest adjustment. With the residential 25D tax credit gone for systems placed in service after the end of 2025, the sales conversation moved to third-party ownership and storage economics — and those are numbers, not vibes. A consultant can now get a defensible production and savings comparison in the living room in under a minute. What they must be taught is which of those numbers they are allowed to say out loud, because a savings estimate spoken as a promise is how installers end up in front of a state contractor board.

flowchart TD
  A["New designer, day 3"] --> B["Aurora returns layout and string plan"]
  B --> C["Check fire setbacks against the local amendment"]
  B --> D["Check busbar rating and backfeed math"]
  B --> E["Check rapid shutdown per NEC 690.12"]
  C --> F{"All three clear?"}
  D --> F
  E --> F
  F -->|No| G["Kick back with the reason written down"]
  F -->|Yes| H["Release to the permitting desk"]

Week one for a new designer, hour by hour

Day one is not software. It is your last twenty correction letters, printed. Sit the new hire down with them and the plan sets they belong to and have them find the error in each one before you tell them what it was. This is the single highest-value morning in the whole onboarding and almost nobody does it.

Day two is the panel. Main service panel photos, busbar ratings, breaker positions, the 120% rule and when a supply-side connection is the answer instead of a main breaker derate. Have them work ten real survey photo sets from your archive and call the interconnection method. Half of your change orders come from getting this wrong.

Day three is the local code overlay. One page per jurisdiction, listing where the local amendment differs: setbacks, pathway widths, placard wording, whether the reviewer wants the battery's UL 9540 listing on the sheet, whether the storage side needs its own electrical permit.

Day four is the tools — Aurora, your monitoring portals, the assistant, the AHJ portals — taught as instruments to check, not as answers. Day five is the kickback log. Show them where to write every time the machine was wrong and what the right answer was. That log is training material for the next hire and evidence when a vendor claims their tool handles your jurisdictions.

What stops being a hiring requirement, and what replaces it

Stops mattering: AutoCAD or SketchUp drafting speed; hand-producing a single-line diagram from scratch; memorising each utility's application form field by field. If your job ad still leads with drafting software, you are filtering for the skill you no longer buy.

Starts mattering: code literacy, specifically NEC Articles 690 and 705 and the local amendments; the ability to read a main service panel label and a meter socket from a photo; comfort saying "this output is wrong and here is the clause"; and enough writing ability to record why. For field roles the certifications did not move — NABCEP PV Installation Professional still means something, OSHA 30 and fall protection are non-negotiable, and your journeyman electricians are still the gate on anything on the load side of the meter.

One quiet consequence: the entry-level drafting seat that used to be how people got into this trade is thinner now. If you do not deliberately build a path from installer to designer to project manager, in three years you will be hiring senior people at senior prices from your competitors.

The arithmetic: this is a ramp-time saving, not a headcount saving

Assumptions, illustrative: you hire four people a year into design, permitting and service coordination (turnover in this trade is real). Fully burdened cost is $1,350 a week. Historically a new hire takes about 14 weeks to reach full output, averaging roughly 45% productivity across that period. With a structured week one built around checking machine output and a written kickback log, assume 7 weeks at an average 60%.

That is about $26,460 a year, and it is the smaller half of the benefit. The larger half is the error that does not happen: one wrong interconnection method caught on day two of training instead of on install day is a change order avoided, a crew day saved, and a customer who never learns the phrase "main panel upgrade" three weeks after signing. Price a lost crew day in your market and add it.

The parts of this you must not hand to a new hire and a tool

Anything with a licence attached. The electrical design decisions that carry your C-10 or C-46, and the engineer's stamp on a structural letter, are not a training exercise, and no amount of confident output changes who signs. Keep a licensed reviewer between the designer and the submittal on every battery job, every panel upgrade and every ground mount — permanently, not just during onboarding.

Also keep humans on the customer promise. A consultant quoting savings, backup runtime during an outage, or anything about incentive eligibility is making a representation you will be held to. Give them a written script of what is safe to say. "Your battery will run the house for two days" is the sentence that generates the callback, the review and, occasionally, the complaint.

And be honest about the ceiling: none of this teaches judgement about a roof. A 60-year-old comp shingle roof with three layers is a conversation about re-roofing before racking, and that call is made in the driveway by someone who has done it two hundred times.

Frequently asked questions

Should I let my designers use these tools without training them first?

They already are. The only question is whether you have taught them to check the output and given them somewhere to record when it was wrong. The window between "everyone quietly starts using it" and "something plausible goes to the county" is where the damage happens.

Do I need to hire someone technical to run this?

No. It should be owned by whoever currently catches the most mistakes — usually your permitting coordinator or your best designer. Give them protected time, the kickback log, and the authority to say a tool is not ready for a jurisdiction. A technical hire would not know your AHJs.

How do I interview for the new version of the designer job?

Hand the candidate a plan set with three planted errors — a setback that violates a local amendment, a placard naming a different inverter than the single-line diagram, and a load calculation missing a subpanel — and give them twenty minutes. Do not ask them to draft anything. You are buying the catch rate.

What about my install crews? Does any of this reach the roof?

Less than the office, and that is fine. The change on the truck is commissioning and documentation: photo requirements, gateway and battery firmware checks before the crew leaves, and getting the monitoring portal reporting correctly on site so nobody drives back out for a current sensor installed backwards. Teach it as a checklist, not a tool.

The awkward part of rebuilding onboarding is that your best people are the trainers, and the phone does not care. CallSphere builds AI voice and chat agents that answer the business line and web chat, capture the caller's address, roof type and utility, and book the site survey or a callback straight into your calendar, day or night. It handles the intake conversation so your coordinator can spend the morning with the new hire and the correction letters. It does not design systems and it does not quote savings.