Building a redeployment-first workforce: cutting redundancies before outplacement is triggered

A practical HRD playbook for standing up internal mobility, skills-based redeployment and honest governance so restructures shrink before they reach the boar…

For most HR directors, the redundancy programme is the visible tip of a much larger workforce planning problem. By the time the paperwork lands, the useful decisions have already been made — or, more often, not made at all. A redeployment-first workforce reverses that sequence. It treats internal mobility, skills visibility and honest governance as the primary intervention, and outplacement as the safety net for the people the organisation genuinely cannot keep.

Why redeployment usually loses the argument

Redeployment is one of those ideas everyone agrees with in principle and quietly under-invests in in practice. The CIPD's 2024 Resourcing and Talent Planning report found that although employers are more likely than ever to talk about internal mobility, the operational plumbing — skills data, hiring manager incentives, redeployment SLAs — rarely catches up with the ambition.

The reasons are familiar. Line managers are rewarded for delivery, not for releasing good people into another team. Recruiters are measured on time-to-fill from the external market, where the pipeline is legible. Finance sees redundancy as a one-off cost and redeployment as an open-ended one. And HR, understandably, defaults to the process it can control: consultation, selection, exit.

The result is that most organisations run an implicit external-first policy. Roles are posted outside before they are seriously offered inside. At-risk employees discover new vacancies from a job board rather than a conversation. And redundancy programmes are sized without ever asking, in earnest, how many of these people we could keep.

A redeployment-first workforce is not a technology project. It is a design choice about where the default sits — inside the organisation, not outside it — and the operating disciplines that make that default enforceable.

The economic case, honestly stated

The case for redeployment is not that it is always cheaper than redundancy. It is that when you count the full stack of costs, redeployment usually wins on any horizon longer than one quarter.

The direct costs of a redundancy are legible: statutory pay, enhanced severance, notice, outplacement, adviser fees, and any settlement risk. What sits underneath is less legible but larger: the recruitment cost of the replacement role you will inevitably open elsewhere in the business within twelve months, the ramp-to-productivity gap while the new hire learns what the leaver already knew, the institutional knowledge that walks out with them, and the productivity drag on the survivors.

McKinsey's work on redeployment and reskilling puts the point plainly: for many exposed roles, the fully loaded cost of replacing a person exceeds the cost of moving and reskilling the person you already have, once recruitment, onboarding and lost knowledge are counted.

What to model, not just what to report

Skills visibility: the foundation you cannot skip

You cannot redeploy people you cannot see. Every serious redeployment programme rests on a working skills inventory — not a perfect one, and not a five-year taxonomy project, but a good-enough live view of who can do what.

Deloitte's ongoing work on the skills-based organisation frames this as a shift from the job as the atomic unit to the skill. In practice, that means capturing skills at three grains: declared (what the employee says they have), demonstrated (what performance and delivery evidence confirms), and adjacent (what they could credibly reach with a defined amount of learning or on-the-job stretch).

The pragmatic starting point is to accept that skills data is a living asset, not a one-off audit. It gets updated when someone completes a project, moves teams, finishes a course, or has a development conversation. It is owned jointly by the employee and their manager, and it is trusted by recruiters. Without that trust loop, the inventory becomes a stale spreadsheet and redeployment defaults back to whoever the hiring manager already knows.

Redeployment SLAs and the mechanics of internal mobility

Once you can see the skills, the mechanics matter. A redeployment-first workforce runs to explicit service levels, not to goodwill.

The four SLAs worth writing down

The point of writing these down is not bureaucratic. It is that redeployment fails in the seams between systems and teams, and the SLAs make the seams visible. When a role sits open for six weeks because no one asked the at-risk pool, that is a failure you can name and fix.

Governance: unions, works councils and the honesty test

Redeployment-first workforces are usually easier, not harder, to explain to employee representatives. The conversation shifts from 'how many are you cutting?' to 'what did you try before you cut?'. That is a better place for both sides to start.

ACAS guidance on collective consultation is explicit that the purpose of consultation is to explore ways to avoid or reduce redundancies. In practice, that means bringing a documented redeployment effort to the table — vacancies mapped, skills adjacencies identified, reskilling options costed — rather than a fait accompli with a helpline attached.

The honesty test is simple. If a union representative asked you today, for a live restructure, to see the list of open vacancies across the group and the skills adjacencies of the at-risk pool, could you produce it inside a week? If not, the redeployment-first workforce is still an aspiration, not an operating model.

Where outplacement sits in a redeployment-first design

Outplacement does not compete with redeployment. It completes it. The people you genuinely cannot keep — because the role is gone, the skills adjacency is too far, or the individual chooses to leave — still deserve a serious, well-resourced transition. Cutting outplacement to fund internal mobility is a false economy and, in most jurisdictions, a reputational one.

Inside the ImaginativeHR ecosystem, the outplacement layer is designed to sit under the redeployment layer rather than around it. Group and Core programmes cover volume transitions; Complete extends the coaching bench for more complex cases; Executive Transition handles the senior population. The Launchpad platform provides the digital continuity — CV work, coaching cadence, market intelligence — so that whether someone lands internally or externally, the support is consistent.

For HRDs, that separation matters. It means the redeployment decision can be made on its merits, without the political pressure of protecting a fixed outplacement budget, and the transition support can be sized to what the leaving population actually needs rather than what is left in the pot.

A ninety-day starting programme

You do not need a two-year transformation to be measurably more redeployment-first than you are today. A ninety-day programme, run with genuine executive backing, moves the needle in most organisations.

Weeks 1-4: make the current state visible

Weeks 5-8: install the minimum mechanics

Weeks 9-12: prove it on one restructure

Ninety days will not fix the operating model. It will produce a defensible baseline, a working example, and the political capital to fund the longer programme.

What the board should be asking

A board that only sees redundancy volumes is looking at the wrong end of the pipe. The right questions for the people committee or remuneration committee are upstream.

None of these questions are hard to ask. All of them are hard to answer without the operating model to back them up. That gap, in most organisations, is where the redeployment-first workforce quietly lives — or dies.