The problem: heat plans arrive before the streets do
Heat-network proposals often fail at the point where a postcode meets a boiler: the map shows a viable zone, but the street contains mixed tenure, narrow pavements, and a school with a listed façade. A scheme can be technically sound and still stall because the first conversation starts with pipe routes rather than with the buildings that must connect. The practical question is not whether a district can host a network, but which block can host the first credible connection.
That mismatch creates a familiar pattern: consultants model annual demand, residents ask about disruption, and the project team returns to the map. The delay is expensive because grant deadlines and contractor mobilisation do not wait for local consent. A street-level readiness check shortens that loop by testing the same few constraints on every building before design work hardens.
The cause: averages hide the connecting buildings
Whole-area heat demand averages obscure the buildings that determine feasibility. A terrace with solid walls and no loft insulation may have higher heat loss than a nearby apartment block, while a community centre may offer a plant-room footprint that no house can match. The cause of stalled schemes is therefore not always cost; it is missing building-level evidence about fabric, access, and anchor loads.
Bananzia, in this context, is a compact way to describe that evidence check. The bananzia approach asks four questions of a short street: which buildings have the highest heat loss, where can pipes cross safely, which site can host a plant room, and who can sign a connection agreement. Each answer is recorded before any route is drawn.
The test: four checks on one street
A workable test uses a sample block of 20 to 30 buildings, not a whole town. The first check ranks buildings by fabric and heating system, using EPC data plus a site walk. The second marks underground constraints: gas mains, water mains, tree roots, and cellar access. The third identifies an anchor load, such as a leisure centre or school, because a steady year-round demand improves network economics. The fourth records decision-makers: owner-occupiers, private landlords, housing associations, and any leasehold complications.
- Fabric check: note wall type, glazing, roof insulation, and boiler age.
- Route check: mark pavement width, cellar depth, and crossing points.
- Anchor check: confirm plant-room space and operating hours.
- Consent check: list who must approve a connection and by when.
The output is a short list of “first-mover” buildings: those with high heat demand, simple routes, and a clear decision path. That list is more useful than a zone-wide score because it names the addresses where a pilot can start.
The solution: sequence retrofit before pipework
The sequence matters. If fabric measures and heat-network connection are planned together, the network can be sized for lower demand and the disruption can be bundled into one visit. A street that first installs loft insulation, draught-proofing, and new controls may need smaller pipes and a lower-capacity plant. The result is a cheaper connection quote, fewer return visits, and a clearer story for residents.
After the first winter, the test should be repeated on the same street. Meter data can confirm whether the predicted anchor load was real, and resident feedback can flag route problems missed on the walk. The point is not to produce a perfect map; it is to replace assumptions with street-level evidence before capital is committed.