High‑level change list (for CSIRO budgeting & TAP capacity)

Purpose of this note: Flag the types of changes we’re proposing—so CSIRO can advise on resourcing/budget impacts and TAP members can plan their time—without locking in final dates or detailed methods.

A. Timeframes (shift from the original, very tight TOR timeframes)

  • Overall delivery horizon moves to Mar/Apr next year for the Ministerial package (exact week to be negotiated).
  • Introduce an interim, consultation‑ready product (plain‑English summary with clear assumptions and key findings) ahead of the Ministerial package—timing window to discuss (e.g., late Jan–Feb), noting consultation lead times.
  • Phased checkpoints (to be scheduled, not fixed yet):
    • Regulatory alignment briefing/workshop to TAP (Department‑led).
    • Targeted revisions & options testing (CSIRO with TAP input).
    • Engagement with Department preparation of Background Report for Minister
    • Consultation pack sign‑off (Department with CSIRO/TAP review).
    • Final advice (Parts A & B) and Ministerial pack integration.

B. Scope (what expands/clarifies)

  • Explicit alignment of assumptions and scenarios to the NT regulatory framework and proposed WAP measures. (Calibration of risk statements/criteria to NT settings.)

  • Expert advice and engagement with Department during drafting of Background report

  • Two products, not one:

    1. a single technical report that
      • builds on risks identified in Part A to align with key policy questions for Ministerial decision-making on the Plan
      • improves process for risk assessment to match sparse data environment.
    2. a public consultation pack (plain‑language summary, methods at a glance, limits/uncertainties, and Q&A).

  • Targeted methods work as needed (to be agreed): limited sensitivity tests, scenario clarifications for policy relevance, additional model runs and use of existing data, and edits addressing key data limitations where they materially affect conclusions.

  • Language/tone and structure revisions to reduce misinterpretation by stakeholders (framing of risk statements, visuals, and caveats).

  • Light QA/review loop before consultation materials are finalised (short, time‑boxed).

Not changing (unless explicitly agreed later): generating new field data; wholesale rebuild of models; open‑ended re‑analysis beyond targeted tests; re‑writing the existing Part A report.

C. Responsibilities (clearer split of roles)

  • Department
    • Lead regulatory settings briefing to TAP; confirm policy assumptions and WAP measures to be used.
    • Own stakeholder engagement and consultation process (timelines, channels, approvals).
    • Draft and approve the consultation pack (with CSIRO technical input and TAP review).
  • TAP (including Chair)
  • Attend Department’s regulatory briefing; advise on the implications for analyses.
  • Implement assumption & scenario alignment to NT settings; provide a concise technical update (short note or addendum).
  • Provide technical content and review for the consultation pack (noting the Department is lead author).
  • Participate in 2–3 focused workshops/check‑ins.
  • Review targeted revisions and the public consultation pack; provide formal TAP advice (drawing on Part A) aligned to the revised assumptions.
  • Participate in checkpoint workshops; help ensure Plan and Background report are technically robust and aligned with TAP expert advice.

D. Likely budget/capacity drivers (for CSIRO to cost)

  • Additional workshops (prep + attendance) and short technical note/addendum.
  • Targeted analyses/sensitivity checks and updates to figures/tables.
  • Time to review and contribute technical advice for the Background report.
  • Time to review and contribute technical content for the consultation pack.
  • Iteration cycles (limited/defined) following TAP and Department feedback.

E. Decisions we propose to negotiate and confirm at the setup meeting

  • Indicative windows for: TAP regulatory briefing; targeted revision period; consultation pack sign‑off; final TAP advice; Ministerial pack completion.
  • Which assumption changes/scenario clarifications are in scope for the targeted methods work.
  • Deliverable formats (length/level for the single technical report and consultation pack).
  • Light addendum to the TOR covering timeframes, scope clarifications, roles, and review cadence.
  • Whether the above triggers a budget variation (CSIRO to propose options).