Employee Relations

Employee relations sits between everyday management and formal process, and it covers a wider range than the disciplinary cases it is usually associated with.

• Grievances raised by individuals, and the process for hearing them.
• Conduct and discipline, from informal conversation through to dismissal.
• Performance concerns where they become formal.
• Consultation and communication about change, including the notice obligations that attach to certain changes.
• Dealings with trade unions and worker representatives where they exist.
• Absence and welfare cases where the ordinary policy has not resolved matters.

The individual and collective halves are genuinely different disciplines. Individual work is casework: facts, procedure, evidence and a defensible outcome. Collective work is negotiation and relationship management, conducted with representatives, over time, where the relationship outlasts any individual issue.

Organisations frequently give both to the same person without acknowledging the difference, and the usual result is that the casework crowds out the relationship work, which then surfaces as a problem during the next contested change.

The clearest measure of whether employee relations is working is whether comparable situations produce comparable outcomes.

Where two employees commit similar conduct and one is dismissed while the other receives a warning, the difference is noticed, discussed and remembered, and it undermines every subsequent decision. It is also the most common way an otherwise defensible dismissal becomes indefensible, since the comparison is the first thing raised.

Inconsistency is rarely deliberate. It comes from decisions being taken by different managers, at different times, without reference to what was decided before, and frequently without anyone holding a record of previous outcomes.

The practical defences are unglamorous: a central record of what was decided in comparable cases, a review step before any significant outcome, and a small number of people who see enough cases to notice divergence.

The alternative, which is a longer policy, does not work. Policies are already longer than the problem requires and inconsistency arises in their application rather than in their absence.

Most formal cases have a history, and it typically involves something that could have been addressed earlier and was not.

The recurring pattern is a manager who avoids a difficult conversation for months, then raises everything at once when the situation becomes intolerable. The employee, who has had no indication that anything was wrong, experiences a sudden formal process as arbitrary, and reacts accordingly. The case is now harder, slower and more contested than it needed to be.

The same applies to grievances. An issue raised informally and dismissed, or acknowledged and then not followed up, returns as a formal grievance, usually with the handling of the original complaint added to it.

This has an implication for where effort should go. Investment in helping managers hold ordinary conversations early prevents more formal cases than any improvement to the formal process does. The formal process handles the residue and cannot substitute for what should have happened earlier.

It also means the volume of formal cases is a management diagnostic. A team or site producing disproportionate escalations is usually reporting something about its management rather than its people.

When a case is examined, whether internally or externally, the contemporaneous record does most of the work.

What helps is a note made at the time: what was discussed, what was agreed, what the employee said, what evidence was considered, and what the reason for the decision was. What does not help is a file assembled after the dispute began, which is visibly retrospective and carries correspondingly less weight.

Two failures are common. Nothing is recorded until the matter becomes formal, so the months of informal management that would have shown a fair process leave no trace. And the record captures the employer's conclusions without capturing the employee's response, which makes the process look one-sided even where it was not.

Recording the employee's account, including where it was not accepted and why, is what demonstrates that it was actually considered.

Where a matter may have a long tail, and most do, the record needs to survive the departure of the manager who created it. Notes held in personal folders and email accounts routinely disappear at exactly the point they become necessary.

Parts of employee relations are structured by statute rather than left to policy, and the obligations attach at thresholds an organisation can cross without noticing.

Section 4 of the Industrial Relations Code, 2020 requires every industrial establishment employing twenty or more workers to have one or more Grievance Redressal Committees, with equal numbers representing employer and workers and a chairperson.

Section 28 applies the standing orders Chapter to an industrial establishment wherein three hundred or more workers are employed, or were employed on any day of the preceding twelve months. Where it applies, standing orders govern conditions of service directly, including the disciplinary procedure for the matters they cover.

Section 40 requires prescribed notice to affected workers before a change to a condition of service specified in the Third Schedule takes effect, which turns certain operational decisions into consultative ones.

The threshold structure means an organisation's obligations change as it grows, and the change is retrospective in form: the standing orders test looks at any day of the preceding twelve months. An establishment that briefly exceeded a threshold is in scope. Checking headcount against these tests periodically is more reliable than assuming continuity.