Quick answer
Site-specific research that identifies responsible permitting authorities and verifies current requirements, sources and dates. Utility interconnection and private consent are separate scopes.
What Are AHJ Lookups?
Answer: An AHJ lookup identifies the authority responsible for a solar project’s permits and verifies its current requirements for that exact site. Research the address and parcel, adopted requirements, submission documents, fees and inspection process. Keep source links and verification dates. Identify the serving utility separately: a permitting authority’s boundary or approval does not establish utility service or permission to operate.
An Authority Having Jurisdiction has a defined scope. A lookup provides verified inputs for design and project planning; AHJ compliance is the subsequent work of addressing those requirements and obtaining the required acceptance.
DOE’s rooftop solar guidance notes that local requirements and fees vary. There is no universal permit checklist, review duration or guaranteed database lookup time applicable to every project.
A Site-Specific Lookup Workflow
- Resolve the site identity. Record the full address and parcel identifier. Confirm whether the site is within the relevant city, county or other authority’s boundary; a postal city name alone may not settle this.
- Identify responsible offices and scopes. Confirm building/electrical permitting, fire and planning responsibilities where applicable. Keep private owner/HOA consent separate from public permitting.
- Verify adopted requirements. Record applicable code editions, effective dates and amendments. Ask the responsible office about transitional rules or unusual project scope rather than assuming an old database entry applies.
- Retrieve the actual application requirements. Capture the current checklist, required forms, drawings, calculations, professional review and delivery format. Identify the applicable project type, such as rooftop, ground-mounted or storage.
- Check fees and inspection procedures. Use current schedules and official booking instructions. Distinguish published processing targets from a commitment for this particular project.
- Identify the utility separately. Verify the actual serving utility, interconnection application, connection arrangement, metering and applicable tariff. Do not infer a compensation rate or system limit from the AHJ profile.
- Save evidence and unresolved questions. Assign a person to confirm critical items before design release or submission, and recheck if project scope or requirements change.
What to Capture in the Lookup Record
| Field | Useful entry | Verification boundary |
|---|---|---|
| Site and jurisdiction | Address, parcel and responsible permitting office | Confirm boundary rather than guessing from postal address |
| Requirement source | Official page, document or written response | Keep document title/version, source link and verification date |
| Codes and amendments | Applicable edition and effective date | State/local adoption and project applicability require confirmation |
| Layout constraints | Applicable setbacks, pathways and equipment clearances | Record exact source and conditions; no universal roof dimensions |
| Professional review | Required calculations, signatures or other submissions | Do not infer a universal kW threshold or engineering-stamp rule |
| Application | Forms, drawing checklist, portal and submission format | Use the checklist for the actual project type |
| Fees and timing | Current fee schedule and published process information | Separate confirmed fees, estimates and unresolved items |
| Inspection and revisions | Booking instructions and field-change procedure | Requirements can differ from the initial plan-review process |
| Utility | Verified provider and interconnection/tariff source | Separate utility scope from local permit approval |
| Responsibility | Researcher, reviewer, status and recheck trigger | A source without an accountable review does not close uncertainty |
A useful status is verified, pending confirmation or not applicable with reason. Do not fill an unknown field with a convenient default. If two sources disagree, retain both references and resolve the conflict with the responsible office before relying on the entry.
Manual Research, Databases and AI Assistance
Official research: current authority documents and written clarification provide the basis for the record. A telephone answer should include the date, relevant contact, question and follow-up needed. Do not present recollection as a published requirement.
Address-based databases: these can organize contacts and stored profiles. Check coverage, update dates, boundary handling, source provenance and correction procedures. Retrieval speed does not establish the accuracy or completeness of the returned requirements.
Design integrations: verify the exact supported rule, inputs and output. A stored setback or template is not automatic acceptance, and entering an address does not demonstrate that all adopted requirements were applied.
AI-assisted research: use it to locate or summarize documents with traceable references. Check the original source and exact applicability. Do not accept an unsupported code interpretation or invent a missing fee, edition or approval requirement.
Checking SolarAPP+ Participation
Use the current SolarAPP+ availability guidance to check locations and products supported in each jurisdiction. Adoption does not mean every system qualifies.
For participating jurisdictions, SolarAPP+’s additional-requirements instructions explain how to view jurisdiction requirements before an application: open Jurisdiction Licenses, find the AHJ and choose View Requirements. Check any linked local documents and requirements for the specific project. The guidance also explains that additional local requirements remain mandatory after automated approval.
Treat adoption, project eligibility, application approval, local permits, inspections and utility operating authorization as separate checks. An address lookup cannot promise a contract-to-installation date.
Illustrative Research-Cost Calculation
A team can evaluate lookup efficiency using its own measured workload. For illustration only, assume:
- 500 projects per year.
- 1 hour of research per project before a workflow change.
- 0.08 hour, or 4.8 minutes, per project afterward, including required verification.
- $45 per hour as the labor-cost assumption.
500 × (1 − 0.08) hours × $45/hour = $20,700 per year of modeled labor capacity.
This retains the distinction between workload arithmetic and proven savings. It is not an observed installer result, a forecast for SurgePV or a guarantee of cash savings. Measure verification work, exceptions, database/software charges, maintenance and rework before estimating net benefit. Released staff time may be used for other work rather than reducing payroll.
Keeping the Record Useful
Designers: perform the lookup before committing to layout and equipment choices. Carry verified requirements into the permit package and assign unresolved items to a reviewer.
Installers: confirm the current inspection and revision procedures. Distinguish binding instructions from an individual preference or a previous project’s experience.
Sales teams: use confirmed fees and describe uncertain scheduling dependencies. Do not translate a published review target into a guaranteed installation date or promise tariff savings without the actual utility terms.
Maintain a service-area database with source provenance and recheck triggers. A change in equipment, project type, code effective date or authority procedure can require another lookup. Entering a new market is a reason to verify requirements, not evidence that a one-time database exercise will permanently prevent corrections.
Discuss your project workflow with SurgePV using the verified requirement record to evaluate the demonstrated product functions and remaining review responsibilities.
Frequently Asked Questions
What information should an AHJ lookup include?
Site identity, responsible office and scope, applicable requirements, documents, fees, procedures, sources and verification dates. Keep utility interconnection and private property consent in distinct records.
Can an AHJ lookup be automated?
Some retrieval and record organization can be automated. Verify current sources, boundary accuracy, project applicability and unresolved items. Automation does not guarantee compliance or authority acceptance.
How long does a lookup take?
It depends on source availability, site boundaries and project complexity. Measure your actual research and verification time rather than assuming a universal manual or automated duration.
Does SolarAPP+ participation settle all requirements?
No. Confirm supported project scope and any additional local requirements. Required inspection and utility authorization remain separate milestones.
Related Glossary Terms
About the Contributors
CEO & Co-Founder · SurgePV
Keyur Rakholiya is identified by SurgePV as its CEO and a company co-founder. His SurgePV author page lists only role information that can be tied to the public profile below; credentials, project totals, testing claims, media appearances, and speaking engagements are not asserted without retained evidence.
Editorial contributor · SurgePV
Rainer Neumann is credited as an editorial contributor on SurgePV content. This profile does not assert engineering credentials, project totals, software-testing experience, education, speaking engagements, or media citations because independent verification evidence is not retained in the publication record.
