Reportable Conduct SchemeAustralia
Back to Intelligence
Compliance NSW, WA, ACT

One Allegation, Two Clocks: Managing NSW, WA and ACT Reportable Conduct Timeframes Without Missing a Deadline

September 18, 2026 7 min read
Share
A compliance manager at a desk with three separate case folders, a laptop displaying a scheduling dashboard, colour-coded sticky notes, and a clock in a quiet government-style office, no text in image

Multi-jurisdiction organisations rarely get the luxury of a single compliance timetable. When an allegation of reportable conduct involves services, staff or records connected to New South Wales, Western Australia and the Australian Capital Territory, the legal issue is not only what happened, but which regulator must be told, when, and by whom. The practical risk is obvious: one allegation can start more than one reporting clock. If escalation pathways and recordkeeping are unclear, deadlines can be missed even where the organisation responds quickly on the ground.

Start with the correct clock in each jurisdiction

For organisations operating across NSW, WA and the ACT, the first control is to distinguish the initial notification deadline from the final reporting obligation.

In New South Wales, the Reportable Conduct Scheme operates under the Children's Guardian Act 2019 and is overseen by the Office of the Children's Guardian. The head of a relevant entity must make an initial notification within 7 business days, and a final report within 30 calendar days.

In Western Australia, the scheme operates under the Parliamentary Commissioner Act 1971 and is overseen by Ombudsman WA. The initial notification is due within 7 working days, and the final report is due on conclusion of the investigation.

In the Australian Capital Territory, the scheme operates under the Ombudsman Act 1989 and is overseen by the ACT Ombudsman. The initial notification is due within 7 business days, and the final report must be provided as soon as practicable.

These differences matter. NSW imposes a fixed final reporting period of 30 calendar days. WA and ACT do not use the same fixed end date, but that does not mean “open-ended”. In practice, organisations still need an active investigation plan, documented reasons for any delay, and disciplined regulator communication.

A common operational mistake is treating all three jurisdictions as if they run on the same timetable because the initial notification periods look similar. They do not. Even where the first notice is due at roughly the same point, the final reporting obligations diverge significantly.

Build an escalation pathway that works on day one

The safest model is a documented escalation pathway that starts as soon as an allegation is received, not after a threshold meeting days later.

At minimum, the pathway should identify:

  • who receives the allegation first
  • who makes the threshold decision on whether the matter is reportable
  • who decides which jurisdiction or jurisdictions are engaged
  • who is authorised to notify each regulator
  • who oversees the investigation
  • who signs off on the final report.

For multi-site organisations, this usually means avoiding a purely local response. A school principal, service manager or regional leader may be the first to hear the concern, but there should be a mandatory same-day escalation to a central safeguarding, legal or people and culture function. That central function should maintain the reporting calendar and confirm whether the allegation touches NSW, WA, ACT, or more than one.

This is especially important where the worker is employed in one jurisdiction but the alleged conduct occurred in another, or where children, records and witnesses are spread across different sites. The regulator question is not always answered by payroll location alone. Organisations should have a triage checklist that captures service location, child location, worker status, alleged conduct type, and where relevant records are held.

Escalation pathways should also distinguish between employment action, child safety action and regulator notification. These streams often run together, but they are not the same thing. A manager might suspend duties or adjust rostering immediately for safety reasons, while the central team prepares the initial notification and scopes the investigation.

Manage the “two clocks” problem with a single case plan

The easiest way to miss a deadline is to run separate informal processes for safeguarding, HR and legal. A better approach is a single case plan that tracks all reportable conduct tasks against the shortest applicable timeframe.

For example, if NSW is engaged, the organisation should plan on the basis that the 30 calendar day final report is the most demanding final-report deadline of the three jurisdictions covered here. Even where WA or ACT also apply, using the NSW timetable as the internal anchor reduces the chance of drift.

A practical case plan should include:

  • date and time the allegation was received
  • date threshold assessment commenced and completed
  • jurisdictions identified as potentially engaged
  • initial notification due date for each regulator
  • investigation lead and decision-maker
  • witness and evidence schedule
  • risk controls for children during the investigation
  • date procedural updates will be reviewed
  • target final report date for each jurisdiction.

Where the same facts must be reported to more than one regulator, consistency matters. Core facts, risk actions and findings should align across notifications and final reports. If there are differences in framing because of each regulator’s forms or requirements, the organisation should document why.

The case plan should also account for investigator resourcing. In NSW, external investigators need a Class 2E (Private Investigator) licence under the Security Industry Act 1997 (NSW), while internal employees are exempt when acting within the scope of their employment. In WA, external investigators must be licensed under the Security and Related Activities (Control) Act 1996. In all jurisdictions, regulators expect investigators to be appropriately qualified. Licensing checks should therefore be part of the early escalation process, not a late procurement issue.

Recordkeeping is the control that proves compliance

Good intentions do not establish compliance; records do. In cross-jurisdiction matters, recordkeeping should be structured so the organisation can show not only what it did, but when it did it and why.

At minimum, maintain a clear chronology containing:

  • the allegation as first received
  • all triage and threshold decisions
  • regulator notification dates and copies lodged
  • rationale for jurisdiction selection
  • safety actions taken for children
  • investigation steps, evidence obtained and interviews conducted
  • updates provided to the head of entity
  • reasons for delay where final reporting took longer than expected
  • final findings and actions taken.

This chronology should be controlled centrally, even if local managers contribute information. Version control is critical. Multi-jurisdiction matters often generate draft letters, duplicate spreadsheets and conflicting diary notes. A single source of truth reduces the risk of inconsistent reporting.

Recordkeeping also supports procedural fairness and defensible decision-making. If the organisation later needs to explain why it treated a matter as reportable, why it notified more than one regulator, or why the final report was not available earlier, contemporaneous records will matter.

For WA and ACT in particular, where final reports are tied to conclusion or to being provided as soon as practicable, documented evidence of active progression is important. If there are delays because witnesses are unavailable, records are dispersed, or an external investigator is being appointed, that should be captured and monitored rather than assumed.

Practical governance tips for multi-jurisdiction organisations

The best-performing organisations do not rely on memory or goodwill. They use simple governance tools that translate legal obligations into repeatable operational practice.

Useful controls include:

  • a jurisdiction matrix listing notification and final reporting deadlines
  • an incident intake form with mandatory jurisdiction questions
  • a central deadline register with automatic reminders
  • template regulator notifications for NSW, WA and ACT
  • a standing panel or pre-vetted list of appropriately qualified investigators
  • monthly assurance reviews of open reportable conduct matters
  • board or executive reporting on overdue actions and emerging trends.

Training should focus on the first 48 hours. That is when most deadline failures begin: a concern is parked as an HR matter, a site assumes another office will notify, or nobody confirms which statutory clock applies. Frontline leaders do not need to become legal specialists, but they do need to know when to escalate immediately and what information must be preserved.

Key takeaways

  • NSW, WA and ACT all require prompt initial notification, but their final reporting deadlines differ in important ways.
  • NSW requires initial notification within 7 business days and a final report within 30 calendar days.
  • WA requires initial notification within 7 working days and a final report on conclusion.
  • ACT requires initial notification within 7 business days and a final report as soon as practicable.
  • Multi-jurisdiction organisations should use a single escalation pathway and central case plan to manage all applicable reporting clocks.
  • Recordkeeping should capture dates, decisions, regulator communications, safety actions and reasons for any delay.
  • External investigators may need jurisdiction-specific private investigator licensing in NSW and WA, so that issue should be checked early.