The 6 EPC Phases Most Project Teams Don’t Coordinate
We were two weeks from financial close on a 47 MW project when the procurement lead called me.
“The modules landed in Hamburg. The installation crew does not know.”
The crew had been scheduled based on a delivery date that was updated three weeks earlier, in a spreadsheet that procurement owned but construction never saw. Four days of crew mobilisation cost, gone. And the module storage fees were clocking at €1,800 per day.
That was not a procurement failure That was not a scheduling failure. That was a coordination failure. And it happened because EPC teams treat their six phases like separate projects rather than a single connected system.
Here’s the dirty secret of solar EPC in 2026
Most teams coordinate within phases. They coordinate poorly across phases.
Your feasibility team hands off to engineering with a PDF. Engineering sends revised drawings to procurement via email. Procurement updates a tracker that commissioning never sees. Each handoff is a potential data gap Each gap is a potential delay. Each delay at commissioning is liquidated damages exposure at €30,000 to €75,000 per day.
The average European utility-scale solar EPC project runs 4.2 weeks behind schedule. Not because teams are incompetent. Because the coordination layer between phases is manual, asynchronous, and human-dependent. For broader sector context, SolarPower Europe continues to track the operational and market realities shaping utility-scale delivery across the region.
Phase 1 → Phase 2: feasibility to engineering
The classic gap is feasibility assumptions that do not survive engineering review.
A topographic survey says the site has 2.3 percent average slope. Engineering models it at 1.8 percent because the PDF quality was poor and the surveyor’s DWG files were not included in the handoff. The pile design gets anchored to the wrong terrain model. Rework lands in week 12, when concrete is already poured.
With ClearSpot’s drone-based site inspection workflow, autonomous drone surveys generate a centimetre-resolution digital elevation model that feeds directly into the engineering model, not as a PDF attachment but as a live data source. Design changes in the terrain model automatically flag pile layout implications. No handoff email. No lost precision.clearspot
Phase 2 → Phase 3: engineering to procurement
This is where most teams bleed money without noticing.
A cable cross-section changes in Revision C of drawing E-204. The procurement order, placed in week 6, specified Revision A. Nobody updated the BOM because the design-to-procurement trigger was “someone remembers to check.”
The SolarEPC Hub orchestration model runs continuous procurement implication analysis on every uploaded drawing revision. When a design change carries a material implication, the procurement action item is created automatically, not when someone thinks to check.
The result: 65 percent reduction in cross-phase rework across teams using this workflow.
Phase 3 → Phase 4: procurement to construction
This is the module-in-Hamburg scenario. The one that costs real money.
Confirmed delivery dates should auto-cascade through the construction schedule. Instead, most teams maintain two separate systems, a procurement tracker and a project schedule, that sync when someone has time to sync them, which is never.
When a delivery confirmation slips 9 days, the SolarEPC Hub immediately models the critical path impact and presents three recovery options ranked by cost and liquidated-damages exposure. That modelling used to take a project manager half a day. Now it takes 40 seconds.
ClearSpot’s broader AI Solar O&M Experts workflow is built on the same principle: get the right operational signal into the right decision layer before the delay compounds.clearspot
Phase 4 → Phase 5: construction to commissioning
This is the punch list that nobody owns.
Construction finishes and hands a list of 94 open items to commissioning. Twenty-three of them are assigned to subcontractors who demobilised last Tuesday. Eleven require equipment that is back-ordered. Fourteen are COD-blocking.
Without velocity tracking, punch list management is reactive. You notice you are in trouble when the interconnection test date is two weeks away and you still have 40 items outstanding.
The SolarEPC Hub categorises every punch list item by criticality and responsible party, tracks closure velocity in real time, and models whether current velocity achieves the interconnection date. When it does not, it escalates, not on Friday’s status call, but the moment the trajectory diverges.
Phase 5 → Phase 6: commissioning to handover
This is where plant knowledge goes to die.
Industry best-practice guidance has repeatedly emphasized the importance of structured documentation, performance verification, and lifecycle information continuity in PV project operations and maintenance. The IEA PVPS O&M guidelines and the NREL best-practices reference are both useful benchmarks for why handover quality matters long after COD.iea-pvps+1
Not because teams do not care. Because handover is a manual compilation exercise done by people under time pressure who are already mentally on the next project.
Serial numbers are missing from equipment registers. As-built drawings are actually red-lined design drawings. IV curve test results sit on paper in a site container that nobody shipped. Warranty registrations never get completed.
The SolarEPC Hub’s handover protocol is agent-to-agent: it transfers a complete, drone-verified digital twin directly to the asset management layer at the moment of COD. Zero manual compilation. Zero data loss. The O&M team inherits a fully operational knowledge graph, not a Dropbox folder.
Phase 6 → Phase 1: the loop nobody closes
This one does not get discussed enough.
What do most EPC teams do with lessons learned from Phase 6? They write them in a document. The document goes into a shared drive. Nobody reads it at the start of the next project.
The ClearSpot AI agent framework maintains cross-project learning, including patterns from commissioning failures, procurement delays, and design rework events, that inform risk models for new projects. The contractor who missed that delivery commitment on Project A flags as elevated risk on Project B before you have signed the PO.clearspot
The number that matters
€18,500 per year per active project. That is the net documented value of replacing the six-phase coordination patchwork with a single intelligent orchestrator.
That is schedule recovery. Rework avoided. LD events prevented. Handover data preserved. Across a 3-project concurrent programme, that is €55,500 per year, before you count the projects you win because you deliver on time.
I am not arguing that EPC teams are bad at their jobs. I am arguing that the tools underneath them make coordination harder than it needs to be. When the connection between phases is email and calendar reminders, your project timeline depends on individual humans not dropping the ball, every day, across dozens of interdependencies.
Agents do not forget to sync the procurement tracker.
Curious what your biggest cross-phase coordination gap actually is, where does the handoff between EPC phases most often go wrong on your projects?
FAQ
What is the main EPC coordination problem?
The main problem is that teams coordinate within phases but not across phases, which creates data gaps and schedule delays.
Why does this matter financially?
Because small handoff delays can cascade into commissioning delays and liquidated damages exposure of €30,000 to €75,000 per day.
Which phase handoffs are most risky?
Feasibility to engineering, engineering to procurement, procurement to construction, construction to commissioning, and commissioning to handover.
How does ClearSpot help?
ClearSpot’s solar farm AI inspection, SolarEPC Hub, and AI Solar O&M Experts workflows help unify live design, procurement, and field progress data.clearspot+2
Which external benchmarks support this approach?
The IEA PVPS O&M guidelines and NREL best-practices reference are the strongest references here.