Redundancy, restructure and job redesign: documentation and consultation

Restructures, redundancies and role redesigns are related but distinct. A restructure changes how work is organised; a redundancy is the consequence for a role that is no longer required; a role redesign changes the duties of a role that continues to exist. Treating them as the same process produces confusion and risk; treating them as related stages of the same program produces coherence.

The starting point is clarity about what is actually being done. Decisions about consultation, redeployment, communication and documentation flow from that clarity.

A documented business case — the operational drivers, the options considered, the financial position and the workforce impact — is the foundation for everything that follows. It is the record that supports the consultation conversation, the redeployment assessment and the eventual decision.

Decision frameworks should be defined before the program begins. Who decides what, on what evidence, with what approval — these questions are far harder to answer once the program is underway.

Consultation obligations vary by instrument and by topic, but the underlying expectation is consistent: consultation should occur at a point where input can genuinely influence the outcome, with the people who will be affected, in a way that allows feedback to be considered.

Consultation that is performative rather than genuine is a common source of dispute. The discipline of documenting what was consulted on, when, with whom and how feedback was considered is the most reliable way to demonstrate the substance of the process.

Redeployment assessment should be active and evidenced. The roles considered, the criteria for suitability, the assessment against those criteria and the outcome for each affected employee should be recorded. Where redeployment is not available, the reasoning for that conclusion should be documented.

Suitable alternative role analysis should include consideration of part-time, hybrid and modified arrangements as well as direct redeployment.

Role redesign should consider workload, classification, support arrangements and the controls needed for any new psychosocial hazards the new role configuration creates. Communications should follow a planned sequence — leaders, managers, affected employees, the broader workforce — with calibrated messaging at each stage.

A short post-implementation review captures what worked, what did not and what should be done differently next time. This is the most reliable way to build organisational capability for change programs over time.

Consultation timing is one of the most consistent sources of dispute. Consultation that begins after the operational decision is settled is treated as performative; consultation that begins so early there is nothing concrete to discuss frustrates participants. The workable middle is consultation that begins when the proposal is sufficiently developed to be discussed meaningfully but before it is sufficiently developed to be unchangeable.

Sequencing also matters. Affected employees should hear from the organisation directly before they hear from colleagues, customers or media. Where this sequencing is not protected, trust in the program — and in subsequent change programs — is materially damaged in ways that take far longer to repair than the time saved by short-cutting the sequence.

Redeployment review should be active. Rather than waiting to see whether affected employees identify suitable roles themselves, the process should produce a documented assessment of the roles available, the criteria used to assess suitability, and the outcome for each affected employee. The reasoning where no suitable role is identified should be recorded with the same care as a positive outcome.

Modified arrangements — part-time, hybrid, location flexibility, role adjustment — should be considered alongside direct redeployment. A redeployment process that examines only like-for-like role matches is rarely sufficient to demonstrate that suitable alternatives were genuinely considered.

Communication should follow a planned sequence — leaders, managers, affected employees, the broader workforce, external stakeholders — with the message calibrated to each audience and consistent across channels. Inconsistency between what is said in a town hall, written in a manager script and published in an internal channel is one of the most common sources of confusion and grievance during change programs.

Manager scripts, FAQs and escalation pathways should be prepared in advance so managers are not improvising at the point they have the most difficult conversations. Where managers feel confident in the material they are working from, the conversations are better; where they do not, the conversations expose the program.

AWS supports employers across business case development, consultation design, redeployment process, role design, communications and post-implementation review. Engagements are structured to integrate with existing project, HR and WHS governance, and to draw on related AWS advisory and psychosocial safety support where the change carries elevated workforce risk.