Policy and governance framework: Investigating agencies, private security firms and organisations that may lawfully use surveillance devices should adopt a written compliance program that maps device types (listening, optical, tracking, data) against statutory permissions and exceptions in ss 4-8. The policy should record criteria for when consent suffices, when lawful interest applies, and when a warrant or emergency authority is required. The program should require legal review before installing or using devices where absence of consent is expected, and include escalation to a chief officer or legal counsel for potential warrant applications.
Warrant application practice and timelines: For tracking device uses, follow the chief officer application procedures in s 14 and ensure contemporaneous written records for non‑written applications and written confirmations within 24 hours (s 14(3)-(4)). For general warrants, prepare written applications with affidavits and appear before a judge unless the remote procedure under s 18 applies; if using the remote procedure, ensure telephone or electronic verification steps are completed immediately and an affidavit and duplicate warrant are forwarded as required under s 18(2)(e)-(f) and s 18(3). For emergency authorities, apply to the chief officer under s 20, document lawful grounds (imminent threat or serious drug offence), and maintain the two business day judicial confirmation timeline under s 22(1).
Recordkeeping, registers and reporting: Chief officers must comply with management and retention obligations in s 26 and maintain registers per s 29. Set up systems to capture required register fields: date of issue, period, judge name, applicant name or code, rank, subject names or descriptions, variation and renewal details, actual periods in force, arrests and prosecutions linked to device use (s 29(2)). Implement templates for the post‑warrant reports to the Minister, including the 3‑month report after a warrant ceases to be in force (s 30(1)(b)) and the annual returns by 30 June summary information and the Minister’s consolidated report to Parliament (s 30(1)(c), (5)-(6)).
Control of material and destruction: Follow s 31 obligations to keep records of applications, warrants and emergency authorities and to control, manage access to and destroy material derived from device use in accordance with the regulations. Establish secure storage, logging of access, and retention and destruction schedules aligned to the regulations and any judicial orders under s 23. If material is used in relevant investigations or proceedings, document chain of custody and legal bases for disclosure pursuant to ss 9 and 27.
Handling communications and media requests: Before communicating or publishing material derived from a device, confirm the relevant statutory exception. If publication is sought on public interest grounds, consider applying to a judge under s 11 for an order authorising publication and document the grounds and the manner of intended disclosure (s 11(1)-(2)). For licensed investigation agents and loss adjusters, ensure communications are limited to prescribed persons or circumstances or otherwise authorised by law (s 9(2)-(3)). Implement internal approval processes requiring legal sign‑off before disclosing material externally.
Code name management and safety protocols: Where safety concerns merit the use of code names, apply for and document code names as permitted by ss 18(4)(a)(iv), 19(3) and 21(3). Maintain a secure mapping of code names to identities accessible only to authorised personnel and ensure compliance with court rules for handling affidavits and warrant duplicates where code names are used (s 26(3)).
Training, delegation and internal authorisations: Train officers on the limits of delegation under s 35. Chief officers may delegate to senior officers only as defined; delegations must be in writing, may be conditional and are revocable (s 36(6)). Ensure delegations are documented and matched to authorised officer ranks and positions set out in the Act to avoid unauthorised decision‑making.
Declared device compliance and inventory tracking: Monitor the Gazette for ministerial notices under s 36. If a device or device class is declared, obtain ministerial consent published in the Gazette before possessing the device, and comply with any conditions or restrictions attached to the consent (s 36(3)-(5)). Keep inventories and acquisition records so that seizure risks under s 37 can be managed and devices can be returned if seized and no proceedings commence (s 37(3)).
Prepare for inspections and review agency interactions: Review agencies may inspect records at least once every six months and may compel information and attendance (ss 32-33). Designate staff to liaise with the review agency, prepare inspection bundles, and ensure timely compliance with information notices. Understand the limited evidentiary use of compelled answers and documents (s 33(5)) and the penalties for non‑compliance (s 33(7)-(8)).
Cross‑jurisdiction execution and corresponding warrants: If operating across state lines or in cooperation with other jurisdictions, verify whether the foreign law is a “corresponding law” declared by regulation before relying on cross‑jurisdiction warrants or emergency authorities (s 3 corresponding warrant/authority definitions; ss 24-25). Treat corresponding warrants as able to be executed in South Australia only in accordance with their terms and until cancelled (s 24(1)-(2)).
Legal review process and pre‑publication checklist: Establish a legal checklist to be completed before using, communicating, publishing or retaining material derived from surveillance devices. The checklist should verify statutory authority (consent or warrant/authority), record entries required by s 29, compliance with s 9 permitted recipients, any media authorisation or judicial order under s 11, code name approvals, and whether the material relates to a relevant investigation or relevant action or proceeding (s 3 definitions; ss 9-11, 27).
Regulatory monitoring and subordinate instruments: Assign responsibility for monitoring regulations made under s 41 and rules of court affecting warrant forms, the management of records and prescribed circumstances that interact with s 3 and ss 4-8. The details of excluded device classes and prescribed exemptions may be implemented by regulation rather than primary legislation, so compliance teams must track changes to subordinate instruments.
Audit trails, evidence preservation and chain of custody: Given evidentiary presumptions in s 39 and the potential for judicial challenges under s 23 where emergency authorities are exercised, maintain meticulous contemporaneous records of applications, verbal confirmations, affidavits, execution logs, device retrievals and chain of custody for all material seized or collected using surveillance devices.
By mapping statutory obligations in the Act to internal procedures and governance steps across authorisation, execution, reporting and oversight, regulated entities can reduce the risk of statutory contraventions and be ready to demonstrate compliance to review agencies and courts. Each operational decision that departs from ordinary consent‑based surveillance should be documented against the specific statutory basis relied upon, with prompt follow up where the Act requires subsequent court confirmation or reports.