Population Growth Rate of London: A Developer's Guide
By Domus
By Domus
Most advice on the population growth rate of london fails at the first underwriting test. It treats London as one demand pool, one growth line, one safe assumption. That's convenient for a slide deck and dangerous for a land bid.
A developer can't price a scheme off a citywide headline if the underlying drivers of demand are weakening, shifting, or moving to different parts of the market. What matters isn't whether London is “still growing” in the abstract. What matters is whether the households your scheme needs are forming, arriving, and staying in your catchment, at the price point and unit mix you're planning to build.
That distinction decides whether a viability model is strong or optimistic.
The biggest mistake I see is simple. People plug a single London population growth number into an appraisal and assume that supports future absorption, pricing and exit liquidity.
It doesn't.

The underlying engine has changed. London Forum's review of recent population change notes that between 2012 and 2023, excess births over deaths added more than 850,000 people to London's population, but births fell from 134,000 in 2012 to 105,000 in 2023. The same review says the migration balance moved from a +49,000 net gain in 2014 to -17,000 in 2020, with GLA projections showing net loss continuing into the 2040s.
That matters because the standard shorthand is wrong. Many buyers, brokers and even some investment committees still talk as if London growth is a durable, self-renewing constant. In practice, both major support beams have weakened.
Population growth isn't the same thing as bankable housing demand. A city can keep growing while a specific submarket loses family households, a commuter belt captures movers, or tenant demand shifts toward smaller rented homes rather than homes for sale.
For appraisals, that changes three things fast:
Practical rule: If your model uses one London growth assumption without separating births, deaths and migration, you're not modelling demand. You're importing a headline.
The useful question isn't “What is the population growth rate of london?”
It's this. Where is growth still investable, what type of households are driving it, and how exposed is that demand to policy, affordability and labour-market shifts?
That's the question a credit paper should answer. It's also the question most market commentary skips.
A better way to think about population change is to treat it like a bath with taps and drains. Water level is the total population. But that level changes for different reasons, and each reason affects property demand differently.
There are four basic components behind population movement in any city.
Put those together and you get the net change. But the mix matters more than the total.
A borough gaining population through births is not the same as a borough gaining population through mobile working-age renters. Those two patterns create different pressure on tenure, unit size, affordability and delivery timing.
A practical example helps. If your site is near a major employment node, migration-led demand may support smaller rental units and faster leasing under the right labour-market conditions. If your site is in a family suburban market, weaker natural change can show up in slower demand for larger homes, even if the city headline still points up.
You can't underwrite a three-bed scheme with the same demographic logic you'd use for a one-bed rental block near a transport hub.
For UK development work, the key habit is to separate stock data from flow data. Census counts tell you where people were. Migration and birth trends help explain why they got there, and whether that demand is likely to persist.
In practice, I'd pull borough-level population history, then test it against planning supply, local affordability, transport access and tenure demand on the ground. The point isn't to build a perfect forecast. The point is to stop pretending one citywide figure can do all the work.
If you want a clean reminder that London is not one market, look at the last full census decade rather than a single city headline.
ONS Census 2021 population change data for London shows Greater London's population rose by 7.7% between 2011 and 2021, reaching 8,799,800 residents in 2021. That sounds steady enough until you break it down by borough.
Then the illusion of one market disappears.
Tower Hamlets grew by 22.1%, the fastest percentage growth in London in that period. Barking and Dagenham grew by 17.7%. Kensington and Chelsea fell by 9.6%. The City of London grew by 16.6%, from about 7,400 in 2011 to 8,600 in 2021, even though the absolute scale there is tiny compared with major residential boroughs.
For a developer, those aren't interesting trivia points. They are a warning against lazy comparables and generic demand assumptions.
If you were underwriting a mid-market apartment scheme in Tower Hamlets using the same demographic baseline as a family-led scheme in Kensington and Chelsea, you'd have been modelling two completely different realities as if they were one.
| Borough | Population 2011 | Population 2021 | % Change |
|---|---|---|---|
| Greater London | 8,170,000 | 8,799,800 | 7.7% |
| Tower Hamlets | Not provided in verified data | Not provided in verified data | 22.1% |
| Barking and Dagenham | Not provided in verified data | Not provided in verified data | 17.7% |
| Kensington and Chelsea | Not provided in verified data | Not provided in verified data | -9.6% |
| City of London | About 7,400 | 8,600 | 16.6% |
The wrong approach is to lift the 7.7% London-wide figure and spread it across every scheme assumption. That hides local demand risk.
The better approach is to ask what borough variation means for your model inputs:
A London average is useful for macro context. It is not evidence for micro viability.
Take two simplified examples. On one site, a developer is assessing compact private units close to a strong transport corridor in a borough that has shown substantial growth. On another, the scheme is larger family housing in a borough that has seen population contraction.
The first scheme still needs proper pricing and supply analysis, but the demographic backdrop may support confidence in depth of demand. The second needs stricter testing on buyer profile, affordability and sales pacing. Using the same population growth rate of london for both would tell you almost nothing useful.
Forecasts still point upward for London, but the shape of future growth matters more than the fact of growth itself.
Trust for London's population time series reports that London's population reached 9.1 million in 2024 and is expected to rise to 9.6 million by 2035. The same verified data set notes a separate summary of ONS projections showing London forecast to grow by 6.7% by 2032, to around 9.7 million, slightly above the projected national average growth of 6.4%.
Those numbers are often read as a green light. They shouldn't be.
The same projection context says London's growth is expected to be driven solely by migration, because natural change is already the lowest in the country and negative in most boroughs. That means future growth is more exposed to labour-market performance, affordability pressure and migration policy than many older models assume.
For development, migration-led growth is not weaker by its very nature. But it is different. It can be more sensitive to job cycles, visa settings, rental affordability and where incoming households choose to cluster.
A sensible appraisal does not treat forecasts as certainties. It treats them as a base case that needs stress testing.
I'd use the projection in three layers:
When growth relies more on migration, the city may still expand while individual product types become more volatile.
For private sale, migration-led growth can support demand in accessible urban locations, but it doesn't automatically support larger owner-occupied family stock in every borough.
For rental, the outlook may be stronger in locations that serve flexible, mobile households. But those same locations can also react quickly to shocks in employment, affordability or policy sentiment.
That's why a forecast population rise should sit near the front of your appraisal pack, but never on its own.
Demographic change in London doesn't happen in isolation. People move because jobs are available, because housing is or isn't affordable, because infrastructure changes commuting logic, and because planning and migration policy shape what can be built and who can stay.

If you want a useful lens for this, think in terms of who is being pulled in, who is being pushed out, and which locations convert that movement into occupied homes. This is also where planning data becomes far more valuable than generic demographic commentary. Good planning intelligence for development decisions helps you test whether apparent demand can translate into deliverable stock in the right format.
Employment remains the first filter. Areas with deep job access tend to attract younger and more mobile households first, especially renters and first movers.
That doesn't mean every transport-rich location is a safe development play. If local pricing pushes occupiers beyond what incomes can support, demand can leak outward even when jobs stay central.
Affordability reshapes London more aggressively than many appraisals admit. When households can't trade up locally, they change tenure, delay moves, leave the borough or leave London.
That has real design implications:
Transport upgrades don't create demand from nowhere, but they can redirect it. They widen the area households consider livable and change which sites compete with yours.
A scheme next to a major interchange doesn't just compete with the immediate neighbourhood. It competes with every other location that offers a similar commute and a sharper value proposition.
The strongest demographic story can still fail to support your scheme if nearby competing locations solve the same housing need better.
Planning policy determines what can come forward, how quickly, and with what obligations attached. Migration policy influences parts of the demand base. Housing policy affects affordability, tenure and investor appetite.
The practical takeaway is straightforward. Demographic demand is never enough on its own. You need the policy environment, infrastructure context and affordability profile to line up with the product.
Demographics become useful when they change model inputs. If they don't alter assumptions on sales rate, unit mix, tenure, pricing confidence or lender risk, they're just presentation material.

London Forum's summary of ONS-based projections says Greater London is projected to grow by 6.7% by 2032, from about 9.1 million to 9.7 million, versus a 6.4% national average. It also states that growth is expected to be driven solely by migration, because natural change is already the lowest in the country and negative in most boroughs. For developers and lenders, that means baseline demand is less tied to local fertility and more exposed to labour-market inflows and migration policy.
A migration-led demand profile usually pushes you to be more precise about household type.
If your scheme is aimed at urban renters or first-stage occupiers, the case may strengthen in accessible employment-led locations. If your scheme is aimed at stable family owner-occupiers, you need much sharper evidence that the local area is retaining or attracting those households rather than growing in aggregate.
Here's where that lands in the numbers you model:
Credit teams don't just want growth. They want evidence that growth supports debt repayment under pressure.
That means borough and submarket demographics should show up in the credit paper as underwriting logic, not background colour. A stronger paper explains why your assumptions differ by product and location, what happens if migration softens, and how much room the scheme has before slower take-up affects interest cover or covenant headroom.
For rental schemes, a sharper framework often comes from testing the site against build to rent operating assumptions, local mobility patterns and replacement demand. For for-sale schemes, it comes from proving who the buyer is and why they'll choose your product now rather than later or elsewhere.
If the demand story depends on “London keeps growing”, the scheme is under-analysed.
Consider three common situations.
A compact apartment scheme in a highly connected urban borough may justify stronger occupancy or sales pacing assumptions if local demand is coming from mobile workers and recent arrivals. But you'd still haircut the downside for policy or job shocks.
A suburban family scheme needs a different test. You'd focus less on city growth and more on whether families can afford to remain in that local market, whether schools and transport support retention, and whether competing stock outside the borough is pulling demand away.
A mixed-tenure scheme sits in the middle. There, population analysis should inform the split between private sale, rental and affordable delivery rather than acting as a generic demand tailwind.
A reliable appraisal doesn't ask for one growth number and move on. It builds a local demand view that can survive challenge from land, credit and investment committees.
Use a borough or submarket demand review before you lock assumptions.
Start with the exact catchment
Don't model “London”. Model the area a buyer, tenant or lender would recognise as your real competition set. If the site sits on a strong transport link, your market area may be wider than the borough boundary.
Match the demographic story to the product
A one-bed rental block, a co-living concept and a family housing scheme should not share the same demand logic. Decide who the end user is first, then test whether local population movement supports that user.
Separate headline growth from household formation
Population can rise without creating equal demand across all tenures and unit sizes. Ask whether the households arriving or staying in the area are the ones your scheme needs.
A decent model has at least one downside case for demographic softness. A strong model has several, each tied to a commercial effect.
Good appraisals don't predict the future perfectly. They show how the deal behaves when the demographic thesis is only partly right.
Before approval, I'd want clear answers to these:
| Question | Why it matters |
|---|---|
| Who is the end occupier or buyer? | Demand quality is product specific |
| Is demand local, incoming, or both? | Different demand sources carry different risk |
| What if migration weakens? | Future growth is more exposed to policy and labour conditions |
| Does the unit mix fit the likely household profile? | Population growth alone won't rescue the wrong product |
| Are we relying on a London average? | Citywide assumptions often hide local weakness |
If your current process can't handle that level of testing, a dedicated development appraisal platform is usually a better answer than building more spreadsheet tabs. The goal is simple. Keep the assumptions auditable, scenario-based and easy to challenge before capital is committed.
Domus helps UK development and lending teams turn demographic assumptions, planning context and finance inputs into one auditable appraisal workflow. If you want fewer spreadsheet blind spots and stronger investment decisions, explore Domus.
From Domus
Domus gives UK developers a structured platform to run development appraisals, residual land value models, planning viability assessments, and cashflow — all in one place.
Domus