Jobs change through hundreds of small requests. A capable employee covers a vacancy, becomes the person who knows a system, takes over a weekly report, or handles customer exceptions because the official owner is unavailable. Months later, the extra work remains while the original role description, priorities, authority, and support do not. This is role drift.
Role drift is not automatically harmful. Employees can grow through new work, and operations need reasonable flexibility. The retention risk appears when added responsibilities are invisible, conflicting, unsupported, or treated as temporary long after the emergency ended. A review brings the real job and the approved job back into an honest conversation.
Identify where drift is likely
Start with events that commonly move work: vacancies, reorganizations, new systems, location changes, manager departures, peak periods, and canceled projects. Ask which employees became default owners during those events and whether the handoff ever ended.
Review calendars, task systems, recurring reports, access lists, meeting attendance, and work instructions. These records show what the employee is expected to touch. Use them to guide a conversation, not to monitor every minute. Some responsibilities, especially informal coaching and interruption-heavy support, may not appear in a formal queue.
Invite employees to describe work that was added, work that stopped, decisions they are expected to make, and requests they receive because others believe they own the subject. Managers should make the same inventory independently. Differences between the two lists often reveal unclear expectations.
Compare the real work with approved scope
Place current responsibilities beside the role's approved purpose, reporting relationship, schedule, qualifications, and decision authority. Mark work that fits, work that may fit with clarification, and work that belongs elsewhere. Do not assume an unlisted duty is inappropriate or that every listed duty remains useful.
Look for responsibility without authority. An employee may be expected to coordinate a process but lack access to the source record or permission to resolve exceptions. They become the messenger for delays they cannot control. Either provide authorized support and a clear escalation or move accountability to the person who can decide.
Check for work that requires training, licensing, privacy controls, or another qualification. A history of doing the task does not prove the assignment is safe or permitted. Pause and route questionable work to the appropriate owner.
Calculate the tradeoffs that were never stated
Every added responsibility competes with something. Review missed deadlines, postponed coaching, canceled leave, extended hours, recurring interruptions, and quality problems that appeared after the drift began. Ask what the employee stopped doing to keep up. That answer may differ from what the manager thought was lower priority.
Avoid treating personal endurance as capacity. An employee may maintain output for a period by skipping breaks, working beyond expected hours, or relying on private notes. Those practices hide the true demand and make the process vulnerable during absence.
Consider the effect on coworkers. When one person becomes the informal expert, others may route all difficult work to them and lose chances to learn. The expert receives more interruptions while the team becomes more dependent on a single point of failure.
Decide whether work stops, moves, or becomes official
For each drifted responsibility, choose a disposition. Stop work that no longer supports a current need. Return work to its authorized owner. Distribute routine parts with training and accountable oversight. If the duty genuinely belongs in the role, use the organization's formal process to review scope, expectations, title, classification, or other employment terms as applicable.
Managers should not make promises about compensation, promotion, or status outside their authority. They can document the work, escalate the decision, and give the employee a truthful update date. Leaving the request open without contact repeats the original problem.
State what will leave the employee's old workload if new work remains. Adding a revised description on paper does not create time. Update priorities, measures, meeting expectations, and coverage so the operating system matches the decision.
Restore boundaries with internal customers
People who relied on the informal arrangement need a clear transition. Tell them where requests now go, who decides, and when the old route ends. Do not leave the employee to refuse former requests one conversation at a time.
Update directories, forms, recurring invitations, documentation, and system ownership. Remove access that is no longer needed through the authorized process. A verbal handback will fail if every visible cue still points to the same employee.
Provide a temporary escalation for missed handoffs. The goal is to correct the route without punishing an employee who follows the new boundary. Managers should reinforce the change when stakeholders attempt to restore the old shortcut.
Check whether development was mistaken for drift
Some added work is an intentional development assignment. It should have a purpose, scope, support person, feedback method, and end or review date. The employee should understand that practice does not guarantee promotion and that declining an optional opportunity will be handled according to policy.
If those conditions were never stated, repair them now. Decide whether the assignment will become a structured development step or end. Do not relabel indefinite unpaid rescue work as growth after an employee raises a workload concern.
Development should expand learning without abandoning the employee's current responsibilities. Adjust capacity and ensure the work receives appropriate review. Mistakes made during supervised practice should be handled as part of learning, within safe and authorized boundaries.
Keep drift visible after the review
Add a brief scope check to regular manager conversations, especially after organizational changes. Ask what new work arrived, which responsibility no longer fits, and where authority is unclear. Maintain a small record of material decisions rather than rewriting history.
Review patterns across teams. Repeated drift toward a certain employee or role may show missing process ownership, thin manager coverage, or a system that requires unofficial experts. Addressing that source protects more than the person who first raised the concern.
A role drift review succeeds when employees no longer have to choose between being helpful and protecting a sustainable job. Leaders can still adapt the operation, but they must name the work, make the tradeoff, provide authority and support, and close temporary assignments. Clear roles are not rigid roles. They are roles that change through decisions instead of accumulation.