What I Learned About Permitting the Hard Way

At SunEdison, we spent months trying to figure out whether a project could get a permit.

I worked on one near an air force base in Nevada. On paper it was supposed to be straightforward, but it wasn't. After months of scouring planning commission meeting minutes and calls to AHJs, we still didn't know whether we could permit it. That project luckily made it through, but many others ended up dead on arrival, after everyone had already put in real time and real money.

It's been over a decade, and the process still looks and feels the same. The VP of Development at a solar developer recently told me his teams were still signing leases without knowing if the project was permittable, and would only realize months later that it would never get permits. A developer at another firm described their current process as: "Call the county and figure out who the AHJ is. If we're lucky, the county has a website."

There are more than 35,000 AHJs in the US, each with its own rules, timelines, and local politics. The standard workaround is to hire a consultant, spend several thousand dollars, wait weeks, and get back 40 pages of irrelevant content. Over $64 billion in data center projects were blocked or delayed by local opposition in the past two years, and over 450 counties now have ordinances restricting utility-scale solar outright.

This week, Spark is launching Permit Matrix as a Service: project-specific permit matrices for solar, BESS, and data center developers, delivered in 7 business days, or less. Every regulatory claim has a URL citation. We log AHJ calls. Credentialed engineers review and sign off.

This is the version I wished existed when I was a developer.

See what's included at sparkhq.ai/permit-matrix-options.