Ask anyone who has run a pay review in St Helier or St Peter Port with a UK salary survey on the desk: the numbers never quite fit. Roles that are scarce on an island of a hundred thousand people are plentiful in Manchester. A trust officer, a fund administrator or a compliance MLRO has no meaningful equivalent in most UK datasets at all. And a survey published once a year describes a market that has already moved on by the time you read it.
Small markets behave differently
The Channel Islands and the Isle of Man are not small versions of the UK market. They are distinct markets with their own gravity:
- Sector mix. Financial and professional services carry a far larger share of employment than in the UK, and the roles inside them are island-specific. Job titles map badly across the water.
- Scarcity premiums. When there are a handful of qualified people on the island for a specialist role, local supply and demand set the price, not national averages.
- Housing and licensing. Residency and work-licence regimes shape who can be hired locally and what it takes to bring someone in. That pressure shows up in pay, and only in local data.
- Three jurisdictions, three markets. Jersey, Guernsey and the Isle of Man are close neighbours and yet price the same role differently. An employer operating across two or three of them needs to see each one, not a blended average.
Stretch a UK dataset over that landscape and the errors compound quietly. You match a role to the nearest UK title, take the regional weighting on faith, and present a number to the board that nobody can actually defend.
What a local benchmark has to get right
Being local is necessary, but it is not sufficient. For a benchmark to be something a People team can stand behind, a few things have to be true:
The data has to come from the market it describes. PayPulse benchmarks are built from organisations operating in Jersey, Guernsey and the Isle of Man, not extrapolated from elsewhere. When you see a percentile, it is a percentile of this market.
Roles have to be matched like for like. Job titles are unreliable, especially here. PayPulse matches roles by family and level, with AI doing the heavy lifting of reading a job description and placing it correctly, so a comparison means what it appears to mean.
It has to show the distribution, not the average. An average hides exactly the thing you need to see: where a role sits in the spread. The useful question is not "what is the average salary" but "we pay at P40, the market hires at P55, and we are losing people".
It has to stay current. Contributions refresh the pool periodically, so the picture sharpens as the market moves rather than ageing between annual print runs.
The confidence this buys you
The point of a benchmark is not the chart. It is the conversation the chart lets you have: with a candidate who wants more than the band, with a manager lobbying for their team, with a board that wants to know the pay bill is competitive but not extravagant. Local data, matched properly and kept current, turns those conversations from opinion into evidence.
That is what we are building PayPulse to do, for the islands, from the islands.