AI for residential solar installers: permits, grid connection and PTO.

Between a signed contract and permission to operate, a residential solar project passes through hands the installer does not control: a building department reviewing the permit, a utility reviewing the interconnection application, an inspector, a meter technician. For most of that stretch the homeowner sees either nothing or a finished array that must not be switched on, and hears little. An installer's back office earns its keep here by knowing, for every project, who holds it today and what moves it on, and by telling the homeowner before the homeowner has to ask.

An office assistant earns its place in that silence: a milestone view built from the installer's own records, update drafts the owner reviews and sends, a warning before a utility reservation runs out, and a check of every proposal for credit and savings language before it leaves the business. They do not design systems, sign permit packs, sign in to utility portals on their own or tell anyone that a system may be switched on. This page is the residential solar guide in Aevrion's home-service industries series; two supporting articles go deeper into the operations desk and the proposal review.

Most home-service jobs are visible while they happen; a solar project mostly is not. After signature the installer prepares the interconnection application and the permit package, then waits. The building department reviews and may ask for corrections; the utility reviews the application and, in some places, issues a time-limited reservation; after the crew finishes, the project waits again for an inspection, a meter change and the utility's permission to operate. The homeowner sees the crew briefly in the middle, and otherwise a roof that may or may not carry panels.

Roseville Electric, the publicly owned utility of the City of Roseville, California, publishes its residential interconnection process in four steps (as checked on 15 October 2026), and the parties it names make a useful map: the customer, the contractor, the city's Development Services Department and the utility. Other utilities run their own versions, so the map is an example, not a rule. It shows that at most moments the project sits with someone other than the installer, and the homeowner cannot tell who.

1. 1

   Application prepared

   Owner

   Customer and contractor, who complete the residential interconnection application together

   Advances when

   The completed application is emailed to the utility

2. 2

   Utility review

   Owner

   Roseville Electric

   Advances when

   Approval, which brings an interconnection reservation confirmation valid for 120 days

   Ends when

   The 120 days for which the confirmation is valid run out

3. 3

   Permit review

   Owner

   Development Services Department

   Advances when

   Permit approval; a submitted packet may come back for corrections and need resubmitting

4. 4

   Ready to build

   Owner

   Contractor

   Advances when

   Construction may begin once the permit is approved and the reservation confirmation has been received

5. 5

   Awaiting inspection

   Owner

   Contractor schedules it; Development Services inspects

   Advances when

   An approved inspection

6. 6

   Meter change

   Owner

   A meter technician

   Advances when

   A multi-register meter is installed

7. 7

   Awaiting permission to operate

   Owner

   Contractor requests it; Roseville Electric reviews

   Advances when

   The utility issues the permit-to-operate

   Ends when

   The utility's page says the customer may then turn the system on

Two details in Roseville Electric's process shape how an installer tracks a project there. An approved interconnection application produces a reservation confirmation that is valid for 120 days. The city's permit is a separate track: Development Services requires its own residential photovoltaic packet, packets may come back for corrections, and construction can begin only after the permit is approved and the reservation confirmation has been received. A project can be ready on one track and stuck on the other while the reservation's days run down.

After installation the same page fixes the order. The contractor schedules the inspection with Development Services; if it is approved, a meter technician is scheduled to install a multi-register meter; the contractor then emails a permission-to-operate request to the utility. If the utility approves it, Roseville Electric issues the permit-to-operate, and the customer may then turn the system on.

This is one utility's process, described on one page and checked on 15 October 2026. Other utilities use different forms, portals, validity periods and sequences. The installer confirms the steps for each utility and permitting authority it works with, from that body's own published material, and writes them down once in the business's own words. An assistant then tracks projects against the owner's written version, never against its own idea of how interconnection works.

SolarAPP+ is an online platform for automated permitting of residential solar and storage. Its own site says installers enter the system design, the platform checks each data point against building, electrical and fire codes, and a code-compliant application receives a permit at the end of that check, along with an inspection checklist among its approval documents. UL Solutions' page for code authorities adds that ineligible projects go through the jurisdiction's usual review, that the platform costs local jurisdictions nothing while contractors pay submittal fees, and that installation practices, workmanship and adherence to the approved design are then verified by the local code official through the inspection process. Both pages were checked on 15 October 2026.

For a back office this shortens the wait without ending it: the project still passes through an inspection and whatever meter and permission-to-operate steps the utility requires. Only jurisdictions that have adopted the platform use it, and the site describes it as available to licensed contractors, who register and submit through their own accounts.

The assistants in this guide are Bots in Grok Bot. The owner creates each one with a name and a single job; it works on a persistent cloud computer with a browser and a shared file area, keeps its own conversation and working context, and leaves files and drafts a person can review. A routine can run a Bot's job on a schedule, with runs at least five minutes apart. The documentation describes no telephony, so a Bot never rings a homeowner, and it names no connector for any solar design, permitting or utility system; the one CRM it lists appears only in an enterprise network-settings table with no description of what it can do.

That last limit decides how project data reaches a Bot. The record stays wherever it lives today, whether a spreadsheet, a CRM or field-service software. A Bot reaches it by custom integration or supervised browser use where the vendor permits it, subject to testing; an integration is built for that one system, depends on the vendor's API or terms, and is not a product feature. Utility and permit portals need a person: the documentation says a Bot should hand control to the user for passwords, two-factor codes, CAPTCHAs and sites that require a human, so the account holder signs in and the Bot reads what the page then shows. Every Bot on the account shares that one computer and its sign-ins, and the documentation is plain that separate Bots are not a security boundary.

Based on the Grok Bot documentation at docs.x.ai as checked on 15 October 2026. Its statements on Bot rules, Bot-to-Bot messaging, routine triggers, connected apps, approval expiry and payments were rechecked against docs.x.ai and Cursor's help pages on 26 October 2026. The trade examples are Aevrion's illustrations, not documented Grok Bot use cases. Aevrion Ops is an independent consultancy. It is not affiliated with, endorsed by or a partner of xAI, SpaceXSI or Cursor. Grok Bot is named here only to describe it.

Consider an illustrative homeowner whose array was finished a week ago. The inspection passed on Thursday. On Saturday a neighbor who has had panels for years points out the disconnect beside the meter. The homeowner has not heard from the installer since the crew left.

That is the moment the installer's update has to arrive first, and say plainly that the system stays off until the utility has issued permission to operate and the installer has confirmed it in writing. In Roseville's published sequence permission to operate comes after the inspection and after the meter change, and the page says the customer may then turn the system on. Other utilities word it differently, so the owner writes the business's standard do-not-switch-on paragraph once, from the utility rules already recorded.

An updates Bot can draft that message from the project record at the right point in the chain: inspection passed, meter change pending, permission to operate not yet requested or not yet issued. The draft appears in the owner's own conversation with the Bot as an editable email, and it goes only if the owner chooses Send. Two lasting rules sit in the Bot's memory: it never writes that a system may be switched on, in any wording, and every update about the meter or permission to operate carries the owner's do-not-switch-on paragraph. A remembered rule steers the Bot without enforcing anything, so the owner reads each draft before sending it.

When the utility issues permission to operate, the owner tells the homeowner personally, with the utility's document in hand.

Trust can also be lost in the proposal. As checked on 15 October 2026, the IRS's section 25D page says the Residential Clean Energy Credit is 'not available for any property placed in service after December 31, 2025.' The same page still describes how the credit applied to qualifying property installed from 2022 through that date. That is the historical rule, not something a homeowner buying a system now can count on. The IRS page has to be re-checked on the date this guide is published, and again before any proposal template is reused. Whether a particular homeowner can claim anything is a question for that homeowner's tax professional, never for the installer or an assistant.

Federal Trade Commission consumer advice on home solar, checked the same day, adds warnings on future rates, fixed charges, leases and power purchase agreements, and contracts that differ from the pitch. A claims-review Bot flags conflicts with either page before the owner sends anything; the proposal claims review article sets that review out.

Two questions come with a solar inquiry, and neither belongs to an assistant. Whether the home's electrical service can take the system, or needs an upgrade first, is an electrician's verdict after seeing the panel; the EV charger and panel upgrade article in this series shows how an office prepares photos for that verdict and tracks the paperwork after it. Whether the roof can carry an array is judged by the installer, a roofer or, where the permitting authority requires it, an engineer.

An assistant lists any project with no recorded capacity verdict or roof note as incomplete. It never answers either question, or infers one from a photo.

The split below holds however capable the drafts become. It is Aevrion's recommended boundary for an installer to adapt; the product enforces none of it.

The roster starts with a single Bot that owns the milestone view, because every update and every reservation warning starts from knowing where a project is. A permit-pack assembler and an updates drafter build on that view; the signature-to-PTO desk article shows all three through one week with thirty projects in flight.

The reservation warning is the routine that must not fail quietly: the documentation describes no automatic retries or failure alerts, and a failed run only shows as Failed in its history. So the owner checks that history each Monday and keeps each reservation's expiry date in their own calendar too, and the routine ends in lists and drafts, because an unanswered approval lapses after about ten minutes (Cursor's help pages say thirty).

Take one recent project that ran long and list, from the installer's records, each date it changed hands and each date the homeowner heard anything. The gaps between the lists show where an assistant helps first.

A free first step is the workflow automation readiness assessment: score the homeowner-update workflow against its twelve dimensions, and ownership clarity is likely to cap the result if nobody owns the weeks between milestones. Scoping the milestone view with Aevrion Ops then covers recording each utility's and permitting authority's steps in the business's own words, designing the update drafts, putting a claims review in front of every proposal, and connecting the systems the business already runs by custom integration, once each vendor's API or terms are confirmed and the link has been tested. An installer who already knows where projects stall can open that conversation through the contact page.

1. Between signature and permission to operate, a solar project mostly sits with a permit office, a utility, an inspector or a meter technician, and the homeowner rarely knows which.
2. Roseville Electric's published process, as checked on 15 October 2026, is one utility's example: a reservation valid for 120 days, building only after both approvals, then inspection, meter and permission to operate.
3. SolarAPP+ can shorten the permit stage where a jurisdiction uses it; installation is still verified through inspection.
4. Update drafts carry the owner's do-not-switch-on paragraph, the owner sends every one, and no Bot ever tells a homeowner a system may be switched on.
5. Proposals are checked against the IRS 25D page, which says the credit is not available for property placed in service after December 31, 2025, and against the FTC's solar warnings; a homeowner's tax position is for their own tax professional.