PERRAM J:
1 Last night at 9 pm I made interlocutory orders the practical effect of which was to restrain the respondents (who are five unions) from continuing industrial action relating to the Sydney rail network and which affects non-metropolitan services too. These are my reasons for making those orders.
2 The first applicant is Sydney Trains which is the network control manager for the Sydney metropolitan rail network and intercity trains network. The second applicant is NSW Trains which operates regional rail and coach services throughout regional New South Wales and into neighbouring states. I will refer to both applicants as the Rail Agencies.
3 Historically, the Rail Agencies have bargained with a group of unions known collectively as the Combined Rail Unions. The Combined Rail Unions comprise all unions which represent the employees of the Rail Agencies, of which there would appear to be seven. However, not all seven unions are involved in this litigation. The five who have been joined as respondents are:
(a) the Australian Rail, Tram and Bus Industry Union ('RTBU'). The RTBU has 7,928 members within the Rail Agencies. The Rail Agencies have 13,314 employees so the RTBU represents around 60% of the employees of the Rail Agencies and is, therefore, the most significant of the five unions for present purposes;
(b) the Communications, Electrical, Postal and Plumbing Union ('ETU') which has 941 members within the Rail Agencies;
(c) the Australian Manufacturing Workers Union ('AMWU') which has 432 members within the Rail Agencies;
(d) the Australian Professional Engineer, Scientists and Managers Association ('APESMA') which has 351 members within the Rail Agencies; and
(e) the Australian Municipal, Administrative, Clerical and Services Union ('ASU') which 455 members within the Rail Agencies.
4 The relationship between the members of the Combined Rail Unions and the Rail Agencies is governed by an industrial agreement known as the Sydney Trains and NSW TrainLink Enterprise Agreement 2022. It reached its nominal expiry date on 1 May 2024.
5 The Fair Work Act 2009 (Cth) ('the Act') contemplates that parties in the position of those in this litigation may bargain with each other with a view to reaching some form of industrial agreement. Once the bargaining process begins, both sides may take industrial action against the other for which, generally speaking, they may not be sued: s 415. Such industrial action is known as 'protected industrial action'.
6 In the present case, the orthodox legal steps which have led to the current situation are as follows:
(a) the service by the Combined Rail Unions of a log of claims on 15 April 2024;
(b) the commencement of the bargaining process on 31 May 2024. The bargaining process commenced upon the service by the Rail Agencies of a Notice of Employee Representation Rights ('NERR') which is at the heart of the present dispute. I will return to its terms in more detail shortly;
(c) the application at various times by the members of the Combined Rail Unions for protected action ballot orders under s 437 of the Act. Industrial action (such as strikes and bans) will not be protected industrial action unless it is authorised by a 'protected action ballot': s 409(2). Such a ballot can only be held pursuant to a protection action ballot order made by the Fair Work Commission ('the FWC') under s 443. The various applications for protected action ballot orders made to the FWC were, therefore, an integral step along the path towards the Combined Rail Unions taking protected industrial action against the Rail Agencies. The FWC authorised ballots between 1 August 2024 and 4 September 2024;
(d) the holding of the ballots contemplated by the orders made by the FWC;
(e) the issuing of notices by each union of an intention to engage in industrial action; and
(f) the taking of that industrial action.
7 In the ordinary course, there could be no doubt that the process described in (a)-(f) resulted in protected industrial action. However, an additional event has also occurred which, the Rail Agencies submit, alters the legal landscape.
8 To understand that step, it is necessary to understand the distinction between a single-enterprise agreement and a multi-enterprise agreement. Confusingly, but sadly typically of Commonwealth legislation, a single-enterprise agreement may involve more than one employer. Where more than one employer is involved, however, the employers must be 'related': s 172(2). Where more than one employer is involved, therefore, a single-enterprise agreement actually means an enterprise agreement with multiple employers who are related. On the other hand, a multi-enterprise agreement is defined in s 172(3) such that it involves multiple employers who are not 'related' (or who fall within the category of related employers in s 172(5A)(c), that is to say, franchisees or related bodies corporate of the same franchisor: s 172(3A)).
9 The current agreement is a single-enterprise agreement which means that it was done on the basis that Sydney Trains and NSW Trains are 'related'. This is consistent with s 172(5A)(b) which, inter alia, declares employers to be related if they are related bodies corporate. Sydney Trains and NSW Trains are both statutory authorities subject to direction and overall control by the NSW Government under the Transport Administration Act 1988 (NSW).
10 The critical provision for the present dispute is s 172(5) which provides:
Requirement for employer specified in single interest employer authorisation
(5) Despite any other provision of this Part, if an employer is specified in a single interest employer authorisation that is in operation:
(a) the only kind of enterprise agreement the employer may make with their employees who are specified in the authorisation is a single interest employer agreement; and
(b) the employer must not initiate bargaining, agree to bargain, or be required to bargain with those employees for any other kind of enterprise agreement.
11 There has been in place since last Friday, 6 December 2024, a 'single interest employer authorisation' for the Rail Agencies. That being so, the effect of s 172(5) is to prevent from that date the Rail Agencies from entering into any kind of enterprise agreement apart from a 'single interest employer agreement'. A 'single interest employer agreement' results when a multi-enterprise agreement is entered into at a time when a 'single interest employer authorisation' was in operation: s 12.
12 Thus, the current effect of s 172(5) is to prevent the Rail Agencies from entering into a single-enterprise agreement. I interpolate here that no submission was made that a single interest employer authorisation could not be made by the FWC because the Rail Agencies are related: cf. s 172(3).
13 Returning then to the orthodox chronology of events set out above, the first legally significant event was the commencement of the bargaining process on the service by the Rail Agencies of notices under s 173(1). Section 173(1) and (2) provides:
Notice of employee representational rights
Employers for single-enterprise agreements to notify each employee of representational rights
(1) An employer that will be covered by a proposed single-enterprise agreement (other than a greenfields agreement) must take all reasonable steps to give notice of the right to be represented by a bargaining representative to each employee who:
(a) will be covered by the agreement; and
(b) is employed at the notification time for the agreement.
Note: For the content of the notice, see section 174.
Notification time
(2) The notification time for a proposed enterprise agreement is the time when:
(a) the employer agrees to bargain, or initiates bargaining, for the agreement; or
(aa) the employer receives a request to bargain under subsection (2A) in relation to the agreement; or
(b) a majority support determination in relation to the agreement comes into operation; or
(c) a scope order in relation to the agreement comes into operation; or
(d) a supported bargaining authorisation in relation to the agreement that specifies the employer comes into operation; or
(e) a single interest employer authorisation in relation to the agreement that specifies the employer comes into operation.
Note: An employer that is required to give a notice under subsection (1) cannot request employees to approve the agreement under section 181 until 21 days after the last notice is given (see subsection 181(2)).
(emphasis added)
14 In this case, however, the NERR was issued by the Rail Agencies on 31 May 2024 at a time when there was no single interest employer authorisation in place (and recalling that that authorisation did not occur until last Friday, 6 December 2024). Unsurprisingly, the notice was given in relation to a proposed single-enterprise agreement:
Sydney Trains gives notice that it is bargaining in relation to a single-enterprise agreement (Sydney Trains and NSW TrainLink Enterprise Agreement 2024) which is proposed to cover employees that are employed by Sydney Trains and are currently covered by the Sydney Trains and NSW TrainLink Enterprise Agreement 2022.
15 The problem which emerges can now be more clearly seen. It is evident, on any view, that prior to 6 December 2024 the bargaining period contemplated by the notice of 31 May 2024 was well and truly underway. In terms of s 172(3) the notification time had been engaged. However, when on 6 December 2024 the FWC made the single interest employer authorisation this appears to have caused the notification time to be reset to 6 December 2024 under s 173(2)(e). (I should add for completeness that at the hearing there was no exploration of whether a notice had to be given in relation to a multi-enterprise agreement (noting that s 173(1) does not appear to apply in that situation).)
16 At the same time, the notices given on 31 May 2024 were given in relation to a proposed single-enterprise agreement which, since 6 December 2024, it seems the Rail Agencies may not lawfully enter into.
17 The Rail Agencies accept that the industrial action which the respondents have been engaging in for some time now was protected industrial action up until 6 December 2024. But they now submit that since 6 December 2024 the making of the single interest employer authorisation means that it is no longer protected industrial action.
18 In this case it is not in dispute that for the industrial action to be protected industrial action it must be 'employee claim action' under s 409(1). That provision defines 'employee claim action' as having various features but relevantly describes it as being 'for a proposed enterprise agreement'. Section 409(2) then provides that the action must be authorised by a protected action ballot. For there to be a protected action ballot there must first be a protected action ballot order (ss 437, 443) and this, too, is defined in terms of a 'proposed enterprise agreement'. As a matter of fact, the protected ballot orders in this case all refer to a single-enterprise agreement. The ballots then all took place and, again, it is clear that each related to the proposed single- enterprise agreement.
19 No protected industrial action could be taken unless notice of it was first given: s 414. As with the provisions just mentioned, however, this provision too takes as its point of departure that the action is in relation to a proposed enterprise agreement.