How to Set Pay Bands for Remote and Distributed Teams

The Problem With Remote Pay That Nobody Talks About Until It Bites You

Picture this: your HR team spent the better part of a quarter building clean salary bands for every role in the company. The spreadsheet finally makes sense. Midpoints are anchored to BLS data, ranges are defensible, the hiring managers stop arguing. Then a senior engineer in Denver accepts an offer — and six weeks later, you're onboarding a second engineer doing identical work from rural Mississippi. Same level. Same job description. Suddenly the "band" is doing nothing, because it was built for one metro area that neither person lives in.

This is the specific problem remote work creates for compensation structure. The traditional band model assumes that everyone in a given role is drawing from a roughly equivalent labor market. Once your team is geographically distributed, that assumption fails. A band anchored to San Francisco wages overpays someone in Chattanooga and may underpay someone who would otherwise have taken a job at a San Jose tech firm.

There is no single right answer — but there are three workable models, and the right one depends on your company's values, growth stage, and tolerance for administrative complexity. This article lays out all three, the trade-offs each one carries, and the decision criteria that should guide your choice.

Why Geography Matters in Compensation (and Why It Is Getting More Complicated)

Wages vary substantially by geography because labor markets are local. A software developer in the New York metro competes for jobs against New York employers; a developer in rural Indiana competes against a narrower, lower-cost market. Those competitive dynamics produce real wage differences — not arbitrary ones.

The BLS Occupational Employment and Wage Statistics (OEWS) program captures this precisely. It produces wage estimates for roughly 830 occupations across approximately 530 metro and nonmetro areas, drawn from a sample of about 1.1 million establishments. When you look at a role's national median alongside its metro-area medians, you often find a wide spread — enough to matter materially to a compensation decision. The BLS OEWS benchmarking guide walks through how to read those tables and pull the right geographic cut for your benchmarking.

What makes this complicated in a remote context is that you can no longer define "the labor market for this role" by your office's zip code. Your remote employee in Boise is not competing only against Boise employers — she can apply to any company that hires remotely, including companies headquartered in high-cost markets that pay accordingly. This compresses the geographic spread from the employee's side, even while cost-of-living differences remain real.

The result: companies must choose an explicit philosophy, not just a default. Leaving it implicit is how you end up with ad hoc pay decisions that become pay-equity problems later.

Three Models for Remote Work Pay Bands

Model 1: National Band

A national band uses a single salary range for each job level, anchored to a national benchmark — typically the national median from OEWS or a comparable survey source — and sized with enough spread to accommodate geographic variation within the range. For context, the all-occupation annual mean wage in the May 2025 OEWS release was $69,770; national benchmarks for specific roles will differ, but that figure illustrates how the national data point sits across a wide population.

How it works in practice. You build one band per level. Everyone, regardless of location, is placed within that band. A candidate in a high-cost metro may be hired closer to the maximum; a candidate in a lower-cost area may be hired toward the minimum or midpoint. The band itself does not move by geography, but managers retain discretion to position offers within it based on experience, market competitiveness, and internal equity.

Best suited for. Companies that are fully or predominantly remote from founding, with a values commitment to equal pay for equal work regardless of location. Also works well for smaller teams where the administrative overhead of multiple geo zones is not justified.

Trade-offs. A wide national band requires you to be thoughtful about band spread and range width — a band wide enough to span New York and rural Alabama may be so wide that it loses its compression function and tells candidates and managers almost nothing. You also accept that people at the top of the band in low-cost markets will be paid above local competitive rates, which may become difficult to sustain.

---

Model 2: Geographic Pay Zones

Geo zones divide the country (or a country plus Canada) into two to four tiers based on labor-market cost levels. Each job level then has a distinct salary band per zone — or, more commonly, a national midpoint that is adjusted up or down by a zone multiplier.

A simple illustrative structure might look like this:

Worked example (illustrative). Suppose your benchmarking produces a national midpoint of $80,000 for a mid-level operations analyst. You assign three zones based on BLS metro cost clusters: Zone A (high-cost metros, e.g. New York, San Francisco, Seattle) at 115% of national midpoint → $92,000 midpoint; Zone B (mid-cost metros) at 100% → $80,000; Zone C (nonmetro and lower-cost areas) at 85% → $68,000. Each zone still has its own min and max built from your chosen band spread. These zone multipliers are illustrative; your actual multipliers should be derived from comparative OEWS or survey data for the roles you hire.

Best suited for. Distributed-first companies that do hire across a wide cost spectrum and want bands to remain meaningfully competitive at the local level. Also useful when operating in Canada — Ontario and British Columbia have distinct wage profiles from US markets, and treating them as a separate zone or set of zones is more defensible than folding them into a US national band.

Trade-offs. Geo zones require more data infrastructure: you need defensible zone definitions, a process for assigning new hires to the correct zone, and a plan for what happens when someone moves. The data work to keep zones current is not trivial — the national vs. metro wage data guide covers the mechanics of building and maintaining those comparisons. Zone models also introduce a new category of internal equity question: two people doing the same job in different zones are explicitly paid differently, which requires a clear, documented rationale employees can understand.

---

Model 3: Single-Rate (Market-Agnostic) Pay

A small but growing number of companies — typically those with a strong egalitarian culture or those operating at a relatively small scale — set a single rate or a very narrow band per level, applied uniformly regardless of location. This is distinct from a national band in that the range is intentionally tight; the company is essentially saying "this is what this work is worth to us, full stop."

Best suited for. Mission-driven organizations (nonprofits, early-stage startups with a specific culture commitment) where the egalitarian signal outweighs the competitive cost. Works best when the total compensation package includes non-cash elements — equity, mission, flexibility — that offset below-market cash in high-cost markets.

Trade-offs. Sourcing talent in high-cost metros becomes significantly harder unless the non-cash package is genuinely compelling. The model is also fragile: if even one exception gets made ("we had to pay more to close the New York hire"), you effectively have an informal geo-zone model with no documentation, which is worse than an explicit one.

How to Choose: Four Questions to Answer First

Before selecting a model, your team should be able to answer these questions clearly. If you cannot, that is a signal that your compensation philosophy needs to be written down before your band structure is built — sequence matters.

1. What is our stated position on location-based pay? Is equal pay for equal work a core value, or is competitive pay at each location the priority? Both are defensible; mixing them without a policy is not.

2. What is our actual geographic distribution, and where are we likely to hire in the next two years? If 90% of your team is in two metros and a few rural outliers, a simple two-zone or national model is probably sufficient. If you are genuinely distributed across the full US cost spectrum and growing into Canada, zones earn their complexity.

3. What happens when someone moves? This is the question most companies defer and then scramble on. Geo-zone and national models handle relocation very differently. Document the policy before the first employee relocates, not after.

4. Do we have the data infrastructure to maintain this model? A three-zone model you cannot keep current with real wage data degrades quickly into something less useful than a single national band you actually maintain. The job band structure complete guide covers the maintenance cycle you should plan for.

Building the Band: The Data Mechanics

Whichever model you choose, the construction process for each band follows the same logic. You anchor on a benchmark midpoint — OEWS national or metro, or a comparable survey source — then build min and max from a chosen spread. The spread decision is covered in detail in the band spread and range width guide, but as a reference point: narrower spreads (20–30% from min to max) suit roles with a tighter proficiency range; wider spreads (40–60%) suit roles where experience and skill variation within a level is broad.

For geo-zone models, the cleanest approach is to maintain one master midpoint per role per level, then apply zone multipliers derived from comparative OEWS metro data. This means you only update one number per role when market data shifts — the zone multipliers stay stable unless you have a reason to recalibrate them. It is a more maintainable architecture than managing fully independent bands per zone.

Documenting and Communicating the Model

Whatever remote pay band model your company adopts, it needs to be documented explicitly — not in a spreadsheet comment, but in a compensation policy that hiring managers, HR generalists, and (in pay-transparency contexts) employees and candidates can consult. As pay transparency laws expand — 17 states and multiple municipalities have active requirements as of 2026, affecting an estimated 65% of U.S. employers — the ability to produce a defensible, internally consistent salary range on demand is increasingly a compliance requirement, not just a nice-to-have.

If your remote pay model lives only in institutional memory, it will produce inconsistent offers, inequitable outcomes, and a documentation gap that is difficult to defend under a pay-transparency audit.

That documentation is also a talent signal. When candidates ask how pay is determined for remote roles — and more of them are asking, specifically — a company that can answer clearly has a meaningful advantage over one that cannot.

Next Step: Get the Framework Before You Build the Bands

The specific model you choose for remote work pay bands matters less than having a documented, consistently applied one. Start with your compensation philosophy, select a model that fits your team's actual geography and values, anchor to real wage data, and document the policy before the first exception forces your hand.

If you want a practical framework for all of this delivered to your inbox — including templates, worked examples, and updates as pay transparency requirements evolve — subscribe to the Job Band Builder newsletter below. ```