DER Hosting Capacity: Why Grid Planning Needs Better Data
Approving the next rooftop solar or EV charger connection used to be a desk-based estimate. Without granular network data, that estimate is either too conservative or too risky — rarely right.
Hosting capacity — how much distributed generation or flexible load a section of the low-voltage network can absorb without voltage or thermal violations — has traditionally been assessed with conservative, worst-case planning assumptions, because that's what the available data supported. Get it wrong in either direction and the cost shows up somewhere: unnecessary network reinforcement, or a connection approved into a constraint nobody saw coming.
Smart meters change what's possible here, but only if the data behind the model is genuinely granular, genuinely current, and genuinely tied to accurate network topology — three conditions that are easy to claim and harder to actually deliver.
This briefing sets out the shift from static to data-driven hosting capacity assessment, and the risks worth naming before trusting the new number over the old one.
Static vs data-driven assessment
Figure 1. "Data-driven" only delivers on its promise if the data is genuinely current and correctly tied to topology — otherwise it's a static model with better marketing.
Six risk points worth naming
Static assessments miss real headroom
A worst-case model can reject a connection a real-time data-informed model would approve.
Static assessments miss real constraints too
Conservative averages can also hide genuine localised violations a granular model would catch.
Data latency undermines "dynamic" claims
Hosting capacity that updates monthly isn't meaningfully more dynamic than a static model.
Topology and meter data must agree
The same mapping risk covered elsewhere in this series undermines hosting capacity just as much as voltage monitoring.
Connection decisions outlive the data that justified them
A headroom-based approval needs periodic revalidation as more DERs connect nearby.
Planning and connections teams working from different data
A hosting capacity model only helps if the team approving connections actually uses its output.
Making "data-driven" true in practice
Base assessments on validated topology and real meter data
Not planning assumptions layered on top of old models.
Match data latency to the decision being made
Genuinely dynamic capacity needs genuinely current data.
Revalidate approvals periodically
As the local DER population grows around an existing connection.
Give connections teams direct access to the same model
Planning teams use — not a summarised, delayed version of it.
Treat hosting capacity as a living calculation
Not a one-time study per feeder.
The value of better hosting capacity data isn't a bigger number — it's a more honest one, in both directions. Some feeders have more room than the old model assumed; others have less. Data-driven planning only earns its name if it's willing to say either.
How a read moves across the estate
HOVER OR TAP A STAGE TO EXPAND TECHNICAL SPECS

Chris Gales
Chris Gales leads CEHG. He converts complex technical and commercial choices into clear decisions and dependable outcomes for utilities running connected device estates at scale.
He writes these field notes from the practice — on bearer migration, smart metering architecture, procurement and operations — to help estates start counting down early.

