How to present salary benchmarks to a steering committee
A benchmark that cannot be explained will fail at steering committee, even when the number is right. Committee members are not checking whether you have a figure. They are checking whether they can defend it to their own stakeholders. The job of the presentation is to make that possible.
Lead with the decision
Open by stating the decision the benchmark supports and the range it justifies. A committee that knows what it is being asked to approve will read the evidence with that question in mind. A table of numbers with no decision attached invites debate about the wrong things.
Show the sources
List where each input came from and when it was captured. Salary guides, rate cards and market observations each carry different weight, so name them. A committee can accept a figure it can trace much more readily than one that arrives with no source.
Show the sample
Give the number of observations behind each figure. If a figure rests on a thin sample, flag it on the page rather than letting it pass as firm. Stating the limits openly tends to build more trust than presenting every number with the same confidence.
Surface the assumptions
Put every adjustment beside the figure it affects, including loadings, allowances and any conversion of period or currency. When the committee asks why a number differs from last year, the answer should already be visible. Hidden assumptions are the most common reason a benchmark is challenged.
Anticipate the challenges
Prepare answers for the questions a sceptical committee is likely to ask: where the data came from, how representative the sample is, and what the benchmark does not cover. Say plainly what falls outside the comparison, such as particular roles, locations or rosters.
A one-page checklist
- The decision and the justified range appear first.
- Each source is named and dated.
- The sample size is shown, and thin figures are flagged.
- Every assumption sits beside the figure it affects.
- The likely challenges and the limits of the benchmark are stated.
RateIndex keeps this audit trail with each benchmark, so the reasoning is ready when the committee asks for it. You can explore the RateIndex workspace to see how it works.