Performance management and procedural fairness in workplace processes

Performance management decisions that go wrong often go wrong on process rather than on substance. Clarity about expectations, accurate evidence of performance against those expectations, genuine conversation about the gap and a fair opportunity to improve are the elements that make any later decision defensible. Without them, even well-founded conclusions are difficult to sustain — and where the eventual decision is separation, the matter becomes a question of termination risk rather than of performance, with the framework described in managing termination risk through fair and documented processes.

Procedural fairness is not an obstacle to managing performance. It is what allows performance to be managed in a way that holds up to scrutiny — by the employee, by an internal review, by an external decision-maker or by a regulator.

Expectations should be defined in terms that can be measured or observed, communicated in writing, and reinforced in regular conversation. Where expectations have shifted — through role change, restructure or strategy change — the change should be made explicit rather than assumed. An employee cannot reasonably be held to expectations they were not told about.

Position descriptions, KPIs and behavioural standards should align with one another. Inconsistency between these documents is a common source of dispute about what was actually expected, and is often the first ground on which a performance decision is challenged.

Performance evidence should be contemporaneous. Records made at the time, in factual rather than evaluative language, carry far more weight than reconstructed accounts. Where examples are used, they should be specific, dated and capable of being discussed with the employee.

Reliance on a single example to support a broader conclusion is a recurring source of risk. Patterns should be evidenced as patterns — a pattern is not established by one instance, however clear. Where the pattern crosses a longer period, the record should reflect that the issue has been observed, raised and given an opportunity to be addressed at each stage.

Where performance concerns are raised, the support being provided should be visible to the employee — coaching, training, mentoring, peer support, workload adjustment where appropriate. A process that identifies a gap but offers no support to close it is far harder to sustain than one that pairs the two.

Manager capability is itself part of the control environment. Managers responsible for performance conversations should be trained and supported; a poorly handled conversation is often the trigger for what later becomes a contested matter. Capability development for line managers — covered in more detail under training and workplace capability — materially reduces the volume of contested performance decisions over time. Reasonable adjustments for disability, caring responsibilities or other relevant factors should also be considered as part of the process rather than treated as a separate workstream.

Performance conversations should be planned, with the manager and employee given a clear understanding of the purpose and outcome of the meeting. Where a performance concern is raised, the employee should be given an opportunity to respond, to put forward their own view, and to identify any context the manager may not have seen. The opportunity to respond should be genuine — sufficient notice of what will be discussed, the option of a support person where appropriate, and time to consider any material being relied on.

Where formal improvement plans are used, they should specify the expectations, the support to be provided, the timeframe and the review points. Plans that do not specify what success looks like are difficult to manage to conclusion. Plans should also state what will happen if the expectations are met and what will happen if they are not, so the employee can engage with the process on a clear footing.

Warnings should be used deliberately, in plain language, and recorded with the date, the substance of the concern, the standard required and the support offered. Warnings issued without those elements are difficult to rely on later, and warnings used as a substitute for direct conversation rarely produce the change they were intended to support.

Alternatives to formal warning processes — coaching arrangements, role adjustment, modified duties, role move — should be considered alongside warnings rather than after them. Review meetings should be scheduled at the points the plan identifies, conducted in line with the same procedural fairness principles, and used to update the record on progress against the expectations.

Where decisions are made — warnings, role changes, separation — they should be made on the evidence and reasoning documented through the process, not on impressions formed outside it. The decision-maker should be able to articulate the material considered, the policies applied and the basis for the conclusion.

Documentation should be coherent across the matter rather than scattered. A single case file — expectations, evidence, conversations, responses, decisions — is the most reliable record. Where independent input from workplace advisory is useful at a decision point, it should be obtained while the decision is still open rather than after it has been made.

AWS supports employers in designing performance management frameworks, training managers in procedural fairness, and reviewing individual matters where independent input is useful. The work is configured to integrate with the organisation's existing performance and HR systems rather than running alongside them.