The Act contains several drafting and operational features that can create compliance traps, enforcement leverage points, and administrative uncertainty. Below are concrete, source‑grounded pitfalls to watch for.
Defined terms are decisive and not reproduced here. The Act refers to a schedule 1 dictionary for “particular words used in this Act” (s5). Terms that determine scope and duty , for example “large resource project”, “nearby regional community”, “fly‑in fly‑out worker”, “owner”, and “proponent” , are defined there. Without checking schedule 1, one cannot reliably determine whether a given project or workforce falls within the Act’s remit. Practitioners should obtain the schedule before relying on any operational conclusions (s5).
Designated day and publication triggers. The timing of the s6 prohibition is fixed to six months after the designated day, which is set as the day the Coordinator‑General publishes the project name under s13 (s6(1), s6(1A), s13). Failure to monitor the department’s website for that publication will not excuse non‑compliance. Publication fixes legal timeframes and starts statutory clocks, so owners may find obligations apply sooner than internal project timelines assume.
Vicarious exposure through related bodies corporate and agents. The owner is taken to contravene s6 and s8 regardless of whether it, a related body corporate, or an agent employs the workforce or engages in the advertising conduct (s6(3), s8(3)). This means owners must control recruitment practices across the corporate and contracting chain, not only direct employees. Structural reorganisation, subcontracting or use of workforce suppliers does not shield an owner from contravention.
Broad prohibition on discriminatory advertising and documents. Section 8 forbids advertising that prohibits nearby regional community residents from applying and prohibits any document stating those residents are ineligible (s8(2)). The prohibition is not limited to job ads and is phrased broadly as “in any way in a document,” increasing the risk that non‑HR documentation or public statements could create exposure.
Operational workforce definition and measurement risk. The s6 prohibition targets an operational workforce “that comprises 100% of workers who are fly‑in fly‑out workers” (s6(2)). Determining whether a workforce is 100% FIFO requires clear operational definitions, counting rules (headcount, FTEs, rostered shifts), and time periods. Those definitional and measurement questions are crucial yet depend on schedule 1 and the Coordinator‑General’s guidelines, which must be consulted.
Requirement notices and short deadlines. If the Coordinator‑General is satisfied s6 was contravened after requesting information under s14A, the owner has three months to submit an operational workforce management plan that complies with the requirement notice unless the Coordinator‑General grants a longer period (s7(1), s7(4)). Three months can be a compressed timetable to consult local government, prepare a detailed plan to meet a guideline, and secure internal approvals.
High penalties for false or misleading documents. Section 14B imposes a maximum penalty of 1,665 penalty units for knowingly providing a false or misleading document to the Coordinator‑General (s14B). That is materially higher than most other statutory penalties in the Act and indicates a high legislative focus on truthful documentation.
Information notices and self‑incrimination. The s14A notice mechanism carries its own penalty (400 penalty units) for non‑compliance, but individuals can rely on the reasonable excuse that answering might tend to incriminate them (s14A(4)-(5)). Organisations, however, lack an equivalent privilege, so corporate officers must take care in responding and should consider legal advice where answers could expose the organisation to criminal liability.
Coordinator‑General’s capacity to impose enforceable conditions that are removed from certain courts’ jurisdiction. Conditions related to operational plans or SIAs may be taken to be enforceable under SDAPWO s157A (s7(6)-(7), s11(2)-(3)). The Act further removes Land Court and Planning and Environment Court jurisdiction in relation to such conditions except as provided in SDAPWO pt 7A (s7(8), s11(4)). This narrows the immediate judicial forum and can alter dispute resolution strategies.
SIA linkage to Environmental Protection Act progress. Section 10 ties the progress of specified EP Act EIS provisions to the Coordinator‑General’s advice that the SIA may proceed (s10(2)). That gives the Coordinator‑General a material gatekeeping role over EIS progress under the EP Act for projects where an EIS notice has been published after commencement, and may lead to inter‑agency timing risks.
Regulatory instruments and fees not yet known. Section 15 authorises regulations on fees and small penalties (s15). Until those regulations are published, the full administrative cost profile, including prescribed fees for applications to change conditions (s11(3)(d) references fees prescribed by regulation), is uncertain.
No prosecution exposure for the State. The Act binds the State but exempts the State from being prosecuted under it (s4). That asymmetry may matter where state entities are involved in projects or approvals.
In sum, the main “gotchas” arise from definitional dependence on schedule 1, publication‑driven timeframes, vicarious exposure through related entities and agents, broad documentation prohibitions, compressed remedial timetables, high penalties for misleading documents, and the Coordinator‑General’s substantial administrative leverage. These are not speculative: each derives directly from the Act text.