Structural Review for Rooftop Solar: Process and Triggers

A roof can support decades of ordinary service and still need careful review before it carries a new photovoltaic system. The question is not whether the building has stood this long. The question is whether the proposed configuration, at the verified location and under the applicable design basis, can be accepted by the responsible professional for its intended use.

That decision cannot be inferred from a satellite image, a module count, or a salesperson’s observation that the roof “looks solid.” A rooftop solar structural review connects building evidence, field investigation, array geometry, support conditions, design loads, and governing requirements. It also says what remains outside the review.

This guide helps installers and commercial solar teams build that process. It is not structural engineering advice and does not establish that any roof is suitable. The licensed or otherwise qualified professional, authority, building owner, insurer, roofing parties, and applicable project documents control their respective decisions.

Make the review request specific

“Please approve the roof for solar” is not a usable brief. A reviewer needs to know what decision the project expects and which design stage the evidence supports. Early screening, proposal support, permit design, procurement release, and construction release carry different consequences.

Write the requested decision in one sentence. For example: “Assess whether the proposed array areas and support concept can proceed to detailed design, and identify field information required before permit release.” That sentence invites a qualified answer and keeps a preliminary review from becoming a final approval through repetition.

The review request should state:

• building and roof area identity;
• project jurisdiction and known governing basis;
• proposed PV scope and current design revision;
• intended output, such as screening, permit, or construction support;
• documents and field evidence available;
• conditions known to be uncertain or inaccessible;
• other work that may affect the roof;
• date and project decision the response must support.

Do not specify the engineering conclusion in the request. “Confirm no reinforcement is needed” asks the reviewer to ratify a commercial assumption. Ask what evidence and analysis support an acceptable path, including limitations and changes that would reopen the decision.

What should a rooftop solar structural-review packet contain?

A rooftop solar structural-review packet should contain the requested decision, building and roof identity, source register, alteration history, proposed array and equipment revision, support concept, product documents, known loads and assumptions, field evidence, governing basis, interface owners, intended release, and open questions. It should distinguish measured, documented, assumed, and unresolved inputs so the reviewer can define an investigation and scope.

Build the packet from an index rather than a folder dump. The reviewer needs to know which documents are current, which roof area each record describes, and where evidence conflicts. A long collection of unlabeled photographs or drawings can create more identity work than useful structural information.

Use this intake table:

Use this copy-ready cover:

Building, roof area, and project revision:
Structural decision requested:
Intended downstream use:
Current drawings and alteration records:
Array, equipment, and support-concept revision:
Documented and measured inputs:
Assumed or unresolved inputs:
Field access and evidence limitations:
Interface decisions owned elsewhere:
Required response, limitations, and reopen triggers:

Do not translate missing structural evidence into a commercial assumption. The review request may identify an allowance, excluded area, or schedule dependency under the project’s commercial process, but the responsible structural professional decides what evidence and analysis are needed for the technical decision.

Before sending the packet, ask someone outside its preparation to locate one roof area, one proposed support zone, one open assumption, and the exact decision requested. If they need a verbal tour, repair identity and indexing before consuming specialist time.

Establish building identity before analyzing loads

Commercial sites often contain additions, roof levels, canopies, mechanical screens, and structures built under different documents. A drawing labeled with the right address can still describe the wrong roof area or a condition changed during later work. Match the records to the physical building before relying on them.

Create a building evidence register:

NIST’s disaster and failure studies collection describes investigations and technical work related to building and infrastructure performance. It is not a project assessment resource. It supports the broader discipline of grounding conclusions in identified evidence rather than visual confidence.

If records conflict, preserve the conflict. Do not select the most convenient drawing without a reason. Ask the reviewer what additional survey, opening, measurement, testing, or document search is warranted.

Describe the proposed solar system as structural inputs

The structural reviewer does not need a glossy proposal. They need a configuration that can be translated into physical effects on the building. Provide array zones, module and racking geometry, equipment locations, support or attachment concept, proposed clearances, and the current product documents that define weights and interfaces.

Distinguish distributed and concentrated effects. A project summary may state a total system weight, while the roof responds to load paths, support spacing, local reactions, uplift, sliding, snow interaction, drainage conditions, and other effects evaluated under the applicable basis. The responsible engineer determines which effects and combinations apply.

ASCE describes ASCE/SEI 7 as a standard addressing minimum design loads and associated criteria for buildings and other structures. A website link does not identify which edition, amendments, risk category, or load criteria govern a project. Record the basis selected by the responsible professional and the authority.

Provide the array in layers:

1. roof plan with identifiable zones and obstructions;
2. module orientation, row geometry, and edge relationships;
3. racking or support concept with attachment or ballast assumptions;
4. equipment point locations and service paths;
5. current product weights and dimensions from manufacturer documents;
6. intended roof penetrations, curbs, pads, or reinforcing concepts;
7. future options that are excluded from the present review.

An option should not become part of the accepted structural scope merely because it remains visible in a design file. Label alternatives and abandoned scenarios clearly.

Screen for evidence triggers before detailed design

A screening stage helps the team decide whether existing information supports further layout work or whether field and engineering work must come first. Screening should route uncertainty; it should never be presented as structural acceptance.

Common evidence triggers include missing structural drawings, unknown framing, conflicting spans, corrosion or deterioration, leakage or ponding, prior roof alterations, planned reroofing, unusual equipment loads, inaccessible areas, and a proposed support system that differs from the available records. Building age alone is not a conclusion, and a recent roof membrane does not prove the underlying structure.

The Department of Energy’s rooftop solar potential page discusses technical rooftop potential at broad scale. Technical potential is not project permission. An individual building still needs site-specific design, ownership, economic, structural, electrical, and regulatory decisions.

Use three screening outcomes:

• Proceed with qualified concept work: current evidence supports an early layout for discussion, with structural assumptions and release limits visible.
• Collect defined field evidence: the reviewer identifies observations, measurements, openings, tests, or documents needed before the next decision.
• Escalate before design continues: an observed condition or missing basis is too material for the intended work to proceed responsibly.

Do not create a fourth outcome called “probably fine.” It has no evidence threshold and tends to follow the project into customer conversations.

Plan field investigation around the open questions

A site visit should be designed by the questions that need resolution. Sending a surveyor to “take roof photos” can produce hundreds of images and no usable framing record. The structural reviewer should identify the observations and measurements needed, who is qualified to collect them, and how locations will be mapped.

The plan may address framing direction and spacing, member size where observable, deck type, connections, equipment and curb locations, roof condition indicators, drainage, alterations, access, and areas that remain concealed. The actual scope varies. Do not instruct unqualified staff to expose structure, walk unsafe surfaces, or make engineering judgments.

OSHA’s construction standard for fall protection duties applies to covered work and conditions. A structural survey checklist does not replace the employer’s safety program, competent-person decisions, access planning, or other applicable requirements. If safe access cannot be established, record the evidence gap and obtain direction.

Give each field record a location reference. A photograph called roof1.jpg cannot reliably support an engineering question on a large facility. Use a roof plan, grid, marked elevation, or another agreed system. Include date, direction, observer, and any measurement method.

How should missing structural evidence be handled?

Handle missing structural evidence by naming the question, affected roof area and decision, evidence checked, qualified owner, investigation required, interim use, and work that must be held. Do not invent framing, condition, connection, load, or capacity information. A narrower concept may proceed only when the structural reviewer accepts its limitations and the release prevents provisional inputs from becoming construction facts.

Use a hold when the missing fact can invalidate the intended decision. The hold should be specific enough for the next person to collect useful evidence. “Verify structure” does not identify a location, observation, record, access method, or reviewer response.

Use this sequence:

1. Identify the exact building, roof area, support concept, and design revision affected.
2. State the missing, conflicting, or inaccessible evidence without proposing an engineering conclusion.
3. List records and observations already reviewed.
4. Ask the structural reviewer what investigation, access, measurement, testing, or document search is required.
5. Assign field and document tasks only to people qualified for their scope.
6. Record safe-access and operational constraints separately from the technical question.
7. Define work or customer discussion allowed before closure.
8. Block permit, procurement, installation, or another dependent release where required.
9. Route returned evidence through identity and quality checks.
10. Obtain the qualified disposition and update every affected project record.

Illustrative workflow example, not a structural assessment: A proposed array uses a roof area whose available drawings do not match visible alteration lines in current photographs. The framing and alteration history cannot be established from the desk record. The design team does not select whichever drawing preserves the largest array.

The structural reviewer defines the document search and field observations needed. The affected roof area is held from the higher-consequence release, while another clearly identified area may remain available for qualified concept work if the reviewer accepts that boundary. Customer and procurement documents exclude or visibly qualify the held area instead of carrying its modules as settled scope.

When evidence returns, confirm building, roof zone, date, observer, method, and limitations before analysis. An unlabeled photograph or isolated dimension can add apparent detail without resolving identity. If the new evidence conflicts again, preserve both sources and return the question to the qualified reviewer.

Close the hold only when the structural disposition, design constraints, affected layout, procurement status, drawing package, field instruction, and reopen trigger agree. A new report stored in a folder does not update dependent work automatically.

Give the reviewer an assumption register

Every structural analysis uses inputs and interpretations. The project record should distinguish measured or documented facts from engineering assumptions and from unresolved information. Otherwise, a provisional member size or support spacing can be copied into later revisions as if somebody verified it.

An assumption register can include:

The responsible reviewer decides which assumptions can remain for a stage. The project team should carry those limitations into the drawing, proposal, schedule, and release record. A structural report filed away from the layout cannot protect the boundary if the layout changes later.

Review the complete load path and interfaces

Rooftop solar does not stop at the racking. The reviewer may need to examine how forces travel through attachments or ballast, roof assembly, deck, framing, connections, and supporting structure. Local effects can control even when a broad area-average check appears comfortable. Wind, snow, seismic, dead, live, and other applicable effects need the governing combinations and project inputs selected by the responsible professional.

FEMA’s building science resources cover hazard-resistant buildings and related technical guidance. These resources do not provide a one-click rooftop PV acceptance. They underline why hazard, building system, location, and load path belong in a structural decision.

Coordinate interfaces beyond calculation:

• roofing warranty, penetrations, flashing, and waterproofing responsibility;
• drainage and maintenance access;
• attachment installation and inspection requirements;
• equipment pads, curbs, and concentrated loads;
• fire and emergency access requirements owned by the relevant reviewer;
• electrical routing and equipment locations;
• construction sequence and temporary conditions.

One approval does not absorb the others. A structural detail can be acceptable in its own scope while roofing coordination remains open. The release record should list those open interfaces and owners.

Translate the review into usable design constraints

A report is only useful when the design team can apply its conclusions correctly. Convert accepted findings into location-specific constraints: usable roof zones, excluded areas, support spacing or details, equipment location limits, required reinforcing, field verification notes, and revision triggers. Keep the engineering source attached.

Avoid paraphrasing technical conditions into looser sales language. “Acceptable only with reinforcing shown on S-5” should not become “roof approved.” The former identifies a condition and source; the latter discards both.

The design release should show:

1. reviewed array and equipment revision;
2. structural report or calculation reference and date;
3. required details and reinforcing;
4. field verification required before or during work;
5. areas or options outside the review;
6. changes that require renewed structural review;
7. parties responsible for roofing and other interfaces.

If a constraint cannot be represented in the design system, add it to the release checklist and drawing notes. Do not rely on the engineer remembering to catch it again.

Reopen review when the structural basis moves

Structural acceptance applies to a defined configuration and evidence set. Reopen it when the array footprint changes near roof edges or zones, equipment weight or location changes, the attachment or ballast system changes, field conditions differ, reinforcing is modified, roof work changes the assembly, or governing criteria and external comments alter the basis.

Use a delta request instead of asking for a complete review with no context. Provide the prior accepted revision, exact proposed change, reason, affected locations, new product information, and any new field evidence. Ask whether previous conclusions remain applicable and which documents must be revised.

The prior reviewer is often best placed to assess the delta, but project arrangements may require another professional. When responsibility changes, transfer the complete evidence and assumption record. A new signature on an incomplete package does not restore lost context.

Field discoveries need prompt routing. If an attachment location conflicts with observed framing, preserve the condition, stop affected work as required, and request direction. Do not move supports casually and assume the overall array weight makes the change insignificant.

When can a prior structural review carry forward after a revision?

A prior structural review can carry forward only for conclusions the responsible structural professional confirms remain applicable to the revised configuration and evidence. Provide the former review, design delta, affected roof locations, new product documents, field findings, and changed governing inputs. Record which conclusions survive, which reopen, what drawings or constraints change, and which release or customer documents are superseded.

Use a delta packet rather than sending the new layout with “please reconfirm.” The reviewer should be able to compare the former accepted array, equipment, support basis, assumptions, and roof zones with the proposed revision. Mark generated differences that were not requested, because a rerun can change neighboring geometry or quantities.

Use this carryover record:

Prior structural review and accepted revision:
Proposed design or evidence change:
Affected roof zones and interfaces:
Product or support documents changed:
New field observations:
Former assumptions affected:
Qualified conclusions carried forward:
Checks, details, or reinforcing reopened:
Downstream documents to revise:
Current release limits and reviewer:

Do not copy the former engineer’s acceptance onto a new option. The current package should show the professional act and scope required by the project, jurisdiction, and organization. A decision can remain technically applicable while a new signed, sealed, or otherwise formal record is still required by the governing process.

Run a regression review after the delta is accepted. Confirm that revised layout and equipment records honor the new structural constraints, while unchanged roof zones still reflect their retained conditions. Check that proposal, BOM, permit set, procurement, and field packages use the same option.

This article remains human-review-only. Structural capacity, loads, combinations, analysis, support, attachment, ballast, reinforcing, inspection, field acceptance, code, safety, and professional responsibility belong to the qualified structural reviewer and applicable authorities. The workflow controls evidence and handoffs; it makes no roof-suitability conclusion.

Before distributing the revised package, give its index to a project role that did not prepare the delta. That person should identify the reviewed roof zones, current array and equipment revision, retained conclusions, reopened conditions, required field evidence, and permitted downstream use without verbal coaching.

Ask the recipient to locate one structural constraint in the active layout and one open interface in the release record. If either exists only in a report narrative that design, procurement, or field staff cannot connect to their work, the handoff remains incomplete.

Record the return reason precisely. Missing zone identity, stale product data, buried assumption, absent field hold, or mismatched customer view requires another correction path. Do not resolve confusion in a meeting and leave the package index unchanged.

After acceptance, preserve the issued set and open a new working revision for later changes. This gives the reviewer a stable historical basis for future delta decisions.

Keep customer and procurement documents inside the boundary

A structural review can change module count, array zones, attachment quantity, reinforcing, schedule, access assumptions, and price. Reconcile those changes with the current proposal, bill of materials, procurement releases, permit set, and field package. The customer should not receive a layout that the technical record no longer supports.

Solar Designing supports roof modeling and array layout, Shadow Analysis supports shade modeling, and Solar Proposals supports customer-facing output. Electrical design provides a related workflow context. These tools can keep records closer, but the responsible people still verify inputs and approve the work within their authority.

Results depend on source data, assumptions, equipment models, configuration, and review. Outputs support design and documentation workflows but do not replace approval by the responsible engineer, authority, lender, insurer, or utility.

Audit the handoff, not only the calculation

Give the released package to a designer or project manager who did not attend the review. Can they locate the accepted array revision, identify excluded zones, find required reinforcing, distinguish assumptions from field facts, and name the changes that reopen review? If they need a verbal reconstruction, the structural work has not been translated into project control.

Then trace one design change through the system. Move a proposed equipment item in a test copy or alter an array zone. Does the workflow flag structural review, or can the revised layout proceed directly to proposal and procurement? The test reveals whether review is a living dependency or merely a completed task in a schedule.

Record returned packages by cause: missing building identity, stale product data, incomplete field mapping, assumption copied as fact, design outside reviewed zones, or structural conclusion absent from the drawing. Improve the earliest control that could have caught the problem.

Assign ownership at the interfaces

Structural review slows down when everybody can identify a concern but nobody owns the next decision. Build an interface matrix at intake and update it after the reviewer defines the required work. The matrix should name a role, deliverable, and acceptance point rather than listing a department that may assume another person is acting.

The structural reviewer may define loading, analysis, member checks, attachment criteria, or reinforcing within an agreed scope. The solar designer owns accurate array geometry and current equipment inputs. A roofing party may advise on assembly, penetrations, warranty, and waterproofing requirements. The building owner supplies available records and access. The project manager keeps conditions and revisions moving between them.

Do not ask the structural reviewer to own product availability or customer communication by default. Do not ask the salesperson to translate an engineering limitation from memory. Give the approved wording and source to the person responsible for the customer conversation.

The interface matrix also helps with substitutions. Procurement can raise a proposed product change, but design and structural reviewers decide whether geometry, weight, reactions, or details need revision. The buyer should receive a clear accepted state before releasing the alternate. If the project must reserve material while review continues, label the commercial risk and authority rather than presenting the reservation as technical acceptance.

At construction handoff, read every structural hold point aloud with the people who will collect evidence. A requirement to verify framing at selected locations is useful only if the installer knows the locations, the record format, and who can release affected work. “Engineer to confirm” on a sheet does not create that path by itself.

Store the resulting field record beside the reviewed detail, not in a separate photo thread. Identify the observer, location, date, drawing revision, requested decision, and response. If the observation differs from the assumed condition, route the delta back before the affected installation continues. That chain preserves what the reviewer actually saw and accepted.

A useful rooftop solar structural process is proportionate. It does not demand final analysis before an early layout conversation, and it does not allow an early screen to masquerade as construction acceptance. It matches evidence and authority to the decision being made, then reopens the review whenever that basis changes.

Frequently Asked Questions

Does every rooftop solar project need structural review?

The required review depends on the building, proposed system, jurisdiction, contract, insurer, and responsible professional. An installer should use a defined screening process and route the project to a qualified structural reviewer whenever required or when evidence cannot support the planned release. A generic checklist cannot grant an exemption.

What information does a structural reviewer need for rooftop solar?

Provide verified building identity, available drawings and reports, roof type and condition, framing observations, alterations, proposed array geometry, equipment and attachment basis, load information, access constraints, governing requirements, and the decision requested. Mark remote estimates and missing records so they are not mistaken for measured conditions.

Can aerial imagery replace a rooftop structural survey?

No. Aerial imagery can support early geometry and planning, but it does not establish concealed framing, material condition, connection details, deterioration, prior alterations, load paths, or safe access. The qualified reviewer should decide what field evidence and testing are needed for the proposed design stage.

When must structural review be repeated?

Repeat or reopen review when the array footprint, equipment weight, support or attachment method, load assumption, roof condition, building alteration, field observation, code basis, or external requirement changes materially. The original reviewer should assess the delta when possible and state whether prior conclusions remain applicable.

Does structural acceptance approve the entire solar design?

No. Structural acceptance addresses only the scope stated by the responsible reviewer. Electrical design, fire access, roofing, waterproofing, worker safety, permitting, utility interconnection, equipment instructions, and contract requirements have their own owners. The project release should make those boundaries visible rather than letting one approval imply all others.