A STAAD report can show that a solar structure works inside a defined model. It cannot prove that the real roof, foundation, connection, or installed structure matches that model. That distinction decides whether an authority, engineer, lender, or client accepts the package.
Direct answer. A STAAD report is analysis evidence, not an approval credential. Reviewers accept a solar structural package when site inputs, adopted loads, model results, connections, foundations, and drawings form one traceable chain. A licensed engineer must review or certify it where required. Exact deliverables follow the jurisdiction and contract. STAAD.Pro output alone does not earn acceptance.
This guide addresses the handoff after analysis. It does not repeat STAAD.Pro model setup or the general contents of a solar structural calculation report. The question here is narrower: what turns software output into evidence that a real reviewer can use?
What can a STAAD report for a solar structure prove?
A STAAD report can prove what a defined analytical model did under stated inputs. It can document geometry, material properties, supports, load cases, combinations, displacements, reactions, member forces, and code checks. It can also expose failed members or excessive movement when the model and reporting scope are complete.
Bentley describes STAAD.Pro as software for modeling, analysis, and design of steel, concrete, and timber structures. The product supports static, dynamic, wind, earthquake, and moving-load analysis. It also includes code checks. Bentley does not describe the output as a permit, professional seal, or lender approval.
That boundary matters. Software can answer questions such as:
- Which modeled member has the highest utilization?
- What reactions reach the modeled supports?
- How much does the frame deflect under a stated combination?
- Which modeled load case controls a member check?
- Do modeled steel members pass the selected design code checks?
Each answer remains conditional. The report is only as sound as its geometry, loads, restraints, releases, sections, material grades, and code settings.
What can a STAAD report not prove?
A STAAD report cannot prove site facts that never entered the model. It cannot verify hidden corrosion, an unknown roof section, soil capacity, anchor installation, concrete strength, weld quality, or drawing revisions. It also cannot decide whether a local authority or lender accepts the package.
The output does not establish these facts by itself:
| Question | Why STAAD output is insufficient |
|---|---|
| Does the existing roof have reserve capacity? | The building members and condition need reliable survey or record data. |
| Will an anchor resist pullout? | The substrate, embedment, edge distance, installation, and tested capacity sit outside a frame model. |
| Is the foundation adequate? | Soil parameters and foundation checks must connect to model reactions. |
| Do the drawings match the analysis? | Software cannot control a separate drawing revision unless the workflow does. |
| Is a professional seal required? | Licensure law and the reviewing jurisdiction decide. |
| Will a lender accept the package? | The finance documents and independent engineer scope decide. |
One green utilization table is therefore weak evidence when the load path stops at an idealized support. A structural design scope must connect that support reaction to a real attachment or foundation.
What is the Seven-Link Solar Acceptance Chain?
The Seven-Link Solar Acceptance Chain is a repeatable review method. Its links are site inputs, governing criteria, load derivation, structural model, local checks, coordinated drawings, and qualified review. Every reviewer enters this chain at a different point. A missing link can make correct software output unusable.
| Reviewer | What STAAD output can support | What must accompany it | Who decides acceptance |
|---|---|---|---|
| AHJ | Analysis results under stated loads and code settings | Local code basis, site data, calculations, coordinated drawings, and a seal when required | Building official or delegated reviewer |
| Licensed PE | Evidence for technical review | Source model, inputs, calculations, drawings, limitations, and responsible-charge review | Engineer licensed for the project jurisdiction |
| Lender or IE | Structural evidence inside technical due diligence | Design basis, geotechnical data, calculations, certified drawings, issue register, and contract deliverables | Finance documents and independent engineer scope |
| EPC or owner | Engineering handoff and procurement evidence | Editable files, approved equipment, fabrication details, revision control, and closeout record | Contract, specifications, and project QA plan |
The table is a routing tool. It is not a universal checklist. A residential roof, utility ground mount, carport, tracker, and floating structure can require different evidence.
Teams can apply the chain in either direction. The designer moves from source inputs toward issued drawings. The reviewer can start at a drawing detail and trace demand back to its source. Both routes should reach the same evidence without an unexplained jump.
Which inputs prove that the model belongs to the project?
Project identity comes from traceable source inputs, not from the file name. A reviewer should be able to connect every controlling input to a survey, record drawing, equipment submittal, geotechnical report, code source, or approved assumption. The report should also identify who provided it and when.
Use an input register before modeling begins:
| Input group | Source evidence | Status to record | Why it matters |
|---|---|---|---|
| Site identity | Address, coordinates, parcel data, and site plan | Verified, provisional, or disputed | Environmental values and jurisdiction depend on location |
| Existing structure | Survey, record drawings, field measurements, and condition notes | Verified, sampled, or unknown | Roof and attachment checks depend on actual members and condition |
| Solar equipment | Module, rail, tracker, inverter, and mounting submittals | Approved, proposed, or substituted | Weight, dimensions, geometry, and connection forces can change |
| Environmental criteria | Wind, snow, seismic, flood, terrain, and topographic sources | Source, edition, and access date | Loads must match the project location and governing criteria |
| Ground conditions | Geotechnical report, testing, and stated design parameters | Final, preliminary, or excluded | Foundation response cannot be inferred from frame analysis |
| Project criteria | Owner requirements, lender schedules, AHJ checklist, and specifications | Current revision and owner | Contract limits may exceed code minimums |
Avoid silent assumptions. If a roof member cannot be verified, the calculation should state the assumed section and the required field confirmation. If geotechnical data is missing, the package should identify the foundation checks that remain open. A clear limitation is more useful than a false statement of completeness.
Input status also affects procurement. A report based on proposed modules should not release final fabrication without an equipment-change check. A model based on preliminary soil values should not become a final foundation design by changing the title block.
Reviewers should see the source date and revision beside each important input. This lets them detect stale equipment data or a survey that predates a roof modification. It also gives the project manager a defined closeout list.
Review test. Select one controlling load and ask for its source, edition, project location, calculation, model case, result, and drawing destination. One missing step exposes a traceability gap.
What does an AHJ need with a STAAD report?
An AHJ needs enough information to verify the applicable building requirements and the installed load path. The package usually needs a code basis, site-specific environmental inputs, structural calculations, member and connection details, and drawings that agree with the calculations. The local building official decides the exact route.
Some residential projects use a prescriptive path rather than a custom structural model. The SolarAPP+ eligibility guidance limits its automated route to eligible residential rooftop systems. Its linked checklist, dated September 16, 2025, excludes ground mounts, carports, and structural modifications. The checklist also limits PV system and hardware weight to 4.0 pounds per square foot.
That example corrects a frequent assumption. A permit package does not need a STAAD report merely because solar equipment has weight. A qualifying system may use a prescriptive route. A project outside that route may need project-specific structural evidence.
An older California example shows the same split. The California Solar Permitting Guidebook, Fourth Edition says listed residential criteria can avoid additional calculations when every criterion passes. When criteria fail, it calls for project-specific drawings and calculations signed and stamped by a California-licensed civil or structural engineer. The guidebook reflects its 2019 publication context, so it should illustrate the process rather than establish a current code edition.
An AHJ reviewer should be able to answer four questions from the submitted set:
- Which code and local amendments govern this project?
- Where did the wind, snow, seismic, dead, and live loads come from?
- How do model reactions reach the building or ground?
- Do the issued drawings show the analyzed geometry and connections?
A report that cannot answer those questions is not ready for permit review.
What must a licensed engineer verify before sealing?
A licensed engineer must exercise professional judgment over the work, not simply attach a seal to software output. The engineer needs the source inputs, model assumptions, calculations, drawings, and revision history. State or territorial law controls licensure and sealing requirements in the United States.
The National Council of Examiners for Engineering and Surveying explains that the United States has no single nationwide PE license. State and territorial boards grant licenses, and their requirements differ. NCEES also identifies stamping and sealing designs as an activity that requires PE licensure.
For a solar structure, the engineer’s review should address at least:
- the project jurisdiction and adopted code basis.
- basic wind speed, exposure, topography, snow, seismic, and other site inputs.
- model geometry against the issued layout and structural details.
- supports, member releases, offsets, and effective lengths.
- member properties, grades, slenderness, and connection assumptions.
- load cases, combinations, directions, and governing results.
- foundation or attachment design using extracted reactions.
- serviceability limits and any client-specific criteria.
- changes after equipment selection or layout revision.
The wind and snow criteria source matrix shows which state, local, and hazard sources belong in that input record.
The structural PE stamp guide explains the US permit context in more detail. A foreign analysis team can prepare calculations. It should not imply that its report already carries the required local professional authorization.
What do lenders and independent engineers accept?
Lenders and independent engineers accept contract-defined evidence, not a universal STAAD format. Their concern is whether the project design supports construction, performance, insurability, and debt risk. A model report can contribute, but the due-diligence scope decides what must accompany it.
The IFC and World Bank utility-scale solar guide treats detailed design as a coordinated package. It includes mounting-structure drawings with structural calculations reviewed and certified by a licensed engineer. The guide also connects foundation design to geotechnical conditions and calls for project-location wind loads.
That source does not create one lender checklist. It shows the evidence chain expected in bankable design work.
| Due-diligence concern | Evidence beyond a STAAD printout |
|---|---|
| Site suitability | Topographic, geotechnical, hydrological, and environmental inputs as applicable |
| Design basis | Codes, project criteria, equipment data, loads, and assumptions |
| Structural adequacy | Analysis, member checks, connections, foundations, and serviceability |
| Constructability | Drawings, tolerances, interfaces, material specifications, and access |
| Certification | Review or certification by the qualified professional required by contract and law |
| Change control | Model, calculation, and drawing revisions tied to one issue status |
An independent engineer may also request editable model files, sensitivity cases, calculation spreadsheets, or a response log. The finance documents may require a specific certification form. These are contract questions. An engineer should read the technical schedules before deciding the report format.
The independent engineer checklist and lender due-diligence guide cover the wider finance review. A structural package should fit that process instead of arriving as an isolated software attachment.
How do US and Indian documentation paths differ?
Both paths need traceable loads, calculations, drawings, and qualified review. The governing standards, licensure system, approval route, and contract vocabulary differ. Teams should not rename an Indian calculation package as a US permit package without rebuilding the jurisdiction layer.
| Documentation question | Typical US path | Typical Indian path |
|---|---|---|
| Loading basis | Adopted building code and referenced standards, including the locally adopted ASCE 7 edition | Contract and authority requirements using applicable Indian Standards |
| Steel design | Adopted material standard and project specification | IS 800 where applicable |
| Wind loads | Locally adopted edition of ASCE 7 | IS 875 Part 3 where applicable |
| Professional authorization | State or territorial PE requirements | Applicable project, client, lender, authority, and professional requirements |
| Permit decision | AHJ and delegated reviewers | Local authority, electrical inspectorate, DISCOM, owner, or other project reviewer as applicable |
| Finance review | Lender and independent engineer scope | Lender and independent engineer scope |
The American Society of Civil Engineers identifies ASCE/SEI 7-22 as Minimum Design Loads and Associated Criteria for Buildings and Other Structures. That does not mean every US jurisdiction has adopted the 2022 edition. The permit set must name the edition adopted for the project location.
Indian projects need the same edition discipline. A report should cite the exact part and year of each standard. It should not use “IS compliant” as a substitute for load inputs and calculations.
What belongs in the seven-file reviewer packet?
A practical reviewer packet separates source facts, analysis, and issued drawings while keeping their revisions aligned. Seven controlled files are usually enough to make ownership visible. Large projects may split them further.
| File | Minimum contents | Review purpose |
|---|---|---|
| 1. Design basis | Scope, codes, criteria, equipment, materials, and limitations | Defines what the analysis means |
| 2. Site input register | Coordinates, wind, snow, seismic, terrain, topography, and geotechnical source | Makes environmental inputs traceable |
| 3. Load calculation | Dead, live, wind, snow, seismic, and project loads with combinations | Shows how actions entered the model |
| 4. Analysis report | Model diagrams, supports, results, utilization, reactions, and serviceability | Documents structural response |
| 5. Connection and foundation calculations | Bolts, welds, anchors, base plates, piles, footings, and substrate checks | Completes the load path |
| 6. Coordinated drawings | Plans, elevations, sections, details, member marks, and notes | Shows what will be built |
| 7. Issue register | File names, revisions, dates, open items, responses, and approvals | Prevents mixed-revision review |
The packet should use one project identifier and one issue status. If the STAAD model says Revision C while drawings show Revision D, the reviewer cannot know which geometry governs.
Which STAAD outputs should the report expose?
A useful report exposes enough model evidence for an independent check without burying the reviewer in thousands of software pages. The selection should follow the review question. A member design review needs different evidence from a foundation-reaction review.
Include these core outputs:
| Output | What it lets the reviewer test | Common reporting error |
|---|---|---|
| Model geometry views | Member connectivity, orientation, and overall form | Views are too small to read member labels |
| Node and member references | Traceability between calculations, output, and drawings | Drawing marks do not match model marks |
| Supports and releases | Whether the structural idealization matches the intended connection | Every base is fixed without a detail that can provide fixity |
| Section and material tables | Sizes, grades, stiffness, density, and design parameters | Default material properties remain in the model |
| Load diagrams | Direction, magnitude, area conversion, and application point | Final loads appear with no derivation |
| Load combinations | Strength and serviceability cases | The report omits one sign or wind direction |
| Displacements | Serviceability response and instability clues | Only the maximum value appears without its case and location |
| Member forces and utilization | Governing demand, capacity, and code check | A pass table hides warnings or unclassified members |
| Support reactions | Inputs for anchor, base plate, pile, footing, or roof checks | Reactions are issued without a sign convention |
| Analysis warnings | Instability, duplicate nodes, disconnected members, and solver concerns | Warnings are removed from the final PDF |
Do not export every page because the software offers it. A shorter report with a clear index and supporting native model is easier to audit. Put detailed result tables in an appendix when they support a specific review question.
Model warnings need an explicit disposition. Some warnings may be benign after engineering review. Others reveal a broken load path or numerical instability. Record who reviewed each warning and why the model remains valid.
How should the source model be checked before its results?
Check the model behavior before trusting its utilization ratios. A clean pass table can coexist with duplicate nodes, disconnected members, unintended releases, wrong local axes, or unrealistic support stiffness. Review should begin with equilibrium and deformation, then move to member code checks.
A practical source-model review follows this order:
- Confirm geometry. Compare bay spacing, slopes, member marks, heights, and support locations with the issued drawing.
- Inspect connectivity. Look for duplicate nodes, isolated members, short members, offsets, and unintended gaps.
- Verify member orientation. Confirm local axes, beta angles, releases, offsets, and tension-only or compression-only definitions.
- Check loads visually. Plot each load case. Confirm direction, magnitude, tributary width, units, and application point.
- Test equilibrium. Compare applied loads with support reactions for simple cases. Large unexplained differences require investigation.
- Read the deformed shape. The movement should match the expected structural behavior. Unexpected twists can reveal modeling errors.
- Review analysis messages. Resolve instabilities, zero stiffness, duplicate specifications, and failed design commands.
- Check governing results. Trace the critical member and support back to their load combinations and drawing locations.
Simple independent checks add value. An engineer can estimate gravity reaction from tributary area or approximate frame deflection by hand. These checks do not replace the model. They test whether its scale and behavior are plausible.
Unit discipline is equally important. Project teams often exchange roof loads in pounds per square foot, wind pressure in kilopascals, member dimensions in millimeters, and drawing levels in feet. The report should state its unit system on every result table. Conversion calculations should remain visible.
The source model review should end with a short disposition log. Each concern needs an owner, answer, model revision, and result. A screenshot without the native model rarely supports this review because it hides assignments and solver settings.
How should reactions connect to attachments and foundations?
Support reactions are the handoff between global analysis and local design. State the coordinate system, sign convention, governing combination, and result basis. The local check must use the same basis.
For a rooftop frame, the next calculation may include a base plate, weld, bracket, fastener group, roof sheet, purlin, rafter, slab, or concrete anchor. For ground mount work, it may include a post, pile, footing, soil bearing, sliding, overturning, and uplift.
Use a reaction transfer table:
| Model support | Governing reaction | Local component | Downstream check | Drawing detail |
|---|---|---|---|---|
| S1 | Uplift and shear from named combination | Rail bracket and fastener group | Pullout, shear, interaction, and substrate | Detail S-501 |
| S2 | Compression, shear, and moment | Base plate and anchors | Plate bending, anchors, and concrete breakout | Detail S-502 |
| P1 | Axial, lateral, and moment demand | Driven pile or drilled foundation | Structural capacity and geotechnical response | Detail S-601 |
The labels above are examples only. A real table should use project member marks and actual drawing references. Its value is the join between global and local calculations.
If the foundation engineer receives only a maximum reaction, ask whether every governing combination and sign is included. Maximum compression, uplift, shear, and moment may occur in different cases. An envelope can create an impossible combination when unrelated maxima are combined without engineering judgment.
How should a team run the acceptance register?
An acceptance register turns vague comments into controlled decisions. Each row names the reviewer, requirement source, evidence owner, file revision, response, and closeout status. It also prevents the team from treating a software pass as a closed review comment.
Use these fields:
| Field | Entry to record |
|---|---|
| Reviewer | AHJ, PE, lender IE, owner, EPC, or fabricator |
| Requirement source | Code section, checklist, contract schedule, or written comment |
| Requested evidence | Exact calculation, drawing, certificate, model file, or clarification |
| Owner | Person responsible for the response |
| Source revision | Model, calculation, and drawing versions used |
| Response | What changed or why no change was required |
| Status | Open, submitted, accepted, superseded, or rejected |
| Closeout proof | Email, comment log, stamped set, acceptance letter, or portal record |
Do not mark a row accepted because it was submitted. Submission and acceptance are different events. The register should preserve the reviewer response that closed the item.
What happens after an equipment or layout change?
Every technical change needs an impact screen before the previous acceptance is reused. The screen asks whether geometry, weight, projected area, reactions, connections, foundations, or drawings changed. A small procurement change can affect several of those items.
Use a change matrix instead of relying on file names:
| Change | Structural questions | Evidence to reissue |
|---|---|---|
| Module substitution | Did weight, dimensions, clamp zones, projected area, or mounting points change? | Equipment register, loads, model where affected, connections, and drawings |
| Row spacing or tilt change | Did frame geometry, wind exposure, member length, or foundation demand change? | Layout, design basis, load calculation, model, and reaction table |
| Rail or member substitution | Did section properties, grade, holes, splice, or corrosion protection change? | Member checks, connection calculations, specifications, and drawings |
| Anchor change | Did diameter, embedment, edge distance, substrate, or installation method change? | Anchor calculation, detail, product data, and field requirements |
| Foundation relocation | Did soil conditions, pile spacing, eccentricity, drainage, or grading change? | Survey, geotechnical basis, reactions, foundation checks, and drawings |
| Added equipment | Did dead load, wind area, vibration, clearance, or maintenance access change? | Loads, model, local checks, layout, and access review |
The result can be one of three dispositions. The change has no structural effect, it requires a limited calculation update, or it requires full reanalysis and review. Record the reasoning even when no update is needed.
Acceptance also has a revision boundary. An AHJ comment closure or lender review letter usually refers to named documents and revisions. It should not be treated as approval of later substitutions. The project register must connect the accepted set to the set released for construction.
Fabrication creates another boundary. A drawing change after material release can affect holes, welds, cut lengths, coatings, and installation sequencing. Engineering change control should therefore include procurement and site teams, not only the analyst.
What does a good review response look like?
A good response answers the comment, identifies the changed evidence, and names the revision. It does not reply with “updated” or attach a new model without explaining the decision.
Consider this review comment:
Confirm that the base reactions used for anchor design include wind from both principal directions and identify the governing load combination.
A controlled response would state:
- The model was checked for positive and negative wind in both principal directions.
- The reaction appendix now lists uplift, shear, and moment by support and combination.
- The anchor calculation references those combination identifiers.
- Structural drawing S-502 now shows the analyzed base plate and anchor pattern.
- The model, calculation, and drawing advanced to the same revision.
That response lets the reviewer close the issue without guessing. It also leaves an audit trail for construction and later equipment changes.
When no calculation change is needed, explain why. Cite the model location, result, code basis, or existing drawing detail that resolves the comment. The response should remain useful after the email thread is archived.
Why do solar structural packages get rejected?
Most rejections come from broken traceability. The model may run while the report still hides the load source. It may also omit reaction transfer or use drawings from another revision.
Common causes include:
- site loads copied from another location.
- code editions that do not match the jurisdiction or contract.
- missing load directions or incomplete combinations.
- idealized supports with no anchor or foundation calculation.
- unverified existing roof members or material grades.
- member checks without connection checks.
- serviceability results omitted from the report.
- drawings that use different member sizes or spacing.
- equipment swaps made after analysis.
- a seal from the wrong jurisdiction or no seal where required.
- a lender deliverable omitted because it was not in the modeler’s scope.
A useful internal QC review starts at the drawing and traces backward. Pick one module support, follow its load into the rail, connection, frame, support reaction, attachment or foundation, and underlying structure. Then repeat the check at the most exposed or highly utilized location.
How should Heaven Designs support the handoff?
Heaven Designs can prepare model-based structural calculations and coordinated solar drawings within a defined scope. The handoff should state the governing inputs, excluded investigations, required client data, file revisions, and the professional review route.
The STAAD.Pro report service covers structural analysis documentation. The broader solar civil and structural engineering service connects loads, members, connections, foundations, and drawings. Neither service should be described as automatic AHJ, PE, lender, or IE acceptance.
Send the project location, reviewer checklist, code basis, site survey, equipment data, structural drawings, geotechnical report, and contract deliverable list when requesting a scope. That input pack lets the team design the reviewer packet before modeling begins.
The service boundary should remain explicit. Heaven Designs does not claim that software output guarantees approval or finance acceptance. The required professional authorization and final reviewer decision remain project-specific. Teams can request a structural engineering scope after assembling the available source documents.
What closes the structural review package?
A package closes when comments, calculations, drawings, models, and issue records point to one accepted revision. A transmitted PDF alone does not prove closeout. The project should retain the evidence that each responsible reviewer completed the required decision.
Before release, confirm these items:
- every open assumption is resolved or carried as an explicit construction hold point.
- the final equipment schedule matches the analyzed equipment.
- model, calculation, drawing, and response-log revisions agree.
- connection and foundation details use the final support reactions.
- every material structural comment has a documented response and status.
- required signatures, seals, certifications, or letters are present where applicable.
- the construction team can identify the current issued set.
- editable source files and calculation records are archived under the contract rules.
Some items may remain conditional. For example, an anchor detail may require field verification of concrete strength. That condition should appear on the drawing, calculation, inspection plan, and issue register. Hiding it in an email weakens the handoff.
The final archive should preserve superseded files without presenting them as current. It should also record the reason for material changes. This protects the owner when questions arise during construction, refinancing, repowering, or forensic review.
Frequently asked questions
Is a STAAD report mandatory for every solar project?
No. Some eligible residential rooftop projects use prescriptive permitting paths. Other structures may use hand calculations, manufacturer evidence, or another analysis platform. The jurisdiction, structure, project criteria, and reviewer decide which evidence is required.
Does a passing STAAD utilization ratio guarantee approval?
No. It shows that a modeled member passed the selected software check under stated assumptions. Approval can still depend on site inputs, connections, foundations, roof capacity, drawings, professional certification, and reviewer-specific documents.
Can an AHJ accept an unstamped STAAD report?
The AHJ decides its submission requirements under applicable law and adopted codes. Some prescriptive projects may not need project-specific stamped calculations. Engineered projects may require calculations and drawings sealed by a professional licensed in that jurisdiction.
Does a lender require the native STAAD model?
There is no universal rule. A lender or independent engineer may request the native model, a calculation PDF, input summaries, sensitivity cases, certified drawings, or all of them. The finance and IE scopes control the requirement.
Can a manufacturer certificate replace structural calculations?
Only when the reviewer accepts it for the actual configuration and its stated limits cover the project. A component certificate may not establish existing roof capacity, project wind loads, attachment adequacy, or foundation resistance.
Should India and US projects use the same STAAD template?
No. The analysis platform can be the same, but the code basis, load inputs, licensure route, reviewer terminology, drawing conventions, and certification requirements differ. Maintain separate jurisdiction-specific templates and source registers.
What is the first document to request from a lender or AHJ?
Request the current submission checklist or technical schedule. Then map every requested item to an owner and file before analysis starts. That step is faster than rebuilding the report after the first review.
The sound package is the one a reviewer can reconstruct. It names the source of each load, completes the load path, matches the issued drawings, and preserves the professional and contractual decision outside the software.
Source and review note
This article was reviewed on 26 September 2026 against six source groups. They include Bentley, SolarAPP+, NCEES, IFC and World Bank, ASCE, and the 2019 California guidebook. Local adoption, professional requirements, and lender schedules can change. Verify the current jurisdiction and contract before issuing a package.