What is job restructuring and how to do it?

Job restructuring is changing what a job contains: which tasks sit inside it, which duties move out, who it reports to, and what a person needs to be good at to do it well. The role survives. The work inside it changes.

That distinction is where most of the confusion starts. People hear "restructuring" and think job cuts. Sometimes it ends there. Often it doesn't.

TL;DR

• Job restructuring changes the contents of a role, not the headcount. Downsizing and redundancy remove people; restructuring moves work around.
• In the US the term also carries a legal meaning. Redistributing the marginal parts of a job is one of the named reasonable accommodations under the Americans with Disabilities Act.
• Run it in five steps: map the work that really happens, design the target role, consult the people in it, match people to the new role on evidence, then review after 90 days.
• The step teams skip is the last one that matters: re-checking who actually fits. A restructured job is a new job, so yesterday's read on who can do it is stale.
• Employers expect 39% of workers' core skills to change by 2030, so the roles you write today are already drifting. Restructuring is maintenance, not an emergency.

What is job restructuring?

Job restructuring is the deliberate redesign of an existing role: adding tasks, removing them, shifting reporting lines, or changing how and when the work gets done. It targets the job, not the person. Done well, the role comes out clearer and better matched to what the business now needs.

Job restructuring meaning, in plain terms

Think of a job as a container. Over time people drop things into it. A support lead picks up billing questions because they sat near finance. A designer inherits the website because nobody else would. Two years on, the container holds a job nobody designed and nobody would hire for.

Restructuring empties the container, sorts what is in it, and decides what belongs. Some tasks go back to the team that owns them. Some get automated away. Some get promoted into the core of the role. What is left is a job you could write a real job description for.

Horizontal and vertical restructuring

Two shapes come up over and over. Horizontal restructuring widens a role at the same level. Vertical restructuring raises it. Same tool, different intent, and they carry different pay and risk consequences.

The horizontal version is the one that quietly goes wrong. Adding 20% more work to a role and calling it growth is a pay cut with extra steps, and people notice within a quarter.

Job restructuring vs downsizing and redundancy

These get used as if they mean the same thing. They don't, and mixing them up in an announcement is how a routine redesign turns into a panic.

A restructure can lead to redundancies. It does not have to, and treating the two as one thing is how you lose people who were never at risk. If cuts are genuinely on the table, say so plainly and run the workforce reduction process properly instead of hiding it inside a redesign.

Why do companies restructure jobs?

Three pressures account for most of it: the work changed, the org chart stopped matching the work, or the law requires an adjustment for a specific person. The first two are business decisions. The third is an obligation, and it runs on different rules.

Business reasons to restructure a job

New tools absorb tasks. A team doubles and the generalist role that worked at 12 people breaks at 40. A product line closes and three roles are suddenly half empty. None of that is failure. It is what happens when a company keeps moving and job descriptions don't.

There is also the retention case, which gets underrated. A role with no room in it is a resignation on a delay. Widening a job, or building a step up inside it, is cheaper than backfilling, and it gives career development something concrete to point at.

What restructuring work looks like in practice

Skills are the clock everyone is watching. The World Economic Forum's Future of Jobs Report 2025 found that employers expect 39% of workers' core skills to change by 2030. That is down from 44% in the 2023 edition, and over the same period the share of workers completing training as part of a long-term plan rose from 41% to 50%.

Read that as a maintenance schedule rather than a warning. If roughly two fifths of what a role demands turns over within five years, a job description written once and filed is wrong long before anyone reopens it. The teams that handle this well treat role design as something they revisit on a cycle, the way they revisit budgets. The ones that don't end up with a skills mismatch they have to fix under pressure.

Is job restructuring a reasonable accommodation?

Yes. Under the Americans with Disabilities Act, job restructuring is one of the named forms of reasonable accommodation an employer may need to provide to a qualified employee with a disability. In that context it means redistributing duties or changing when and how the job is done, not redesigning the role for business reasons.

This is the half of the topic most articles drop, and it is the half with legal consequences. The business version of restructuring is discretionary. The accommodation version can be required.

Essential functions versus marginal functions

The line that decides most cases is the split between essential and marginal duties. Essential functions are the reason the job exists. Marginal ones are the extras that happen to sit in it.

The EEOC's enforcement guidance on reasonable accommodation sets the rule out clearly: an employer may need to restructure a position by redistributing marginal functions a person cannot perform because of a disability, and may swap marginal duties between two employees to make that work. An employer never has to reallocate an essential function, though it can choose to. The Job Accommodation Network, funded by the US Department of Labor, draws the same line.

So the practical first move in an accommodation case is not a redesign. It is an honest audit of which duties are genuinely essential. Plenty of things that live in a job description turn out to be habits.

Pro tip: write down which duties are essential BEFORE anyone requests an accommodation or a restructure. Deciding what was essential after a request has landed looks like a decision built to reach an answer, and it reads that way to a regulator too.

Workplace restructuring guide: the 5 steps

Here is the sequence that holds up in practice. It works for a single role or for a whole team, and the order matters more than the paperwork.

Step 1: Map the work that actually gets done

Not the job description. The work. Ask the people in the role to list what they did last month and how long each thing took. You will find duties nobody assigned, duties nobody needs, and one person quietly holding a process together.

This is unglamorous and it is the step that decides whether the rest is real. A restructure designed from out-of-date documents just moves fiction around.

Step 2: Design the target role on paper

Write the role you need, not the role you have. List the outcomes it owns, the duties that deliver them, and the competencies those duties demand. Mark each competency as required at hire or trainable within 90 days. That single mark is what later tells you whether to redeploy someone or recruit.

Step 3: Consult the people in the role

Talk to them before the design is locked, and mean it. Two reasons. They know which duties are load-bearing, and you will be wrong about at least one. And in many jurisdictions, consultation before a change to terms is a legal step, not a courtesy. In the UK, collective consultation rules require it to start at least 30 days before any dismissal when 20 to 99 roles are affected, and 45 days at 100 or more.

Tell people plainly whether jobs are at risk. Vagueness reads as bad news, so ambiguity costs you the people you were trying to keep.

Step 4: Match the new role to evidence, not tenure

Here is the part almost everyone gets wrong. The role changed, so the question of who fits it changed too, and the answer from before the redesign no longer applies. Teams still default to whoever held the old job longest.

The Testlify Competency-to-Evidence Matrix is built for this. It maps a role to the competencies that matter, then connects each competency to measurable evidence through assessments, simulations, interviews, references and structured reviewer feedback. Applied to a restructure, it turns a redesigned job description into a short list of things you can actually check, so redeployment decisions rest on what people can demonstrate rather than on who has been there longest.

Say a 200-person agency merges two coordinator roles into one that now owns client reporting. Three people want it. A structured assessment of the two new competencies (data handling and client communication) takes each of them under an hour, and the decision stops being a popularity contest. The two who miss get a named gap and a training plan instead of a shrug.

Step 5: Review after 90 days

Put the date in the calendar during step 2, before anyone is invested in the redesign being right. Check three things: is the new workload real, did the duties you moved out actually land somewhere, and are the people in the role still there.

What goes wrong in a job restructure?

Most failures are not design failures. They are communication failures wearing a design costume.

How to restructure a role at work without losing people

Say what is happening, when, and what it means for the person in front of you. Then say what you don't know yet. People handle uncertainty far better than they handle the sense that something is being withheld.

Watch the workload arithmetic too. If you move four duties out of a role and five in, that is not a redesign, that is a bigger job. Either the extra work gets resourced or it gets dropped on purpose. Pretending neither happened is how employee wellbeing programs end up treating a problem the org chart created.

And pay attention to who is absorbing the leftovers. In most restructures there is one person, usually the most capable one, who quietly picks up whatever fell between the new roles. That person is your flight risk.

When to restructure a job instead of cutting it

Restructure when the work still exists but sits in the wrong shape. Cut when the work itself is gone. That is the whole test, and it is worth applying honestly, because a restructure used as cover for a cut is both worse for morale and, in a lot of places, legally riskier than the cut done openly.

The other case for restructuring is cost. Reshaping a role and retraining the person in it is usually cheaper than an exit plus a hire, and it keeps the institutional knowledge that takes 18 months to rebuild.

How do you know the restructure worked?

Decide the measures before you start, because afterwards everyone grades on a curve. Four hold up well.

1. Duty coverage. Every duty from step 1 sits in exactly one role. Orphaned tasks are the most common residue of a rushed redesign.
2. Time to competence. How long until people in the new role hit the benchmark you set in step 2. If it runs past 90 days, the role was designed beyond what the training supports.
3. Retention in the affected group. Track it against the rest of the company for two quarters, not two weeks. Restructure-driven exits show up late.
4. Manager load. If spans of control moved, check whether managers now carry more reports than they can support. Restructures quietly create 12-report managers all the time.

None of these need a new system to track. A spreadsheet and a calendar reminder cover it, and a measure you actually check beats a dashboard you don't.

Hire for the restructured role with evidence

Once a role changes, the old shortlist logic stops working. Testlify helps you define what the new role demands and test for it directly, with role-based and custom assessments, work simulations, weighted scoring and structured reviewer feedback, so redeployment and hiring decisions rest on demonstrated skill. Book a demo and see how it maps to a role you are redesigning right now.

Key takeaways

• Restructuring is about the job, not the headcount. Downsizing and redundancy remove people; restructuring changes what a role contains. Saying which one you are doing, in the first sentence of the announcement, prevents most of the damage that follows a vague memo.
• The ADA version runs on different rules. Redistributing marginal duties can be a required reasonable accommodation, while essential functions never have to be reallocated. That means knowing which of your duties are genuinely essential is a compliance task, not an HR nicety, and it has to be settled before a request arrives.
• Skills turn over faster than job descriptions. With 39% of core skills expected to change by 2030, a role written once and filed is wrong within a couple of years. Put role review on a cycle so restructuring is routine maintenance instead of a crisis response.
• Consult before the design is locked. The people doing the work know which duties are load-bearing, and in many jurisdictions consultation is a legal step with real notice periods. Late consultation costs you both accuracy and trust, and you cannot buy either back afterwards.
• Re-test fit after the role changes. A restructured job is a new job, so seniority in the old one proves little. Deciding redeployment on measurable evidence protects the decision if it is ever challenged and gives the people who miss out a real gap to close.
• Watch the quiet absorber. Every restructure leaves duties that fell between roles, and the most capable person on the team usually picks them up without being asked. Find that person in the 90-day review, because they are the exit you will not see coming.

FAQs