Summary
Details
- Australia
Mandatory for:
Proponents whose actions are determined to be “controlled actions” requiring federal approval, and any person or entity bound by approval conditions (including operators and, in some cases, successors in title).
Exemptions are limited and fact-specific. In practice, compliance depends on proper referral decisions and defensible significance assessments rather than relying on broad exclusions.
Common boundary issues:
Proponents sometimes assume state approvals are sufficient. EPBC is a separate federal trigger and can still apply.
Project segmentation (splitting a project into smaller parts) can create compliance risk if the overall action should have been assessed as a whole.
Maintenance and expansions can retrigger assessment needs depending on the impact of the change.
Deep dive
📩 Stay ahead of climate regulation and reporting shifts
Regulatory updates, reporting standards, and new climate software — distilled into one concise weekly brief for decision-makers.
Thanks for signing up. Please check your inbox to confirm your subscription.
Practical updates. Once per week.
What’s Required
The EPBC regime is activated when a proposed “action” may have a significant impact on protected matters. The compliance-critical step is early legal and technical screening to determine whether a referral is required. A conservative posture is essential because proceeding without required approval creates severe enforcement risk and can halt projects.
Typical compliance workflow includes:
Significance assessment: Desktop screening and field studies to identify protected matters and potential impacts.
Referral submission: If a controlled action is possible, prepare and submit a referral with sufficient technical evidence.
Assessment approach: Depending on complexity, the regulator determines the assessment pathway and information requirements.
Decision and conditions: If approved, projects must comply with conditions, which can include avoidance/mitigation measures, offsets, monitoring, reporting, adaptive management, and independent auditing.
Ongoing compliance duties after approval. Approval conditions are effectively a compliance program that can last years. Operators must:
Implement environmental management plans and mitigation controls.
Monitor impacts and report in line with condition cadence.
Manage contractors and supply chain to ensure on-ground compliance.
Maintain records to demonstrate compliance, often suitable for regulator inspection.
The EPBC Act is administered federally by the same portfolio department that also houses climate and energy policy functions. For project developers, compliance governance should include: clear accountability, condition tracking systems, escalation protocols, and evidence retention that can withstand enforcement scrutiny.
Important Deadlines
Act entry into force: The EPBC Act came into force on 16 July 2000.
Project-specific statutory timelines: Referral and assessment stages have procedural timeframes, but practical schedules are driven by information quality, consultation, seasonal ecological survey windows, and iterative requests.
Condition timelines: Approval conditions typically include milestone dates for plan submission, pre-clearance surveys, staged construction approvals, offsets delivery timing, and post-construction monitoring periods.
Current Status
The EPBC Act is in force and maintained on the federal legislation register, with current departmental guidance describing its purpose and administration.
Penalties for Non-Compliance
While penalty provisions are detailed and case-specific, EPBC non-compliance risk is typically high because regulators can pursue:
Injunctions or stop-work outcomes.
Civil and criminal pathways for serious breaches.
Enforcement for breach of approval conditions, including remediation requirements.
From an industry perspective, the most material “penalty” is often schedule disruption, stranded capex, financing covenant breach, and loss of social licence resulting from regulatory intervention.
Examples of Known Violations
Recurring real-world failure modes in EPBC-style approvals regimes include:
Failure to refer: Proceeding on the assumption that impacts are not significant, later challenged by evidence or third parties.
Non-compliance with conditions: Clearing outside approved areas, missing pre-clearance survey requirements, or failing to implement mitigation controls.
Inadequate offsets delivery: Delays in securing offsets, poor equivalence, or insufficient documentation of offset management.
Contractor non-compliance: On-ground actions by subcontractors inconsistent with approval conditions or management plans.
Monitoring and reporting gaps: Incomplete monitoring data, late reports, or weak corrective action responses when impacts exceed thresholds.
Resources
Cut through the green tape
We don't push agendas. At Net Zero Compare, we cut through the hype and fear to deliver the straightforward facts you need for making informed decisions on green products and services. Whether motivated by compliance, customer demands, or a real passion for the environment, you’re welcome here. We provide reliable information. Why you seek it is not our concern.