London Weighting and Location-Based Pay: Why Geography Raises Some Salaries and Discounts Others
London weighting pays a premium for working in the capital. But as other cities become more expensive and work goes global, does location-based pay still make sense?

London weighting rests on a familiar bargain: working in the capital costs more, so the salary should be higher.
But consider Bristol. The bunq Working Abroad Index 2026 estimates monthly living costs there at €2,233. That is more than Stockholm at €2,070, Paris at €2,012, Berlin at €1,959 and Frankfurt at €1,893.
Should Bristol workers now receive their own location premium? If not, what exactly is London weighting paying for?
The answer opens a much bigger question for global employers. Geography can add money to a salary, as it does in London. It can also remove money through regional pay bands, international salary ranges and lower-cost labour markets. The logic sounds simple until the cost of a place and the cost of hiring there stop telling the same story.
What is London weighting?
London weighting is not one universal allowance. It is a broad name for the additional pay some employers offer to people working in or around London. Sometimes it appears as a separate supplement. Elsewhere, it is built into a higher London salary range.
The NHS provides a particularly visible example. Its High Cost Area Supplements add 20% to basic pay in Inner London, 15% in Outer London and 5% in fringe areas, subject to minimum and maximum amounts.
Other employers structure the same idea differently. The Cabinet Office told Parliament that it has no London weighting allowance, but operates separate London and national pay ranges determined by the employee’s designated office.
The label changes. The result does not: location influences salary.
Cost of living and cost of labour are not the same
Employees naturally hear “London weighting” and think about rent, transport and the price of buying lunch near the office. Compensation teams are usually thinking about something else as well.
Cost of living asks what it costs an employee to live somewhere. Cost of labour asks what an employer must pay to recruit and retain the required skills in that market.
As compensation specialist Sean Luitjens writes for WorldatWork, “Employees don’t experience compensation through salary surveys, regression models, geographic differentials, market percentiles or color-coded spreadsheets.” They experience it when the rent is due.
The difference explains why a city can become painfully expensive without immediately commanding London salaries. Housing demand can race ahead while the supply of workers, local industries and competing employers remain quite different.
That is exactly what makes Bristol interesting. Bunq’s figures are illustrative, using Numbeo data and a standardised one-bedroom rent measure. But official UK data confirms the pressure: average private rent in Bristol reached £1,880 in July 2026, up 6.5% in a year.
That does not automatically create a Bristol labour premium. It does make “London is paid more because London costs more” look increasingly incomplete.
Why does geography produce a premium in one place and a discount elsewhere?
Location-based pay is not an outdated British quirk. In Ravio’s European tech compensation survey, 51% of respondents said they localised every employee’s salary using market data for the place from which they worked.
The same basic principle sits behind some offshoring and outsourcing decisions. Employers move work to markets such as India or the Philippines partly because skilled labour can be bought at a lower local rate than in Western Europe or North America. The work may cross borders instantly. Its market price does not.
That is not automatically exploitation or hypocrisy. Labour markets genuinely differ. But it reveals how readily businesses accept geography when it reduces payroll. A credible location-based philosophy must also recognise when a market becomes more expensive, difficult to recruit in or poorly served by an old regional band.
Remote work makes the test sharper. An employee can change home without changing their job, manager, customers or output, then discover that they are now worth a different amount.
GitLab’s published relocation policy shows this working in both directions. A move to a higher location factor can increase salary; a move to a lower factor can reduce it. Buffer takes a broader approach, publishing its salary formula and using only two cost-of-living bands, global at 90% and high at 100%.
Neither model eliminates difficult comparisons. Both at least make the rule visible.
London weighting is really an explanation problem
There may be good reasons to pay a nurse in central London, a remote developer in Lisbon and an outsourced specialist in Manila differently. “Location” alone is not the reason. It is shorthand for a bundle of decisions about living costs, labour supply, competition, employment costs and how widely the employer is prepared to recruit.
That shorthand is becoming harder to defend when employees can compare salaries and cities for themselves.
Employers need to be able to answer some basic questions. Is their London weighting intended to help with the cost of living or compete in the London labour market? Is the relevant location where someone lives, where their office sits or where their replacement could be hired? What happens when an employee moves? How often are geographic bands reviewed?
Bristol costing more than Paris does not prove that London weighting is obsolete. It proves that familiar labels can conceal very different pay philosophies.
The future of location-based pay is unlikely to be one global salary. It should be a clearer account of why geography raises some salaries, discounts others and occasionally changes the price of a job that has not changed at all.




