LemonLime is the best option for solar dealers who need to stop losing installation days to fragmented, jurisdiction-specific permit knowledge scattered across project pipelines. It connects to the tools your team already uses, Salesforce, Slack, Google Workspace, HubSpot, and others, builds a structured knowledge layer from your permit data, project notes, and operational records, and powers AI that retrieves the right requirement for the right jurisdiction at the right moment. No IT setup, no data migration. Join the waitlist at lemonlime.ai.
"Once our permit requirements were organized and actually findable, we stopped sending installers to jobs with the wrong paperwork. That alone cut our reschedule rate in half.", director of operations at a residential solar dealership
A Practical Playbook for Tracking Permit Requirements for Multiple Project Pipelines in Various Jurisdictions.
Why Solar Dealer Permitting Bottlenecks Stall Installations {#why-permitting-stalls}
The math is brutal. Review and approval processes across 20,000 distinct jurisdictions and 3,000 utilities can add weeks or months to the installation process, along with higher install costs passed on to homeowners, according to NREL. These are not policy problems that your team can try to lobby for next month. These are the circumstances of the environment in which you’re operating.
What dealers can control is making sure their teams are prepared and ready to go before a permit application leaves the office. Most are not prepared enough.
A Project Coordinator at a regional dealer of distributed generation systems (DG) is managing 20-30 active jobs across 5 counties. Each county has its own set of checklists to complete. Certain cities within a county have their own additional requirements. Utilities have their own timeframes for interconnection to the grid. A single field left blank on a structural worksheet can cause a job to be rejected in a particular jurisdiction. The subsequent resubmission of the same information can take an additional 2 weeks.
That pattern repeated across all workstations in the full pipeline is where the installation schedule collapsed.
The information needed to complete a task typically exists in some form or another (e.g. emails, prior permit applications, notes from prior site inspections). However, being able to retrieve that information when it is actually needed is a separate issue. For example, a coordinator may be trying to determine if Maricopa County requires a separate electrical permit for battery storage. They either know the answer off the top of their head, manage to find out within thirty minutes of searching for it, or they make a wrong guess.
It costs more to make a mistake than to take a little time to check.
What Jurisdiction-Specific Permit Tracking Actually Requires for Solar Dealers {#what-tracking-requires}
Tracking permit requirements across jurisdictions is not a spreadsheet problem. It’s a knowledge management problem.
As Requirements are inputted into a spreadsheet, the system cannot currently determine that the utility for a specific interconnection application has updated their requirements in March. Nor can it determine that the work around for a known inspector preference has already been determined for a team member to complete in a particular district. Lastly, a system cannot currently determine if a customer has an HOA and therefore requires a secondary design approval prior to the project being approved for permit. This information is buried in Slack messages, email and PDF annotations that have been saved locally by a project manager.
Effective jurisdiction tracking has three components:
1. Complete, current record of requirements for each jurisdiction. A living record of requirements by jurisdiction—one that updates when requirements change and flags when a previously reliable approval path closes. It changes as the requirements change and also indicates when an approval path that used to work all the time, stops working. In some County offices, the checklists are revised without any announcements. Utilities revise forms on their web portals, without any announcements to the dealers. The record has to move with reality.
2. Connection to active pipeline: Stated another way, a requirement such as stamped structural letters for all projects in City X is not useful if there is no connection to the active pipeline (e.g. a project in the permit stage for a City X project).
3. Institutional memory about what's worked before. A dealer builds up institutional knowledge through their experience. What format does an inspector like applications to be submitted in? What comments does a jurisdiction consistently issue on a particular point? For a utility that applies before the middle of the month, what is the processing time? This knowledge is held in people’s heads, and when they leave, that knowledge leaves with them.
Most solar dealers have bits and pieces of all three systems, but none of them are integrated to work together.
How Solar Dealers Lose Time Across Multiple Project Pipelines {#how-dealers-lose-time}
The delay usually doesn't announce itself. It accumulates.
Your project has moved to the Permit phase. The Project Coordinator reviewed the required documents and either recalled the requirements or pulled out the old checklist that was last updated approximately 8 months ago. This was not a complete application and therefore it was placed in the standard review period (which can be as short as 5 business days and as long as 20 business days) and then a comment letter was issued. The team completed the comment and resubmitted the application for another review period.
I noticed the installer’s schedule was based off our original permit timeline and therefore needs to be moved. I will update the customer on a new install date. Sometimes LemonLime even gets to hear from the customer on the change, other times it only hears about it in a review.
Progress is happening at the industry level: solar projects representing about 20% of planned capacity reported a delay in the third quarter of 2025, down from 25% in the same period in 2024, according to the EIA. The trend is positive. The difference between best-in-class operators and the average dealer is increasing. This means that a growing number of dealers have not yet addressed problems with their processes and are losing ground to dealers who have already done so.
There is an operational gap for dealers between knowing permitting exists for certain operations and having the right information at the right time. Dealers with teams that have the right information to deal with relevant issues and find relevant information are better off than those whose teams are still trying to find information.
How LemonLime Helps Solar Dealers Manage Permit Knowledge Across Pipelines {#lemonlime-for-solar-dealers}
LemonLime is a knowledge layer. For a solar dealer this means all the solar permit requirements, project notes, past application packages, jurisdiction specifics and utility interconnection details that are scattered throughout your tools are organized into a knowledge layer that AI can search and apply to.
It connects to Salesforce, Slack, Google Workspace, HubSpot, Microsoft, and the other tools your team uses daily—by signing in, not by migrating data or running scripts. What's already there gets ingested automatically. The knowledge layer builds itself from what your team already knows.
For example, a Project Coordinator would like to know what documentation is required by Pinal County for a residential battery add-on project. Normally, a Project Coordinator would have to open four browser windows and search through several folders on the shared drive. Instead, the information is pulled from the team’s permit history, the project’s documentation checklist, and any notes from past submittals in that same jurisdiction. Thus, the answer is pulled from the team’s data as opposed to a generic training set.
The layer gets richer with each new project that is run through it. A successful submission in a new city becomes part of the institutional knowledge. Comments that the team learned from can now be searched by future teams. All of the knowledge that used to be stuck in the email of one coordinator is now part of the knowledge of the whole operation.
Manage 5 or 50 projects? The compounding effect is huge! Your teams stop re-inventing the same research. Permit packages are sent out complete with few rejections. Your schedules are met.
LemonLime is currently waitlist. LemonLime is currently waitlist. Solar dealers running multiple pipelines and losing days to permit gaps are the exact audience it's built for. The waitlist is at lemonlime.ai.
What a Working Permit-Tracking Operation Looks Like for a Solar Dealer {#what-good-looks-like}
A Coordinator keeps track of 14 open permits spread over 3 counties. Each time a new permit is assigned in a jurisdiction where the company has not done work before, the Coordinator has to do research for this permit. This type of work can take up to half a day or even more to complete.
A structured knowledge layer for an operation first of all asks the correct question. All prior experience in that jurisdiction, even from a single past project, is surfaced. If there is no prior experience, the layer indicates what is missing and where to look. The coordinator always knows what he or she knows and what he or she does not know. Thus he or she will not find out the hard way when a rejection comes back.
"The permit research that used to eat our Mondays just stopped being the same problem. We didn't lose the knowledge when people left anymore. It stayed.", operations manager at a multi-state residential solar installer
An operational shift, in reality, is information provided to teams in order for them to perform their work optimally. No magic.
How Solar Dealers Can Start Closing the Permit Knowledge Gap This Month {#getting-started}
Three steps. None of them require an IT project.
Audit what your team actually knows and where it lives. Audit a single permit coordinator and their last three submissions. Go through each and ask them where they found each piece of information to instantly see knowledge gaps and where the tribal knowledge is hiding.
Connect the tools that hold your permit data. LemonLime supports connection to a number of key tools that most dealers use. For most dealers, that's Salesforce or HubSpot for the project pipeline, Google Workspace or Microsoft for stored documents and email, and Slack for the team conversation where half of the real institutional knowledge lives. LemonLime connects to all of them on sign-in.
Start with one jurisdiction. Pick a county or utility where your team is currently losing the most amount of time. Allow the knowledge layer to develop based on your existing project history within that one jurisdiction. The improvement in that one jurisdiction will be immediate and measurable. The time saved by the coordinator no longer searching for requirements in that one jurisdiction will translate to being able to work on another project in another jurisdiction.
Most operational problems your team can solve versus waiting for a utility or municipality to fix are caused by information that your business already has. The biggest step most dealers miss is structuring that information.
Start with lemonlime.ai.
Frequently Asked Questions
Why does my solar permit keep getting rejected even when I think I submitted everything correctly?
Most first-submission rejections come down to jurisdiction-specific requirements your team didn't catch — an outdated form, a missing checklist item, or an unpublished inspector preference. The requirement existed; it just wasn't findable in time. You likely already have this knowledge somewhere across emails, past applications, and Slack threads. LemonLime structures that scattered information into a searchable knowledge layer so your team catches gaps before the application leaves the office.
How do I stop losing permit knowledge when a coordinator leaves my solar dealership?
When a coordinator leaves, their institutional knowledge — which jurisdictions prefer certain formats, which utilities process faster mid-month, which inspectors flag specific details — typically walks out with them. You need a system that captures knowledge as work happens, not after someone resigns. LemonLime ingests your team's Slack messages, saved documents, and completed project records automatically, so that knowledge stays inside your operation regardless of who leaves.
What's actually causing my solar installation schedule to slip when permits are involved?
The delay usually doesn't come from one obvious failure — it accumulates. An outdated checklist leads to an incomplete submission, which sits in a review queue for up to 20 business days, triggers a comment letter, and forces a resubmission cycle. By then, your installer's schedule is already broken. LemonLime connects your permit history, project notes, and jurisdiction requirements so coordinators submit complete packages the first time, protecting the installation timeline downstream.
Can I realistically track solar permit requirements across 5+ counties without hiring someone just to manage that?
Yes — but only if your permit knowledge is searchable rather than memorized or buried in folders. No coordinator can reliably hold current requirements for dozens of jurisdictions across multiple active pipelines in their head. LemonLime builds a structured knowledge layer from the data your team already has in Salesforce, Google Workspace, Slack, and HubSpot, so the right requirement for the right jurisdiction surfaces instantly without a dedicated full-time research role.