Puzzling industrial-relations laws

Image source: study-aids.co.uk
Image source: study-aids.co.uk

DIANA MAHABIR-WYATT

A recent dispute brought to court by the Government and Industrial Workers Union focused on a question that has often puzzled most industrial-relations stakeholders over the years. It is not caused by conflicting interests as usual – although there is that as well – but, I respectfully submit, by the act itself.

Let me start at the beginning.

A young man joined the union that represented the workers in the company he worked for. His position – manager, information technology – was an important one, and his expertise in IT needed by the company, as it is by most organisations.

If you are involved in industrial relations at all, you will be aware that it is not up to the executive director or the CEO these days to determine the status of an employee, to decide whether they are a “worker” or a “manager.” That determination is made, where it is in question, by the Registration, Recognition and Certification Board (RRCB).

People have forgotten that as the board was not constituted by government for a number of years companies just went ahead and attended to that themselves.

In this case, the union wanted to have the IT man included in the bargaining unit, but the company did not want him there, presumably because the IT person within the organisation is privy to its private and confidential information.

They claimed exclusion because he was a manager (it was in his job title). So the union went to the now (thankfully) reconstituted Recognition Board to ask for his job title to be varied into the existing bargaining unit. The board said he could be included and was prepared to vary the existing bargaining unit to include him.

This is not an unfamiliar or unique disputed area. What is significant, however, are the implications attached.

In this case, as it turned out, excluding an IT manager from the bargaining unit did not mean he is or is not a manager; nor does the title given to him by his employer.

Some employers call all professionals "managers" because the prestige of the title means more to them than the salary itself.

The IT manager title is given to an employee who may be a worker under the criteria set out by common law or the criteria used by the RRCB, but excluded from a bargaining unit because his “community of interest” or even his “periodicity of payment” would more reasonably place him in a different bargaining unit. There is an assumption that the mere exclusion implies that he is not a worker, but this assumption is wrong.

Many years ago there was a company called Trinidad Meat Processors in which all employees were union members, including managers, but excluding the general manager.

The Industrial Relations Act does not define the word “manager”; indeed, it never uses the word. But it does state who is excluded from the word “worker.” When the act was passed over 50 years ago, the exclusions included: “a person who in the opinion of the board – (i) is responsible for the formation of policy in any undertaking or business, or the effective control of the whole or any department of any undertaking or business; or (ii) has an effective voice in the formulation of any undertaking or business."

But the world has changed since then, as has the distinction between what is a worker and what is a manager. A manager used to be the sole owner/entrepreneur, major shareholder – on that level. Someone who had the sole authority to hire and fire.

In the public service everyone is legally employed by one person, the Chief Personnel Officer. He has the sole authority to hire and fire employees. Those authorities do not come under any minister, who would be the equivalent to a chief executive/managing director in the private sector.

As the Industrial Court has been trying to tell employers for the past couple of years, things have changed. The old concept of a court of human relations first conceived by the court has shifted over the intervening 50 years into a court of law, where legal procedures are expected.

In the case cited above, the defendants never asked the RRCB whether the IT manager was a worker or if he was excluded from that rather vague definition, so the RRCB never ruled on that issue.

And therein lies one of the outstanding problems. The definition by itself is ambiguous. What kind of “policy” is the act referring to? Cleaning up after work is done? Does that mean it is not necessary to get agreement on new policies from the union? And what happens when they don’t respond for five months because they are understaffed and have no time?

What, exactly, is “an undertaking?” Does my control of my little area of responsibility constitute an undertaking? How big does it have to be to be to qualify as an undertaking? How separate from anyone else’s responsibility? Do I stay in my silo?

What is meant by an “effective voice?” Does that mean I don’t have to consult anyone else before I decide? Not even the union, if there is one?

And what is “effective control,” anyway? Does that mean if a worker does not obey my orders, I can discipline them just to illustrate that I am in effective control?

Business structures have changed over the past 50 years. Technology has changed everything, as have banking regulations, as have international treaties, trading blocs, who the US will allow you to trade with and the control over everything else exerted by the International Economic Forum, or what it is evolving into.

Isn’t it time we at least looked at our industrial relations?

Comments

"Puzzling industrial-relations laws"

More in this section