The earliest restructuring decisions are often made before HR is formally involved. A leader redraws a team chart, removes a role or names the person they expect to remain. By the time a process is planned, assumptions may already look like conclusions.
Good preparation creates a safer starting point. It tests the business need while there is still time to consider alternatives and design a fair process.
Write the business case in plain language
Explain the problem the restructure is intended to solve. Is it a cost gap, duplicated work, reduced demand, a new service model or a missing capability? State the evidence and the expected outcome.
Avoid beginning with a preferred organisational chart. Start with the need. This makes it easier to test whether the proposed structure is proportionate and whether another option could achieve the same result with less disruption.
Identify assumptions and alternatives
List the assumptions behind the proposal: expected savings, workload forecasts, required skills, reporting lines and implementation timing. Mark which assumptions are supported by evidence and which still need testing.
Consider alternatives before announcements. These might include vacancy controls, reduced non-staff costs, redeployment, changed hours by agreement, retraining, natural turnover or a phased redesign. Not every option will be viable, but the record should show that realistic alternatives were considered.
Build an accurate people picture
Check job descriptions, actual duties, reporting lines, locations, hours, contractual terms, length of service, current vacancies and temporary arrangements. The organisation chart may not reflect how work is really done.
Look for employees who are absent, on family leave, working remotely or otherwise easy to miss in informal planning. Consider equality impacts and whether proposed criteria could disadvantage a protected group.
Keep access to sensitive information limited to those who need it for the planning process.
Map the process before naming dates
The appropriate process depends on the nature and scale of the proposal. Build a realistic sequence covering governance approval, employee communications, consultation, selection if relevant, consideration of alternatives, decisions, appeals and implementation.
Do not publish a completion date before checking whether statutory or contractual obligations make it unrealistic. If redundancies, contractual changes, transfers or large groups may be affected, obtain specialist advice at the planning stage.
Prepare managers without pre-deciding outcomes
Managers need to understand the rationale and proposed process, but they should not be encouraged to reassure particular people that they are safe or imply that another person will leave.
Give them an agreed holding line for questions and a route for escalating new information. Explain the difference between a proposal and a decision. Ask them to disclose any information that could affect the plan, including current performance processes, grievances, health issues or planned leave.
Plan the first communication carefully
Decide who needs to hear what, in what order and through which channel. Wherever possible, affected employees should hear directly from the organisation before wider announcements.
Prepare a concise written summary that covers the reason for the proposal, what may change, the process, how employees can contribute and where they can find support. Avoid language that suggests the outcome is already final.
Set up a decision log
Record key decisions, evidence considered, alternatives explored and changes made in response to employee input. A clear log supports consistent decision-making and helps the organisation explain its reasoning later.
Restructuring preparation is not about scripting the final answer. It is about creating a process in which the organisation can make a sound decision after listening, testing and considering the evidence.
