Executives heading to DCD Connect London 2026 do not need another session list. They need a way to test what vendors, developers, operators and capital partners say about the constraints shaping new data center capacity.
This guide turns five broad themes—power, cooling, construction, investment and European capacity—into decision questions. Use it to prepare meetings, compare answers and record what deserves a closer review after the event.
What should leaders watch at the London event?
At DCD Connect London 2026, watch for evidence that a proposed site, design or investment can move from ambition to delivery. Ask where power comes from, which cooling assumptions drive the design, what can delay construction, how risk is divided and which capacity claims are backed by a workable plan.
The executive watchlist
- Power: Separate an energy requirement from a deliverable connection plan.
- Cooling: Ask which operating conditions and workloads shaped the design.
- Construction: Find the interfaces most likely to disrupt cost, sequence or handover.
- Investment: Test who carries development, delivery and demand risk.
- Capacity: Define what “available” means before comparing market claims.
The goal at DCD Connect London 2026 is not to collect the most predictions. It is to identify the assumptions that should be tested before a business commits capital, signs a contract or repeats a market claim.
Start with decisions, not themes
Power, cooling and AI can become vague conference language. A buyer gets more value by linking each theme to a pending decision. That decision might involve site selection, design, procurement, financing, market entry or the way a project is presented to customers and communities.
Before DCD Connect London 2026, write down the decisions your team expects to make during the next planning cycle. Then list the evidence required for each one. This creates a filter for meetings that might otherwise stay at the level of trends and forecasts.
Use four prompts for every issue:
- What changed in the underlying assumption?
- Which party is exposed if that assumption is wrong?
- What evidence would change our decision?
- What should we listen for at the event?
1. Power: Is the connection plan as clear as the demand story?
A proposed facility can have a detailed demand case while its energy path remains less clear. Buyers should ask how the power requirement was developed, which project stage the connection has reached and what dependencies sit between the current position and an operating facility.
The useful evidence will vary by project. It may include written milestones, defined responsibilities, design assumptions, dependencies and contingency choices. The purpose is not to reduce a complex power strategy to one document. It is to expose where confidence rests on an untested step.
At DCD Connect London 2026, listen for precise language. “Planned,” “reserved,” “contracted,” “energized” and “operational” do not describe the same condition. Ask each speaker or partner to define the term being used and explain what still has to happen.
Who is exposed: developers, occupiers, investors, contractors and customers whose schedules depend on a power milestone.
What would change the decision: evidence that clarifies timing, responsibility, dependencies and fallback options.
2. Cooling: Which workload and operating assumptions shaped the design?
Cooling discussions often begin with a technology label. A better conversation begins with the expected workload, equipment profile, operating range, deployment sequence and service model. Those inputs help a buyer understand why a design choice fits the proposed use.
Ask what happens if the workload mix changes. Explore which parts of the design can adapt and which would require a larger intervention. Also ask how maintenance, commissioning and operational responsibility were considered. These questions reveal whether the concept has been examined as an operating system rather than a single component.
Use DCD Connect London 2026 to compare reasoning, not slogans. If two providers recommend different approaches, ask which assumptions produced the difference. A clear answer is more useful than a claim that one design is universally better.
Who is exposed: owners and operators responsible for performance, as well as contractors and suppliers responsible for integration.
What would change the decision: a design basis that connects the proposed approach to defined workloads, operating conditions and responsibilities.
3. Construction: Where can interfaces break the delivery plan?
Data center construction brings multiple disciplines, suppliers and approval paths into one delivery sequence. The important questions often sit between work packages. A design can look complete while responsibility for an interface remains unclear.
Ask where long-lead choices affect later design work. Ask which decisions must be frozen early and which can remain flexible. Review how changes move through design, procurement, field execution, testing and handover. The point is to find the small number of interfaces that could create a large schedule or cost effect.
For construction leaders at DCD Connect London 2026, the useful conversations will connect technical ambition to buildability. You can request project-specific decision gates, responsibility maps or commissioning plans and then identify which details require specialist review.
Who is exposed: developers, general contractors, trade partners, equipment suppliers and customers tied to a delivery date.
What would change the decision: a clear account of interfaces, decision rights, sequence dependencies and change control.
4. Investment: Who carries each risk before revenue begins?
Capital discussions become easier to compare when every party uses the same risk language. Start by separating development risk, construction risk, financing risk, operating risk and demand risk. Then ask when each risk moves from one party to another.
A headline funding figure does not explain whether a project is ready to advance. Buyers should examine conditions, dependencies, commitments and the relationship between the financing structure and the delivery plan. Percepture’s guide to data center financing structures provides a useful primer for preparing those questions.
At DCD Connect London 2026, ask capital providers and project sponsors what evidence makes them pause, proceed or change terms. That question is more revealing than asking whether the market is attractive in general.
Who is exposed: sponsors, lenders, investors, operators, contractors and customers whose commitments depend on financial close or another funding milestone.
What would change the decision: transparent conditions, risk allocation and evidence that the commercial plan matches the delivery plan.
5. European capacity: What does “available” mean?
Capacity can refer to land, planning status, a power pathway, buildings under construction, fitted technical space or service that is ready for a customer. Record the category attached to each capacity claim before making a comparison.
When comparing locations or partners, ask for the unit of comparison, the relevant date and the conditions attached to availability. Also ask which constraint is most likely to govern delivery. A market-level statement may be directionally useful while remaining too broad for a site-level decision.
DCD Connect London 2026 offers a chance to compare how operators, developers, investors and suppliers define the same market. Record those definitions. Differences in language may explain why two confident capacity stories point to different conclusions.
Who is exposed: occupiers, developers, investors and suppliers making plans from market-wide capacity claims.
What would change the decision: a consistent definition tied to location, project stage, timing and material dependencies.
Use this scorecard during meetings
The table below is an original editorial tool for DCD Connect London 2026. It does not rate vendors or predict project outcomes. It helps a buyer distinguish a broad proposition from an answer that can support further diligence.
| Issue | Ask this | Listen for | Record next |
|---|---|---|---|
| Power | Which milestone supports the stated delivery date? | Defined status, ownership, dependencies and fallback choices | Document or specialist review required |
| Cooling | Which workloads and operating assumptions shaped the design? | A reasoned design basis and clear responsibility boundaries | Assumptions that require technical review |
| Construction | Which interface can most affect sequence or handover? | Named decision gates, dependencies and change controls | Owner for each unresolved interface |
| Investment | Who carries each risk before operations begin? | Conditions, transfer points and alignment with delivery | Commercial terms requiring diligence |
| Capacity | What exactly is available, where and when? | A consistent definition with project stage and dependencies | Basis for an equal comparison |
When comparing answers, note whether each speaker defines the claim, identifies the responsible party and names the next diligence step. Also record any change in terms, missing project stage or assumption presented without its supporting milestone.
Build a personal agenda from unresolved questions
The official DCD Connect London 2026 event page is the right place to verify current event and agenda information. Do not copy the whole programme into your own plan. Select sessions and meetings based on the questions your team cannot answer internally.
For DCD Connect London 2026, divide your agenda into three types of conversation:
- Market conversations test definitions, direction and regional differences.
- Project conversations test a specific site, design, schedule or commercial proposition.
- Specialist conversations identify where engineering, legal, financial or operational review is required.
Use these categories to decide whether a question belongs with a market expert, a project party or an independent specialist.
Prepare better one-to-one meetings
Send a short question before the meeting when possible. Explain the decision behind it and the type of evidence you want to understand. That gives the other party a chance to bring someone who can answer rather than spending the meeting arranging a follow-up.
At DCD Connect London 2026, use the same core question with several relevant parties. Do not expect identical answers. Compare definitions, assumptions and boundaries. Where answers conflict, record the conflict without trying to settle it in the room.
If network reach or interconnection affects the decision, review the available data center interconnect options before supplier meetings. For broader procurement planning, use the data center buying guide checklist to connect event conversations to a structured evaluation.
Keep this URL useful after the event
After the event, review your DCD Connect London 2026 notes and update this page with verified takeaways rather than publishing a thin recap. Each update should state what was learned, identify the source that supports it and explain whether it changed one of the five decision questions.
Post-event update test
- Keep: documented changes to definitions, decision criteria or official event information.
- Add carefully: attributed expert observations that materially improve a buyer’s decision.
- Leave out: unattributed hallway claims, predictions presented as facts and technical conclusions without suitable review.
For DCD Connect London 2026, this approach preserves one canonical resource across the event lifecycle. It also makes later revisions useful to readers who did not attend but still need to understand what evidence matters.
Questions leaders may still have
What is DCD Connect London 2026?
DCD Connect London 2026 is an event for the data center and digital infrastructure market. Use the organizer’s official page for current logistical and programme information. This Percepture guide focuses on the questions business leaders can use to evaluate power, cooling, construction, investment and capacity discussions.
Who should use this watchlist?
The watchlist is designed for owners, executives, marketing leaders, investors and commercial teams that need to understand the business effect of infrastructure decisions. It does not replace engineering, legal, financial or operational diligence.
How should a buyer compare capacity claims?
Ask every party to define the location, project stage, timing, unit of comparison and material dependencies. For a like-for-like comparison, record land, planned development, construction and operating capacity as separate categories.
What should construction leaders ask?
Focus on interfaces. Ask which decisions must be made early, which packages depend on them, who owns changes and how testing and handover have been planned. Escalate technical conclusions to qualified project specialists.
How can marketing leaders use the event?
Marketing leaders can test whether company claims use the same definitions that buyers and technical teams use. They can also identify unanswered customer questions that deserve clear, evidence-backed content after the event.
Should every event conversation become content?
No. Publish only what serves a reader and can be supported appropriately. Private remarks, unattributed claims and unreviewed technical conclusions should not be turned into public evidence.
Before attending DCD Connect London 2026, readers can also compare the event with Percepture’s guide to the best data center conferences. Companies preparing pre-event, live and post-event communications can review Percepture’s omnichannel marketing services to connect expert content, outreach and follow-up around one buyer journey.
Plan the communication work around the event
Review Percepture’s service and pricing paths if your team needs a coordinated programme for expert content, search visibility, media outreach and post-event follow-up.
About Bob Generale
Bob Generale is President of Percepture.
This guide does not present Bob as an engineer or operator. Technical conclusions about power, cooling, construction and interconnection remain subject to review by the qualified specialists responsible for the work.
