The Regulation operationalises several core concepts that interface with the Act. These are defined or adopted in the instrument and drive who may act, what information flows, and what administrative duties arise.

• Monitoring device condition and monitoring information: The Regulation treats the “monitoring device condition” as an Act power subject to court imposition (see s 66B of the Act, referenced in s 1B and 1C). “Monitoring information” is defined in s 1F for the division: it includes information relating to a monitoring device or safety device, including alerts, notifications and a person’s geographical location. The concept imports location data into the statutory sharing regime and explicitly contemplates device alerts and notifications.
• Prescribed entities and specialist DFV service providers: The Regulation repeatedly uses the terms “prescribed entity” and “specialist DFV service provider” and cross‑references the Act’s definition for specialist DFV providers (s 169C of the Act, cited in s 1F). The text does not list prescribed entities in the Regulation, so the identity and scope of those entities depend on the Act or other subordinate instruments.
• Purpose‑limited sharing and use: Section 1G enumerates authorised purposes for sharing monitoring information, including administrative functions (fitting/removal and remote monitoring), compliance support, victim support (support/assistance), risk assessment and emergency response, and evaluation by the chief executive. Section 1M mirrors these as permitted uses for recipients and explicitly allows the chief executive to use monitoring information for evaluation of the policy’s effectiveness.
• Reasonable belief threshold for sharing in risk contexts: Sections 1J and 1K permit sharing between prescribed entities or specialist DFV service providers where the holder “reasonably believes” the information may help assess or lessen a serious threat to life, health or safety. The “reasonable belief” standard is a fact‑sensitive, potentially reviewable threshold directing an evidential inquiry before sharing.
• Limitations and safeguards: The Regulation incorporates the Act’s information‑sharing principles by reference (s 1H referring to s 169B(a)-(c) of the Act), and forbids giving monitoring information that is covered by s 169J(a)-(e) of the Act (s 1O). It also makes the police’s use of such information subject to the Act’s relevant operative provision (s 169L(2)-(5), applied by s 1P).
• Geographic and jurisdictional bounds: The instrument restricts which Magistrates Courts can impose monitoring device conditions (Caboolture and Townsville in s 1B) and then restricts the postcode ranges for respondent and aggrieved residential addresses where those courts may do so (s 1C). The Regulation also lists which interstate orders are treated as interstate orders for recognition purposes (s 3) and defines which New Zealand registered orders are to be treated as registered foreign orders (s 4).
• Publication carve‑outs: Section 2 allows publication under the Act’s publication power (s 159) where a proceeding is in the public domain or the community has a legitimate interest, and sets concrete tests for each (conviction after a DVO for public domain, and death/injury that results in death for community interest), while retaining the ban on publishing material that would identify a child.

These concepts convert statutory powers into operational decisions about who may capture and move sensitive location and device data, who may see or store it, the legal thresholds for sharing, and the recordkeeping and publication duties for courts and agencies. The Regulation deliberately aligns permitted data flows with discrete operational goals,fitting and monitoring devices, compliance facilitation, safety device distribution, risk assessment and emergency response, and policy evaluation,rather than establishing an open‑ended data exchange regime.

The Regulation’s scope touches multiple categories of actors: respondents and aggrieved or named persons in domestic and family violence matters, courts, prescribed entities, specialist DFV service providers, the chief executive (agency level), police, clerks of court, New South Wales, Northern Territory, Tasmanian, ACT, Victorian, South Australian and Western Australian statutory regimes (by recognition), and providers and operators of monitoring and safety devices.

• Respondents and aggrieved or named persons: Individuals who are the subject of domestic violence orders, or beneficiaries (aggrieved persons or named persons), are directly affected. The regulation authorises sharing monitoring information about respondents fitted with monitoring devices and sets conditions under which aggrieved or named persons may receive monitoring information (consent required for aggrieved/named persons under s 1L(2)). Respondents themselves may be given monitoring information relating to a monitoring device fitted to them (s 1L(1)). The Regulation also restricts which Magistrates Courts may impose monitoring device conditions depending on the postcode of the parties’ residential addresses (s 1C), so some persons will be eligible for monitoring device conditions only if their addresses fall within specified postcode ranges and the court is Caboolture or Townsville.
• Courts and clerks of court: Magistrates Courts are directly named as decision‑makers under s 66B of the Act, and the Regulation narrows which Magistrates Courts can impose monitoring device conditions (s 1B). Clerks of court are given an administrative duty to register New Zealand orders by entering details into a register (s 5).
• Prescribed entities and specialist DFV service providers: These bodies will receive, share, use, store and record monitoring information under the Regulation. They will need to make “reasonable belief” assessments for risk‑based sharing (ss 1J-1K), comply with the Act’s information‑sharing principles (s 1H), follow permitted use rules (s 1M), and record and store information only to the extent necessary to ensure compliance with a chief executive’s request (s 1Q). The Regulation therefore imposes operational, legal and data‑governance obligations on them.
• Chief executive and agency staff: The chief executive can make requests under s 66E(2) of the Act that prescribed entities must facilitate (see ss 1I and 1M). The chief executive may also use monitoring information to evaluate whether monitoring device conditions improve safety (s 1G(2) and 1M(2)). That creates an evaluative and coordinating role for the chief executive’s office.
• Police: The Regulation permits police to receive monitoring information from prescribed entities or specialist DFV service providers under ss 1I-1K, and makes police use subject to s 169L(2)-(5) of the Act (s 1P). Police will therefore have access to location and device alert data but their subsequent use and disclosure is constrained by the Act.
• Device suppliers and service operators: Entities that manufacture, supply, install or host monitoring devices and safety devices will be affected operationally, because the statutory regime contemplates remote monitoring, alerting and real‑time location information (s 1I(b)(i), (iii) and 1F definition). Although not named as “affected” persons in the Regulation, these commercial parties will need to interface with prescribed entities and specialist DFV service providers and meet expectations about data flows, access and reporting.
• Media and members of the public: Section 2 modifies publication rights under the Act and creates narrowly defined circumstances where publication is permitted , proceedings in the public domain (where a DVO was made and the person was later convicted of a related offence) or where the community has a legitimate interest (as defined by specified fatal or injurious incidents). Media outlets considering publication will need to apply these tests and avoid identifying children.

Who pays and bears operational costs is not spelled out in funding terms, but the distribution of duties indicates that prescribed entities, specialist DFV service providers and courts will incur administrative and compliance costs: recording and storing monitoring information “to the extent necessary” (s 1Q), assessing reasonable belief thresholds (ss 1J-1K), obtaining consent from aggrieved persons for sharing (s 1L(2)), and complying with chief executive requests (ss 1I and 1M). The chief executive’s evaluation function under s 1G and 1M creates analytical obligations (data collection, analysis), implying further administrative resource needs at the agency level. The clerk of court’s register duty (s 5) imposes a discrete administrative obligation on court staff.

The Regulation sets out explicit duties, rights and legal thresholds for parties who handle monitoring information, courts considering monitoring device conditions, and officials registering or publishing information.

Duties

• Courts (Magistrates Courts): Only the Magistrates Courts in Caboolture and Townsville are listed as courts that can impose a monitoring device condition under s 66B of the Act (s 1B). Further, when those courts impose a monitoring device condition, they must ensure that both the respondent’s and the aggrieved’s postcodes are within specified ranges (s 1C). This imposes a substantive eligibility duty on those courts when applying the s 66B power.
• Prescribed entities and specialist DFV service providers: Have duties to share monitoring information to facilitate compliance with a chief executive’s request under s 66E(2) (s 1I). They must apply the Act’s information‑sharing principles when deciding whether to share (s 1H). They are permitted to record and store monitoring information only to the extent necessary to ensure compliance with a request under s 66E(2) (s 1Q). They must not give monitoring information if it falls within the categories protected by s 169J(a)-(e) of the Act (s 1O). Section 1N imports s 169H(2)-(3) of the Act in relation to who may give or receive monitoring information on behalf of the relevant entity, which imposes further statutory constraints on representative arrangements and authorisation for staff or contractors.
• Chief executive: May make requests under s 66E(2) of the Act, and may use monitoring information given under the division to evaluate whether imposing monitoring device conditions has been effective in improving safety (s 1G(2) and s 1M(2)). This creates an administrative duty to design and conduct evaluation activity and to set requests that prescribed entities must facilitate.
• Clerks of court: Must register New Zealand orders by entering details of the order in a register kept for registering New Zealand orders (s 5).
• Police: When police receive monitoring information from a prescribed entity or specialist DFV service provider under ss 1I-1K, the Act’s operative provisions (s 169L(2)-(5)) apply to police use of the information (s 1P), placing limits on how police may use or disclose the material.

Rights and permissions

• Right to receive monitoring information: Prescribed entities and specialist DFV service providers may receive and exchange monitoring information in specified circumstances: to facilitate compliance with chief executive requests (s 1I), to assess or respond to serious threats where they reasonably believe the information may help (ss 1J-1K), and to share with respondents fitted with a monitoring device or with aggrieved/named persons who consent (s 1L).
• Use of monitoring information: Recipients may use monitoring information to the extent necessary to comply with a chief executive request (s 1M(a)), assess whether there is a serious threat (s 1M(b)), or lessen or prevent a serious threat (s 1M(c)). Contacting or offering assistance to involved persons is explicitly permitted as ways to lessen or prevent serious threats (s 1M(1)(c)).
• Consent requirement for aggrieved/named persons: A prescribed entity or service provider may share monitoring information with an aggrieved or named person only if that person consents to being given the information (s 1L(2)). This is a strict consent gate for victim/beneficiary disclosures.
• Publishing certain proceedings: Publication that would otherwise be restricted by the Act is permitted where the proceeding is in the public domain (a DVO was made and the person was later convicted of a factually related offence) or where the community has a legitimate interest as defined by fatal or injurious incidents (s 2), subject to the absolute restriction on identifying children.

Standards and thresholds

• “Reasonable belief” threshold: Sections 1J and 1K require that a holder must reasonably believe the monitoring information may help another prescribed entity or specialist DFV service provider to assess or to lessen or prevent a serious threat. This is an objective, contextual standard requiring an assessment of the probative value of the information against the potential intrusion of sharing.
• “Extent necessary” limits: Multiple provisions condition recording, storing and use of monitoring information on being “to the extent necessary” to comply with chief executive requests (s 1Q) or to achieve permitted uses (s 1M). That phrasing imports a proportionality constraint into recording and storage practices.

Interplay with Act sections

• The Regulation is functionally subordinate to multiple Act provisions. It specifies courts for s 66B (s 1B), prescribes matters for s 66F via a division (s 1E), and cross‑references Act limits on information that cannot be shared (s 169J) and operational police provisions (s 169L). Practitioners and compliance officers therefore must read the Regulation and the cited sections of the Act together to form the complete set of duties and rights.

In practice, duties fall on courts and relevant entities to apply postcode and geographic eligibility rules, to apply consent and reasonable belief gates for sharing, and to limit recording and storage to what is necessary for compliance and evaluation. Rights to receive and use monitoring information are tightly circumscribed and conditioned on statutory thresholds and consent where relevant.

The Regulation itself sets out permissions, duties and limits but does not create standalone criminal penalties in the text provided. Its enforcement and penalties are therefore likely to arise through the Act’s enforcement framework and other directly applicable statutory provisions that govern misuse or unauthorised disclosure of protected information. The Regulation does, however, structure enforceable obligations in ways that create compliance responsibilities with potential consequences under the Act or other laws.

• Delegated enforcement via the Act: Several provisions of the Regulation import sections of the Act (for example s 169H, s 169J and s 169L) and require prescribed entities to act in accordance with those sections. Any penalty or remedy for non‑compliance with those Act provisions would therefore be governed by the Act. The Regulation does not redefine or add penalties; it channels data flows into the Act’s enforcement matrix.
• Police constraints and accountability: Section 1P applies s 169L(2)-(5) of the Act to police use of monitoring information received under the division. While the Regulation does not itself describe sanctions, the application of s 169L likely brings statutory prohibitions, reporting or evidence admissibility rules that police must follow; any breach by police would be addressed under the Act’s mechanisms (internal disciplinary processes, judicial oversight or statutory offence provisions, if in the Act).
• Limits on sharing and possible consequences: Section 1O forbids giving monitoring information if it is information to which s 169J(a)-(e) of the Act applies. That prohibition creates a compliance boundary; contravening it would be an act of unauthorised disclosure. Consequences for such unauthorised disclosures are not restated in the Regulation, so remedies and sanctions will be those provided in the Act and relevant privacy or confidentiality laws.
• Administrative obligations with potential operational consequences: Duties such as registering New Zealand orders in a register (s 5), applying postcode eligibility (s 1C) and obtaining consent from aggrieved or named persons before sharing monitoring information (s 1L(2)) are administrative duties. Non‑compliance could produce procedural challenges, judicial scrutiny of orders, or undermine admissibility or lawfulness of device conditions; these downstream effects are mechanisms of enforcement even if not penal in the Regulation.
• Recordkeeping and proportionality tests: The Regulation repeatedly uses “to the extent necessary” language for recording and storage (s 1Q) and for permitted uses (s 1M). That language informs what constitutes lawful processing; excessive retention or use beyond necessity may attract regulatory action under the Act, the Privacy Act regime (if applicable to the entity), or other supervisory mechanisms.

Because the Regulation does not itself enumerate new criminal offences or monetary penalties, enforcement will operate through (a) compliance with the Act’s restrictions and sanctions, (b) internal and statutory oversight of police and prescribed entities, (c) judicial review or challenge where procedural or substantive duties are breached, and (d) privacy and data‑protection law remedies where applicable. Practitioners should therefore map the Regulation’s duties onto the Act’s enforcement sections (including those cited in the Regulation) and the general legal framework for information handling to identify specific sanctions and remedies.

The Regulation functions as a subordinate instrument to the Domestic and Family Violence Protection Act and explicitly links to several of the Act’s sections. It also interfaces with other State and interstate legislation by declaring which interstate and registered foreign orders will be recognised under the Act. Key points on interaction follow.

• Direct integration with the Act: The Regulation repeatedly cross‑references and imports operative standards from the Act. Examples include:
  • Courts’ power to impose monitoring device conditions is exercised under s 66B of the Act; the Regulation specifies which Magistrates Courts can exercise that power (s 1B) and sets postcode eligibility rules (s 1C).
  • The division on monitoring information prescribes matters for s 66F of the Act (s 1E). It imports the Act’s information‑sharing principles (s 169B) and other Act provisions (s 169H, s 169J, s 169L) to constrain who may act, what can be shared, and how police may use such information (ss 1H, 1N, 1O, 1P).
  • The chief executive’s request power under s 66E(2) of the Act is operationalised by the Regulation, which permits prescribed entities and specialist DFV service providers to share monitoring information to facilitate compliance (s 1I).
• Privacy, data protection and evidentiary law: The Regulation imports duties that implicate personal information (location data, alerts and device notifications). The Regulation’s “extent necessary” and “reasonable belief” thresholds function as proportionality and necessity tests. While the Regulation does not mention the Privacy Act or state privacy laws, entities handling monitoring information should assess interactions with privacy legislation, data‑security obligations and data breach notification requirements. The Regulation’s prohibition on sharing information covered by s 169J(a)-(e) of the Act (s 1O) adds an additional statutory constraint; the content of s 169J must be checked for privacy‑sensitive categories.
• Police powers and criminal law interface: The Regulation permits police to receive monitoring information but applies s 169L(2)-(5) of the Act to police use (s 1P). That connects the monitoring data regime to operational policing, criminal investigation, and potential evidentiary uses. Any secondary uses of monitoring data must be assessed against those Act provisions and usual criminal law safeguards (chain of custody, warrants if required, admissibility rules).
• Inter‑jurisdictional recognition of orders: Sections 3 and 4 declare specific interstate orders (NSW, NT, Tas, ACT, Vic, SA, WA) to be interstate orders, and certain registered New Zealand orders to be registered foreign orders. This creates statutory recognition for orders made under various interstate and New Zealand statutes, reducing jurisdictional friction in enforcement and giving statutory certainty about which foreign or interstate instruments are treated as equivalent for the Act’s purposes. The clerk’s registration duty for New Zealand orders (s 5) operationalises this recognition.
• Publication law and suppression: Section 2 authorises publication under s 159 of the Act in narrowly defined circumstances (public domain or community interest), while preserving the Act’s prohibition on identifying children. This interacts with media law, suppression orders, open justice principles and the Act’s protective objectives: publication rights are expanded only in tightly defined factual circumstances.
• Administrative law and oversight: The chief executive’s evaluative use of monitoring information (s 1G(2), s 1M(2)) creates an administrative function that will intersect with public sector records and evaluation obligations, including transparency and oversight frameworks that govern public agencies.
• Transitional interaction with criminal law amendments: Section 7 provides a transitional rule for the Criminal Law (Coercive Control and Affirmative Consent) and Other Legislation Amendment Act 2024, by limiting the reference to conviction in s 2(3)(b) of the Act to convictions where the charge was laid after commencement. This ensures the interaction between the regulation’s publication test and the amended criminal offence timing is clarified.

In summary, the Regulation is tightly integrated with the Act and interacts with policing, administrative, privacy, evidentiary, and inter‑jurisdictional recognition frameworks. Because it delegates operational permissions and constraints to a combination of the chief executive, prescribed entities and police, compatibility with other statutory obligations (privacy laws, criminal procedure, and inter‑jurisdictional instruments) must be checked in each implementation context.

The Regulation text contains multiple amendment notations that show recent insertions and changes and a temporal provision. Below are the amendment markers and what they indicate in the Regulation’s text.

• Insertions in 2025: Several provisions show the annotation “ins 2025 SL No. 129 s 6”, indicating those sections were inserted by Statutory Instrument No. 129 of 2025, section 6. The following sections carry that insertion annotation: s 1A (definitions), pt 2-div 1 sections such as s 1B to s 1D, pt 2-div 2 sections s 1E to s 1Q, and possibly s 1N-1Q. These inserted provisions implement detailed monitoring information sharing rules and the court/postcode regime for Caboolture and Townsville.
• Expiry notation for s 1D: Section 1D is noted as inserted in 2025 and has an expiry date: “exp 31 January 2026 (see s 1D(2))”. The Regulation therefore contains at least one time‑limited provision. The content of s 1D is not shown in the excerpt, but the expiry indicates a transitional or temporary measure.
• Amendment in 2024: Section 2 carries “amd 2024 Act No. 5 s 53”, indicating an amendment was made by the Criminal Law (Coercive Control and Affirmative Consent) and Other Legislation Amendment Act 2024 (Act No. 5 of 2024), section 53. Section 7 of this Regulation is noted as inserted by that same 2024 Act (s 7 ins 2024 Act No. 5 s 54), which provides the transitional rule about convictions being limited to charges laid after commencement.
• Omissions: Section 6 is labelled “om 2025 SL No. 129 s 7”, indicating section 6 has been omitted by the 2025 statutory instrument. The presence of this marker shows the Regulation has been actively edited and parts removed.

What the annotations imply about legislative development and implementation risks

• Recent and staged change: The inserted sections and expiry notation suggest the monitoring‑device and monitoring‑information provisions are recent interventions with some temporary components (e.g. s 1D expiring 31 January 2026). Practitioners should expect ongoing legislative activity in this area and verify the current version of the Regulation before acting.
• Linked amendments: Amendments interact with the 2024 criminal law amendment, creating transitional rules (s 7) to clarify temporal application of publication eligibility where convictions are relevant. This indicates co‑ordination between the Act’s publication limits and criminal law changes.
• Administrative roll‑out: The batch of insertions by the 2025 Statutory Instrument No. 129 suggests a policy package introduced in a single instrument; some elements (postcode‑limited court powers, detailed sharing rules) were staged as subordinate instruments rather than primary Act amendments. This may reflect an implementation choice to enable procedural detail to be iterated without re‑opening the principal Act.

For compliance and advice, readers should check the official consolidated version of the Regulation and the Act to capture any subsequent amendments, expirations, or re‑inclusions that follow the 2025 insertions and the 2024 Act changes. The Regulation’s amendment history shows active, recent change and a mix of permanent and time‑limited provisions that affect operational planning.

The Regulation text does not name any cases nor report any judicial decisions concerning its provisions. It contains no references to litigation, judicial interpretation, or precedent. Therefore, based solely on the Regulation text provided:

• There is no litigation history recorded in the instrument. The Regulation does not cite or rely on judicial decisions to explain or contextualise its provisions.
• Because the Regulation imports standards from the Act (for example s 169B, s 169H, s 169J, s 169L), litigation that interprets those Act provisions may indirectly affect how the Regulation is implemented, but the Regulation itself contains no case law references. Practitioners must therefore look to judicial decisions concerning the Act or the cited Act sections for interpretive guidance; none are provided in the Regulation.
• The Regulation’s reliance on terms such as “reasonably believes” and “to the extent necessary” creates factual and legal standards that are ordinarily amenable to judicial review and civil challenge. The absence of litigation history in the text does not mean these provisions will not be litigated; it only means there are no cases recorded in the instrument.
• The Regulation’s limits on publication (s 2) and its postcode restrictions on where monitoring device conditions may be imposed (s 1C) are the kinds of provisions that could be subject to judicial review or challenge on procedural, administrative law or human rights grounds in future. Again, the Regulation does not document any such proceedings.

If a practitioner requires precedent or judicial interpretation, they must search case law on the relevant Act provisions (for example s 66B, s 66E, ss 169B, 169H, 169J, 169L) and on analogous information‑sharing or surveillance regimes. The Regulation itself provides no litigation path, and any assessment of how courts have treated these kinds of provisions must be sourced from external case law databases and judicial decisions, not from the Regulation text.

Several practical and legal pitfalls arise on the face of the Regulation. These are not evaluative judgments but identification of potential operational, legal and compliance traps that practitioners and agencies should note and mitigate.

• Postcode and court eligibility complexity: Sections 1B and 1C constrain which Magistrates Courts can impose monitoring device conditions and impose postcode matching requirements for respondent and aggrieved addresses. Practitioners or parties may expect that a local Magistrates Court can impose monitoring device conditions; here, only Caboolture and Townsville are prescribed for that power (s 1B), and only if both parties’ postcodes fall within listed ranges (s 1C). The requirement that the aggrieved’s residential address be “a postcode mentioned in paragraph (a)” (s 1C(2)(b) and (4)(b)) can create logistical or transfer issues when parties’ addresses cross postcode boundaries, or when the last known residential address is used (s 1C(5)). Failure to verify postcode eligibility risks orders being made in excess of the Regulation’s prescribed bounds.
• Consent gate for aggrieved/named persons: Under s 1L(2), monitoring information may be shared with an aggrieved or named person only if that person consents. This creates a strict consent requirement that must be documented. Practitioners must not assume implied consent; written and informed consent processes will be necessary to rely on this disclosure route.
• “Reasonably believes” as a fact‑sensitive test: Sections 1J and 1K permit sharing where the holder “reasonably believes” the information may help another entity to assess or lessen a serious threat. The Regulation does not define “reasonable belief” or set a required evidential baseline. That vagueness creates legal uncertainty and potential exposure to review: recipients must document the basis for their reasonable belief to demonstrate compliance. Absent robust recording, a reasonable belief decision may be vulnerable to challenge.
• Limits on storage and retention: Recording and storage are allowed “to the extent necessary to ensure compliance with a request made by the chief executive under section 66E(2) of the Act” (s 1Q). The “extent necessary” formulation implies proportionality and minimisation requirements; storing more data than necessary may breach the Regulation or the Act. Entities should avoid blanket retention and instead adopt narrow retention rules tied to specific requests.
• Overlap with protected categories in s 169J: Section 1O forbids giving monitoring information if it falls within s 169J(a)-(e) of the Act. Because the regulation excerpt does not reproduce s 169J, practitioners must check the Act to know what material is protected. Failure to cross‑check could result in unlawful disclosures.
• Police use constraints: Section 1P applies s 169L(2)-(5) of the Act to police receiving monitoring information. The Regulation therefore allows police receipt but binds police use to other Act limits. Agencies and practitioners must communicate and co‑ordinate with police to ensure data is used for the permitted purposes only. Misuse by police could complicate investigations or evidence admissibility.
• Evaluation access and data flows to chief executive: Sections 1G(2) and 1M(2) permit sharing with the chief executive for evaluation of whether monitoring device conditions are effective. Those clauses may create pressure for additional data collection and aggregation, requiring data governance arrangements that protect privacy and limit secondary use. Entities may face competing obligations: to share for evaluation versus to safeguard privacy and consent.
• Interaction with publication rules and timing of convictions: Section 2 allows some publication but links the “public domain” test to convictions “later” arising from the DVO or related offending. Section 7 clarifies that reference to a conviction in s 2(3)(b) is to a conviction where the charge was laid after the commencement. This temporal nuance could be missed and lead to premature publication that breaches the Act’s publication controls.
• Temporary provisions and expiry: Section 1D has an expiry date (31 January 2026). The presence of a temporary provision means implementation plans must account for the effect of expiration. If s 1D supports other operational features, its expiry may create transitional ambiguity.
• Delegation and authorisation: Section 1N applies s 169H(2)-(3) of the Act in relation to who may give or receive monitoring information on behalf of an entity. The Regulation excerpt does not reproduce s 169H, so entities must consult the Act for rules about delegation and authorised officers; improper delegation could render an exchange unlawful.

These “gotchas” point to required diligence: verify postcode eligibility before seeking monitoring device conditions; secure and record informed consent from aggrieved persons before sharing; document reasonable belief assessments; adopt minimal retention practices tied to chief executive requests; cross‑check s 169J and s 169H in the Act for protected categories and delegation rules; and watch for temporal rules affecting publication and the expiry of temporary provisions.

Below is a practical compliance checklist and operational steps mapped to the Regulation’s sections. This is a source‑grounded, concrete set of actions for courts, prescribed entities, specialist DFV service providers, clerks of court and police receiving monitoring information.

1. Read the Act sections referenced by the Regulation before implementation

   • Mandatory step: obtain and read s 66B (monitoring device conditions), s 66E(2) (chief executive requests), s 66F (information relating to monitoring device conditions), s 169B (information‑sharing principles), s 169C (definition of specialist DFV service provider), s 169H (authorisations), s 169J (protected information), and s 169L (police use). The Regulation repeatedly cross‑references these Act sections (see ss 1B-1Q). Compliance requires their integrated application.

2. For courts (Magistrates Courts)

   • Confirm court authority: If seeking to impose a monitoring device condition under the Act, confirm the court is prescribed in s 1B. Only the Magistrates Courts held in Caboolture and Townsville are listed.
   • Verify postcode eligibility: Before imposing a monitoring device condition in those courts, verify both the respondent’s and the aggrieved’s residential addresses fall within the specific postcode lists in s 1C. Remember “residential address” includes last known address (s 1C(5)).
   • Document eligibility: Record the postcode checks in court file notes and order templates to show compliance with s 1C.

3. For prescribed entities and specialist DFV service providers

   • Map internal roles: Identify who in the organisation is authorised to give, receive and use monitoring information in accordance with s 169H, applied via s 1N. Ensure authorisations are documented to satisfy s 169H(2)-(3) as applied.
   • Implement consent procedures: For sharing monitoring information with aggrieved or named persons, obtain express consent as required by s 1L(2). Consent should be informed, recorded and revocable. Do not share without documented consent.
   • Reasonable belief decision‑making: For sharing under ss 1J-1K, develop a checklist or standard operating procedure that records the factual basis for any “reasonable belief” that the information will help another entity assess or lessen a serious threat. Keep contemporaneous notes to support a reasonableness assessment.
   • Facilitate chief executive requests: When the chief executive makes a request under s 66E(2), share monitoring information to the extent necessary to comply (s 1I). Establish secure channels for such requests and a documentation trail showing minimisation of data disclosed.
   • Minimise storage and retention: Record and store monitoring information only “to the extent necessary” to comply with the chief executive request (s 1Q). Draft retention schedules tied to specific requests and delete excess data promptly.
   • Apply information‑sharing principles: Ensure all disclosures are made “having regard to” the same principles mentioned in s 169B(a), (b) and (c) of the Act (s 1H). Incorporate those principles into policies (for example, necessity, proportionality and confidentiality obligations).
   • Protect prohibited categories: Before giving monitoring information to another entity, check whether s 169J(a)-(e) of the Act applies; if it does, do not disclose (s 1O). Maintain an escalation pathway to legal counsel for borderline cases.
   • Data security: Implement encryption, access controls and audit trails for monitoring information to prevent unauthorised access. Log all shares and recipients for auditability.

4. For police

   • Understand Act constraints: If receiving monitoring information under ss 1I-1K, ensure police officers apply s 169L(2)-(5) as imported by s 1P. Police must adhere to any use, disclosure or retention limitations in those Act provisions.
   • Evidence handling: If data is to be used for investigation or admissibility in court, maintain chain‑of‑custody protocols and document how the information was obtained under the Regulation.

5. For clerks of court and registry staff

   • Register New Zealand orders: On receipt of a New Zealand order that must be registered under the Act, enter details in the register kept for registering New Zealand orders as required by s 5. Maintain metadata about registration dates, issuing NZ court, and order type.
   • Publication clearance: If a media request or publication is contemplated under s 2, confirm that the proceeding satisfies either the “public domain” test (DVO and later conviction of a factually related offence as in s 2(3)(a)) or the “community legitimate interest” test (specified death/injury facts in s 2(3)(b)). Do not permit publication that would identify or likely identify a child (s 2(5)).

6. For device suppliers and operators

   • Contractual controls: Enter contracts with prescribed entities and specialist DFV service providers that specify data flows, retention, security, obligations to assist with fitting/removal and remote monitoring, and obligations to supply alerts in formats consistent with s 1I(b) and s 1I(b)(vi).
   • Data minimisation: Provide only the monitoring information necessary for the purpose requested. Retain logs of what was provided and why.

7. For agencies involved in chief executive evaluation

   • Data governance for evaluation: When using monitoring information to evaluate effectiveness (s 1G(2), s 1M(2)), ensure evaluation plans specify the minimal data required, anonymisation where practicable, ethical approvals if needed, and secure analytical environments.
   • Reporting and transparency: Document the use of monitoring information for evaluation and prepare to justify the necessity of data flows if challenged.

8. Publication compliance

   • Apply temporal rule: Under s 7, the reference to a conviction in s 2(3)(b) is limited to convictions where the charge was laid after commencement. Check charge and conviction timing before permitting publication.
   • Child identification prohibition: Explicitly screen proposed publications to avoid identifying a child; if identification risk exists, refuse disclosure (s 2(5)).

9. Training and recordkeeping

   • Train staff: Provide role‑specific training for prescribed entities, specialist DFV service providers, police and court staff on the Regulation’s thresholds and consent and documentation requirements.
   • Keep logs: Maintain written logs of requests from the chief executive, reasonable belief assessments, consent records, disclosures made, data retention actions and register entries.

10. Legal advice and escalation

• Seek counsel for edge cases: For borderline questions,whether information is covered by s 169J, whether a reasonable belief is supportable, whether publication meets the tests in s 2,seek timely legal advice. Keep written legal advice on file for audit trail and defence.

Following these steps and documenting decisions will create an auditable compliance trail that reflects the Regulation’s proportionality, consent and necessity constraints. The Regulation ties sharing and storage to specific statutory triggers and thresholds; compliance requires aligning operational procedures with those triggers and with the underlying Act provisions cited throughout the instrument.