Urgent versus formal authority timing and documentation: Urgent authorities and urgent variation authorities may be granted orally, by telephone, fax, email or other means (ss 11(1)(b), 13(10)(b)). However, urgent authorities are limited to a shorter validity period (s 11(3)(i): urgent authorities not exceeding 7 days; formal authorities up to 3 months). Applicants who use urgent procedures must follow up with written records: the applicant must make a written record of an urgent application as soon as practicable and give it to the chief officer (s 9(6)), and the chief officer must ensure written notes are kept of particulars for each urgent authority (s 11(5)). Failure to reduce urgent actions to appropriate written form can undermine later proof of authorisation or compliance with the register requirements (ss 29-30) and potentially affect indemnity entitlement (s 19(2)(e)).
Delegation limits and who may decide: The chief officer's functions are generally non‑delegable (s 34(1)), but the statute permits delegation only to a defined set of senior officers (s 34(3)). Agencies must ensure that delegated signatories are within the statute's definition of "senior officer"; otherwise, decisions risk being legally vulnerable. Section 17 confirms that non‑material defects do not void an application or authority, but material defects will; delegation outside statute may be material.
Defect tolerance: Section 17 provides that applications and authorities are not invalidated by defects unless the defect affects the application/authority in a material particular. This reduces the availability of technical challenges, but it does not protect material non‑compliance with s 10(2) thresholds (for example, absence of reasonable grounds).
Inducement and entrapment line: The Act prohibits authorising or engaging in conduct that intentionally induces a person to commit an offence they would not otherwise have intended to commit (s 10(2)(g), s 18(b), s 19(2)(b)). However, the terms "induce" and "would not otherwise have intended" require fact‑sensitive assessments. Operational plans that actively create criminal intent in persons not otherwise predisposed risk breaching these prohibitions and thereby invalidating immunity and indemnity protections.
Civilian participant constraints: Civilian participants can be used, but the chief officer must be satisfied their role could not adequately be performed by a law enforcement officer (s 10(2)(i)), and civilians must follow law enforcement instructions to retain immunity/indemnity (s 18(d), s 19(2)(d)). Misclassification of civilian roles, poor training or failure to document instruction protocols may expose civilians to civil liability and erode indemnity coverage.
Recordkeeping and register detail: The Act requires retention of detailed documents (s 29) and a general register with extensive particulars (s 30(2)). Operators must ensure matching between assumed names/code names and true identities where used (s 11(4)). Failure to maintain the required register entries or to keep matching data can create gaps in statutory reporting, complicate inspections, indemnity claims and later evidentiary proof (s 33).
FOI and privacy carve‑outs and Parliamentary redaction: The Act excludes FOI, archives and personal information regimes from applying to operations and records under the Act (s 7(8)). Annual reports must not identify suspects or participants (s 28(5)), and Ministers may exclude material before tabling where disclosure could endanger safety, prejudice investigations/prosecutions, or compromise operational methodology (s 28(7)-(8)). These features limit transparency and can complicate external oversight and public scrutiny.
Scope of indemnity and regulatory preconditions: Indemnity under s 19(2) is subject to any requirements specified in the regulations (s 19(2)(e)). If agencies fail to comply with regulationally imposed preconditions (for example, training, documentation standards), indemnity may not be available. Users must check the regulations for those preconditions.
Mutual recognition mismatch risk: Section 25 applies the Act's provisions to corresponding authorities under corresponding laws "with any necessary changes." Where corresponding laws differ materially, agencies must ensure compatibility before relying on mutual recognition. The Act permits regulations to declare corresponding laws, but it does not supply a dispute resolution mechanism where laws conflict; operational cooperation therefore requires careful legal coordination.
Information disclosure criminalisation: The offence in s 26 has both actual knowledge and recklessness limbs. Especially for journalists, legal advisers, or agency staff, careless or reckless communications about operations can attract severe penalties (up to 10 years in aggravated cases, s 26(2)) if the disclosure is reckless as to endangering safety or prejudicing an operation. Agencies must train all staff on these obligations.
Exclusions for other investigative powers: Ss 18-19 do not apply to conduct authorisable under other laws governing searches, interception, forensic procedures and similar powers (s 20). Operations that simultaneously involve use of other statutory powers must be carefully structured to ensure the source of authority and the applicable protections or lack of protections are clear.
Timing constraints and reporting: Principal officers must report within two months of completion (s 27(1)); annual reports must be prepared by chief officers as soon as practicable after 30 July each year (s 28(1)). Inspection reports must be made within three months after the end of each financial year (s 32(4)). Non‑compliance with these timelines can trigger oversight criticism and complicate indemnity or defence positions in litigation.
Crown prosecution immunity: The Act binds the Crown (s 6(1)) but expressly provides that nothing in the Act makes the Crown liable to be prosecuted (s 6(2)). This split means the State cannot be criminally prosecuted under the Act, a nuance important when considering remedies and accountability.