Desktop Structural Reports for EPC Contractors: Integrating Fast Structural Sign-Off into Your Pre-Construction Programme

For EPC contractors delivering commercial rooftop solar installations, structural sign-off is a pre-construction gate that sits outside their direct control. It depends on a third party, the structural engineer, and it occupies a sequence-critical position in the programme. G99 applications cannot be finalised without confirmed structural parameters. MCS certification cannot be prepared without structural clearance. Material procurement cannot be locked without confirmed racking and fixing specifications that depend on the structural verdict.

When structural reports take two to four weeks, the industry standard at general structural engineering practices unfamiliar with solar PV workflows, that delay propagates forward through the entire programme. A two-week structural report gap on a ten-week pre-construction programme occupies 20% of the available time before a panel or inverter has been specified.

Desktop structural reports, delivered within a 48-hour benchmark, eliminate this bottleneck when they are integrated correctly into the EPC pre-construction sequence. This article explains how to do that, what to specify, what data to prepare, how to align structural clearance with G99 applications, and how to manage the sites where desktop assessment is not appropriate.

Where Structural Reports Sit in the EPC Pre-Construction Sequence

A commercial solar EPC pre-construction programme typically runs across three stages: site feasibility and consenting, pre-construction engineering, and procurement and mobilisation. Structural assessment belongs in Stage 1, early in feasibility, not at the end of pre-construction engineering.

The reason for early commissioning is that the structural verdict determines downstream specifications. If a desktop assessment concludes that the existing purlins cannot carry a standard portrait-mounted array without reinforcement, that constraint must be reflected in the racking selection, the panel weight specification, and potentially the array layout. Commissioning the structural assessment after racking and panels have been selected creates the risk of discovering that the specified system exceeds the structural capacity, requiring a design iteration that could have been avoided.

The correct sequence for structural integration is: commission the desktop structural report at the point of initial site feasibility, using the site address and a provisional array size; receive the structural verdict within 48 hours; incorporate any structural constraints into the system specification before racking and panel selection is finalised; and proceed to G99 application with confirmed structural parameters already in the submission pack.

EPC contractors who treat structural assessment as a late-stage compliance tick-box rather than an early-stage engineering input consistently experience the delays that early commissioning would have prevented.

The Specification Problem, What Most EPC Teams Get Wrong

The most common structural commissioning error made by EPC teams is over-specification. Believing that compliance requires an on-site survey, or that a more expensive assessment is inherently more thorough, EPC contractors commission site visits for standard commercial buildings that could be cleared by desktop assessment in 48 hours.

The second most common error is under-specification: commissioning a structural report without adequate site data, resulting in an assessment that either cannot reach a definitive conclusion or produces caveated output that requires follow-up before it can be used for G99 submission or MCS documentation.

The correct specification approach for EPC structural commissioning is:

Data Packages That Enable 48-Hour Turnaround

The speed of a desktop structural assessment is directly linked to the quality of the data provided. Engineers working with complete, well-organised data packages can execute and deliver in 48 hours. Engineers working with incomplete data spend time requesting information, and the clock does not start until they have what they need.

For a standard commercial building, the ideal data package comprises the site address and postcode; structural drawings for the building (ideally as-built drawings showing primary and secondary member sizes, spacing, and connection details); the proposed array size in kWp or panel count, with approximate roof coverage area; the proposed panel and racking system specifications including panel weight, racking dead load, and fixing type; and any available roof condition survey or recent maintenance inspection records.

If structural drawings are not available, common for buildings constructed before 1990 or where drawing records have not been maintained, the next best alternatives are: building control submission records (accessible via the local authority), photographs of the roof structure taken from inside (showing purlin size markings, spacing, and any visible condition issues), and the construction date and building use class.

For EPC contractors managing multiple sites concurrently, standardising the data package format into a spreadsheet template with consistent fields for each site dramatically reduces instruction preparation time and enables batch submission to the structural engineer. A standing template also ensures that no critical information is omitted and that instructions received by the engineer are immediately actionable.

G99 Application Integration, Structural Reports in the DNO Submission

G99 applications for grid connection of commercial solar PV installations above 50 kW require technical documentation demonstrating that the proposed system meets the DNO's connection requirements. Structural documentation is a component of the G99 technical pack, confirming that the host building is structurally adequate for the proposed installation.

The structural report submitted with a G99 application must confirm the proposed array size and configuration for which structural clearance has been given, the fixing system for which wind uplift adequacy has been verified, and any structural constraints on the installation specification. DNOs and their technical reviewers will check that the installation specification in the G99 application is consistent with the structural constraints stated in the structural report. Inconsistencies, for example, a G99 application specifying a 250 kWp array when the structural report cleared 200 kWp, will generate queries that delay the application.

EPC contractors who integrate structural assessment early in the programme avoid this problem because the structural verdict informs the G99 application specification rather than following it. The report is produced before the application is submitted, not after the application has already stated parameters that the structural assessment has not yet verified.

Framework Arrangements and Standing Instruction Agreements

EPC contractors with consistent volumes of structural assessment requirements benefit from a framework arrangement with their structural engineering provider. A framework establishes pre-agreed terms: report format, delivery benchmarks, pricing for standard buildings, escalation protocols for non-standard sites, and a standing data template. Instructions can then be submitted without each one requiring individual negotiation or format alignment.

The practical benefits of a framework are most visible at programme scale. An EPC contractor running twenty active sites through pre-construction simultaneously cannot manage twenty separate structural engineering procurement processes. A framework converts structural assessment from a procurement event into an operational workflow, instruction in, report out, within 48 hours, to a known format, at a known cost.

Framework arrangements also support portfolio-level reporting. Where a lender's technical adviser or an asset manager requires a consolidated structural assessment summary across a multi-site programme, a framework with a consistent report format makes compilation straightforward. Report-by-report format inconsistency, the product of using different structural engineering firms across a programme, creates unnecessary consolidation work at due diligence.

Managing Exceptions, Sites That Require On-Site Survey

In a typical EPC contractor's portfolio, the majority of commercial rooftop sites will be assessable by desktop methodology. Steel portal frame warehouses, flat-roofed logistics units, and modern industrial buildings all fall within the range of standard construction for which desktop assessment is appropriate. However, a minority of sites will require on-site survey: older buildings with unknown structural typology, buildings with no available drawings and non-standard construction, and buildings where desktop assessment identifies loading at or near the structural capacity margin.

The key principle for EPC programme management is: identify these exceptions early. A desktop assessment that concludes with a referral to on-site survey still represents useful programme information. It tells you at the feasibility stage, before significant pre-construction resource has been committed, that this site requires an additional engineering step. That information allows you to plan the programme accordingly: sequence the on-site survey early, adjust the programme milestone dates, or in some cases reconsider whether the site economics support the additional engineering cost.

The worst outcome is discovering that a site requires on-site survey after G99 application has been submitted with unverified structural parameters. Commission desktop assessments early enough that exception identification is a programme planning input, not a programme-critical delay.

Report Formatting for EPC Handover Packs and Contractor Obligations

EPC contractors assembling documentation for project handover, MCS certification, and lender due diligence need structural reports that are formatted consistently and contain all required information without supplementary requests. A structural report that satisfies MCS auditors but requires additional annexes for a lender's technical adviser, or that confirms structural adequacy without stating the fixing parameters for which clearance was given, creates downstream rework.

The most efficient approach is to specify at instruction that the report must be formatted to satisfy three outputs simultaneously: MCS MIS 3002 Section 5.9, G99 DNO submission, and lender TA review. Structural engineering firms with high-volume solar PV experience produce reports in a format that meets all three requirements from first issue. Firms without this background often produce technically sound assessments that require reformatting or supplementary documentation before they can be used for commercial and certification purposes.

For EPC contractors standardising their pre-construction documentation across a programme, requiring a consistent report format from the structural engineer is as important as requiring consistent formatting from the electrical design team. The documentation stack at handover should be a set of consistently formatted reports, not a collection of differently structured documents from different engineering firms at different stages of the programme.

EPC Design Coordination with Structural Constraints

EPC contractors delivering design-and-build solar installations are responsible for coordinating their electrical and mechanical design with the structural constraints established by the structural clearance report. This coordination is most efficient when the EPC contractor receives the structural report early in their design process, before the detailed racking layout, fixing schedule, and electrical design are finalised, rather than after these elements have been designed to a specification that may not comply with the structural conditions.

The structural conditions most likely to affect EPC design are: maximum dead load constraints that limit panel weight or racking system choice; wind zone fixing specifications that require enhanced fixing centres in defined roof perimeter zones; and exclusion zones where the roof has been assessed as structurally inadequate for PV attachment. Each of these conditions requires a specific design response from the EPC contractor.

Dead load constraints are managed through racking and panel specification. The EPC contractor’s design team must confirm that the proposed panel weight plus racking dead load per unit area is within the stated maximum. If the initially specified panel exceeds the limit, the contractor selects a lighter panel from within the project’s acceptable module range. If no acceptable panel meets the limit, the racking system design must be revised to reduce the racking’s self-weight contribution, or the array density must be reduced to lower the overall distributed load.

Wind zone fixing specifications are managed through the installation method statement. The EPC contractor confirms with the racking installer that edge zone fixing requirements are documented in the site-specific installation drawing, and that the racking installer’s method statement references the structural report’s zone map and fixing specification. The installation drawing supersedes the racking manufacturer’s standard fixing schedule for the edge zones, and the EPC project manager must confirm that the installation team has received and understood this instruction before installation begins.

As-Built Structural Records: EPC Contractor Responsibilities at Handover

At project handover, the EPC contractor is responsible for delivering a documentation package to the building owner or solar asset owner that includes the as-built structural records. The content of this package, and the format in which it is delivered, affects the building owner’s ability to maintain the asset, obtain insurance, and manage future structural obligations over the asset’s 25-40-year life.

The minimum as-built structural records required in the EPC handover package are: the pre-installation structural clearance report (signed PDF, including any supplementary wind zone plans or fixing specifications); written confirmation from the installer that all structural conditions in the report were complied with during installation; the as-installed racking specification confirming panel weight, racking manufacturer and model, and fixing system; and any structural engineering confirmation notes or supplementary reports issued in response to design changes during the construction period. These records should be filed in a dedicated structural section of the O&M manual, clearly indexed and cross-referenced to the relevant installation drawings.

EPC contractors who deliver complete and well-organised as-built structural records at handover distinguish themselves from contractors who deliver disorganised or incomplete documentation packages, and this distinction matters at two points in the asset lifecycle: MCS certification audit (which occurs shortly after commissioning) and the first major transaction or refinancing (which may occur years later). A building owner who can rapidly locate and produce complete structural documentation at both of these points has benefited directly from the EPC contractor’s documentation discipline. EPC contractors who incorporate structural document management into their handover process as a standard deliverable specification are building a reputation for professionalism that differentiates them in a competitive market.

WHERE SOLAR SURVEYS ADDS VALUE