Clarify Facts Before Changing a Role’s Responsibilities

A manager rarely walks in asking for a job redesign. They ask for something smaller sounding, "can we just add this to their role," or "they're already doing half of this anyway." That framing feels efficient, but it skips the step that protects everyone involved, a clear look at the actual work. As an HR business partner, your job in that first conversation is to slow the request down long enough to gather facts, not to approve or reject a title change on the spot.

Why this conversation goes wrong

Managers describe role change requests in terms of relief or reward, not evidence. A team is overloaded, so expanding one person's scope feels like the fastest fix. An employee has been reliable, so widening their title feels like a fair way to recognize them. Both instincts are reasonable, but neither one tells you what the job actually requires now. If you accept the manager's framing at face value, you end up building a job description, a pay grade, and an approval chain around a story instead of around the work. Later, when compensation or legal reviews the change, the gaps show up, the manager feels blindsided, and the employee feels misled by a promise that never should have been made in the first place.

How to prepare

Before you sit down with the manager, decide what facts you need and what you can supply once the conversation starts. You need to know what work has changed, how often it happens, who owns it right now, and what decision authority it carries. You also need to know what work would leave the role if new work gets added, because scope rarely just grows in these conversations, it usually needs to shift somewhere else too. Ask the manager to bring five recent examples of the work in question, each with the task, how often it occurs, the decision made, the current owner, and what happens if the work is delayed. That request does two things. It gives you real material to review, and it shows the manager, gently, that a title change is not a paperwork formality you can approve on a whim.

What to say

Manager Owen opened with a request that sounded settled. "I want Casey's coordinator role to include vendor approvals. Casey already handles the emails." Priya, the HR partner, did not accept or reject the premise. They asked, "What approval decisions is Casey making right now." Owen said, "Casey gathers the quotes and tells the vendors which option I prefer." Priya replied, "That's coordination work, not approval authority. Let's map the actual approvals, the spend involved, and who signs off on them today before we talk about changing the role." Owen pushed back a little, "I need relief before the busy season starts." Priya did not dismiss the urgency and said, "We can look at temporary coverage and the workload forecast in parallel, while the role change request goes through the normal review. That way you get help now without a decision made on partial information."

Notice what Priya did not do. Priya did not tell Owen the idea was wrong, and did not promise the title change would happen. Priya separated the two problems, the short term staffing pressure and the longer term question of whether Casey's job should formally include approval authority. Priya also gave Owen a next step instead of a flat no, the work map, a review with Owen's own leader, and a parallel path for coverage.

Mistakes to avoid

The most common mistake is accepting the manager's summary of the work instead of asking for examples. A claim like "Casey basically approves vendors already" is not a fact, and it needs to be tested against real instances from recent weeks. A second mistake is letting urgency compress the review. A busy season is real pressure, but it is a staffing problem, and staffing problems have their own solutions, temporary coverage, delegation, or a short term backfill. Folding that pressure into a permanent role change skips the compensation and approval review the change actually needs. A third mistake is implying an outcome before the people who own job and pay review have looked at the evidence. Saying something sounds like it should work in the first conversation puts the manager and the employee in a position where a later no feels like a broken promise. Stay specific about what you can confirm and what still needs review.

A fourth mistake, easy to miss, is treating the role change request as a single clean fact when it might actually rest on something the manager heard rather than something the manager saw directly. If Owen's sense that Casey is already approving vendors came from a comment someone else made, rather than from something Owen observed directly, that is worth separating out before it becomes part of the record. The same care applies when you Document a Report That Contains Secondhand Informationmark what the manager observed directly and what they were told, so the review is not built on a rumor treated as a fact.

How to practice and score it

This conversation is hard to get right the first time you have it live, because the manager's urgency is real and your job is to slow things down without sounding like you are blocking them. Rehearsing it first helps you find the calm, specific version of your own questions before you need them in the room. Practice asking for the five work examples without sounding like you are demanding proof. Practice the line that separates urgent staffing relief from a permanent role change, because managers hear that distinction better when it comes with an offer of help, not just a delay. Score yourself on whether you asked for frequency and decision authority before discussing outcomes, whether you avoided promising a result, and whether you gave the manager a concrete next step instead of leaving the conversation open ended.

DealSpeak's HR and Leadership practice conversations let you run this exact scenario against an AI manager who pushes back the way Owen did, so you can practice holding the line on facts before you are doing it with someone whose team is genuinely stretched thin. The scoring points out where you accepted a claim without asking for evidence, where you promised more than you could confirm, and where you skipped the parallel offer of short term help. A related scenario worth practicing alongside this one is how to Document a Request for a Scheduling Practice Exceptionsince both conversations depend on the same skill, separating what someone wants from what the facts actually support.

Close

A role change built on facts protects the manager, the employee, and the review process that comes after your conversation ends. Ask for the work map, keep the urgent staffing question separate from the permanent one, and let the designated reviewers make the call on job and pay. Getting this order right the first time saves everyone a harder conversation later.