Pay Above the Band for Scope, or Record It as an Exception

Does the Capability Change What the Person Owns?

Start with the ownership question, because the answer decides which instrument you need. If the capability means the role now owns work the requisition did not contain, the job changed. Owning the vendor evaluation, holding the verification step nobody currently holds, reviewing what four other people produce with a model: those are scope, and scope carries a level. Ask comp to re-level the requisition rather than to bless an exception.

The test is what the person will be accountable for on Monday, not what they demonstrated on Thursday.

Plenty of real capability changes nothing about scope. An analyst who drafts three times faster still owns the same three reports and the same sign-off. The work arrives sooner and the accountability is identical, which is a gain for the team and no argument at all for a different level.

Scope is checkable and a skill label is not. Write the two or three sentences naming what this person will own that the posted job description does not. If those sentences will not come, the request is about the candidate rather than about the job, and that is the version that fails on a second reading.

Writing that scope statement before the loop opens is the same exercise one stage earlier, which is a defensible bar for good enough at AI in a specific role. A bar written after a finalist impressed the panel is a description of the finalist.

Why the Market Number Cannot Price One Person

Because both published figures compare adverts, not people. Lightcast's analysis of its job posting database reports that salaries in postings mentioning AI skills run 28% higher than postings that do not, roughly $18,000 more a year ¹. PwC's 2026 Barometer puts the same idea at 62%, and states on the same page that its estimates do not control for education, experience or location ².

The two instruments differ by more than two to one on a similar question, asked of different posting databases.

Neither number describes a person. Both are gaps between two piles of postings, and postings that name AI skills skew senior, urban and toward higher-paying industries before anyone reads the comparison. PwC's own spread shows how far the figure moves with context: the premium runs from 118% in consumer markets to 16% in government and the public sector ².

In 2024, more than half of the postings requesting AI skills were outside IT and computer science ¹.

Postings that ask for AI skills are also a small share of the market. Lightcast reports that 2.5% of all US job postings now mention AI skills, up 55% from the prior year ³.

A figure measured on those adverts is evidence about employer demand. Employer demand is not a price for the person in your final round, and a comp partner who has read the methodology will say so first. Whether the AI skills pay premium is real and would apply to one person takes that figure apart and sets out what it can honestly carry.

The posting-stage version of this question gets answered before anyone applies, and for the whole role: whether the salary band has to move when a posting adds an AI requirement. Your exception sits at the other end of that argument, one person deep into a loop.

Write the Exception the Way a Pay Audit Reads It

An audit reads the reason, not the intention. California's Equal Pay Act, at Labor Code section 1197.5, lets an employer defend a wage differential on a bona fide factor other than sex, such as education, training or experience. The factor holds only where the employer demonstrates that it is not based on or derived from a sex-based differential in compensation, is job related with respect to the position in question, and is consistent with a business necessity ⁴.

Two clauses further down the section are the ones that bite.

The statute requires that each factor relied upon be applied reasonably, and that the factors relied upon account for the entire wage differential ⁴. A reason covering part of a gap fails. So does a reason applied to this hire and not to the next person who met it.

Prior salary, the same section says, shall not justify any disparity in compensation ⁴. Whether a competing offer counts as a bona fide factor is a question for counsel. But a request built on what the candidate currently earns is standing on the one factor California names and rejects.

Other states word this differently, so check the version in force where the person will work.

What goes in the file, at the time of the decision rather than afterwards:

• The scope. What this person will own that the posted description does not name.
• The factor. Training, experience or demonstrated capability, written as the job-related thing it buys.
• The size. Which part of the differential each factor accounts for, so the whole gap is covered rather than gestured at.
• The term. The date the exception is reviewed, and what happens on that date.
• The comparison. The last offers approved on this requisition, and what is different about this one.

The last line is the one people skip and the first one an analysis starts from.

Keep One Rule Across Every Offer on the Requisition

A pay-equity analysis reads patterns, and a pattern is assembled out of decisions nobody thought of as one. Five exceptions granted one at a time, each defensible in its own memo, become a distribution when somebody runs them together two years later.

The individual letter is never the exhibit. The set is.

So the rule gets written before the first exception, and it reaches everyone who negotiates on that requisition. One sentence covers it: above-band offers on this role require a scope statement, a named factor and a review date.

The posted range is part of the record too. California requires an employer with 15 or more employees to include the pay scale in any job posting ⁵. Pay scale, in the same section, means a good faith estimate of the salary or hourly wage range the employer reasonably expects to pay for the position upon hire.

Three consecutive hires above the top of a posted range have retired that range.

A prior question is cheaper than all of this. Which roles actually need AI skills right now is worth settling before any offer goes out. Paying above band for a capability the role does not use creates a differential nobody can tie back to the position.

What to Offer When Comp Refuses the Exception

Offer a re-leveled requisition or terms other than base pay, and ask what the refusal is protecting to decide which. A refusal protecting band integrity across a whole function is a different problem from a refusal protecting this quarter's budget. The first is answered by re-leveling the requisition and accepting the longer approval. The second is answered by moving something that is not base pay.

Non-cash terms carry more weight here than a deck implies. Decision rights, the tooling budget, the reporting line and what this person is allowed to stop are all specifiable in an offer letter.

What to offer when you cannot match the salary sorts the non-cash terms worth what they cost you from the ones that are not.

A candidate holding a competing offer may have days to decide, and an exception routed through two approvals can take weeks. That gap is the argument for going above band on the call and writing none of it down. Employers who skip the paperwork do sometimes get the person, and the pay-equity cost lands years later on somebody else's desk.

Two years later is also when the memo is read. The exception written this week lands in a file somebody opens during a compensation review, or in answer to a charge, with none of this week's urgency attached to it.

Written as a scope change, the exception reads as a level. Written as a premium for a skill, it reads as a preference. The words are cheap now and impossible to add later.

See a sample report >