The regulation is about prescribed data fields, auditability and specification of substantiating material for investigatory and coercive processes authorised by the Act. It introduces a menu of discrete factual elements, each treated as a required component of an application or report. The main concepts, as expressed in the regulation, are:

• Required factual specificity. Across warrant types (search, surveillance, covert search, additional powers) the regulation consistently requires the applicant to identify when and where applications were made, and when, where and by which court any warrants were issued if issued (secs.3-5, 10-16). This reduces reliance on generic statements and pushes applicants to provide temporally and geographically precise particulars.
• Activity and outcome mapping. The regulation mandates information linking the exercise of warrant powers to operational outcomes. Typical fields are whether any evidence was seized, the benefits derived from exercising powers (expressly including evidence seized and whether proceedings were started) and, for surveillance/ covert search, how the use of the power helped the investigation (secs.3-6, 10-16). The objects are traceability and an evidence-to-outcome trail.
• Differentiation by warrant function. The regulation recognises distinct warrant functions and tailors the information fields accordingly. For example, surveillance warrant entries require a description of the place and whether the warrant related to a person or place, and if a surveillance device was not installed, an explanation (secs.4, 11, 12). Covert search reports require particulars of anything photographed, inspected or tested and description of any order sought in relation to seized or photographed items (sec.6).
• Specificity for financial-investigative tools. Monitoring order and suspension order applications must identify the financial institution, the suspected serious crime related activity or derived property, the account names believed to be used, the nature of the information sought from the institution and the evidence supporting reasonable suspicion (secs.7 and 8). The regulation thereby links intelligence on financial accounts to the statutory thresholds in the Act and requires applicants to identify the type of information to be sought from financial institutions.
• Register and recordkeeping emphasis. Part 4 prescribes what information is to be captured for the register referenced in section 166(6) of the Act (secs.9-16). This provides a common standard for data capture for oversight and later audit.
• Procedural continuity and transitional matters. The regulation repeals the 2005 instrument (sec.21) but preserves its applicability to pending applications (sec.23) and provides rules for interpreting references to the repealed regulation in documents or other instruments (sec.24).

The wording of several provisions contains repeated or duplicated lines within the printed text. Those duplications do not change the listed items but may affect readability. The regulation frequently qualifies required entries with “if known” or “if and when” language, indicating that some fields are conditional on operational knowledge or events (see, for example, secs.3, 10-16). The instrument consistently links factual fields to the statutory provisions it supplements, referencing the Act’s section numbers where the prescribed information will be used (see sec.3 referencing s 86(4)(c), sec.4 referencing s 121(4)(c), sec.5 referencing s 148(3)(d), sec.6 referencing s 156(1), secs.7-8 referencing ss 119C and 119I, and sec.9 referencing s 166(6)).

The regulation affects a defined set of actors by mandating what information must be produced, recorded or included in applications and reports. The parties materially affected are:

• Applicants for warrants and orders. The regulation prescribes the specific factual material that must accompany applications for search warrants, surveillance warrants, covert search warrants, additional powers warrants and applications to extend such warrants (secs.3-5, 10-16, 12, 14, 16). Applicants will include commission officers and police officers exercising powers under the Act. The regulation requires the applicant to state their name and if a police officer to include their rank and registered number for certain applications (secs.7 and 8).
• Courts and decision-makers. Courts that issue warrants are named in the required fields (for example, applications and register entries must record the court that issued a warrant and when and where it was issued; secs.3-5, 10-16). The decision-maker receives the structured information the regulation prescribes, which is intended to support judicial oversight and review.
• The commission and its officers. The regulation repeatedly refers to “the commission” and “commission officer” functions under the Act. Commission officers who authorise disclosures, prepare covert search reports or execute seizure operations must ensure required particulars are recorded (secs.6, 17, 18). For disclosure of information under s 130(2)(f)(ii) or (g) of the Act, the regulation requires the names of disclosing officer and recipient, particulars of the information and timing (sec.17).
• Police officers. Where the person preparing a report is a police officer, the report must identify rank and registered number (sec.6). Receipts for seized property must include the commissioner officer details and, if a police officer, the officer’s rank (sec.18).
• Financial institutions and account holders. Applications for monitoring and suspension orders must identify the financial institution and the name or names in which relevant accounts are believed to be held and specify the type of information sought from the institution (secs.7 and 8). This creates an interface with private sector entities that may be required to provide information pursuant to monitoring or suspension orders made under the Act. The regulation does not itself compel institutions to produce information; it prescribes what must be stated in applications that, if granted under the Act, will impose obligations on those institutions.
• Persons or occupiers from whom items are seized. Receipts for seized property must include details about the person from whom the item was seized, or the occupier of an occupied place, if known (sec.18). This affects property holders by requiring a traceable chain of custody record.
• Agencies listed in schedule 1. Section 19 makes entities listed in schedule 1 into “declared agencies” for the Act’s schedule 2 definition of declared agency, subject to any schedule 1 restrictions. The text of schedule 1 is not included in the regulation excerpt here, but the provision affects entities that appear in that schedule (sec.19).
• Those relying on or referencing the repealed regulation. The instrument repeals the Crime and Corruption Regulation 2005 (sec.21) but preserves its application to pending applications that were made but not decided before commencement (sec.23). Documents that reference the repealed regulation may, where context permits, be taken to refer to this new regulation (sec.24). References in Acts and other statutory instruments are to be handled under the Acts Interpretation Act 1954 and Statutory Instruments Act 1992 as indicated (sec.24).

Who pays: the principal burdens of compliance fall on applicants (typically commission officers or police officers) who must produce the prescribed particulars; on those maintaining the register required by s 166(6) of the Act who must capture the prescribed information (Part 4); and on financial institutions and account holders when monitoring or suspension orders are pursued and the orders, if granted, require them to supply specified information. Who decides: courts and the commission retain decision-making authority under the Act; the regulation prescribes the information they may expect to receive. Behaviour change: applicants must document more specific operational and outcome-focused evidence; agencies must retain and record the prescribed data items for administrative and oversight purposes.

The regulation imposes a set of procedural duties , primarily information-provision duties , and clarifies certain rights to information and continuity of regulatory regimes. The duties and the contexts in which they arise are as follows:

Duties on applicants for warrants and orders

• Search warrant applications must include when and where the application was made, the suspected person if known, the type of offence or activity, whether the warrant was issued and, if so, the issuing court, duration, benefits derived from exercising the warrant (including evidence seized and proceedings started), and information about the return, destruction or disposal of seized evidence (sec.10). This is a content duty for the application and for the register entry prescribed by the Act.
• Surveillance warrant applications must state when and where the application was made, the name of the person (if known) believed by the chairman to be involved in corruption, a description of the place, the type of corruption, whether the warrant was issued and if so details of the issuing court, duration, benefits from exercising powers including any proceedings started because of surveillance device use, a brief description of how surveillance helped the investigation, whether powers were exercised and if no device was installed an explanation (sec.11). Extensions must report on previous use of powers, whether devices were installed and the benefits derived post-extension (sec.12).
• Covert search warrant applications require the application particulars to include when and where the application was made, the suspected person if known, a description of the place, the type of major crime, whether the warrant was issued and, if so, issuing court details, duration and benefits derived (including evidence seized and proceedings started) (sec.13). Extensions must explain whether powers were used before application, and if not why, and report benefits if extended (sec.14).
• Additional powers warrant applications must identify application date and place, the person being investigated and any suspected associate (if known), description of the place, the type of investigation (including terrorism-related corruption or crime), whether the warrant was issued and, if so, issuing court, duration, benefits and evidence copied or seized and any proceedings started (sec.15). Extensions must explain why copies or seizures did not occur if authorised and not used, and whether statutory declarations or affidavits required under the warrant were not sought and why (sec.16).
• Monitoring order and suspension order applications must include the applicant’s name and, if applicable, rank and registered number (secs.7 and 8). They must specify the named person, the financial institution, the serious crime related activity or derived property at issue, the information or evidence relied on to support reasonable suspicion that the named person was or is about to be involved or acquire serious crime derived property, the account names believed relevant, and the type of information the financial institution is to be required to give (secs.7 and 8).

Duties on commission officers preparing reports and receipts

• Reports on covert searches under s 156(1) of the Act must identify the report preparer (with police rank and registered number where applicable), state if and when powers were exercised, set out factual circumstances of compliance with the warrant and its conditions, list particulars of anything seized, photographed, inspected or tested, and describe any order sought in relation to seized or photographed items and the reason for the order (sec.6).
• Receipts for seized property under s 112(2) must include date and time of seizure, name/address/telephone of person from whom the thing was seized (if known), name/address/telephone of occupier if seized from an occupied place (if known), name/contact telephone number of the commission officer who seized the thing and police rank where applicable, where the thing will be taken if known, and the date the receipt is issued (sec.18).

Duties on the register and disclosure reporting

• Part 4 prescribes entries for the register under s 166(6) of the Act. The register must capture the information items specified in secs.10-16 for the relevant warrant types. This is a data-capture duty for the agency maintaining the register.
• Disclosure under s 130(2)(f)(ii) or (g) of the Act must be recorded to include the name of the commission officer who disclosed or authorised disclosure, the officer or declared agency to whom disclosure was made, brief particulars of the information disclosed and the reason for disclosure, and when disclosure occurred (sec.17).

Rights and constraints

• Continuity of rights under prior regulation. Section 23 preserves the repealed regulation’s application to applications made but not decided before commencement. This is a transitional protection that allows pending matters to proceed under the procedural framework that applied when they were made rather than being subject to new requirements unexpectedly (sec.23).
• Interpretation alignment. Section 24 provides that references to the repealed regulation in documents may be taken to refer to this regulation where context permits, and points to statutory interpretation provisions in the Acts Interpretation Act 1954 and the Statutory Instruments Act 1992 for references within Acts and statutory instruments (sec.24). This reduces technical discontinuities in legal drafting and administrative references.

Notably, the regulation itself does not create offences or specify penalties for failure to provide the required information within the regulation text. It prescribes content requirements that interact with the Act’s processes; any sanction for non-compliance or remedy will derive from the Act or other applicable law. The regulation frequently uses qualified language such as “if known” and “if and when” which recognises operational limits on what the applicant can state at the time of application or reporting (see, e.g., secs.3, 10-16).

The regulation contains no express penalty provisions within its text. It is entirely procedural and prescriptive of information content. Therefore the instrument does not itself create an offence, levy a fine, or establish a penalty regime. The enforcement and sanctioning consequences of non-compliance with the information requirements in this regulation are not set out here and must be sought in the Act or in other applicable legislation and administrative rules. Specific observations based on the regulation text are:

• No penalty clauses. Nowhere in the included sections (secs.1-24) does the regulation designate offences, maximum penalties, infringement notices, or administrative fines for failing to include prescribed information. The duties created are informational; the regulation leaves enforcement to the Act’s mechanisms or supervisory processes external to the regulation text.
• Reliance on the Act for legal effect. The regulation repeatedly links the prescribed information to specific sections of the Act (for example, sec.3 links to s 86(4)(c) of the Act; sec.4 links to s 121(4)(c); sec.5 links to s 148(3)(d); sec.6 links to s 156(1); secs.7 and 8 link to ss 119C and 119I; and sec.9 links to s 166(6)). Compliance significance therefore depends on how the Act treats failures to provide required information, whether by invalidating an application, permitting judicial scrutiny, or otherwise. The regulation itself does not specify those consequences.
• Administrative and evidentiary effects. The primary enforcement function of the regulation is administrative: it standardises the information that must be available for decision-makers and registers. Non-compliance may therefore produce administrative effects such as rejection of an application, a requirement to supply additional particulars, or an adverse inference in oversight processes. Those outcomes, however, would be grounded in the Act or in agency practice rather than in this regulation.
• Oversight transparency. By prescribing specific report and register fields (secs.6, 10-16, 17, 18), the regulation builds an audit trail and creates data that oversight bodies, courts or later review processes may use to examine compliance. For example, the covert search report items (sec.6) and the prescribed register entries (Part 4) are structured to enable post-facto review of whether detention, search, seizure, surveillance or financial monitoring activities produced lawful and effective results. The regulation thus increases the factual material available for enforcing legal standards set out elsewhere.
• Transitional protection for pending applications. Section 23 enforces continuity by allowing pending applications made under the repealed regulation to continue to be governed by that regime. This is an enforcement-protective measure for applicants caught between regulatory regimes rather than a penalty mechanism (sec.23).

Practitioners should therefore look to the Act and any agency policies for enforcement detail. The regulation should be understood as setting minimum content standards which, if unmet, will engage the Act’s procedural consequences or administrative handling rather than on-the-face penalties in the regulation.

The regulation is explicitly framed as subsidiary to the Act and functions by prescribing the form and content of material to be used under specific sections of the Act. Interaction with other laws follows two main pathways: (1) the Act’s substantive and procedural framework; and (2) statutory interpretation and instrument-reference rules for the repeal of the prior regulation.

Interaction with the Act

• The regulation directly supplements specific sections of the Act by prescribing the information that must be included in particular applications, reports and registers. The text references the Act repeatedly: see sec.3 referencing s 86(4)(c); sec.4 referencing s 121(4)(c); sec.5 referencing s 148(3)(d); sec.6 referencing s 156(1); secs.7 and 8 referencing ss 119C and 119I; sec.9 referencing s 166(6); sec.18 referencing s 112(2); sec.17 referencing s 130(2)(f)(ii) or (g). The regulation therefore operates as procedural detail for how the Act will be implemented on the ground.
• The regulation does not displace or alter the statutory thresholds or substantive legal tests in the Act. For example, where the Act requires reasonable suspicion or judicial authorisation for a warrant or order, the regulation prescribes what supporting factual materials must be provided with an application but does not change the legal threshold itself. Assessment of whether the threshold is met remains for the Act’s decision-maker.
• Where the Act provides for registers or reporting (e.g. s 166(6)), the regulation determines what entries must be recorded. Compliance obligations that follow from not recording or reporting as prescribed will depend on the Act’s enforcement or remedy provisions.

Interaction with statutory interpretation and other instruments

• The regulation repeals the Crime and Corruption Regulation 2005 (sec.21). Sections 23 and 24 address transitional application and references. Section 23 provides that applications made but not decided before commencement continue to be governed by the repealed regulation. Section 24 allows references to the repealed regulation in documents to be taken as references to this regulation where context permits and points to the Acts Interpretation Act 1954 s 14H for references in Acts and to the Statutory Instruments Act 1992 s 14(1) and schedule 1 for statutory instruments (sec.24). Those cross-references ensure continuity in statutory reading and avoid interpretive breaks where other legislation or instruments still reference the old regulation.
• The instrument’s annotation that s 20 was omitted in 2016 (s 20 om 2016 No. 62 s 58) signals an interaction with later amending instruments. Any statutory or regulatory environment that has amended or omitted parts of the regulation will affect how the regulation interacts with other laws. The omitted s 20 indicates an amendment history that must be accounted for when reconciling the regulation with other instruments.
• The regulation’s prescription of information to be required from financial institutions in monitoring and suspension order applications anticipates interaction with privacy, banking secrecy, and financial services laws in the event an order is granted under the Act. The regulation itself does not pre-empt the operation of those laws. The practical effect will be that, where a monitoring or suspension order is made under the Act, affected financial institutions must reconcile the statutory compulsion under the order with obligations under other laws. The regulation’s role is limited to ensuring the application identifies which institution, which accounts and what information is sought (secs.7 and 8).

Administrative interaction

• The regulation places recordkeeping duties on commission officers and applicants by specifying receipt and report contents (secs.6 and 18). Those records intersect with agency administrative law, evidence preservation obligations, freedom of information considerations and other administrative disclosure frameworks. How those regimes apply depends on statutory and policy overlays beyond the regulation itself.

In sum, the regulation is explicitly subordinate to the Act and acts as an instrument of implementation. It ensures that applications and reports made under the Act contain defined factual fields, and it sets transitional rules in relation to the prior regulation. It does not displace substantive duties in other laws, and its enforcement consequences depend on the Act and other legal frameworks that deal with misuse or non-compliance.

The regulation includes a small, concrete amendment and a structural change, and it repeals the predecessor regulation. The amendment history visible in the text is:

• Commencement: The regulation commences on 1 September 2015, as set out in sec.2. This is the fixed commencement date for the instrument’s operative effect.
• Repeal of predecessor: Section 21 repeals the Crime and Corruption Regulation 2005, SL No. 108. The regulation therefore replaced the 2005 instrument as the operative procedural regulation for the Act’s warrant, monitoring, suspension and related processes from its commencement date (sec.21).
• Transitional provisions: Sections 22-24 set out transitional arrangements and interpretive continuity. Section 22 defines “repealed regulation” as the repealed Crime and Corruption Regulation 2005 (sec.22). Section 23 applies to applications for warrants or warrant extensions that were made but not decided prior to commencement and preserves the continued application of the repealed regulation to those pending applications (sec.23). Section 24 addresses the interpretation of references to the repealed regulation in documents and points to the Acts Interpretation Act 1954 s 14H and the Statutory Instruments Act 1992 s 14(1) and schedule 1 for references in Acts and statutory instruments (sec.24).
• Later omission note: The text contains a marginal note that “s 20 om 2016 No. 62 s 58”. This indicates that section 20 was omitted by a 2016 amending instrument (No. 62) under s 58 of that amending instrument. Section 20 in the present text is simply the heading “Entities declared to be criminal organisations” and the marginal note indicates its omission occurred after initial commencement. No further detail on the content of the omitted provision is included in the text provided.
• No other amendments are recorded in the provided text. The remainder of the regulation is presented in its operative form, and many clauses repeat elements for readability or emphasis. The text contains duplication in a number of sections (for example, repeated bullets or repeated lines in secs.3-5 and secs.10-16). Those textual repetitions appear to be drafting duplications rather than substantive amendments.

Practical consequence for practitioners and administrators is to treat the 2005 Regulation as formally repealed as of the commencement date, except where pending applications are preserved by sec.23, and to note that one provision (s 20) has been removed by a later amending instrument in 2016. For statutory referencing, sec.24 directs attention to established interpretation provisions in the Acts Interpretation Act 1954 and the Statutory Instruments Act 1992 to resolve continuing references in other legislation or instruments.

The regulation text provided contains no reported litigation, case references or judicial interpretations. There are no cited decisions in the body of the regulation and no schedule or note that records litigation outcomes or authoritative interpretations. The practical implications of that absence, and the limited ways the regulation interacts with litigation practice, are:

• No direct judicial gloss within the instrument. Because the regulation does not include case law or interpretive guidance from courts, practitioners must rely on the plain text of the regulation and the Act for application requirements. Any ambiguity or operational dispute will need to be resolved either administratively, by agency policy, or through litigation in courts authorised to interpret the Act and its regulations.
• Potential for future litigation to test informational sufficiency. The regulation prescribes what information must be included in applications and reports. Courts may in future be asked to decide whether an application complied with the regulation’s content requirements and whether non-compliance affects the validity of a warrant, the admissibility of evidence, or procedural fairness. Such litigation would arise under the Act or in judicial review proceedings rather than under the regulation itself.
• Transitional litigation possibility. Section 23 preserves the repealed regulation’s application to pending matters. That transitional rule has potential to generate disputes about which regime applies to particular applications made close to the commencement date. Those disputes would be resolved by reference to the explicit language of sec.23 rather than any litigation history in the regulation.
• No recorded enforcement cases in the regulation. There is no textual indication of prosecutions, fines or administrative enforcement actions based on the regulation’s information prescriptions. Any enforcement consequences must therefore be sought in the Act or in external instruments and their litigation histories.

For practitioners, the absence of litigation history in the regulation highlights the need to proceed on the careful textual reading of the prescribed fields and to document compliance meticulously. If a party wishes to challenge whether an application complied with the regulation, judicial proceedings will depend on the Act’s procedural and judicial review architecture. The regulation’s content therefore sets a predictable checklist for what the court or decision maker will expect to see, and failure to meet those standards could form the factual basis for litigation about procedural compliance under the Act.

The regulation contains a number of practical traps and interpretive points that can cause operational friction if not anticipated. These are concrete items drawn strictly from the text:

• Conditional fields create evidentiary gaps. Many prescribed items are qualified with “if known” or “if and when” (see secs.3, 10-16, 18). Applicants must therefore document what they do not know as well as what they do know. Failure to explain an absence of information may be read as incomplete application material. Practitioners should ensure that statements such as “if known” are expressly addressed in the application when information is not available rather than leaving the field blank.
• Duplication and textual repetition. Several sections include repeated lines or duplicate bullets (for example secs.4-5 and secs.10-16). While the duplicated material does not alter the substantive prescription, the repetition can create confusion in drafting and cut-and-paste practice. Practitioners should avoid replicating duplication in templates and ensure a single, coherent set of particulars is provided to decision-makers.
• Register format and timing not specified. Part 4 prescribes the content to be captured in the register under s 166(6) of the Act but does not specify the register’s format, the time within which entries must be made, or how the register is to be made available or audited (secs.9-16). This omission leaves administrative discretion to the commission or relevant agency. Practitioners should ask agencies for the required templates and timelines rather than assuming the register will be contemporaneously updated in a particular way.
• Ambiguity about the evidentiary weight of “benefits derived”. Several provisions require applicants to state “the benefits derived from exercising powers under the warrant” and provide examples such as evidence seized or a proceeding started (secs.10, 11, 13, 15). The regulation does not define “benefits derived”, which could be read narrowly (for example, successful prosecution outcomes) or broadly (for any investigative lead). Applicants should clarify in the application what they mean by “benefits derived” and provide concrete factual examples to avoid misunderstanding.
• Interaction with privacy and third-party obligations. Monitoring and suspension order applications must identify specific account names and the type of information the financial institution is to be required to give (secs.7 and 8). The regulation does not address how those information requests intersect with privacy, secrecy or banking laws. If a monitoring or suspension order is made under the Act, financial institutions may face conflicting legal duties. Applicants should craft applications that balance specificity with awareness of third-party legal constraints and should consult those institutions’ compliance functions or seek judicial guidance where needed.
• No penalties in the regulation. Because the regulation does not provide enforcement mechanisms or penalties for non-compliance, it may not be immediately clear what consequence follows an incomplete application. The risk is administrative delay, return for further particulars or judicial rejection. Practitioners should assume that failure to comply will have procedural consequences under the Act and plan accordingly.
• Section 20 omission. The marginal note indicates s 20 was omitted in 2016 (s 20 om 2016 No. 62 s 58). The absence of the text for “Entities declared to be criminal organisations” as originally present may cause uncertainty if historical references relied on s 20. Practitioners should verify the current status of any entities formerly referenced in s 20 and check schedule 1 for declared agencies under sec.19.
• Transitional-limbo risk. Section 23 preserves the old regulation for pending applications. Parties handling matters straddling the commencement date must take care which regime applied at application time. That question may be material to whether an application is treated as compliant. Always record the application date and link it to the applicable regulatory regime (sec.23).
• “If a person is a police officer” drafting. Several duties depend on whether an individual is a police officer, which then requires additional identification information (e.g., rank and registered number; secs.6, 7, 8, 18). Administrative processes that assume all applicants are commission officers rather than police officers risk missing required identification data for police officers; templates should include conditional fields for police officer identity details.

These practical “gotchas” focus on the mechanics of complying with the regulation and on points likely to produce administrative delay or disputes. They do not invent legal consequences beyond the text; rather, they identify interpretive and operational risks that arise from the regulation’s drafting and its relationship with the Act and third-party laws.

Complying with the regulation requires adopting standardised application templates, robust recordkeeping and clear internal procedures to capture the conditional fields the instrument prescribes. The following actionable checklist is grounded in the regulation’s sections and designed for operational use by commission officers, police officers and lawyers preparing applications, reports and register entries.

General steps

1. Use a master checklist mapped to the regulation. Create a checklist that maps each information field in the regulation to a discrete line item in the application or report template. Sections to map include secs.3-6, 7-8, 10-16, 17-18.
2. Capture the “if known” fields explicitly. For any field qualified by “if known” or “if and when” (for example, suspect name, occupier contact details, whether powers were exercised), include an express entry such as “Not known at time of application” rather than leaving fields blank. This avoids ambiguity about whether the applicant neglected to search for the information.
3. Preserve contemporaneous evidence of the application date and place. The regulation repeatedly requires “when and where the application was made” and “when and where the warrant was issued” (secs.3-5, 10-16). Ensure applications and file records include timestamped copies of the application and court orders.

Specific templates and items to include

• Search warrant application and register entry (sec.10; sec.3 for information for s 86(4)(c)):
  • Date and place of application.
  • Suspected person, if known.
  • Type/nature of the offence or activity.
  • Whether the warrant was issued; if issued, the issuing court and place and date.
  • Duration the warrant was in force.
  • Benefits derived from exercising the warrant, with concrete examples (evidence seized, proceedings started).
  • Details of evidence seized and any return, destruction or disposal of seized evidence.
  • A field noting whether a proceeding was started because of the search.
• Surveillance warrant application and extension (secs.4, 11, 12):
  • Date/place of application.
  • Name of target person if the chairman reasonably believes that person has been or is likely to be involved in corruption.
  • Description of place targeted.
  • Type of corruption alleged.
  • If the warrant was issued, the issuing court and dates, duration in force.
  • Whether powers were exercised, and if not why a device was not installed.
  • Benefits derived from using the surveillance device, including whether proceedings resulted and how surveillance assisted the investigation.
  • For extension applications, include prior use of powers, reasons devices were not installed before, the date to which the warrant is sought to be extended and benefits after extension (sec.12).
• Covert search warrant application and report (secs.5, 13, 14, 6):
  • Application fields as per search warrants plus the specific requirement to describe if the warrant related to a person or place.
  • After execution, prepare a covert search report that includes the preparer’s name and police rank/registered number if applicable, exact times of exercise of powers, detailed compliance facts, particulars of anything seized/photographed/inspected/tested, and any order sought relating to seized or photographed items and the reasons (sec.6).
  • For extension applications, record whether powers were used before the application, and if not, provide a factual reason, date to which extension is sought and benefits derived after the extension (sec.14).
• Additional powers warrants and extensions (secs.15, 16):
  • Application must identify the person being investigated and any suspected associates, the place, the type of corruption/crime (including terrorism-related investigations where relevant), issuance details and the benefits derived from exercising powers such as copies/seizures and proceedings initiated.
  • Extension applications must explain why authorised powers to copy or seize records were not used, why required affidavits or declarations were not required under the warrant if that was authorised, whether the warrant was extended and the benefits post-extension (sec.16).
• Monitoring and suspension order applications (secs.7 and 8):
  • Applicant identification including rank/registered number for police applicants.
  • Named person, financial institution name, the serious crime related activity or serious crime derived property at issue.
  • Information or evidence supporting reasonable suspicion that the named person has been or is about to be involved in serious crime related activity or has or is about to acquire serious crime derived property.
  • The name(s) in which relevant accounts are believed to be held.
  • The type of information required of the financial institution.
  • For banks, preserve in a separate secure file any supporting affidavits or intelligence that form the evidentiary basis for the “reasonable suspicion” item.
• Disclosure reporting under s 130(2)(f)(ii) or (g) (sec.17):
  • Log the name of the commission officer who disclosed or authorised disclosure, the recipient officer or declared agency, brief particulars of information disclosed, the reason for disclosure and the time and date of disclosure.
  • Ensure this disclosure log is synchronised with the central register where appropriate.
• Receipt for seized property (sec.18):
  • Issue a receipt at the time of seizure that records date and time, person or occupier details if known, name and contact for the seizing commission officer with police rank if applicable, where the item will be taken if known, and the date the receipt is issued.

Recordkeeping and register maintenance

• Create a digital register template in line with secs.9-16. The register should have discrete fields for each prescribed item to ensure completeness and to facilitate audit and oversight. Confirm with the commission whether the register must be public or internal and what timeframes apply for entry.
• Maintain a folder for each application that includes the application form, supporting affidavits, the court’s warrant order (if issued) and post-execution reports such as the covert search report or seizure receipts.
• Time-stamp and retain originals. Keep original signed receipts for seized property and signed covert search reports. For entries that require officer rank and registration numbers, ensure a secure method for verifying and archiving those identifiers.

Administrative practice and quality control

• Use standardised templates but require a supervisory check. Because the regulation’s fields will be used by courts or oversight bodies, implement a supervisory sign-off to confirm that “benefits derived” are adequately described and that conditional items are either provided or explained as unknown.
• Train applicants on what “benefits derived” means in context. Provide examples drawn from the regulation’s own examples (evidence seized, a proceeding started) and encourage applicants to relate how the warrant materially advanced the investigation.
• Address privacy and third-party legal risks in advance. For monitoring and suspension applications involving financial institutions, coordinate with legal counsel to identify potential conflicts with privacy or bank secrecy rules and include mitigating statements or targeted requests for only the information necessary for the investigation to reduce friction when orders are made.
• Manage transitional matters. For any application made before 1 September 2015 and not decided before that date, treat the application under the repealed regulation per sec.23. Keep a clear docket noting the application date to avoid misapplication of the new regulation.

Audit readiness

• Prepare an audit trail for each matter, matching the required register fields to documentary evidence: application filings, warrants, execution reports, receipts, and disclosure logs. The regulation’s emphasis on “benefits derived” and specified particulars is designed to enable post-activity review; a well-structured file will make such review straightforward.

By following the above mapping from the regulation’s sections to concrete templates and checklists, agencies and practitioners will align operational practice to the regulation’s requirements and reduce the risk of incomplete applications or reporting gaps.