A solar installer or permit coordinator can lose days by asking the wrong PE stamp question. State boards decide who may practice engineering and seal work. The local permitting authority decides what a specific solar permit must contain. Those are separate decisions.
Quick answer. A solar PE stamp is a licensed professional engineer’s seal on solar permit drawings, certifying the structural or electrical engineering under that state’s licensing law. No national rule says when one is required. The local authority having jurisdiction (AHJ) sets the trigger, and the sealing engineer must hold an active license in the project’s state.
This guide provides a verification method and an official licensing-board directory for every state. It does not turn a state licensing rule into a statewide solar permit rule.
What does a solar PE stamp mean?
A PE stamp identifies engineering work prepared under a licensed Professional Engineer’s responsible charge. The seal links the work to that engineer and the state’s professional regulation system. It is not a promise that a permit will be approved. The same rule applies when drafting is done offshore, as our domestic vs offshore permit design comparison explains.
The stamp can apply to one discipline or a defined set of sheets. A structural review does not automatically cover the electrical design. An electrical seal does not establish roof capacity.
| Reviewed scope | Typical questions addressed | Documents that may carry the seal |
|---|---|---|
| Structural | Can the existing structure resist added gravity, wind, and snow effects? | Calculations, attachment details, framing plans |
| Civil | Are grading, drainage, access, and foundations adequately designed? | Civil plans, drainage details, foundation sheets |
| Electrical | Does the engineered electrical design satisfy the adopted rules? | Single-line or three-line diagrams, calculations, details |
The exact practice boundaries depend on state law and the engineer’s competence. The permit checklist controls which documents the reviewer expects.
Who decides whether solar plans need PE stamping?
Two authorities answer different questions.
- The state licensing board governs engineering practice. It sets licensure, seal, signature, and responsible-charge rules. The NCEES member licensing board directory links to the official board for each jurisdiction.
- The authority having jurisdiction sets the permit path. The local building department may use a prescriptive checklist, an expedited pathway, or a full engineered review. See the AHJ definition if that term is new.
- The adopted code and project facts shape the review. Building type, attachment method, environmental loads, and existing construction can change the evidence required.
- The utility may run a separate review. Interconnection documents do not replace building-permit documents. Requirements can overlap, but they are not interchangeable.
This division explains why a broad statement such as “Florida requires stamps” is too loose. It does not identify the permit authority, project type, discipline, or document.
Is there a statewide solar PE stamp rule?
Do not assume one exists. A board rule can say how an engineer must seal work without saying when a rooftop solar permit needs engineering.
California provides a useful example. Its Professional Engineers Act governs engineering practice. The state’s Solar Permitting Guidebook, fourth edition describes an expedited process and prescriptive eligibility. Neither source supports a claim that every California solar project needs a stamp.
Florida also separates these issues. Florida Administrative Code Rule 61G15-23.001 addresses signatures, dates, and seals on engineering documents. The project still needs the current building-department checklist and applicable product or structural documentation.
Use this wording when research remains incomplete:
No statewide solar-specific trigger was verified in the reviewed source. Confirm the current permit path with the project AHJ.
That sentence does not mean “not required.” It means the available statewide source did not answer the local permit question.
Solar PE stamp requirements by state: 50-state table
This matrix is a licensing-source directory, not a blanket permit verdict. The official board link verifies who regulates engineering in that jurisdiction. It does not prove that every solar project needs a seal.
Matrix status: reviewed September 26, 2026. The project-level result for every row is AHJ verification required. Check the current municipal or county checklist before design begins.
| Jurisdiction | Engineering licensing source | Statewide solar trigger status | Permit action |
|---|---|---|---|
| Alabama | Alabama Board | Not established by the directory | Verify with AHJ |
| Alaska | Alaska AELS Board | Not established by the directory | Verify with AHJ |
| Arizona | Arizona Board of Technical Registration | Not established by the directory | Verify with AHJ |
| Arkansas | Arkansas Board | Not established by the directory | Verify with AHJ |
| California | California BPELSG | Project pathway varies | Verify checklist and prescriptive eligibility |
| Colorado | Colorado AES Board | Not established by the directory | Verify with AHJ |
| Connecticut | Connecticut DCP | Not established by the directory | Verify with AHJ |
| Delaware | Delaware Association of Professional Engineers | Not established by the directory | Verify with AHJ |
| Florida | Florida Board of Professional Engineers | Project pathway varies | Verify with building department |
| Georgia | Georgia PE and LS Board | Not established by the directory | Verify with AHJ |
| Hawaii | Hawaii PVL | Not established by the directory | Verify with AHJ |
| Idaho | Idaho Board | Not established by the directory | Verify with AHJ |
| Illinois | Illinois IDFPR | Not established by the directory | Verify with AHJ |
| Indiana | Indiana PLA | Not established by the directory | Verify with AHJ |
| Iowa | Iowa Professional Licensing | Not established by the directory | Verify with AHJ |
| Kansas | Kansas Board of Technical Professions | Not established by the directory | Verify with AHJ |
| Kentucky | Kentucky Board | Not established by the directory | Verify with AHJ |
| Louisiana | Louisiana LAPELS | Not established by the directory | Verify with AHJ |
| Maine | Maine Board | Not established by the directory | Verify with AHJ |
| Maryland | Maryland Board for Professional Engineers | Not established by the directory | Verify with AHJ |
| Massachusetts | Massachusetts Board | Not established by the directory | Verify with AHJ |
| Michigan | Michigan Professional Engineers | Not established by the directory | Verify with AHJ |
| Minnesota | Minnesota AELSLAGID | Not established by the directory | Verify with AHJ |
| Mississippi | Mississippi PEPLS Board | Not established by the directory | Verify with AHJ |
| Missouri | NCEES listing for the Missouri Board | Not established by the directory | Verify with AHJ |
| Montana | Montana Board | Not established by the directory | Verify with AHJ |
| Nebraska | Nebraska Board | Not established by the directory | Verify with AHJ |
| Nevada | Nevada Board | Not established by the directory | Verify with AHJ |
| New Hampshire | New Hampshire Board | Not established by the directory | Verify with AHJ |
| New Jersey | New Jersey PELS Board | Not established by the directory | Verify with AHJ |
| New Mexico | New Mexico Board | Not established by the directory | Verify with AHJ |
| New York | New York State Education Department | Not established by the directory | Verify with AHJ |
| North Carolina | North Carolina Board | Not established by the directory | Verify with AHJ |
| North Dakota | North Dakota Board | Not established by the directory | Verify with AHJ |
| Ohio | NCEES listing for the Ohio Board | Not established by the directory | Verify with AHJ |
| Oklahoma | NCEES listing for the Oklahoma Board | Not established by the directory | Verify with AHJ |
| Oregon | Oregon OSBEELS | Not established by the directory | Verify with AHJ |
| Pennsylvania | NCEES listing for the Pennsylvania Board | Not established by the directory | Verify with AHJ |
| Rhode Island | Rhode Island Board | Not established by the directory | Verify with AHJ |
| South Carolina | South Carolina Board | Not established by the directory | Verify with AHJ |
| South Dakota | South Dakota Board of Technical Professions | Not established by the directory | Verify with AHJ |
| Tennessee | Tennessee Board | Not established by the directory | Verify with AHJ |
| Texas | Texas PELS Board | Not established by the directory | Verify with AHJ |
| Utah | Utah DOPL | Not established by the directory | Verify with AHJ |
| Vermont | Vermont Board | Not established by the directory | Verify with AHJ |
| Virginia | Virginia APELSCIDLA Board | Not established by the directory | Verify with AHJ |
| Washington | Washington BRPELS | Not established by the directory | Verify with AHJ |
| West Virginia | West Virginia Board | Not established by the directory | Verify with AHJ |
| Wisconsin | Wisconsin DSPS | Not established by the directory | Verify with AHJ |
| Wyoming | Wyoming Board | Not established by the directory | Verify with AHJ |
| Washington, DC | DC Board of Professional Engineering | Not established by the directory | Verify with AHJ |
The repeated status is deliberate. Licensing directories identify regulators. They do not establish local solar submittal rules. Our state reference pages cover licensure detail for less common jurisdictions such as PE licensing for solar in Alaska, Hawaii solar PE licensing and Puerto Rico solar PE licensing.
Which project facts can change the answer?
The address starts the inquiry, but it does not finish it. Reviewers apply a permit path to a specific building and system.
Residential rooftop solar
A qualifying residential rooftop project may fit a prescriptive or expedited pathway. The checklist can set limits for framing, roof condition, array weight, attachments, and electrical configuration.
Do not describe that pathway as a statewide exemption. Confirm every eligibility condition. Record the one that sends the project to engineered review, if any.
Existing conditions matter. A standard racking product does not prove that an unknown roof structure is adequate. Photos also do not establish concealed framing dimensions.
Commercial rooftop solar
Commercial rooftops can introduce long spans, open-web steel joists, lightweight deck, rooftop equipment, and complex load paths. The permit authority may ask for engineering even when a residential checklist would be prescriptive.
Define the structural scope before layout work becomes expensive. An array location can affect point loads, attachment distribution, access, drainage, and fire pathways.
The design team should also identify the record drawings available. A calculation based on assumed joists carries a different risk from one based on verified framing data.
Ground-mounted solar
Ground mounts add geotechnical and civil questions. Foundation type, soil assumptions, frost depth, corrosion exposure, grading, drainage, and flood conditions can affect the design.
A module count alone is not enough for a responsible review. Provide the site plan, topography, equipment geometry, design criteria, and available soil information.
The building permit and land-use review may also be separate. A PE seal on structural sheets does not satisfy zoning, environmental, or access requirements.
Solar carports and canopies
These structures carry solar equipment above occupied or vehicle areas. Their review can include frame stability, foundations, vehicle clearances, drainage, and impact protection.
Treat the canopy as a structure with solar attached. Do not reduce the engineering question to module weight.
Battery storage added to a PV project
Battery equipment can affect structural support, working clearances, fire review, and electrical design. The battery review path may differ from the PV pathway.
Confirm whether the permit is combined or separate. Identify which calculations and sheets require professional engineering, if any.
| Project fact | Why it matters | Evidence to collect |
|---|---|---|
| Permit address | Resolves the governing authority | Parcel record and jurisdiction lookup |
| Building use | Can change code path and review depth | Occupancy and permit history |
| Structural system | Establishes the load path | Plans, field measurements, photographs |
| Mounting method | Controls connection forces and details | Racking data and attachment layout |
| Environmental criteria | Affects wind, snow, flood, and seismic design | AHJ criteria and adopted code |
| Project configuration | Separates rooftop, canopy, and ground-mount scope | Site and array plans |
| Prescriptive exception | Can trigger project-specific engineering | Completed checklist with failed condition marked |
How do you verify the requirement for one project?
Use a project-specific check before estimating the permit package. Save the answer with the job record.
1. Resolve the exact permitting authority
Start with the installation address. City limits, county boundaries, and special districts can change the reviewer. Do not choose an AHJ from the postal city alone.
Record:
- project address and parcel number;
- building department name;
- permit portal URL;
- utility service territory;
- contact name or ticket number for any clarification.
2. Identify the permit path
Find the current checklist for the correct project class. Residential rooftop, commercial rooftop, carport, and ground mount may use different paths.
A prescriptive pathway may avoid project-specific structural calculations when every condition is satisfied. That is not a universal stamp exemption. One out-of-range condition can move the project into engineered review.
3. Extract the actual trigger
Look for precise language around:
- existing framing and allowable spans;
- attachment spacing and mounting method;
- wind design criteria and exposure;
- ground snow load;
- roof covering and roof condition;
- dead load or point load;
- equipment weight and location;
- ground-mount foundations, grading, and drainage;
- electrical calculations or engineered diagrams.
Copy the relevant sentence into the project notes. Include the checklist revision date and page number.
4. Ask a narrow written question
If the checklist is unclear, send the AHJ a specific scenario. Avoid asking, “Do I need a stamp?”
Use a question such as:
This residential rooftop PV system meets every listed condition in the attached prescriptive checklist. Does that checklist allow an unstamped submittal for this address? If not, which sheets or calculations require a state-licensed engineer’s seal?
That wording gives the reviewer enough context to answer. It also separates structural and electrical scope.
5. Verify the engineer and submission format
Use the state board’s public license lookup. Confirm the name, license status, jurisdiction, and relevant discipline. Then check the AHJ’s document rules for electronic signatures, digital seals, or paper originals.
Do not assume that uploading an image of a seal satisfies a digital-signature rule. Florida’s Rule 61G15-23.001 shows why state-specific signature and seal details matter.
6. Freeze the evidence with the permit set
Save the checklist, email response, board lookup, and calculation basis used for the design. Requirements can change between projects.
Our solar permit package checklist shows where this evidence fits within a complete submittal. The AHJ rejection guide explains how missing jurisdiction details create corrections.
What should the verification record contain?
A good record lets another team member reproduce the decision. It should survive staff changes and a later plan-check question.
Use one record per project. Do not treat a past approval as the current rule for a new address.
The record should include:
- the address and confirmed permitting authority;
- the permit type and portal;
- the checklist title, revision, and retrieval date;
- the project’s eligibility result;
- each condition that fell outside the prescriptive path;
- the AHJ response to any written question;
- the required discipline and document scope;
- the engineer’s license verification;
- electronic-signature or paper-submission instructions;
- the person who completed the check and the date.
Keep the source file, not only a screenshot. A screenshot can omit a revision date or surrounding exception.
If an AHJ answers by email, save the full thread. Tie the answer to the address and described system. A general phone comment is difficult to audit.
A compact decision log
The following format works inside a project management system:
| Decision field | Example of acceptable evidence |
|---|---|
| AHJ resolved | Official parcel or jurisdiction lookup |
| Permit path selected | Current AHJ checklist URL and revision |
| Prescriptive path passed | Completed checklist with every condition marked |
| Engineering triggered | Exact checklist clause or written AHJ response |
| Discipline identified | Structural, civil, electrical, or defined combination |
| License checked | Official board record and verification date |
| Submission format checked | Current portal or board instruction |
This log separates evidence from interpretation. It also exposes missing facts before drafting begins.
How should you scope the engineering request?
Ask for a defined review, not “a stamp.” The latter hides the analysis, inputs, and drawing responsibilities behind one word.
Start with the permit requirement. Then map each required document to the person preparing and reviewing it.
| Scope question | What the request should state |
|---|---|
| Jurisdiction | Project address, AHJ, and state |
| Permit path | Residential, commercial, ground mount, canopy, or another defined path |
| Trigger | Checklist clause or written AHJ request |
| Discipline | Structural, civil, electrical, or a defined combination |
| Inputs | Field data, drawings, design criteria, and equipment information provided |
| Deliverables | Calculations, details, plans, response letter, or another named output |
| Responsibility | Who verifies field conditions and who revises the drawings |
| Revisions | What happens when the layout, equipment, or site data changes |
| Submission | Required file format, signature method, and portal rules |
Avoid vague requests such as “stamp the plan set.” A full plan set can contain material outside one engineer’s discipline. It can also contain sheets that the engineer did not prepare or control.
The request should identify dependencies. Structural calculations may depend on the final array layout and attachment spacing. Electrical calculations may depend on selected equipment and service data.
Set a change-control point before the review starts. A module substitution or shifted array can change engineering assumptions. The team needs a clear path for returning those changes to the responsible engineer.
What not to send as final evidence
Early sales material can help with orientation, but it is not always suitable for engineering. Avoid treating these items as verified facts:
- satellite measurements without field confirmation;
- generic framing assumptions copied from another project;
- product data without an exact model number;
- wind or snow values taken from an unrelated address;
- an old AHJ checklist without a revision check;
- a screenshot that omits the source URL and date;
- an installer note that does not explain how a dimension was measured.
Label preliminary information clearly. The engineer can then state what must be verified before the design is released.
What do worked verification decisions look like?
The following scenarios are illustrative. They show the reasoning process, not the rule for any named jurisdiction.
Scenario 1: residential rooftop within a prescriptive checklist
The permit coordinator resolves the city and finds its current residential rooftop checklist. The project team fills every field using verified roof and equipment data.
Every listed condition appears satisfied. The coordinator still checks the checklist’s submission instructions and confirms the selected pathway applies to the address.
The decision record includes the completed checklist, retrieval date, and jurisdiction lookup. It does not say that the entire state exempts residential projects from engineering.
Scenario 2: rooftop project with unknown framing
The same checklist asks for framing dimensions and spans. The site package does not contain them.
The team should not enter a common framing size to keep the project moving. It should request field verification or written AHJ direction.
If the missing condition sends the project outside the prescriptive path, the team records that trigger. It then requests the appropriate engineering review with the verified field data.
Scenario 3: commercial rooftop with record drawings
The owner provides structural drawings, but the proposed array sits near existing rooftop equipment. The engineering request identifies the affected roof area and equipment loads.
The engineer decides whether the available documents support the analysis. The permit coordinator does not treat record drawings as proof that current field conditions match.
The resulting permit package identifies the reviewed scope. Other disciplines remain under their assigned reviewers.
Scenario 4: ground mount with limited soil information
The layout and racking geometry are available, but the project lacks site-specific soil data. The request states that limitation.
The engineer determines what information is necessary for foundation design. The design team does not convert a preliminary soil assumption into a verified site value.
The project record preserves the final basis used. If later geotechnical information differs, the change returns to the responsible engineer.
Scenario 5: plan-check comment affects sealed work
The reviewer requests a revised attachment detail. The permit coordinator sends the full comment and submitted drawing version to the engineer.
The engineer reviews the requested change and its effect on calculations. The drafting team updates the sheet only after receiving that direction.
The response package identifies the revision and includes the required updated signature or seal. It does not reuse an image from the earlier submission.
These scenarios share one habit: the team records why engineering entered the workflow. That record is more useful than a statewide yes-or-no spreadsheet.
When does structural engineering enter the solar workflow?
Structural engineering often enters when the project falls outside a prescriptive path. It can also enter when the AHJ expressly requests calculations.
Common review questions include:
- Does the roof structure support the added equipment loads?
- Can attachments transfer wind forces into the existing structure?
- Do field conditions match the assumptions on the plans?
- Does a ground-mount foundation suit the stated soil assumptions?
- Will a carport or canopy need a project-specific frame analysis?
The answer may be a calculation package, revised attachment layout, field verification, or another design change. A seal should follow engineering work. It should not be treated as a detached graphic added after drafting.
For a deeper look at the deliverable, read the solar structural calculation report guide, and see how to read a PE-stamped solar drawing for what the sealed sheet should show. Heaven Designs also offers solar civil and structural engineering for defined design scopes. Availability of sealing must be confirmed separately for the project jurisdiction.
When might electrical engineering require a seal?
An electrical seal may be requested for a project-specific engineered design. The trigger must come from the applicable reviewer or governing rule.
Potentially relevant documents include:
- single-line and three-line diagrams;
- conductor and overcurrent protection calculations;
- service or feeder load calculations;
- transformer and medium-voltage design;
- grounding and bonding details;
- protection and coordination studies;
- utility-required studies or drawings.
The National Electrical Code provisions still need the edition adopted by that jurisdiction. Naming the newest edition does not prove local adoption.
The permit reviewer and utility can request different material. Map both review paths early. This reduces late redesign after the building package is complete.
Can one PE stamp projects in several states?
Only where that engineer holds the required active license or lawful authority to practice. NCEES records can support comity applications, but they are not a national engineering license.
An engineer licensed in one state may apply elsewhere. The second board still decides whether to issue that license. The engineer should not seal work for the second state before authorization is active.
Multi-state installers should keep a live coverage register. It should record:
| Field | Why it matters |
|---|---|
| Engineer name | Matches the sealed documents and board record |
| State | Confirms the project jurisdiction |
| License number | Supports the board lookup |
| Status and renewal date | Prevents use of an inactive credential |
| Discipline or practice limits | Aligns the engineer with the reviewed scope |
| Firm authorization, when applicable | Some jurisdictions regulate engineering firms |
| Verification date | Shows when the record was checked |
Never market a state as covered from an old spreadsheet alone. Recheck before assigning the project.
How to verify a license record
Use the official state lookup reached through the board. Search by the engineer’s name and license number when both are available.
Match the record to the person signing the documents. Similar names are not enough. Confirm the state, credential type, status, and expiration or renewal information shown.
Some jurisdictions also regulate engineering firms. Check whether the business entity needs authorization for the offered service. An individual’s active license does not answer every firm-registration question.
Save the verification date and source URL. Do not store more personal information than the project record needs.
If the lookup is unavailable, contact the board. Do not rely on a seal image or a third-party directory as proof of current status.
What the license record does not prove
An active record establishes licensure status shown by the board. It does not prove all of the following:
- that the engineer accepted this project;
- that the work falls within the engineer’s competence;
- that the engineer reviewed the final drawing version;
- that the seal and signature are authentic;
- that the permit authority will accept the package;
- that the project satisfies the adopted code;
- that another discipline’s documents are covered.
Those questions need project evidence. Keep the engagement scope, drawing revision, and submission record with the license check.
Are digital PE stamps accepted?
The answer depends on the state rule and the receiving authority’s submission system. A scanned seal image, an electronic signature, and a cryptographic digital signature are not always equivalent.
Verify three items:
- What does the state board require for electronic or digital engineering documents?
- What file type and signing method does the permit portal accept?
- Must revisions receive a new signature, date, or seal?
Do not state that digital seals are accepted everywhere. The safe workflow checks both the professional rule and the portal instructions.
How to control signed electronic files
Treat the signed file as a released engineering document. Preserve it without flattening, extracting, or recombining pages in a way that breaks signature validation.
Use a clear filename and revision. Keep the engineer’s transmitted original and record when it was received.
If the permit portal compresses or transforms files, check its instructions before submission. Do not assume the downloaded portal copy will preserve every signature property.
When a revision is needed, return the source document to the responsible engineer. Do not paste the earlier seal onto a new PDF.
The final package should make document status obvious. Superseded signed files should remain in project history, not in the active submission folder.
What does a PE stamp cost?
There is no defensible national price table. The fee depends on the engineering scope, available field data, project complexity, jurisdiction, and revision terms.
A quote should define:
- discipline and sheets reviewed;
- calculations included;
- field verification responsibility;
- assumptions and exclusions;
- number and type of revisions;
- permit-response scope;
- delivery format;
- governing jurisdiction.
Compare scope before comparing price. A low fee for seal-only handling is not equivalent to a full structural analysis. This article does not publish price ranges because no current first-party source supports a nationwide range.
Does a PE stamp guarantee permit approval?
No. The AHJ retains review authority. A sealed design can still receive comments for code interpretation, incomplete information, product documentation, or mismatched site conditions.
Treat the stamp as professional accountability for a defined engineering scope. It does not certify unrelated sheets. It does not waive the adopted code. It does not bind the plan examiner.
If comments affect sealed work, route them back to the responsible engineer. Do not revise sealed calculations or drawings without that engineer’s review.
How should teams handle comments on sealed drawings?
First, classify the comment. It may concern an engineering assumption, a drafting inconsistency, missing product data, or an unrelated permit item.
Send the engineer the complete correction notice. Include the submitted drawing version and any new field information. Isolated screenshots can remove useful context.
The response should identify what changed and why. If a sealed calculation or drawing changes, the responsible engineer decides the required review and resealing action.
Use document control for every revision:
- Keep the submitted file unchanged.
- Record the comment against the affected sheet.
- Assign the response to the correct discipline.
- Update calculations before dependent drawings.
- Mark the drawing revision clearly.
- Obtain the required signature and seal for revised engineering work.
- Submit the response with a concise comment matrix.
Do not copy a seal from the earlier file. Do not let drafting staff revise an engineering conclusion without review.
The plan-check response letter guide provides a practical format for returning corrections to the AHJ.
What should installers send for engineering review?
A complete input package reduces assumptions and rework. The exact list varies, but this starting set is useful:
- project address and AHJ;
- current AHJ checklist;
- site survey and clear roof photographs;
- framing size, spacing, span, and condition;
- roof covering and attachment details;
- module, inverter, and racking data sheets;
- array layout and equipment locations;
- design criteria used by the jurisdiction;
- existing electrical service information;
- known deviations from the prescriptive path;
- reviewer comments from earlier submissions.
Mark unknown field data as unknown. Do not convert an unverified assumption into a site fact.
Heaven Designs can prepare solar permit design documents around an agreed scope. PE sealing, state coverage, and submission timing require separate written confirmation. Use the contact page to share the project address and AHJ checklist.
Solar PE stamp FAQ
Is a PE stamp always required for commercial solar?
No universal rule supports that statement. Commercial projects often receive more detailed review, but the actual requirement comes from the governing law and the AHJ’s permit path.
Is a PE stamp always required in Florida’s High-Velocity Hurricane Zone?
Do not infer a universal answer from the zone name alone. Check the current building-department requirements, project type, product approvals, and engineering scope. Florida’s board rules govern how engineering documents are signed and sealed.
Can an out-of-state PE seal the plans?
Not merely because the engineer holds a license elsewhere. The engineer must have lawful authority to practice in the project jurisdiction. Verify the active state record before submission.
Does SolarAPP+ remove every engineering requirement?
No. An automated or expedited permit path has eligibility conditions. A project outside those conditions may need additional review or documentation. Confirm the AHJ’s current implementation and the project’s eligibility.
Can a permit designer add a PE seal after drawings are complete?
The responsible engineer must review work within the requirements of state law. A seal is not an administrative add-on. The design inputs, calculations, and drawings may need revision before sealing.
How often should this matrix be rechecked?
Check the licensing board and AHJ source for every project. Review the directory at least quarterly for operational planning. Recheck immediately when a board link, permit portal, code edition, or checklist changes.
The decision to make before drafting
Resolve four facts first: the correct AHJ, the permit path, the out-of-path condition, and the licensed engineer’s scope. Then build the drawing set around those facts.
That sequence is more reliable than adding a stamp near submission. It also creates a record that estimators, designers, engineers, and permit coordinators can audit.
Source status: The regulatory sources and board directory were checked on September 26, 2026. Local permit requirements remain project-specific, so get written confirmation from the licensing board and the authority handling your permit before relying on any entry here for a live project.