Standardise the governance principles, not the assumption that every jurisdiction will ask the same questions in the same way.
Organisations operating across Australia often want a single project playbook. That instinct is sensible. Common gates, roles, templates and decision rights reduce confusion and support portfolio reporting.
Environmental Impact Assessment, however, creates a boundary condition for standardisation.
The supplied 2019 comparison of Australian jurisdictions found recognisable similarities across states and territories, including referral or initiation, determination of assessment level, proponent-prepared assessment material, public review and a final government decision. It also identified differences in the treatment of economic and social impacts, guidance, authority structures and terminology.
That means the enterprise should standardise how it governs environmental decisions, while adapting how each project satisfies jurisdictional requirements.
FACT CHECK REQUIRED: refresh all current Australian jurisdictional legislation, agencies, assessment pathways, terminology and consultation requirements before publication.
The Strategic Context
Multi-jurisdiction organisations face two opposing risks.
The first is fragmentation. Every project develops its own approach, templates, advisers and approval strategy. The organisation loses comparability, lessons are not transferred and executives struggle to understand portfolio exposure.
The second is false standardisation. A central method assumes the same triggers, assessment levels, documents and decision pathways apply everywhere. Project teams then discover local requirements late.
The better operating model separates enterprise control from jurisdictional compliance.
Enterprise control should be consistent: early screening, material-risk identification, alternatives analysis, evidence planning, accountability, decision gates, escalation and monitoring.
Jurisdictional execution should be adaptable: the relevant legislation, agency, statutory instrument, consultation process, submission format and approval sequence.
What Leaders Commonly Misread
A common error is to treat different terminology as the main problem. The deeper issue is that authority, thresholds and decision pathways can vary, affecting schedule, evidence and stakeholder strategy.
Another misread is to assume that the most rigorous internal standard automatically satisfies every jurisdiction. A strong internal process improves readiness, but statutory requirements must still be mapped explicitly.
Conversely, some organisations allow local compliance to drive the entire project management model. That can create unnecessary variation in internal governance.
A third error is to treat regulatory strategy as a legal or environmental workstream. Approval sequencing can affect land access, procurement, design freeze, funding and stakeholder commitments. It therefore belongs in integrated project and portfolio planning.
Reframing the Issue
Think in terms of a two-layer EIA operating model.
The first layer is enterprise-wide and answers:
- What is the project's environmental and heritage risk profile?
- What evidence could change the investment or design?
- What are the decision rights?
- Which risks require escalation?
- How will alternatives and residual obligations be assessed?
- What monitoring will close the loop?
The second layer is jurisdiction-specific and answers:
- Which statutory pathway applies?
- Which authority decides or advises?
- What documents and studies are required?
- What consultation process applies?
- What approvals are dependent on one another?
- What local guidance changes assessment expectations?
This structure gives executives comparability without pretending legal environments are identical.
Strategic Analysis: Governance Should Travel Better Than Templates
Templates are useful, but they are not the operating model.
A national infrastructure, energy, defence or property organisation can use a common front-end environmental screen for every project. That screen might classify potential significance, identify sensitive receptors, highlight approval dependencies and determine whether specialist escalation is required.
From there, the project should activate a jurisdictional module.
This allows the portfolio office to compare projects on common dimensions while local teams retain the flexibility to address the relevant statutory process.
Regulatory variation affects capital allocation
Jurisdictional complexity is not simply an administrative cost. It can affect investment attractiveness.
Two technically similar projects may face different approval schedules, consultation demands, data gaps or cumulative constraints. Those differences can influence time to value and execution risk.
A portfolio therefore should not compare projects only on engineering cost and strategic benefit. Where approvals are material, the maturity and complexity of the regulatory pathway belong in the investment comparison.
Local knowledge is an asset
Centralised organisations sometimes under-value local environmental knowledge. Yet site history, seasonal constraints, community expectations and agency practice can materially affect execution.
The enterprise should therefore create a network model: central standards and assurance combined with trusted local expertise.
Related article: Scoping Is Capital Discipline: Spend Evidence on Decisions That Can Still Change
Build a common data model even when processes differ
A practical way to preserve enterprise visibility is to standardise the information that every project must report, even when the statutory documents differ.
At minimum, a national portfolio should be able to compare each project’s assessment status, material environmental and heritage issues, approval dependencies, key evidence gaps, consultation commitments, residual risks, forecast decision dates and ongoing conditions.
This common data model is more valuable than forcing every project into the same template. It allows executives to see where approvals are immature, where multiple projects depend on the same specialist or authority, and where assumptions are beginning to threaten schedule or investment value.
It also supports lessons learned. If the organisation records only local document names, knowledge remains jurisdiction-bound. If it records the underlying decision information, learning can travel across the enterprise even when statutory language changes.
Decision Framework
A national organisation can apply the following governance test to each project.
| Enterprise question | Jurisdictional translation |
|---|---|
| What level of environmental risk does the investment create? | What assessment trigger or pathway is likely to apply? |
| What evidence could alter the decision? | What studies and baseline data are expected locally? |
| Who owns the decision? | Which statutory and internal authorities have decision rights? |
| When must uncertainty be resolved? | Which submissions, consultation periods or approvals affect the schedule? |
| What residual obligations remain? | Which conditions, licences, monitoring or reporting duties may continue after approval? |
The exact statutory answer must be verified for the relevant project and date. The enterprise logic can remain consistent.
From Strategy to Execution
Immediately, organisations operating across jurisdictions should maintain a current approval-strategy register for major projects. It should show the likely pathway, key dependencies, evidence gaps, accountable owner and next decision.
In the medium term, build jurisdictional playbooks inside a common enterprise framework. Each playbook should have a named owner and a review date, because regulatory guidance and agency structures change.
Longer term, portfolio governance should capture approval performance: actual versus assumed timelines, recurring requests for additional information, common causes of rework and lessons from stakeholder engagement. This becomes a strategic dataset for future capital allocation.
Related article: The Hidden Cost of Starting Environmental Assessment Too Late
Signals to Monitor
Watch for repeated legal or agency changes, projects discovering approval dependencies after funding, local teams maintaining shadow procedures outside the enterprise system, contradictory advice across jurisdictions and portfolio reporting that treats all “approval risk” as one generic category.
Also monitor internal drift. If every region invents different risk language, categories and gate evidence, the organisation may have adapted too far and lost enterprise control.
Questions for the Leadership Team
- Which environmental governance principles should be identical across every Australian project?
- Which elements must remain jurisdiction-specific?
- Are approval assumptions included in capital and schedule comparisons between projects?
- Who is accountable for keeping jurisdictional playbooks current?
- Where are we relying on generic templates instead of local regulatory intelligence?
- What lessons from one jurisdiction can improve governance elsewhere without creating false standardisation?
Closing Perspective
A national EIA capability should be neither completely centralised nor completely local.
The organisation should standardise the disciplines that create good decisions: early assessment, explicit uncertainty, alternatives, accountability and monitoring. It should then adapt the statutory execution to the jurisdiction in which the project actually operates.
The objective is not one environmental process everywhere. It is one standard of decision quality everywhere.