By Dropalo Editorial
Watch a new district being built and you will notice that the order of work is not random. Long before the first front door is hung, the ground is opened up for things nobody will ever see. Drainage runs go in. Water mains are laid. Cable routes and ducts are threaded under future pavements. Roads are built to a standard so that, one day, someone else can take them on.
There is a simple logic behind that sequence. Anything that is hard, disruptive or expensive to add once people live there goes in first. Nobody wants to dig up a finished street to lay a pipe that could have gone in when the trench was already open.
That logic has now reached broadband. It has not yet reached the place itself.
The pipe is planned in
Since 26 December 2022, the Building Regulations in England have included specific requirements for connectivity in new homes. According to the government’s guidance for developers on new build connectivity, new dwellings must be built with gigabit-ready physical infrastructure, and, subject to a cost cap of £2,000 per dwelling, with a working gigabit-capable connection. Where a gigabit connection cannot be secured within that cap, the next fastest available connection is to be installed instead. The detail sits in Approved Document R, the statutory guidance that supports Part R of the regulations.
Two details stand out. First, information about the planned infrastructure and connection is expected at an early stage, as a “connectivity plan” provided with the building approval application. Second, the stated purpose is the same sequencing logic as the drains and the water. The explanatory memorandum to the regulations says the measures will help prevent the need for “disruptive, time-consuming and expensive retrospective works” to homes.
So the pipe is now part of the plan. It is designed, documented and installed before anyone moves in. (This is a description of what the rules say, not guidance on how any particular scheme should comply.)
The pipe is not the layer
A gigabit connection tells you that information can reach a home quickly. It says nothing about what information the district itself has to offer, who is responsible for it, or whether it is true.
Think about the questions a new district actually has to answer in its first year. Which entrance should residents use while the next phase is under construction? Where do parcels go for the blocks that have no concierge yet? Which path across the site is open and lit after dark this month? When is the shared room free, and who holds the key? Who should someone tell about a broken gate on the estate road, and is that road the developer’s, the management company’s or the council’s?
None of that travels down a fibre on its own. It is the place’s own account of itself: what is here, what is open, what has changed, and who looks after it. That account is as much a part of a working district as the drainage. Yet there is no equivalent of a connectivity plan for it. In most schemes it is not designed in at all. It is bolted on after handover, by whoever happens to be holding the problem at the time.
The first months set the habits
The reason this matters is timing. People form habits quickly in a new place, and the first months set the pattern.
If there is no clear, trusted source for what is happening on site, residents will create one. A messaging group appears within weeks. Someone pins a sheet of paper by the lifts. A managing agent rolls out the resident app it uses elsewhere. A shop on the ground floor posts its own updates. Each fills a real gap, and each is done in good faith.
But whatever fills the gap first tends to become the default, and defaults are sticky. Once a few hundred households have learned to ask the messaging group, a better-organised source arriving in year three has to compete with an established habit. In that sense, the place’s information layer behaves just like the ducts under the pavement. It is far cheaper to put in at the start than to retrofit around people who are already living there.
The layer splits along the lines of the build
There is a second problem, and it follows the shape of construction itself.
Large districts are rarely delivered as one piece. They arrive in phases, in plots and in blocks, often with different contractors, different operators and sometimes different owners. Each of those boundaries is a natural place for the information layer to split. One block has one app, the next has a different one. The retail units are run by a separate team with its own channels. The park is looked after by a management company that communicates by email. The roads may be adopted by the highway authority, the open spaces may not.
The result is a district that is one place on the masterplan and several unconnected places on a phone screen. A resident trying to find out whether the footpath to the station is open has to know which of those fragments is responsible for that particular strip of ground. A visitor has no idea at all.
Who keeps it when the builders leave?
The infrastructure world already has a clear way of thinking about this, called adoption.
When a developer builds a new estate road, it can enter into an agreement with the local highway authority under section 38 of the Highways Act 1980. Under that agreement, the road becomes a highway maintainable at the public expense from a date set in the agreement. In other words, the hand-over of responsibility is planned, written down and dated before the work is finished. New sewers and water mains have comparable adoption arrangements of their own.
The planning world has a name for the wider principle, too. The Town and Country Planning Association’s Garden City Principles include “long-term stewardship of assets” as one of the elements of a well-made new settlement.
The place’s own information layer rarely gets that treatment. There is no adoption agreement for what the district says about itself. When the sales team moves on and the site office is removed, the knowledge it held tends to move on too. The managing agent, the residents’ association, the shops and the local authority each inherit a piece, and nobody inherits the whole.
Why this happens, without a villain
It would be easy to frame this as somebody’s failure. It is not.
Developers are asked to deliver homes, sell them and hand them over well. Utilities are asked to connect them. Managing agents are asked to run buildings and collect service charges. Connectivity now has a regulation, a standard and a plan attached to it, so it gets designed in. The place’s own information layer has none of those, so it gets handled as a marketing task during sales and an operational task afterwards.
Everyone is doing the job they were given. The gap sits between the jobs.
The parts that will commoditise, and the part that will not
Much of the technology around a new district is already becoming interchangeable, and more of it will.
Connectivity itself is being standardised by regulation. Resident apps, service-charge portals, parcel lockers, amenity booking tools, access control and smart-building systems are all available from many suppliers, and they increasingly resemble one another. Maps, property listings and review sites will cover the district once it exists, as they cover everywhere else. All of these are useful. None of them is unique to a particular place, and each can be swapped for a similar one.
What does not copy so easily is the place’s own current account of itself. Which entrance, which path, which room, which change, which steward, at this location, today. That knowledge is tied to the ground. It has to stay coherent across phases, blocks and operators, and it has to survive the hand-over from builder to the people who will look after the place for decades.
That is where Dropalo is pointing its work. The aim is a place-native layer: a district, a block or a single courtyard able to hold what is currently true about it and share that with whoever is there, maintained by those who actually look after the ground. Dropalo is digital, and this is the layer where it aims to offer what the commoditised tools are not built to provide. It is a direction of travel. It is not a shipped product for developers, and nothing here describes any particular scheme.
A line in the plan, not a launch campaign
The practical shift is small to describe. Treat the district’s information layer the way the drains, the roads and now the broadband are treated: as part of the infrastructure, with a line in the plan and an owner.
A few questions are enough to start that line:
- What will this place need to tell people in its first month, before most of it exists?
- Where will that live so that it works across every phase, block and operator?
- Who owns it during construction, and to whom does it pass at each hand-over?
- How will it stay true when the site changes, as it will, week by week?
Those questions cost very little to answer before the first resident arrives. They are much harder to answer once a dozen informal channels have already taken root.
The fibre now arrives on day one. The place’s own information layer should arrive with it.
New districts deserve a digital layer from day one.
This article describes a direction rather than a shipped capability.