A new CHRO's first 90 days on comp in the GCC

A new CHRO walking into a Gulf employer inherits a compensation structure built by someone else, on assumptions nobody wrote down, priced against data of unknown age. The instinct is to fix everything in the first month. The better move is a sequence: audit first, benchmark second, take a position to the board third. Ninety days, in that order.

Days 1 to 30: audit what exists

Before touching a single number, find out what is actually there. Pull every current pay band, however informal, and note when each one was last set and against what evidence. Most organisations discover in this step that "the band" for a given role is actually three different numbers living in three different systems, none of them dated.

Map the seniority ladder the organisation is currently using against titles, not levels, since Gulf title inflation means the two rarely line up. This audit alone usually surfaces the first real problem: roles priced years apart in market terms sitting on the same nominal band because nobody re-checked the level mapping when the market moved.

Note which bands, if any, carry a source count or a citation. A band with no stated evidence is not wrong by default, but it cannot be defended if questioned, and that is a fact worth establishing in month one rather than discovering during a board meeting.

Days 31 to 60: benchmark the gaps and find the outliers

With the audit complete, benchmark every role against current, source-counted market data, not the numbers the previous structure was built on. This step routinely finds two categories of problem: roles priced meaningfully below market, which are retention risk with a number attached, and roles priced meaningfully above it, which are either a deliberate strategic premium or a legacy overpay nobody has revisited.

Rank the gaps by risk, not by size. A role five percent below market with no succession plan behind it is a higher priority than a role fifteen percent below market with three people internally ready to step into it. The benchmarking step produces the list; judgment decides the order.

This is also the point to check whether the organisation needs a track split anywhere in its structure, the same question that governs how a sector's bands should be built in the first place: if two roles at the same nominal level have genuinely different peer sets, one ladder will misprice one of them no matter how carefully it is built.

Days 61 to 90: take the board a defensible position

By day 90, the deliverable is not a finished comp overhaul. It is a defensible position: here is what we found, here is where the highest-risk gaps sit, here is the evidence behind each figure, and here is the proposed sequence for closing them. A new CHRO who tries to fix every band before the first board update loses the credibility that comes from showing disciplined, evidence-led work in the first quarter.

The three questions a board will ask, and the data that answers each

"How do we know this number is right?" Answered by the source count and refresh date behind the figure, not by a general appeal to "market data." If the audit in days 1 to 30 found ungrounded bands, this is the moment to say so plainly rather than paper over the gap.

"Why this role and not another?" Answered by the risk ranking from days 31 to 60. A board wants to see that the priority list follows a method, sources and percentile position first, urgency second, not whichever manager pushed hardest.

"What does fixing this cost?" Answered by modelling the closure cost against the actual roster, the same discipline that governs the October budget-modelling stage of the annual review cycle. A rough estimate here undermines the credibility built in the first two answers.

What derails the 90 days

The most common failure is skipping straight to benchmarking without finishing the audit, because benchmarking feels like progress and auditing feels like paperwork. The result is a set of gap figures measured against internal bands that were never actually grounded in anything, which produces a confident-looking number built on an ungrounded starting point. The audit is slow on purpose; it is what makes everything built on top of it defensible.

The second failure is bringing the board a list of problems with no sequence attached. A board response to "here are fourteen underpaid roles" is "fix them all now," which is rarely fundable and never well-prioritised. A ranked sequence, tied to risk and evidence, is what turns a long list into an approvable plan.

Building this into the annual cycle

The 90-day plan above is a one-time audit, but the questions it answers recur every year. The GCC comp-review calendar turns the same audit-benchmark-defend sequence into an annual rhythm rather than a one-off project. For the board-facing step specifically, comp committee prep walks through building the same evidence-backed report the dashboard automates.

If you are 90 days into a new comp mandate and want to see how the current market data lines up against your existing bands, book a demo and we will run it against your actual sectors and levels.