Salary survey data and real market signals are often discussed as if they were the same kind of thing — both labelled "market data," both used to inform compensation decisions, both priced in the thousands per seat. They are not the same kind of thing. They answer different questions, with different methodologies, at different latencies.
For a CHRO making compensation decisions, the distinction matters. A survey is a useful reference for understanding sector medians. It is a poor reference for pricing a specific role at a specific company in a specific moment. Real market signals do the second; surveys do the first. Using one for the other is the source of most compensation-data disappointments.
What each one actually is
Salary survey
Aggregated declarations from HR teams at participating companies, collected on a defined cycle (usually annual). Each data point is "what we say we pay for this role." The artefact is a sector-level distribution.
Market signal
A real compensation decision made between a specific company and a specific candidate. The artefact is a transaction: an offer extended, accepted, or rejected, with a specific number attached.
The survey is a snapshot of declared intentions. The signal is a record of decisions made. The two diverge for predictable reasons.
Four ways they diverge
1. Recency. Survey data is collected at a fixed point in the year and published 3–6 months later. By the time a CHRO consults the 2026 survey, the data is from 2025 — and the labour market has moved. Market signals are continuous; the most recent decision is yesterday.
2. Granularity. Survey output is sector-level — "Senior Software Engineer, fintech, Lisbon, 50–250 FTE." The candidate sitting in your funnel is more specific than the bucket the survey provides. The signal can be specific to the role description, the seniority signal, the geography mix. The survey cannot.
3. Participation bias. Survey respondents are HR professionals filling out their own company's data, often estimating across roles they don't personally manage. The accuracy of any individual data point depends on the respondent's familiarity. Signals — recorded as transactions — have no estimation step.
4. What is measured. Surveys typically capture base salary at a point in time. Signals can capture total compensation, including variable pay, equity, and the structure of the offer (sign-on, retention, geography adjustment). The shape of the offer is part of the signal.
When each is useful
This is not a survey-is-bad argument. Surveys are useful for purposes the methodology fits.
Surveys are the right reference for:
- Sector benchmarking. "Where does our company sit in the broader market for this role family?" is a question the aggregation answers well.
- Annual band calibration. The midpoint of a salary band, set once a year, benefits from the breadth and statistical confidence the survey provides.
- Headline comparisons for the board. "Our salaries are at the 60th percentile of the sector survey" is a useful single number for a CFO conversation.
- Internal equity validation across departments where the company has no signal data (e.g., a function with no recent hires).
Signals are the right reference for:
- Pricing a specific offer. The exact candidate, exact role, exact moment is too granular for the survey bucket but well-served by recent transaction data.
- Detecting market movement mid-year. The survey publishes in February; if the market moves in May, the signal sees it first.
- Defending offers under Article 5. The directive requires the offer range to be defined and disclosed before the interview — a recent transaction is more defensible as the reference than a 12-month-old survey median.
- Calibrating per-category compensation under Article 4. The categories of equal work or work of equal value are company-specific; signals operate at that granularity, surveys generally do not.
The latency cost in concrete terms
Consider a 200-person company hiring 30 roles a year. The survey published in February 2026 reports on 2025 transactions. By June 2026, when the company is making its tenth offer of the year, the survey data is approximately 9–12 months old.
If the market for the role has moved 4% year-on-year — typical for technical roles in EU markets in the 2024–2026 window — the survey midpoint is now 4% below the operational reference. An offer constructed from the survey midpoint lands 4% below the market. The company wins fewer offers; the offers it does win compress the existing team less but create different problems (under-the-band positioning of new hires relative to their actual external value).
A live signal would have surfaced the 4% drift in May. The survey would surface it in February of the following year.
The 4% drift example is the central case, not the extreme. In rapidly moving markets (specific technical specialisations, regions with active relocation policies), 12-month survey lag can produce 8–12% mispricing relative to current market. The directive's reporting deadline does not care about this — the report is calculated on reference-year data, internally consistent. But the offers extended between surveys do feel the drift.
Combining the two — when to use each
The practical answer is to use both, at different scales of the decision:
- Annual cycle (band calibration, board reporting): survey data. Statistical confidence and sector breadth.
- Mid-year recalibration (drift detection): signals. Continuous, granular, fast.
- Individual offer construction: signals for the role-specific reference, survey for the broader sector context.
- PTD reporting (Article 9 metrics): internal company data, calibrated against survey for context, validated by signals where available.
The CHRO's job is not to pick one or the other. It is to know which question each is the right answer to.
Why this matters under the directive
Article 5 (transparency at hiring) requires the indicative pay range to be disclosed before the interview. The range must be defensible — observably connected to the role, the cohort, and the market. "We used a survey from 18 months ago" is a weaker defence than "we triangulated against recent offers and the sector survey." The first is acceptable; the second is stronger under scrutiny.
Article 9 (reporting) operates on internal company data; signals and surveys are external references that inform the underlying compensation decisions but do not enter the report directly. The methodology behind the band structure — what references the company uses to set midpoints — is part of what is examined if the report is challenged.
The survey tells you what the market looks like. The signal tells you what the market just did. Different questions, different answers, both useful.
Where the diagnostic starts
Neither surveys nor signals replace the structural inputs the directive's reporting obligation requires: a defined category structure, documented pay-setting methodology, and a clean payroll record. Both are external context; the report runs on internal data.
The ReadinessCheck™ surfaces whether the internal inputs are in place — by axis of the directive's principal obligations. The decision about which external reference to use sits downstream of that.
The market reference matters. The internal structure matters first.
ReadinessCheck™ takes about 20 minutes and requires no salary data. It produces an observational position view of where the company sits on category construction, pay-setting documentation, and the methodology that determines whether the survey or the signal is the right reference for any given decision.
Start the ReadinessCheck →