Skip to main content
Loading...
hr

Handle a Compensation and Raise Dispute

Practice a scheduled 1:1 where an employee presents pay comparisons, cites extra responsibilities, and challenges a no-raise decision. Build a fair response that explains policy, acknowledges frustration, and ends with a clear next step.

Every employee gets a seat — priced per employee in Performance & Learning, quoted with this template ready.

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.

Built for: Technology · Healthcare · Financial services · Retail · Professional services

Overview

This AI roleplay practice scenario helps a manager or HR partner handle a compensation conversation when an employee believes they deserve a raise and is challenging the decision. The situation is specific: during a scheduled 1:1, the employee brings pay comparisons, points to six months of extra responsibilities, and expects a raise in this cycle. The learner must respond without sounding evasive, defensive, or overly personal.

Use this template when you want to practice a fair, policy-based explanation that acknowledges the employee’s frustration and still holds the line on the decision. It is especially useful before review cycles, after promotion or merit decisions, or when a manager needs to explain why a request was not approved. The persona is prepared and persuasive, so the learner has to stay grounded in process, not debate every data point.

Do not use this scenario as a substitute for legal advice or as a script for making compensation decisions. It is not meant for casual praise conversations, general performance feedback, or situations where the employee is raising a complaint about discrimination or retaliation. The value of the template is in the practice rep: read the situation, start the roleplay, respond to the persona, complete the scored attempt, and retry until the explanation is clear, respectful, and policy-aligned.

How to use this template

  1. Read the situation carefully and note the employee’s stated concerns, the pay comparison angle, and the expectation of a raise in this cycle.
  2. Start the roleplay and open with a calm, direct response that acknowledges the employee’s disappointment before you explain the decision.
  3. Talk to the persona using policy-based language, respond to the comparison data without getting pulled into side-by-side debate, and keep the conversation respectful.
  4. Complete the attempt and review the rubric criteria to see whether you explained the decision clearly, stayed fair, and offered a concrete next step.
  5. Retry the scenario with a tighter explanation, a better acknowledgment, or a more specific development path until the conversation lands cleanly.

Best practices

  • Acknowledge the employee’s disappointment before you explain the compensation decision.
  • Use policy, process, and role expectations as the basis for your answer, not personal preference or vague judgment.
  • Address comparison data directly by explaining why pay decisions are not made from a simple teammate-to-teammate comparison.
  • Name the next step clearly, such as a review timeline, development milestone, or follow-up with HR or the manager.
  • Keep your tone calm and consistent even if the employee becomes more forceful or argumentative.
  • Avoid promising a raise later unless you can tie it to a specific process, date, or documented criterion.
  • If the employee raises extra responsibilities, distinguish between temporary stretch work and a formal change in scope that affects pay.

What this template typically catches

Issues teams running this template most often surface in practice:

Jumps to the compensation explanation before acknowledging the employee’s disappointment.
Relies on personal opinion instead of the organization’s compensation policy or review process.
Gets pulled into a direct comparison of teammates’ pay without explaining the broader decision framework.
Overpromises a future raise or implies approval is likely without a defined process.
Uses vague language like 'we’ll see' or 'keep doing what you’re doing' instead of a concrete next step.
Sounds defensive when the employee challenges the decision with data.
Fails to distinguish between extra responsibilities and a formal role change that would trigger review.

Common use cases

HR Business Partner coaching a manager before review season
An HRBP uses the scenario to help a manager practice explaining a no-raise decision after the employee cites pay comparisons and extra workload. The focus is on staying policy-based and avoiding inconsistent messaging.
Engineering manager handling a merit-cycle dispute
A manager practices a conversation with a senior engineer who believes six months of stretch work should have triggered a raise. The learner has to explain the cycle, the criteria, and the next review path without sounding dismissive.
Retail district leader responding to a pay equity challenge
A district leader rehearses a conversation with a store employee who has compared pay with peers and wants an immediate increase. The scenario helps the leader stay calm, consistent, and clear about what can be reviewed locally versus centrally.
Healthcare supervisor explaining a compensation decision after added duties
A supervisor practices responding to a staff member who has taken on extra responsibilities during a staffing shortage and now expects a raise. The roleplay tests whether the learner can separate temporary coverage from formal compensation changes.

Frequently asked questions

What does this compensation dispute roleplay actually cover?

It covers a scheduled 1:1 where an employee brings pay comparisons, cites added responsibilities, and challenges a raise decision. The learner practices acknowledging the concern, explaining the decision using policy or process, and offering a respectful next step. It is designed for the moment after a compensation review, not for general performance coaching. The goal is a clear, fair conversation the employee can understand even if they disagree.

Who should run this practice scenario?

This template is best run by HR partners, people managers, compensation leaders, or anyone who has to explain pay decisions. It also works for new managers who need a safe rehearsal before a real conversation. The roleplay is especially useful when the learner must stay calm under pressure and avoid sounding defensive. If compensation decisions are centralized, the manager can still use the scenario to practice the explanation they are allowed to give.

How often should teams use a raise-dispute scenario like this?

Use it before annual review cycles, after compensation planning changes, and whenever managers are promoted into people leadership. It is also useful as a refresher before difficult 1:1s if the team has recently had pay compression or promotion delays. Because the scenario is specific, it works well as a short practice rep rather than a long workshop. Repeating it with different temperaments helps managers build consistency.

Does this template help with legal or compliance risk?

Yes, indirectly, because it trains managers to stick to policy, avoid personal judgments, and avoid inconsistent explanations. That matters in pay conversations where fairness, documentation, and consistency are critical. The scenario is not legal advice, but it reinforces good HR practice around compensation communication. It is especially helpful for reducing off-the-cuff statements that can create confusion or perceived inequity.

What are the most common mistakes this roleplay surfaces?

The most common mistakes are jumping straight to the decision without acknowledging disappointment, relying on personal opinion instead of policy, and getting pulled into a teammate-by-teammate comparison debate. Learners also often overpromise a future raise or give a vague 'keep doing what you're doing' answer. Another common issue is failing to leave the employee with a concrete next step. This template makes those gaps visible in the rubric.

Can I customize the pay details, policy language, or employee temperament?

Yes. You can swap in your own compensation cycle, job level language, promotion criteria, and review timing. You can also make the persona more calm, more skeptical, or more assertive depending on the skill level you want to test. If your organization uses a specific compensation philosophy, you can reflect that in the scenario and rubric. The key is to keep the situation concrete and the decision criteria realistic.

How does this compare with an ad-hoc manager script?

An ad-hoc script usually gives a manager talking points, but it does not test whether they can handle pushback in real time. This roleplay creates a live attempt with a persona who reacts to how the learner responds. That makes it better for deliberate practice, because the learner gets immediate feedback on acknowledgment, clarity, and policy alignment. It is more useful than a static checklist when the conversation is emotionally charged.

Can this be integrated into manager training or onboarding?

Yes. It fits well in manager onboarding, compensation training, promotion calibration prep, and HR business partner coaching. It can also be paired with a policy review, a compensation philosophy deck, or a manager guide on what can and cannot be promised. Many teams use it as a pre-work exercise before live roleplay or as a follow-up assessment after training. It works best when learners can retry after feedback.

Go deeper on the topic

Related concepts
  • Human resources (HR) — increasingly called people operations, people ops, or simply "people" — is the organizational function responsible for the systems and...
Related guides

Ready to use this template?

Every employee gets a seat. Request pricing for Performance & Learning and we quote into a workspace with Handle a Compensation and Raise Dispute ready.

Request pricing

Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.