Geographic Pay Adjustment

A salary adjustment based on the cost of living or labor market rates in an employee's location.

Geographic pay adjustments (also called location-based pay or geo-banding) reflect the reality that labor markets and costs of living vary dramatically by location. A software engineer in San Francisco commands a higher salary than the same role in Nashville — both because local living costs are higher and because local market rates have historically been higher. Employers adjust pay to remain competitive in each market while managing costs.

With remote work now widespread, geographic pay has become one of the most contested compensation topics. Companies that once handled location-based pay informally have had to formalize written policies. The approaches divide into two broad camps: companies that pay a single national rate regardless of where you live, and companies that apply location multipliers or geo-tiers that reduce pay if you're in a lower-cost area.

Geographic pay cuts became a flashpoint during the remote work era. When employees relocated from high-cost cities to lower-cost ones, many employers reduced their salaries proportionally — sometimes significantly. Employees who had chosen where to live based on a stated remote-first policy felt blindsided. The lesson: before relocating, get your employer's geo-pay policy confirmed in writing, including whether a relocation triggers a mandatory review.

When comparing offers across locations, always normalize for geography. A $150K offer in San Francisco and a $125K offer in Raleigh may represent similar purchasing power after accounting for cost of living — or the San Francisco offer may still be materially better depending on specific expenses, housing costs, and career trajectory. Tools like NerdWallet's cost of living calculator or the Economic Policy Institute's family budget tool help make this concrete.

Common Geo-Pay Structures

  • Single national rate: One salary for a role regardless of location — typically set at or above major market rates. Rare but increasingly used by companies trying to attract remote talent.
  • Tiered geo-bands: Cities grouped into tiers (e.g., Tier 1: NYC/SF/Seattle; Tier 2: Austin/Denver/Chicago; Tier 3: lower-cost markets). Each tier has a different pay scale.
  • Continuous cost-of-labor index: Salaries adjusted by a location factor derived from ongoing market data, updated annually.
  • Point-of-hire rate: Salary set based on where you were hired; relocation may or may not trigger renegotiation depending on policy.

Questions to Ask Before Accepting a Remote Role

  • Does the company use geo-banding? If so, what tier is my current location?
  • If I relocate to a lower-cost area, will my salary be adjusted? What's the process?
  • Is the geo-pay policy documented somewhere I can reference?
  • Does remote work eligibility change if I move to a different state?
  • Are there states the company doesn't allow remote work in due to tax or legal complexity?

Example

An engineer accepts a remote offer at $160K while living in Seattle (Tier 1). A year later she moves to Boise, Idaho. Her employer's geo-pay policy reduces her salary by 12% on relocation — bringing it to $140,800. Because she didn't confirm the policy before moving, she's surprised by the adjustment. Her offer letter referenced the Seattle rate with no mention of relocation impact.