Which jurisdiction is costing you eleven days?

If you search for solar permitting software, you will usually find three different products: tools that generate permit packages, tools that submit to automated AHJ review, and tools that track jobs after approval. None of them, by itself, tells you why one county costs you eleven more days than another.

For a solar installer or EPC, that matters because the delay is rarely one thing. It is a chain of waits: time to assemble the package, time in first review, time lost to corrections, time to inspection, time in the utility queue, and time to PTO, or permission to operate. If you want to know which jurisdiction, utility, or internal step is slowing you down, you need a cycle-time record with a small set of timestamps and a clear rule for who owns each gap.

The three products that all call themselves solar permitting software

The search term is overloaded. That is why the results feel helpful and still miss the point.

• Permit-package generation builds the drawings and documents needed for submittal. It helps standardize plan sets and reduce manual prep, but it does not tell you where jobs stall after submission.
• Automated plan review routes certain jobs through jurisdictions that support tools such as SolarAPP+. The U.S. Department of Energy says SolarAPP+ has been adopted by 160 communities, which is a sign that fast approval is now real in some places, not just a pilot concept. See DOE’s SolarAPP+ program page.
• Project execution platforms track work after the permit clears. They can help coordinate scheduling, inspections, and field work, but they usually do not model the local permitting and utility rules that explain why a job sat for nine days in one market and two in another.

The right tool depends on the question. If you need better permit packages, use a plan-set tool. If you operate in jurisdictions that accept automated review, use that path where it applies. If your real problem is that 140 jobs are stalled and nobody can say where, you need measurement first.

Break permit-to-PTO into the parts you can own

Most teams talk about permitting as one number. That hides the real levers. A useful record starts with these timestamps:

• Package ready - the permit package is complete and ready to submit.
• Submitted - the AHJ, or authority having jurisdiction, has received it.
• First AHJ response - the first review result or correction notice arrives.
• Correction issued - each correction set is documented.
• Correction cleared - each resubmittal or response is sent.
• Approved - the permit is approved.
• Inspection requested - the inspection is booked.
• Inspection passed - the site passes inspection.
• Interconnection submitted - the utility application is filed, if that is separate.
• Utility response - the utility issues a reply, approval, or correction.
• PTO issued - permission to operate is granted.

That sounds like a lot, but the point is simple: each gap belongs to one of three buckets. It is either yours, theirs, or the customer’s.

• Ours means the delay came from packaging, design errors, missing signatures, late resubmittals, or internal handoff time.
• Theirs means the job is waiting on the AHJ or utility to review, respond, or schedule.
• The customer’s means you are waiting on access, signatures, photos, or another action outside your control.

Boundary cases matter. A correction notice is not a jurisdiction delay. It is a response from the jurisdiction, but the gap before the correction is usually on you if the package was incomplete. The days after you resubmit are theirs, assuming the file is now complete. If a job sits waiting for a customer signature, do not count that as permitting time. Count it separately so you do not blame the wrong party.

Once you track this, the median and the 90th percentile become more useful than the average. The average hides the jobs that are killing cash. The 90th percentile tells you which jurisdictions create the long tail that ties up crews, billing, and capital.

Correction rate is a design metric, not a permitting metric

A high correction rate can come from two very different places.

If an AHJ sends corrections to everyone, the problem is usually a requirements issue. The jurisdiction wants different documents, a different stamp, or a different review sequence than your template assumes. If only one designer, one equipment package, or one system type triggers corrections, the problem is probably internal.

That distinction changes what you fix. If it is jurisdiction-wide, update the local template, the checklist, and the permit matrix. If it is designer-specific, fix the training, the rules in your design tool, or the review step before submittal. Do not throw coordinator time at a template problem. That just makes the same mistake faster.

A practical way to measure this is to calculate first-pass approval rate by AHJ, by designer, and by system type. If one designer’s jobs fail in three counties while everyone else passes, the issue is likely the design process. If every installer who works that county sees the same correction themes, the issue is the county.

Turn the permit matrix into a real data structure

Most installers already have a permit matrix somewhere. The problem is that it lives in a spreadsheet, a coordinator’s head, and a pile of portal bookmarks. That makes it hard to search, hard to update, and easy to lose when someone leaves.

A useful jurisdiction record needs more than a name and a note. It should include:

• submittal channel and portal
• required documents and stamp requirements
• structural and electrical review triggers
• fee schedule
• typical first-review days
• common correction themes
• inspection scheduling rules
• contact of record

A utility record needs a similar structure:

• interconnection portal
• application prerequisites
• study triggers
• system-size and equipment thresholds
• meter-swap coordination rules
• PTO issuance pattern

This is valuable because it survives staff turnover. It also becomes the source of truth for your timestamps. The same asset that tells a coordinator what to submit is the asset that tells an owner why jobs are slowing down in one utility territory and not another.

That is why a well-structured permit matrix is usually the highest-value internal build for a company at this size. It removes tribal knowledge from the process and makes the process measurable.

Build, buy, or just instrument what you already have

Many installers do not need a new platform on day one. They need disciplined stage timestamps in the CRM or project tracker they already pay for.

Use this as a simple decision guide:

• Instrument what you have if you operate in a manageable footprint, your CRM can store stage dates, and your team mainly needs visibility into where jobs stall.
• Buy an execution platform if you need better cross-team coordination, automated tasking, and stronger workflow control across a large volume of jobs.
• Build a permitting and interconnection layer if your AHJ and utility footprint is wide, the rules vary a lot, and the permit matrix is now strategic infrastructure rather than a side spreadsheet.

For many companies, the first move is not six figures of software. It is a four-figure or low five-figure process change: add the timestamps, make the attribution rules consistent, and review the data every week. Once you can see where the delay sits, the software question becomes much easier to answer.

What changes when you can see the delay

Once you have per-AHJ and per-utility cycle time, the business decisions get sharper.

• You can stop selling in a county that consistently destroys margin.
• You can staff a second permit coordinator for the utility territory that creates the longest queue.
• You can tell whether slow jobs are a jurisdiction problem or a design problem.
• You can set sales expectations that match reality instead of averages.
• You can align financing, billing milestones, and crew scheduling to actual approval timing.
• You can separate jobs stalled on you from jobs stalled on someone else.

That last point is often the most useful. Owners usually know the pipeline is slow. What they do not know is which jobs are slow because the company missed something, and which are slow because a county or utility is taking its time. Those are different operational problems, and they deserve different fixes.

Better’s experience with systems like this

Better’s energy work includes solar proposal and operating software, and related data and document pipelines in oil and gas. The common engineering problem is not the screen or the dashboard. It is modeling external parties that change their rules without warning, then ingesting data from portals and documents that break in different ways. You can read more about our energy work and the Nesh case study.

The useful lesson for solar installers is the same one we see in other operational systems: if the outside world is inconsistent, your software has to make inconsistency visible instead of hiding it. That starts with the right timestamps, the right record structure, and a rule for attribution.

How to start this week

If you want a practical first step, do not start by buying a new permit platform. Start by adding these fields to every open job:

• package ready date
• submitted date
• first response date
• correction issue and correction clear dates
• approved date
• inspection requested and passed dates
• interconnection submitted date
• utility response date
• PTO date
• AHJ name
• utility name
• designer
• system type

Then review one month of jobs and classify each gap as ours, theirs, or the customer’s. After that, sort by AHJ and utility. The pattern will usually make the next decision obvious: fix the template, tighten the process, or change the market.

If you already have the dates but not the structure, the next step is to turn the spreadsheet into a record that your team can update without relying on one person’s memory. That is what makes solar permitting software useful in the way owners actually need it to be: not as a generic label, but as a system for finding where the days go.

FAQ

How long does solar permitting take?

There is no single answer that holds across jurisdictions. The useful number is your own permit-to-PTO cycle time by AHJ and by utility, split into submittal, review, correction, inspection, interconnection, and PTO. That is the only way to compare markets fairly.

Why does permitting take so long?

Because the delay is usually a mix of internal work, review queues, correction cycles, inspection scheduling, and utility processing. If you do not separate those parts, the whole timeline gets described as one bottleneck even when the bottlenecks are different.

Is permitting or interconnection the bigger cause of delay?

It depends on the market and the utility. Some teams lose more time in first review and corrections. Others clear permitting quickly and then wait on utility interconnection or PTO. Measure both before you decide where to invest.

What is a solar permitting matrix?

It is a structured record of what each AHJ and utility requires, how they accept submissions, what triggers extra review, and how long each step usually takes. In practice, it is both a playbook and a measurement asset.

Does SolarAPP+ apply to my jurisdictions?

Only if the specific AHJ or community has adopted it and your job meets the program’s eligibility rules. The best source is the jurisdiction itself or the SolarAPP+ program information from DOE. If it applies, it can remove a large part of the permit wait. If it does not, you still need the same cycle-time record to see where the delay moves next.