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. Factual records made at the time can provide useful evidence, though their weight depends on their reliability and the evidence as a whole. 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.

Performance management can attract legal scrutiny before dismissal, including under applicable contracts, industrial instruments and discrimination laws. Procedural requirements depend on the applicable framework; the unfair-dismissal criteria are not a universal statutory code for every performance meeting. On unfair dismissal, s 387 of the Fair Work Act 2009 (Cth) sets the criteria the Fair Work Commission must consider in deciding whether a dismissal was harsh, unjust or unreasonable: whether there was a valid reason related to capacity or conduct (including its effect on the safety and welfare of other employees); whether the person was notified of that reason; whether they had an opportunity to respond; any unreasonable refusal to allow a support person at discussions relating to the dismissal; where the dismissal related to unsatisfactory performance, whether the person had been warned about it before the dismissal; the degree to which the employer's size, and any absence of dedicated HR expertise, would be likely to affect the procedures followed; and any other relevant matters. The Fair Work Commission's unfair dismissals benchbook explains how each factor is applied.

Two features of that list drive day-to-day practice. First, the support-person factor is about unreasonable refusal — there is no general statutory duty to offer a support person at every performance meeting, though policies and instruments often go further and offering one is usually sensible. Second, the warning factor applies specifically where the dismissal relates to unsatisfactory performance: a performance-based dismissal without a prior warning about that performance starts at a disadvantage under s 387(e).

General protections risk runs alongside unfair dismissal and is not capped in the same way. Under Part 3-1 of the Fair Work Act, adverse action — including dismissal, but also demotion, disciplinary action and other detriment — is prohibited where it is taken because a person has or exercises a workplace right (ss 340–341), and s 351 prohibits adverse action because of specified protected attributes, subject to its statutory exceptions. A performance process that begins shortly after an employee raises a complaint, takes leave, or exercises an entitlement invites an allegation that the real reason was the workplace right, not the performance; a reliable contemporaneous record can help establish the actual reasons for the action.

For small business employers, Code compliance means a dismissal is not unfair under s 385(c). The fewer-than-15 headcount includes employees of associated entities and regular casual employees; the checklist is an aid, not the legal test. For dismissals other than summary dismissal, the Code requires a valid conduct or capacity reason, a warning that dismissal is risked without improvement, an opportunity to respond and a reasonable chance to rectify the problem. An employee may have another person assist in discussions where dismissal is possible, but that person cannot be a lawyer acting professionally.

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.