Why team collaboration breaks in solar project development

Utility-scale solar project development is becoming increasingly complex. To face the modern development challenges such as grid congestion, terrain limitations, and financial constraints, developers now depend on a growing number of specialized leads and teams.

However, this growth comes at a price: the bigger the team, the larger the risk of miscommunication and workflow frictions. Compounded by disconnected toolstacks and opaque processes, it explains why most projects fail before reaching construction, as exposed by the 2025-2026 State of Solar Project Development:

• Financing: 39% failure rate

• Permitting & grid connection: 36% failure rate

• Feasibility: 24% failure rate

• Construction: 23% failure rate

• Site selection: 19% failure rate

This blog post aims to break down when, where, and why collaboration breaks, how it impacts the project’s lifecycle, and what can be done to avoid it.

During initial screening, land teams and grid analysts assess the same geography from different perspectives:

• Grid analysts: Work with restricted Critical Energy Infrastructure Information (CEII) datasets to evaluate points of interconnection (POIs) using full power-flow simulations and grid upgrade projections in specialized software. 

• Land originators & site selection leads: Screen target areas using basic parcel maps, looking for cheap, flat acreage within physical proximity to a transmission line or substation. They typically see open land, but lack line-of-sight into transmission congestion, location marginal pricing (LMP), or hidden grid upgrade costs.

Where collaboration breaks

Land teams rarely have the access to the specialized datasets of grid analysts. Thus, they are forced to pick potential sites first and have them evaluated later.

This usually results in originators securing control options on viable land to meet land acquisition quotas, unaware that queue submissions upstream have saturated the local substation — leading to million-dollar network upgrade requirements and year-long delays.

The situation only worsens when the grid analysis are conducted by external consultants, as each request can take several days and prices quickly add up due to the high probability of “no-go” sites being assessed.

Once a parcel clears initial grid screening, it is tested for technical feasibility. However, here too, a gap emerges between teams:

• GIS & site selection analysts: See grid headroom, LMP, and property lines, but cannot assess micro-topography, 3D slope hazard limits, or piling tolerances.

• Preliminary CAD engineers: Receive raw parcel boundaries and quickly discover that unmapped environmental setbacks, steep terrain slopes, or hydrological hazards eliminate usable acreage.

Where collaboration breaks

The handoff of a potential site’s data is, simply put, a translation of parcel data into a CAD-compatible format for design, which is usually done manually. 

1. Static data export: The site selection or GIS team identifies a prospective parcel and exports raw shapefiles or KML boundaries, emailing them to the CAD engineering team.

2. Manual CAD import: The preliminary CAD engineer imports the raw spatial file into AutoCAD. Because GIS shapefiles lack native AutoCAD layer standards, the engineer spends hours manually cleaning polylines, setting unit consistencies, and generating 3D terrain meshes.

3. Spatial hazard discovery: Upon overlaying high-resolution topography or local hydrological setbacks, the engineer discovers that steep terrain slopes or floodplains eliminate a portion of the buildable acreage.

4. Layout modification & feedback: The CAD designer manually redraws the array footprint, recalculates DC capacity (MWdc), and exports a static PDF or spreadsheet back to the site selection team.

5. Re-iteration: If the land team adjusts the property boundary or adds an adjacent parcel to compensate for lost capacity, the entire manual export, ingestion, and cleaning cycle repeats from the beginning.

Because each iteration takes days or weeks, project managers often lock in preliminary layouts before confirming true energy yield potential — accepting underoptimized site geometries simply to meet permitting or queue submission deadlines. 

Additionally, design managers also lock in preliminary layouts before fully understanding their energy potential, leaving significant energy yield and capital efficiency on the table. 

Once a project moves to detailed engineering, manual data handoffs and asynchronous feedback delay development and strain collaboration between stakeholders further:

• CAD designers & engineers: Work exclusively inside high-fidelity 3D spatial coordinates, slope hazard overlays, collision meshes, and stringing configurations.

• Project developers & managers: Need simple, up-to-date capacity metrics (module counts, string lengths, DC capacity). They are completely locked out of active design files. 

This lockout stems from three main constraints:

• Enterprise licensing costs: High CAD seat pricing makes it cost-prohibitive to deploy licenses to non-design personnel.

• Hardware demands: Rendering dense 3D utility-scale layout files requires high-end workstations with dedicated graphics processors that standard corporate laptops cannot run.

• Node-locked licenses: Software licenses tied to specific physical office computers prevent remote project leads and field teams from inspecting active layouts.

Where collaboration breaks

Because project managers and business leads cannot open CAD files, CAD designers become gatekeepers: they’re put in charge of reviewing and transcribing feedback in a continuous loop.

1. Manual data extraction: Designers pause engineering work to transcribe panel counts, tracker quantities, and string lengths into spreadsheets. 

2. Non-technical review & feedback: Managers evaluate capacity and track milestones using Excel sheets and static PDF screenshots. 

3. The left-to-right transcription workflow: Designers interpret vague PDF text notes or drawn redlines to update spatial coordinates in CAD.

Translating disconnected feedback into CAD relies entirely on human memory and manual checks. This introduces revision errors, severing the digital thread and forcing avoidable rework.

It also obscures project status across entire portfolios, as business leaders are forced to evaluate project viability using stale screenshots or static PDF exports. 

Separate teams means separate objectives too. Engineers, project managers, and financial teams use different metrics to reach the project’s potential and success, which can also lead to strained communication.

• CAD Engineering: Exact spatial coordinates, 3D slope profiles, pile clearance tolerances, stringing configurations, and civil earthworks volumes.

• Project Management: Site control status, permitting schedules, delivery deadlines on non-spatial tools like Monday.com.

• Finance and Investment: Project viability using high-level directional targets — primarily a single $/W EPC cost estimate — in custom, proprietary Excel models built for specific Power Purchase Agreements (PPAs) and feed-in tariffs. 

Where collaboration breaks

The issue stems from the way project updates propagate across non-integrated tools in a growing chain of challenges:

1. Spatial modification: An engineer modifies a site layout in CAD to resolve a physical constraint — such as reducing table counts to avoid a 12% terrain slope or introducing a setback for an unmapped wetland.

2. Sync Breakdown: The cloud directory receives no automated signal that the previous layout's bill of materials (BOM), system capacity (MWdc), or tracker quantities have changed.

3. Data harvesting: A commercial analyst opens the shared drive, locates the latest exported spreadsheet or preliminary layout file, and extracts the unvetted capacity and module count.

4. Model corruption: The analyst inserts these unvetted numbers into a custom sheet to calculate Levelized Cost of Electricity (LCOE), PPA pricing, or equipment purchase orders.

The result: bidding on unapproved draft layouts

Finance sheets based on unvetted numbers lead to financial models built on false assumptions. Thus, the commercial team might submit PPA bids or sign equipment supply contracts, but  detailed engineering maps the actual 3D slope, civil earthworks cut/fill requirements, and pile-driving limits, the project's real construction costs can rise while its total capacity drops. 

This metric mismatch forces developers to either absorb unexpected civil engineering costs — eroding the project's Internal Rate of Return (IRR) — or attempt late-stage PPA renegotiations that jeopardize project viability and investor confidence.

Alternatively, it forces engineers into rework hours during detailed engineering, which also erodes IRR and can lead to project design version chaos. 

Even after a project has received financial approval, the detailed design stage also sees gaps emerge between co-dependent teams, in this case:

• Mechanical CAD designers: Lay out single-axis trackers or fixed-tilt tables inside AutoCAD based on target DC capacity, module orientation, and standard pitch dimensions. They place equipment directly over 3D terrain meshes without native visibility into mechanical slope tolerances or civil grading limits.

• Civil & structural engineers: Perform 3D cut/fill earthwork calculations, pile reveal height analyses, and soil slope stability modeling in specialized civil software. Their goal is to prevent structural frame collisions and control earthwork costs.

Where Collaboration Breaks

Because mechanical layout tools often lack built-in civil collision algorithms, designers generate layouts that work on flat paper but fail on real terrain.

When civil engineers run grading and pile height analyses on these raw layouts, they find that steep terrain slope variations cause tracker frames to exceed maximum structural pile reveal limits. 

To keep piles within structural tolerances, civil teams are thus forced to introduce massive earthwork grading plans, driving up civil costs and triggering new environmental permitting reviews.

After detailed design is mostly finished, developers share layout files with racking and tracker manufacturers so vendor engineers can verify Ground Coverage Ratios (GCR), model structural pile reveal heights across sloped terrain, and generate an accurate Bill of Materials (BOM) for equipment supply contracts. 

However, exchanging technical design files through standard Virtual Data Rooms (VDRs), client portals, or email attachments introduces two new risks:

• Data privacy exposures: Standard file-sharing mechanisms lack role-based attribute filtering. Sending an unfilleted DWG file to an external partner exposes internal financial notes, land lease rates, and proprietary cost models embedded within the project data layers. 

• Pre-sales delays: To protect proprietary cost models, developers frequently export flat PDFs or static CSV spreadsheets instead of live CAD geometry. External engineers are thus forced to manually re-enter module counts, energy yield estimates, and structural specs across CAD, PVSyst, and Excel spreadsheets.

Where collaboration breaks

Having to manually copy spatial data across disconnected software tools slows down pre-sales comparative reviews, adds days to equipment quotes, and creates high risk of transcription errors that weaken investor trust during final project due diligence. 

1. Cross-functional role permissions

Define role-based data view rights across disciplines. Provide non-technical teams direct access to web-based visual environments so they can inspect parcel boundaries, site capacity, and panel counts without requiring manual spreadsheet exports from CAD designers.

2. Standardized asynchronous review protocols

Implement structured review processes where feedback is pinned directly to spatial coordinates. Replacing static PDF markups with direct spatial comments eliminates transcription errors and guarantees no reviewer notes are lost.

3. Change management & decision logging

Maintain a permanent decision log tracking why layout changes occurred across the project lifecycle. Capturing historical engineering rationale protects institutional knowledge when project personnel changes.

4. Automated revision triggers

Establish system alerts that notify financial and project management leads whenever a layout modification alters system capacity or bill of materials (BOM) attributes. This prevents commercial teams from running PPA models or debt sizing on stale preliminary drafts.