Location-Based Pay or a Single Rate

Once you hire beyond one city you have to decide whether pay follows the person or the place. Organisations often adopt one without deciding, then discover the consequences.

The two positions

Location-based. Pay reflects the market where the person lives. A role pays differently in a high-cost city than in a small town.

Single rate. One rate for the role regardless of where the person sits.

Each has a coherent logic. Location-based says you buy labour in a market and markets differ. Single rate says you buy the work, and the work is identical.

What location-based costs you

Constant boundary disputes. Which market — where they live, the nearest city, the national average? Someone forty minutes outside an expensive city will argue, reasonably, about which band applies.

Relocation becomes a pay event. An employee moving to a cheaper area faces a cut for doing nothing wrong. Almost nobody accepts this gracefully, and the alternative — freezing their rate — creates two people doing the same job on different terms with an explanation nobody likes.

Data that ages. Market data has to be maintained per location, and it drifts.

A visible fairness problem. Two people on the same call doing the same work on different money is uncomfortable in a way that abstract policy documents do not resolve.

What a single rate costs you

Money, at the top end. You pay the highest-market rate to everyone, or you pay a middle rate and lose candidates in expensive markets.

A distorted applicant pool. A single national rate is generous in low-cost areas and uncompetitive in expensive ones, so applications skew accordingly. That may be fine or may not.

Difficulty adjusting. Moving from single rate to location-based later is nearly impossible without damage.

The middle options

Broad bands. Two or three tiers rather than per-city precision. Fewer boundary arguments, most of the cost control, and simple enough to explain.

Single rate within a country, differentiated across countries. Common and reasonably defensible.

Rate set at hire, held on relocation. Removes the cut-for-moving problem while keeping market sensitivity at the point of hire. Creates drift over time, which you accept knowingly.

Whatever you choose, do these three things

Publish the approach. Not necessarily the numbers, but the method. Undisclosed location adjustment is discovered eventually and reads as something done to people rather than a policy.

Say what happens on relocation before anyone relocates. This is the question that generates the most bad feeling and it is entirely foreseeable.

Be consistent. Exceptions negotiated individually become the actual policy within a year, and the written one becomes a document people know to ignore.

The question underneath

The disagreement is really about what you are paying for.

If you believe you are compensating someone for the cost of living where they are, location-based follows. If you believe you are paying for output, and output does not vary with the rent, a single rate follows.

Most organisations have not articulated which they believe, which is why their policy is inconsistent and their explanations unconvincing.

Pick one, write down the reasoning, and apply it evenly. The specific choice matters less than whether people can see it being applied the same way to everyone.