DP World Sydney Ltd v Construction, Forestry and Maritime Employees Union

DP World runs major container terminals around Australia. Its 2024 enterprise agreements for Sydney, Melbourne, Brisbane and Fremantle all contained the same Appendix 4 dealing with “Automation”. That appendix was designed to manage what would happen if DP World decided to introduce a significant change to the mode of operation at a terminal during the life of the agreement.

The process in Appendix 4 was detailed and time-sensitive. It required notification of a definite decision, provision of information, discussions about the proposed mode change, attempts to reach agreement on matters such as roles, rosters and labour arrangements, and, if agreement could not be reached, referral of outstanding issues to an Independent Panel before the proposed go live date.

By late 2024 and early 2025, DP World had decided to proceed with certain automation-related projects at Port Botany, West Swanson and Fisherman Islands. It had also started consultations about a project at Fremantle and was considering a further project at Port Botany. Some of those projects plainly fell within Appendix 4, so the process had real commercial significance and was not hypothetical.

The immediate dispute was procedural but important. Clause 2 of Appendix 4 said the Independent Panel would consist of three panel members and that “Each party will nominate one member with one agreed presiding panel head.” DP World said that meant one nominee from the relevant DP World entity, one nominee from the union, and a separate presiding panel head agreed between those two sides.

The individual employee respondents said something different. They argued that the employees at each terminal were also a separate collective “party” for clause 2, so employees should nominate one member as well. On that reading, DP World, the union and the employees would each nominate one member, and those three would then agree which of them would act as the presiding panel head.

The union had initially accepted DP World’s interpretation and had taken steps to formalise the panel on that basis, but later changed position and largely supported the employees’ construction.

That disagreement was holding up empanelment of the Independent Panel while automation projects were being pursued or consulted on. DP World therefore went to the Federal Court for declarations about the proper meaning of clause 2.

The legal issue was the proper construction of the words “Each party” in clause 2 of Appendix 4. The court had to decide whether those words referred only to DP World and the union, or whether they also included the employees covered by the agreements as a separate collective party entitled to nominate a panel member.

The judgment shows that this was not treated as a free-standing language puzzle. Shariff J placed the clause in the statutory setting of enterprise agreements under the Fair Work Act 2009 (Cth). The court noted that enterprise agreements made under the Act are statutory artefacts. In industrial practice, people often speak of “parties” to an enterprise agreement, but the judgment emphasised that this language must be used carefully.

The Act distinguishes between who makes an agreement, who is covered by it, and to whom it applies.

The court referred to provisions including sections 50, 51, 52, 53, 183, 186(6) and sections 738 to 740 of the Fair Work Act. Those provisions helped explain how enterprise agreements operate, why dispute resolution procedures matter, and why representation of employees is contemplated in such procedures. But the statutory context did not itself answer the construction question. Instead, it informed the court’s reading of the particular words used in Appendix 4.

The judgment also set out accepted principles for construing enterprise agreements. The starting point is the ordinary meaning of the words, read as a whole and in context, including industrial context. A purposive and practical approach is preferred over a narrow or pedantic one. Context can extend beyond the immediately surrounding words to the whole document and its industrial purpose. Words are not interpreted in a vacuum divorced from industrial realities.

The court’s reasoning turned on the text, structure and operation of Appendix 4 itself. Shariff J said clause 2 had to be read in its immediate context, by reference to the purpose of Appendix 4, and in the context of the enterprise agreements as a whole.

A key point in the judgment is that the word “party” can mean different things in different settings. It may refer to parties to an agreement, or to parties to a dispute. The court gave an example from the general dispute resolution clause in the enterprise agreements, where “either party” plainly referred to the sides in the dispute rather than every person who might be described as connected to the agreement. That supported the broader point that context was everything.

The court also observed that the drafters had used the words “party”, “Party”, “parties” and “Parties” in different ways throughout the agreements, including within Appendix 4 itself. Because of that, the judge rejected any approach that assumed those words carried a single consistent meaning throughout the whole instrument.

The most important contextual feature was clause 1(b) of Appendix 4. Under that clause, DP World had to provide the union with appropriate information to assist the Parties to attempt to reach agreement around prospective working arrangements and rostering. The information included matters such as a prospective berth schedule, forecast idle shifts, data relating to working within, above or below grade, roster option data, and labour modelling inputs and outputs in a protected format.

The court treated that information-sharing step as critical to the operation of the rest of Appendix 4. Clause 1(c) then required the Parties to immediately commence discussions regarding the mode change. The use of the word “then” linked those discussions temporally to the prior provision of information under clause 1(b). Because the information was to be given to the union, the judgment said this strongly indicated that the discussions were to occur between DP World and the union.

The same logic carried into clause 1(d), where the Parties were to seek to reach agreement regarding roles, rosters, labour arrangements and requirements. The court considered that the subject matter of those discussions reinforced the importance of the information given under clause 1(b). As a matter of text, context and common sense, the judge considered that this pointed to DP World and the union as the operative participants in that process.

Although the published reasons available here are truncated before the end of the detailed analysis, the declarations and the reasoning that is available make the court’s approach clear. The judge did not accept the respondents’ argument that employees collectively were a separate “party” for clause 2 nomination purposes.

Shariff J upheld DP World’s construction. The court made declarations that clause 2 of Appendix 4 in each of the four enterprise agreements provided for an Independent Panel consisting of three panel members with one member nominated by the relevant DP World entity, one member nominated by the union, and one presiding panel head to be agreed between the relevant applicant and the union.

That meant the court rejected the competing construction advanced by the individual employees and largely supported by the union, under which employees at each terminal would also collectively nominate one member to the three-member panel.

Procedurally, the case was brought as an application for declaratory relief. The court was satisfied there was a justiciable controversy because the dispute was holding up empanelment of the Independent Panel in advance of the changes DP World proposed to implement at each terminal. The judgment therefore resolved a live dispute affecting the operation of the agreed automation process.

The decision did not finally determine every issue that might arise about the automation projects themselves. What it did do was settle the threshold question about how the panel had to be constituted under the enterprise agreements, allowing the agreed process to proceed on the court’s construction.

For business owners, the case is a reminder that major workplace disputes often begin with process, not substance. A business may be ready to implement automation, a restructure, a new roster model or another significant operational change, but the project can still be delayed if the governing document is unclear about who has formal rights at each stage.

The drafting lesson is especially strong where a clause uses broad labels such as “party”, “representative”, “employees”, “union”, “committee” or “independent panel” without carefully allocating functions. If one clause says information goes to a particular participant, and later clauses say “the Parties” must discuss, seek agreement, refer issues or nominate decision-makers, a court may infer that the same participants are intended to carry those later roles.

That is exactly the kind of process design reasoning that shaped this case.

Businesses should also note that the court did not assume one universal meaning for the word “party” across the whole agreement. That matters in practice. A term may refer to the sides in a dispute in one clause, but to a different set of actors in another clause. If your agreement intends different meanings in different places, define them or draft the clauses more directly.

This is particularly important where project timing is linked to milestone dates. Appendix 4 required discussions and panel steps to occur months before the scheduled go live date. In that kind of framework, a dispute about panel constitution is not a technical side issue. It can affect implementation timing, bargaining dynamics and litigation risk.

For employers negotiating or reviewing enterprise agreements, side letters or bespoke workplace change protocols, the practical approach is to map the process from start to finish. Identify who is notified, who receives supporting information, who participates in discussions, who seeks agreement, who can refer issues onward, who nominates panel members or experts, and who is bound by the outcome.

If employees are intended to act through a committee or elected representative, say so expressly rather than relying on a broad word like “party”.

Does this case mean employees can never have a direct nomination right? No. It means a court will look for that right in the actual wording and structure of the instrument. If a document intends employees, an employee committee or another representative body to nominate a panel member, it should say so clearly.

Is this only relevant to enterprise agreements? The judgment is about enterprise agreement construction, but the drafting lesson is broader. Similar issues can arise in shareholder agreements, joint venture documents, service contracts, franchise arrangements and other instruments that create panels, experts or escalation pathways.

What if our document uses the same term in different ways? That is a warning sign. This case shows that a court may decide the term takes its meaning from context each time it appears. Consistent drafting or clear definitions reduce that risk.

Should businesses rely on industrial custom to fill gaps? Not if the document can be made clearer. Industrial context matters, but the court still starts with the text and how the process is structured. Clear drafting is safer than hoping context will solve ambiguity later.

The judgment was delivered by Shariff J on 13 May 2026 in the Federal Court of Australia. The hearing took place on 7 May 2026. The court made declaratory orders resolving the construction dispute about clause 2 of Appendix 4 in the four DP World enterprise agreements.

This page explains the decision on the basis of the published judgment text available for the matter. It covers the dispute, the statutory setting, the court’s construction approach and the declarations made. It does not address any costs outcome or later appellate history because those matters are not confirmed here.