One global rate or pay by location?
A few clear zones beat both one rate for everyone and a rate for every city.
Short answer: For most remote companies, location-based pay works best as a few clear zones built on the labor market for your jobs, not on living costs. One rate everywhere is a hidden location choice. A rate for every city cannot be explained. Decide the move rule before anyone moves and set pay separately in each country.
Two engineers, one job, two cities
Picture a 160-person B2B software company that went remote-first in 2021. It was founded in Denver and now employs people in 26 states. For four years it has set pay case by case. Offers in Denver used the company's salary survey. Offers elsewhere used whatever the hiring manager thought it would take.
The cracks show up in one month. A senior engineer in Kansas City learns that a new hire in Seattle, doing the same job at the same level, earns about 20% more. A product manager tells her manager she is moving from Austin to Boston and asks whether her pay goes up. A finance lead in Ohio, hired at the Denver rate, asks whether he is about to be cut to "Ohio pay". The CEO wants one rule before the next pay review.
In the leadership meeting, two camps form fast. The CFO wants location-based pay set city by city, because the survey can produce a number for every metro. The VP of engineering wants one national rate, because "we're remote, a job is a job". Both arguments sound principled. Both would leave the company with a different set of problems by next year.
The real question is not "location or no location". It is how much location should matter, for which roles and what story the company tells about it.
This company is a composite of situations common at this size. It is not a client and the details are illustrative.
Why pay by location is hard
Location-based pay means the same job at the same level pays differently depending on where the person works. The difference is usually set through pay zones: Groups of places treated as one labor market, each with its own pay range or its own adjustment to a national range.
Two good goals pull against each other. The first is competing in each labor market. Pay levels for the same job differ from place to place, because employers compete for people locally even when the work is remote. A company that ignores this pays more than it needs to in some places and cannot hire in others. The second is internal fairness. Two people doing the same work for the same team, in the same meetings, will compare their pay. A difference that looks arbitrary does more damage than one that is large but explained.
A second tension sits underneath. Simplicity and precision both cost something. One rate for everyone is easy to run and to explain, but it is accurate for almost nobody. A precise rate for every city tracks the market closely, but it produces rules nobody can remember and a pay event every time someone moves.
Employers have not settled the question. In a 2026 survey of 3,413 organizations, mostly in the US, 26% paid everyone a flat rate based on their headquarters location. Others used pay zones, zip code adjustments or other location models. The survey publisher's own conclusion was that no geographic method is better than the others as long as it is applied consistently [1]. In a 2025 survey of 534 larger US employers with remote or hybrid roles, the authors summarized that very few had put geographic pay differences in place for remote and hybrid work. 58.8% had rules on where remote employees could work, such as staying in the same state or country [2].
Remote work has also stayed large enough that the question will not go away. In September 2026, about 27% of full paid working days in the US were worked from home [5]. For a company that hires across states, every new hire outside headquarters is a location-based pay decision, whether or not anyone calls it that.
Five ways location-based pay goes wrong
Each of these starts from a reasonable idea and ends in a policy that is either expensive, unfair or impossible to explain.
"We pay for the cost of living"
What it looks like: The policy is explained as a cost-of-living adjustment. People in cheaper places are paid less because "it costs less to live there".
Why smart teams fall into it: Cost of living is intuitive. Everyone understands that rent in San Francisco is higher than rent in Little Rock. It sounds kind, almost generous, to say pay follows people's costs.
What it costs: It explains the policy on the wrong basis. Employers do not pay for people's expenses. They pay what it takes to hire and keep someone in a labor market. Those two measures differ. In 2024, US state price levels ranged from 86.9% of the national average in Arkansas to 110.7% in California, with housing rents the main driver of the difference [4]. Pay gaps for specific jobs can be wider or narrower than that, depending on how many employers compete for the role in each place. A cost-of-living story also invites arguments about personal circumstances. The employee who moved to a cheaper town to care for a parent hears that the company has decided what her life should cost. The engineer in an expensive city with a paid-off house asks why he is paid more. Once the policy is framed as covering costs, every person's costs become a fair question. Cost of labor is harder to say in a sentence, but it is the basis the policy actually runs on. It is the one that holds up when an employee pushes back.
"One rate everywhere is simpler and fairer"
What it looks like: The company pays the same for each job wherever the person lives, usually at the headquarters rate or a national figure.
Why smart teams fall into it: It is easy to explain and easy to run. It feels like the honest answer for a remote company: The work is the same, so the pay is the same. It avoids every awkward conversation about moves.
What it costs: One rate is a location decision in disguise. It is pegged to some market, usually the headquarters city or a national average. If it follows a high-cost market, the company overpays in most places and the cost compounds every year through percentage raises. If it follows a national average, the company struggles to hire in the most expensive markets. Over time the rate tends to drift upward. Each hard-to-fill role in a high-cost city pushes it up. The higher number then applies everywhere. Across countries, one rate breaks almost at once. Currency movements, payroll taxes, statutory benefits and local markets make a single salary figure mean very different things in different countries. One rate within a country can work well. It works best when most of the workforce sits in similar labor markets or when the company has decided, on purpose, to pay above market in cheaper places as a recruiting advantage. It fails when it is chosen to avoid the conversation.
"A zone for every city"
What it looks like: The company builds a separate rate for every metro area its survey covers. An offer in Raleigh differs from one in Charlotte and from one in Durham.
Why smart teams fall into it: The data allows it. Salary surveys and pay tools can produce a figure for almost any location, so precision looks free. More zones also feel more accurate and therefore more defensible.
What it costs: Precision costs trust and time. Every move between neighboring cities becomes a pay decision. Staff in the same team end up on many slightly different numbers, with differences too small to matter and too frequent to explain. The data underneath is also thinner than it looks. For a small city and a specialized role, the survey figure may rest on a handful of employers. Each year the city figures move by different amounts for reasons that are mostly noise. A company that follows them faithfully moves pay for noise. The worst version is a city rate that changes when an employee moves a few miles across a boundary. That rule will be tested. The person testing it will tell colleagues about the answer. A few zones, each covering many places, give up some precision. In return the policy can be stated in one sentence and lasts more than a year.
"Remote work is worth a discount"
What it looks like: Remote roles are paid below office roles, or remote staff are told that flexibility is part of their pay. Sometimes the discount is hidden inside the location rule, with "remote" treated as its own lower zone.
Why smart teams fall into it: Workers do value remote work. Some say they would accept less pay to keep it. It seems logical to price that preference.
What it costs: It mixes up two different questions: Where someone works and how they work. A study of US tech workers using real job offers found they would give up about 25% of pay for partly or fully remote roles. The same study found that remote jobs did not pay less than comparable in-person jobs, which the authors called a puzzle [3]. Employers have mostly not tried to collect that discount. In the 2025 survey, 65.5% made no pay changes when staff returned to the office. The authors found almost no employers lowering pay based on workplace [2]. A company that does introduce a remote discount stands out. It signals that remote staff are second-class. It also makes every hybrid arrangement a pay negotiation. If a location difference is justified, it should come from the labor market where the person lives, not from the fact that they work at home.
"We'll decide when someone moves"
What it looks like: There is no written rule for relocations. When someone moves, their manager, HR and finance agree an answer for that person.
Why smart teams fall into it: Moves are rare at first and every case feels different. A family reason, a strong performer or a critical role all seem to deserve their own answer. Writing a rule before the first case feels premature.
What it costs: The first answer becomes the rule. If the company protects one person's pay after a move to a cheaper place, the next person expects the same. If it cuts one person's pay, everyone learns that moving is risky and some stop telling the company where they live. Ad hoc answers also create equal pay risk. In the US, women worked from home on a larger share of their paid days than the workforce as a whole in every month from August 2025 to September 2026: 28.1% against 26.8% in September 2026 [5]. A location rule that is applied unevenly can produce a gender pay gap without anyone intending it. In the EU, a pay practice that looks neutral but puts one sex at a particular disadvantage must be objectively justified by a legitimate aim through means that are appropriate and necessary [6]. Location differences are not banned. A difference that cannot be explained by a written rule, applied the same way to everyone, is hard to defend. Our guide on which pay gaps you can defend covers why an explanation alone is not a defense.
What a sound location policy looks like
The two extremes fail for opposite reasons. A sound policy usually sits between them: A small number of zones with a clear story. In our view it has these qualities.
- It rests on the labor market. Zones group places where pay levels for the company's own jobs are similar. They are not built on rent or living costs.
- There are few zones. Within one country, a handful of zones is usually enough. Each one covers many places, so most moves do not change anyone's pay.
- The story fits in one sentence. A manager can explain it without a spreadsheet: "We pay in line with the labor market where you work, in three bands of places."
- Countries are separate. Each country has its own structure. A single global salary figure is treated as a deliberate exception, not a default.
- The move rule exists before the first move. Everyone knows in advance what happens to pay when they relocate, in either direction and from when.
- It reaches job ads. Where pay range laws apply, posted ranges match the zone rule. Either each ad shows the range for the zones it covers or it states the location rule next to the range. Our guide on which pay law applies to remote job ads covers this in detail.
- It is checked for side effects. Once a year, someone looks at who sits in which zone and whether the zone rule is producing a gap by gender or another protected group.
The last test is the simplest. Ask three managers in different states how pay is set for someone in their team who lives elsewhere. If they all describe the same rule, the company has a location policy. If each one describes a different deal, it has a set of exceptions.
The calls only you can make
Data can show how pay levels differ between places. It cannot decide how much those differences should matter to your company. These decisions belong to leadership.
How far apart the zones sit. Following the market fully saves money in cheaper places. Narrowing the gaps costs more but makes the policy feel fairer to the people in lower zones. Some companies narrow the gaps on purpose and say so.
Whether cheaper places are a hiring advantage. A company can pay a national rate partly so it outbids local employers in lower-cost markets. That is a legitimate strategy. It should be chosen for its benefits, not adopted by default.
What happens on a move. Pay can follow the new location both ways, rise only, stay frozen until the zone catches up or change only at the next pay review. Each choice sends a different message. The answer must be the same for everyone.
Where people may work. Allowing work from anywhere widens the talent pool. It also adds payroll, tax and employment law obligations in every new state and country. Many employers restrict remote work to certain states or countries for that reason [2].
How much to say. Publishing the zones and the move rule builds trust and invites comparison. Keeping them internal avoids debate but leaves people to guess. They usually guess the worst. Your compensation philosophy is the natural place to say where location fits.
Who owns exceptions. Someone will ask to keep their old zone after moving. Decide now who can approve that and how it is recorded.
The numbers and the law
- Methods vary. In a 2026 survey of 3,413 organizations (fielded October to December 2025, 80% in the US), 26% paid a flat rate based on headquarters location. Others used pay zones, zip code adjustments or other location models. 42% posted salary ranges for all jobs regardless of location [1].
- Remote pay rarely discounted. In a 2025 survey of 534 US employers with remote or hybrid-capable roles (fielded June to August 2025; median size 4,300 employees), 65.5% made no pay changes when staff returned to the office and 58.8% restricted where remote employees could work [2].
- The value of remote work. US tech workers would accept about 25% less pay for partly or fully remote roles, yet remote jobs in the study's data did not pay less than comparable in-person jobs [3].
- Cost of living. In 2024, US state price levels ranged from 86.9 (Arkansas) to 110.7 (California) against a national average of 100. Housing rents ranged from 54.2 (West Virginia) to 154.3 (California) [4].
- Remote work. About 26.8% of full paid working days in the US were worked from home in September 2026; for women the figure was 28.1% [5].
- EU. Pay structures must allow work to be compared on objective, gender-neutral criteria. A neutral-looking practice that puts one sex at a particular disadvantage is indirect discrimination unless it is objectively justified and the means are appropriate and necessary. Applicants must receive the initial pay or range for the position. Workers can be compared across a single source that sets the pay conditions, such as one pay policy covering several entities [6].
- US job ads. Some state pay range laws cover remote roles that could be done in the state. Washington, for example, covers remote work that could be performed by a Washington-based employee [7]. A zoned policy has to show up in those posted ranges.
This is general information, not legal advice.
Our view
For most companies of 50 to 500 people that hire across a country, we think a few clear zones beat both extremes. Base them on the labor market for your jobs, not on living costs. Keep them few enough that a manager can explain the rule in one sentence. Write the move rule down before anyone moves.
One national rate is a sound choice when most of your people sit in similar markets or when you have decided to use it as a hiring advantage. It should never be a way to avoid the conversation. Across countries, we would always set pay by country.
We would argue hardest against three things: Calling the policy a cost-of-living adjustment, setting a separate rate for every city and treating remote work itself as a reason to pay less. Each one turns a pay policy into an argument about people's lives.
Where we help
Our pay band work covers location: We agree with your leaders how much location should matter, group your hiring locations into a few zones based on the labor market for your roles and write the move rule and the job ad wording with it. The starting point is a pay band project, priced by roles and locations. If a conversation would help first, Book a free call.
*We don't provide market data. We use the data you have or buy. No data yet? We help you choose a survey or tool that fits your size and budget.
Sources
- Payscale, 2026 Compensation Best Practices Report (3,413 respondents, October to December 2025), location section, checked 2026-10-25
- Payscale, Empsight and Deloitte Consulting, What's next for workplace flexibility and geographic pay? (webinar slides; survey of 534 organizations, June to August 2025), checked 2026-10-25
- Cullen, Pakzad-Hurson and Perez-Truglia, Home sweet home: How much do employees value remote work? NBER Working Paper 33383 (January 2025), checked 2026-10-25
- US Bureau of Economic Analysis, Real personal consumption expenditures by state and real personal income by state, 2024, regional price parities (19 February 2026), checked 2026-10-25
- Barrero, Bloom and Davis, Survey of Working Arrangements and Attitudes, work from home rate, all workers and women (FRED series WFHCOVIDMATQUESTION and WFHCOVIDFRACMATWOMEN, updated 5 October 2026), checked 2026-10-25
- Directive (EU) 2023/970 on pay transparency, Articles 3(1)(j), 4(4), 5 and 19 (EUR-Lex), checked 2026-10-25
- Washington L&I, Administrative Policy ES.E.2, Job Posting Requirements (issued 3 December 2025), checked 2026-10-24