A commercial operation date can look precise long before the underlying project is capable of supporting that precision. In Spanish digital infrastructure transactions, a stated COD may sit beside planning approvals, construction progress, power-access milestones, network discussions, equipment delivery schedules, and commissioning assumptions that do not mature at the same pace. The issue is that an investment model can compress several different readiness conditions into one calendar date, even when those conditions remain dependent on separate permitting, infrastructure, connectivity, power and commissioning evidence. A site can have substantial construction progress while critical infrastructure remains unavailable, and a facility can have physical power equipment installed without having completed the testing required for dependable operation. Connectivity can create the same problem because geographic network coverage does not establish that a specific facility has completed physical routes, facility entry infrastructure or an activated customer connection.

Spanish development conditions make this issue particularly relevant because construction and occupancy requirements can involve municipal authorization, while environmental and other infrastructure processes can involve different competent authorities depending on the project. Construction and occupancy requirements can involve municipal authorization, while environmental and infrastructure matters can involve regional or national processes depending on the project and affected assets. The existence of separate approval processes means that evidence of progress in one process does not by itself establish completion of every other prerequisite. Connectivity introduces another layer because national coverage statistics demonstrate network availability at broad geographic levels, but those measurements do not establish that a specific facility has diverse physical entrances, completed ducts, commissioned optical infrastructure, or contracted delivery dates. Valuation work that treats these conditions as interchangeable can assign excessive certainty to a COD that remains dependent on several unfinished interfaces.

Why a Single COD Assumption Masks Three Distinct Readiness Milestones

A more useful COD model begins by separating civil completion from infrastructure readiness and customer-ready energization. Civil completion refers here to the point at which the physical works required for the relevant phase are sufficiently advanced for the associated technical systems to proceed. Infrastructure readiness goes further by requiring the relevant electrical, mechanical, communications and control systems to progress through installation, testing and readiness activities appropriate to the intended operating configuration. Customer-ready energization adds the commercial layer by asking whether the contracted capacity has reached the technical and handover conditions required for the customer workload represented in the valuation. These milestones can overlap in a schedule, but they should not receive the same evidentiary weight. Treating them as one date can make an early-stage project appear closer to revenue generation than its actual dependency chain supports.

A disciplined valuation should therefore assign a confidence level to each readiness layer and identify the evidence required to move that confidence upward. A civil milestone supported by completed inspections and documented acceptance deserves a different treatment from an infrastructure milestone supported only by procurement commitments or installation forecasts. Likewise, a claimed energization date should carry stronger weight when the evidence for grid access, physical connection works, applicable approvals and commissioning activities is consistent with the stated capacity. Therefore, the model can represent COD as a range whose probability improves as independent dependencies mature rather than as a fixed date copied from a development schedule. This approach makes schedule slippage visible inside the valuation rather than leaving it as a post-investment operational surprise. It also forces the investment committee to ask which missing evidence can actually move the revenue start date and which items merely improve construction visibility.

Connectivity Procurement vs Connectivity Deliverability at the Data Hall

Fiber availability near a site is an input to connectivity diligence, not proof of connectivity delivery. A regional or municipal coverage record can show network availability in an area, yet it does not by itself establish the facility-specific route, building entry, physical diversity or commercial activation conditions required for a particular service. Spain’s national coverage reporting provides granular information down to municipal level, but the existence of network coverage does not establish the final civil route, duct occupancy, building entry, optical termination, or provider acceptance required for live service. The practical diligence question therefore shifts from which providers operate nearby to what facility-specific evidence exists for the route, delivery path, testing and service activation required for the intended connection. A connectivity route can remain schedule-sensitive when physical infrastructure required to reach the facility has not yet been completed, even when network availability in the surrounding area is established.

Route diversity deserves the same treatment because geographic separation on a network map does not automatically create physical independence at the building. Two services can approach from different directions and still converge into a common duct, chamber, carrier room, riser, or internal pathway before reaching the customer handoff. Public evidence on Spanish connectivity shows that interconnection activity is concentrated in major network locations, while new terrestrial and submarine routes continue to add connectivity options. However, investment diligence should translate that macro connectivity advantage into facility-specific evidence: surveyed routes, confirmed entry points, duct capacity, construction responsibility, delivery dates, optical testing, and contractual service activation. The resulting COD confidence should fall when a supposedly diverse path still depends on an unbuilt segment or an external party without a committed execution schedule. This prevents a strong regional connectivity story from becoming an unsupported assumption about customer-ready service.

The Commissioning Phase as the Determinant of True Operational Readiness

Construction completion does not establish that interconnected electrical, mechanical, control, and safety systems will perform correctly under operating conditions. Commissioning progressively moves from installation verification toward functional testing, performance validation, integrated systems testing, and operational handover. Commissioning practice for critical facilities includes functional checks, performance testing and integrated testing intended to verify the behavior of interconnected systems under operating and failure scenarios. The commercial importance lies in what those tests reveal about dependencies that remain invisible during ordinary construction inspections. A system can pass its individual test while still failing when another system changes state, transfers load, loses a source, generates an alarm, or triggers an automated response. COD confidence should therefore increase only as the evidence moves from installed equipment toward proven behavior of the complete operating configuration.

Staged energization can make the schedule more sensitive because individual systems may require sequential energization and separate validation before the integrated configuration is ready. Electrical distribution may require sequential energization, controls may need live validation, mechanical systems may require balancing and functional testing, and integrated scenarios can depend on equipment from multiple vendors reaching readiness simultaneously. Recent commissioning guidance emphasizes the importance of real-time visibility into system boundaries, pre-commissioning readiness, functional testing, integrated testing, and structured handover data because late discovery of interface problems can affect the transition into operations. Third-party dependencies can also include utility interfaces, specialist testing, manufacturer support, communications activation, applicable inspections and customer acceptance activities, depending on the project configuration. A credible COD model should identify each dependency as either complete, contractually committed, scheduled but unsecured, or unresolved. That classification turns commissioning from a late-stage project activity into a direct input to investment probability.

Transitioning From a Presented COD to a Provable Investment Case

The investor question is not whether a developer can present a credible COD, but whether independent evidence across disciplines supports the same date, capacity, configuration, and commercial outcome. A useful diligence process should reconcile planning status, construction completion, utility readiness, network deliverability, equipment commissioning, integrated testing, documentation, and customer acceptance against one common operating scenario. Permitting evidence should be reconciled with the physical configuration being valued rather than treated as evidence for a project configuration that has since changed. Connectivity evidence should establish the facility-specific routes and service conditions required for the contracted connection rather than rely solely on broad geographic availability. Commissioning evidence must demonstrate that the systems supporting the stated capacity can operate together rather than simply confirm that individual components have reached installation.

The result should be a COD confidence curve rather than a binary ready-or-not-ready label. Early development may justify a wide COD range because several dependencies remain exposed, while later-stage evidence can progressively narrow that range as permits, physical works, power, connectivity, testing, and handover converge. This approach is particularly important where individual projects can still face unresolved grid-access and execution dependencies, making delivery evidence an important investment consideration alongside headline development volume. Ultimately, a project should command higher COD confidence only when the evidence supporting capacity and timing comes from multiple independent workstreams that have reached compatible maturity. If those workstreams point to different dates or different usable configurations, the valuation should preserve that uncertainty rather than absorb it into an apparently precise commercial operation date.