Crimes (Assumed Identities) Regulations 2016

The Regulations operate by specification and cross‑reference. They do not institute new powers but clarify who, and which external laws, fall within the scope of the Crimes (Assumed Identities) Act 2004.

Key conceptual devices in the text are:

• Cross‑reference definitions: regulation 5 imports statutory meanings by reference. Specifically, "Chief Executive Officer" is the person appointed under s 33 of the Independent Broad‑based Anti‑corruption Commission Act 2011, "Deputy Commissioner" and "IBAC Officer" are given the same meanings as in that Act, and "police officer" is given the same meaning as in the Victoria Police Act 2013. The mechanism is one of incorporation rather than independent definition, so interpretive questions about status or rank turn on the source Acts.
• Correspondence mapping: regulation 6 and Schedule 1 declare certain laws in other jurisdictions to be "corresponding laws" for the Crimes (Assumed Identities) Act 2004. Each Schedule entry pairs a jurisdiction (Column 1) with a named enactment (Column 2). The declared corresponding laws include Commonwealth Part IAC of the Crimes Act 1914 and named state and territory Acts or Parts (for example, the ACT Crimes (Assumed Identities) Act 2009, NSW Law Enforcement and National Security (Assumed Identities) Act 2010, and others listed in Schedule 1).
• Role classifications for IBAC: regulation 7 prescribes which positions and classes of employees fall within the statutory term "prescribed IBAC Officer" under the Act. The list comprises specific senior positions (Commissioner, Deputy Commissioner, Chief Executive Officer), IBAC Officers classified as Executive Officers, IBAC Officers classified as non‑executive employees, police officers engaged by IBAC, and members of police forces of other jurisdictions engaged by IBAC.
• Supervisor and senior officer categories: regulation 8 prescribes which positions may be appointed as supervisors under the Act’s supervision provision (section 5(4)(c) of the Act). It distinguishes among Chief Executive Officer, IBAC Executive Officers, IBAC non‑executive employees Grade 6 or Senior Technical Specialists, police engaged by IBAC who are sergeant or above, and equivalent ranks for engaged interstate police. Regulation 9 prescribes which positions are "senior officers" for the Act’s definition in s 34(5), namely Deputy Commissioner, Chief Executive Officer, and IBAC Executive Officers.

These concepts are administrative and classificatory. The Regulations set the legal identity of particular roles and laws for the Act’s mechanics: who may be authorised, who may supervise, and which external statutes count as corresponding. Because the instrument achieves its effect mainly by reference to other Acts and to internal IBAC classifications, the meaning of its terms is tethered to those other instruments' content and to IBAC’s HR classification framework.

The instrument primarily affects public bodies and officials, with secondary operational implications for organisations that interact with IBAC assumed‑identity operations.

Directly affected persons and entities:

• The Independent Broad‑based Anti‑corruption Commission (IBAC). The Regulations prescribe which IBAC positions and classes of employees are "prescribed IBAC Officers" (regulation 7), who can be supervisors (regulation 8), and which positions count as senior officers (regulation 9). These prescriptions determine internal authorisation, supervision and seniority structures for any activity carried out under the Crimes (Assumed Identities) Act 2004.
• IBAC‑engaged police officers. Regulation 7(f) and 7(g) expressly include police officers engaged by IBAC and members of a police force or police service of another jurisdiction engaged by IBAC among the prescribed IBAC Officers. Regulation 8(d) and 8(e) limit supervisors among police to those who are officers of or above the rank of sergeant. Those provisions affect police personnel both in Victoria and in other jurisdictions who are seconded or contracted into IBAC operations.
• Police services and police employers. Because the Regulations treat engaged police as IBAC Officers for the Act’s purposes, police agencies that supply personnel to IBAC will need to record and manage any obligations and role expectations arising from assumed‑identity operations, including maintaining the rank threshold for supervisors.
• Administrators responsible for classification and HR at IBAC. The Regulations rely on internal staff classifications (executive, non‑executive, Grade 6, Senior Technical Specialists). Those who assign classifications, maintain payroll codes and manage positions are affected because those classifications determine who may supervise or exercise senior‑officer functions under the Act.
• Legal and compliance teams within IBAC and partner agencies. Counsel, compliance officers and operational managers must consult these Regulations alongside the Crimes (Assumed Identities) Act 2004 to determine legal authority and supervisory lines for assumed‑identity operations.
• Agencies in other jurisdictions listed in Schedule 1. The Regulations declare specific enactments in other jurisdictions to be "corresponding laws" for the Act. That declaration affects how cross‑jurisdictional personnel and operations are treated under the Act; it also affects the legal footing for interstate cooperation or recognition when personnel from those jurisdictions are engaged by IBAC.

Indirectly affected parties:

• Subjects of assumed‑identity operations. While the Regulations do not create substantive powers or offence provisions, they help define who may lawfully be authorised or supervised under the Act. That has the downstream effect of determining which persons may take on assumed identities in operational contexts governed by the Act.
• External oversight, audit and parliamentary scrutiny bodies. The Regulations change the legal framework that oversight bodies must evaluate when auditing assumed‑identity use. The Endnotes indicate the statutory instrument and its sunset date; those facts are relevant for parliamentary or oversight scheduling.

Who bears the direct administrative and compliance costs: primary costs fall on IBAC to maintain classifications, to ensure correct appointment of supervisors and senior officers, and to ensure any engaged police meet the rank criteria. Costs also fall on police services supplying personnel to IBAC, who must confirm rank and engagement status. The Regulations do not impose obligations on private sector entities directly; their effect is felt through public agency practice.

The Regulations are prescriptive: they identify who exercises duties and who holds positions with rights under the Crimes (Assumed Identities) Act 2004. They do not themselves create operational duties, procedural steps, or rights independent of the Act, but they define the persons to whom statutory duties and rights in the Act attach.

Who may exercise statutory functions

• Prescribed IBAC Officers: regulation 7 identifies which IBAC positions and classes of employees are "prescribed IBAC Officer" for the Act. Where the Act gives powers, protections or duties to prescribed IBAC Officers, those functions attach to the persons and classes listed in regulation 7(a) to 7(g). For example, if the Act requires a prescribed IBAC Officer to approve an application, that approval function applies to those listed categories.
• Supervisors: regulation 8 prescribes who can be appointed as supervisors under s 5(4)(c) of the Act. The specified supervisors are the Chief Executive Officer, IBAC Executive Officers, certain non‑executive employees (Grade 6 or Senior Technical Specialists), and police engaged by IBAC who are sergeant or above, including equivalent interstate ranks. Where the Act imposes supervisory duties or requires supervisor approval, those duties fall to these categories.
• Senior officers: regulation 9 prescribes who is a "senior officer" for the definition in s 34(5) of the Act. The listed positions are Deputy Commissioner, Chief Executive Officer and IBAC Executive Officers. Any statutory rights or duties in the Act conditioned on a "senior officer" apply to these persons.

Rights and entitlements

• Legal status conferred for Act purposes: persons meeting the prescribed categories receive whatever statutory protections, immunities or authorisations the Crimes (Assumed Identities) Act 2004 confers on those roles. The Regulations determine who is entitled to claim those Act‑based legal positions by naming the roles and classes (regulation 7-9).
• Inter‑jurisdictional recognition: by declaring corresponding laws in Schedule 1, the Regulations set a legal foundation for recognising certain interstate or Commonwealth assumed‑identity provisions when the Act relies on the concept of a "corresponding law" (regulation 6, Schedule 1). That recognition can affect rights and procedural requirements for interstate cooperation or personnel engagement.

Duties implied by the Regulations

• Administrative duty to classify and maintain evidence: although not phrased as a duty within the Regulations, the practical effect is that IBAC must maintain accurate staff classifications (executive/non‑executive/Grade 6/Senior Technical Specialist) so that the statutory tests in regulations 7-9 can be applied. The text prescribes categories; operational compliance requires record‑keeping.
• Rank verification for police supervisors: regulation 8(d) and 8(e) set a substantive threshold: police supervisors must be of or above the rank of sergeant. Where the Act requires a supervisor, the duty to ensure that the supervisor meets this rank standard falls on the engaging agency.

Limits and boundaries

• No delegation of Act content: the Regulations do not expand or alter the substantive powers in the Crimes (Assumed Identities) Act 2004. They construe the Act’s terms by specifying which persons and laws are relevant, but duties and rights arise from the Act itself.
• Dependence on other enactments: for precise contours of certain titles and ranks the Regulations depend on definitions in the Independent Broad‑based Anti‑corruption Commission Act 2011 and the Victoria Police Act 2013 (regulation 5). Consequently, the rights and duties that attach to "Chief Executive Officer", "IBAC Officer" and "police officer" depend on how those source Acts define and treat the terms.

In sum, the Regulations determine which persons are empowered, obliged or protected under the Crimes (Assumed Identities) Act 2004 by prescribing named positions and classification categories, and by mapping corresponding interstate laws. Practical compliance therefore requires cross‑checking these prescriptions against the Act and the source Acts for precise operational effect.

The Regulations themselves contain no offence, penalty or enforcement machinery. They are classificatory and declaratory instruments made under s 35 of the Crimes (Assumed Identities) Act 2004 (regulation 2). Any criminal or administrative penalties, enforcement mechanisms or oversight provisions relevant to assumed‑identity activities come from the parent Act or from other substantive statutes, not from these Regulations.

What the source explicitly shows

• Absence of penal provisions: none of regulations 1-9 imposes criminal penalties, fines, or specific enforcement procedures. The Schedule likewise lists corresponding laws but does not introduce enforcement rules.
• Role of the Act for enforcement: because these Regulations exist "for the purposes of" the Crimes (Assumed Identities) Act 2004 (regulation 1), enforcement of duties created by the Act will depend on the Act’s text. Where the Act conditions a power or immunity on an authorised or prescribed person, these Regulations identify the persons who meet that condition, but any penalty for misuse would be in the Act or other applicable law.
• Administrative consequences: while not penal, non‑compliance with the Regulations’ prescriptions could mean that a person acting under the assumption they are authorised under the Act is in fact not a prescribed IBAC Officer, supervisor or senior officer. That factual misalignment could expose the person or the agency to legal consequences under the Act or civil exposure; the Regulations themselves do not create an enforcement right but materially affect legal status.

Enforcement lines to consider operationally

• Verification and audit: the practical enforcement mechanism is likely administrative verification and internal oversight. Agencies will need to check that their supervisors and senior officers meet the rank or classification thresholds in regulations 7-9 as a matter of operational governance.
• Interplay with corresponding laws: if an interstate or Commonwealth law listed in Schedule 1 is relied on in a particular operation, any enforcement or penalty regime under that corresponding law will remain with the law named in Schedule 1, not these Regulations. The Regulations merely declare those laws to be corresponding laws for the purpose of the Act (regulation 6 and Schedule 1).
• Sunset and continuity risks: the Endnotes state the Regulations will sunset 10 years after making (Endnote 1). If not renewed or remade, the legal status conferred by these Regulations (the list of prescribed officers, supervisors and corresponding laws) may lapse, potentially producing enforcement and compliance uncertainty. Any enforcement or operational reliance should account for that statutory expiry date.

Practical advice for enforcement planning must therefore start with the Crimes (Assumed Identities) Act 2004 to locate penalties, and then use these Regulations to identify the persons and external laws to whom those Act provisions attach. The Regulations do not supply enforcement hooks; they supply the identity map for where enforcement and accountability will fall under the Act.

The Regulations are explicitly connective: they operate by reference to other Victorian Acts and by declaring specified Commonwealth and interstate enactments to be "corresponding laws" for the Crimes (Assumed Identities) Act 2004. Their meaning and practical effect therefore depend on reading them in conjunction with those other statutes.

Cross‑references and incorporations

• Independent Broad‑based Anti‑corruption Commission Act 2011: regulation 5 imports meanings from that Act for "Chief Executive Officer", "Deputy Commissioner" and "IBAC Officer". The Regulations then proceed to prescribe which IBAC positions and classes fall within the Act’s definitions by naming posts and classification grades that exist under the IBAC Act or IBAC’s internal classifications (regulations 7 and 9). To interpret who qualifies as an Executive Officer or non‑executive employee, the IBAC Act and IBAC’s classification scheme must be consulted.
• Victoria Police Act 2013: regulation 5 incorporates the definition of "police officer" from the Victoria Police Act 2013. That connection affects which police personnel engaged by IBAC are treated as prescribed IBAC Officers under regulation 7 and which police meet the supervisory rank threshold in regulation 8.
• Crimes (Assumed Identities) Act 2004: the Regulations are made under s 35 of that Act (regulation 2) and declare matters for the purposes of the Act (regulation 1). Several provisions in the Act rely on definitions such as "prescribed IBAC Officer", "supervisor" and "senior officer"; the Regulations specify those terms. For full operational understanding, the Act is the primary source; the Regulations identify the persons and external enactments that the Act references.
• Schedule 1 corresponding laws: regulation 6 and Schedule 1 list, by jurisdiction, the enactments declared to correspond to the Crimes (Assumed Identities) Act 2004. For example, the Commonwealth is linked to Part IAC of the Crimes Act 1914; New South Wales is linked to the Law Enforcement and National Security (Assumed Identities) Act 2010; Western Australia to Part 3 of the Criminal Investigation (Covert Powers) Act 2012, and so on. These declarations affect cross‑jurisdictional recognition and cooperation under the Act by specifying which foreign statutory schemes the Act treats as equivalent for prescribed purposes.

Interpretative and operational implications

• Dependent interpretation: because regulation 5 imports meanings from other Acts, any change in those source Acts, or differing terms used across jurisdictions, may alter who qualifies under these Regulations. For example, an alteration to the definition of "Executive Officer" in the IBAC Act or to the rank structure in the Victoria Police Act could change who is a prescribed IBAC Officer.
• Static mapping of corresponding laws: Schedule 1 is a static list in the regulation. If a jurisdiction amends or renames its corresponding enactment, or replaces it with a different legal regime, the regulation will need to be amended to reflect the change. Until amended, the Schedule remains the operative list, which may lag behind legislative change in other jurisdictions.
• Interaction with Interpretation of Legislation Act 1984: the Endnotes reproduce matters of interpretation under the ILA (for example, that headings, notes and punctuation form part of the instrument from 1 January 2001) and confirm that explanatory materials printed after Endnotes do not form part of the Statutory Rule (Endnote 1). That affects how one reads these Regulations and any inserted notes.
• Revocation and continuity: regulation 4 revokes earlier subordinate rules, replacing or updating the prior statutory configuration. This shows the Regulations function as the operative specification until further amendment or revocation.

Practical consequence for lawyers and compliance professionals: to apply the Crimes (Assumed Identities) Act 2004 in any operational context, you must read the Act together with these Regulations and the source Acts cited in regulation 5 and Schedule 1. The Regulations allocate legal identity and cross‑jurisdictional equivalence; the substantive powers, limits and penalties remain in the Act and in the corresponding laws listed in the Schedule.

The Regulations present a narrow amendment record in their Endnotes and text. The operative instrument is Version No. 001 as at 22 June 2016.

What the instrument records about amendments

• Revocation of earlier instruments: regulation 4 explicitly revokes three earlier instruments: the Crimes (Assumed Identities) Regulations 2006 (S.R. No. 74/2006) and two 2013 amendment instruments (S.R. Nos 10/2013 and 93/2013). The Explanatory Details in the Endnotes identify which instruments are being revoked and cross‑reference the relevant Statutory Rule numbers. This repeal indicates the 2016 Regulations superseded prior subordinate legislation on the same subject matter (regulation 4; Endnotes 4).
• No subsequent amendments recorded: Endnote 2, the Table of Amendments, states that there are no amendments made to the Crimes (Assumed Identities) Regulations 2016 by statutory rules, subordinate instruments or Acts. Endnote 3 notes there are no amendments not in operation at the date of publication. Therefore, as at the version date included in the document (22 June 2016), the instrument is in its original form and unchanged since making.
• Commencement and making: the Endnotes state the Regulations were made on 21 June 2016 by Governor in Council under s 35 of the Crimes (Assumed Identities) Act 2004 and came into operation on 22 June 2016 (regulation 3, Endnote 1).
• Sunset provision applicable via Subordinate Legislation Act: Endnote 1 records that the Regulations "will sunset 10 years after the day of making on 21 June 2026 (see section 5 of the Subordinate Legislation Act 1994)". That puts a legislated expiry on the instrument unless it is remade or a saving provision is enacted. The instrument itself does not extend or vary that sunset; it records it.

Implications of the recorded amendment history

• Stability to date: there is no recorded amendment after initial making, so the lists and prescriptive categories in regulations 5-9 and Schedule 1 have remained as made.
• Revision pathway: the revocation of prior subordinate instruments in regulation 4 shows that these Regulations are the vehicle used to update the statutory lists and prescriptions. Future changes to the set of corresponding laws, or to which posts count as prescribed or supervisory, will require a new subordinate instrument to be made under the empowering section of the parent Act.
• Time‑limited authority: the automatic sunset in 2026 creates a legislated endpoint for the instrument unless remade. Agencies planning long‑term operational arrangements that rely on these Regulations should account for the expiry and consider legislative or administrative steps required to maintain continuity beyond the sunset date.

For drafting and compliance teams, the operational takeaway is to monitor for any successor instruments before the 2026 sunset and to be prepared to seek amending instruments if other jurisdictions change their corresponding laws or if internal classification schemes are reorganised.

The Regulations’ Endnotes and the body of the instrument contain no reference to case law, litigation, determinations, or judicial interpretation. There are no cases named in the instrument. The Explanatory Details and Table of Amendments list only prior statutory instruments and do not record any judicial review or Court consideration.

Facts from the source on litigation

• No reported litigation referenced: neither the Regulations nor the accompanying Endnotes set out any litigation. Endnote 2’s Table of Amendments confirms there are no subordinate instruments or Acts that have amended the Regulations; it does not record court activity.
• No citations to case law: the text does not cite judicial decisions or provide interpretative examples, and the instrument does not include examples or notes that would suggest how courts have applied it.

Operational consequence

• Absence of judicial guidance: because the Regulations are silent on litigation history, users cannot rely on precedents interpreting the precise interplay between these Regulations and the Crimes (Assumed Identities) Act 2004. Any interpretive ambiguity arising, for example, from classification boundaries (what counts as an Executive Officer or Grade 6) or from the scope of "corresponding law" is not clarified by judicial commentary in the instrument.
• Reliance on primary Acts and administrative practice: in the absence of reported cases, practical interpretation will depend on the primary statutes (the Crimes (Assumed Identities) Act 2004, the IBAC Act, the Victoria Police Act 2013), administrative guidance or internal IBAC practice. If contested, judicial resolution would start from those primary sources with the Regulations as a statutory specification.

If legal certainty is required in contentious operational circumstances, stakeholders will need to rely on legal analysis of the Act together with the Regulations, and, where necessary, seek declaratory relief or other judicial determination because there is no litigation history recited in the instrument to guide interpretation.

The Regulations are compact, but several practical pitfalls and points of interpretive caution arise from their structure and cross‑references. These matters are not speculative; they follow directly from how the Regulations operate by incorporation and static prescription.

1. Reliance on external definitions

• The Regulations import key terms from the Independent Broad‑based Anti‑corruption Commission Act 2011 and the Victoria Police Act 2013 (regulation 5). If those source Acts use classifications or rank structures that differ in practice or are amended, the list in the Regulations must be read against them. Practical consequence: you must consult the IBAC Act and Victoria Police Act when determining who counts under the Regulations.

2. Internal classification labels matter

• The Regulations refer to IBAC classification labels such as "Executive Officers", "non‑executive employees Grade 6", and "Senior Technical Specialists" (regulations 7 and 8). These HR classifications are internal to IBAC and may not be self‑evident. Gotcha: operational staff may assume a title satisfies the test when it is the classification code that matters. Maintain HR records linking staff to the relevant classification.

3. Rank threshold for police supervisors

• For police engaged by IBAC to serve as supervisors, the Regulations require officers to be "of or above the rank of sergeant" (regulation 8(d) and 8(e)). Gotcha: police ranks vary across jurisdictions. The Regulations treat interstate members similarly only if engaged by IBAC and of equivalent rank. Verify rank equivalence and engagement status before relying on a police member as a supervisor.

4. Static list of corresponding laws

• Schedule 1 is a static list naming the corresponding laws in each jurisdiction (regulation 6 and Schedule 1). Gotcha: if another jurisdiction amends, renames or replaces its statute governing assumed identities, Schedule 1 will not reflect that until the Regulations are amended. Do not assume that an up‑to‑date interstate regime is captured without checking the text of the Schedule.

5. Sunset date

• The Endnotes record the statutory sunset on 21 June 2026 (Endnote 1). Gotcha: operational continuity beyond that date requires remaking or replacement. Planning for multi‑year programs must factor in the expiry risk.

6. No standalone procedural detail

• The Regulations do not set out operational procedures for authorisations, record‑keeping, or oversight. Gotcha: absence of procedural prescription means agencies must refer to the parent Act and to internal policies; there is no procedural checklist in the Regulations themselves.

7. Revocation history and transition

• The Regulations revoke earlier instruments (regulation 4), but they do not contain transitional provisions explaining how pre‑existing authorisations under the revoked instruments are to be treated. Gotcha: where an operation started under prior rules, agencies should confirm continuity of authorisations and whether transitional measures under the Act apply.

8. Ambiguity in titles vs classifications

• The Regulations name specific positions (Commissioner, Deputy Commissioner, Chief Executive Officer) and broader classes (IBAC Officers classified as Executive Officers). Gotcha: a person with a particular title may not be in the classification intended by the Regulation. Clear mapping between title and classification is essential.

9. Engagement vs employment

• Regulation 7 includes "police officers engaged by the IBAC" and "members of the police force or police service (however described) of another jurisdiction who are engaged by the IBAC" (regulation 7(f)-(g)). Gotcha: the distinction between being "engaged" and being otherwise seconded, contracted or merely cooperating should be settled in writing to confirm whether a person is a prescribed IBAC Officer.

10. Interpretive weight of Endnotes and explanatory materials

• The Endnotes make it clear that explanatory material printed after Endnotes does not form part of the Statutory Rule (Endnote 1). Gotcha: reliance on appended explanatory memorandum or table of provisions as legal text is misplaced; only the Regulations and the parts that form part of the Statutory Rule have legal effect.

These are concrete, documentable issues that arise when operationalising these Regulations. They indicate where legal and administrative attention should be focused to avoid misapplication or gaps in authority.

Compliance requires combining statutory reading, HR alignment, record‑keeping and interagency verification. Below are concrete steps grounded in the Regulations (regulations 1-9, Schedule 1) and the instrument’s Endnotes.

1. Map roles to the Regulations

• Identify all IBAC positions and employees who perform functions under the Crimes (Assumed Identities) Act 2004. Then map each person to the categories in regulation 7 (Commissioner, Deputy Commissioner, Chief Executive Officer, Executive Officers, non‑executive employees, police engaged by IBAC, interstate police engaged by IBAC).
• Maintain a register that records for each person: name, position, IBAC classification code (executive/non‑executive/Grade level/Senior Technical Specialist), and employment/engagement dates. The Register is the operational ledger for determining who is a "prescribed IBAC Officer".

2. Verify HR classifications and grades

• Ensure Human Resources documentation links job titles to the IBAC classification bands referenced in regulations 7 and 8. Where the Regulations refer to "non‑executive employees Grade 6 or Senior Technical Specialists" (regulation 8(c)), keep explicit records showing which individuals are in those grades.

3. Confirm police engagement and rank

• Before assigning supervisory roles, confirm whether engaged police are of or above the rank of sergeant, as regulation 8(d) and 8(e) require. For interstate police engaged by IBAC, obtain written evidence of rank and engagement status. Where police are seconded from another jurisdiction, secure written terms that establish the engagement relationship.

4. Use the Schedule to check corresponding laws for interstate operations

• If an operation relies on cross‑jurisdictional legal equivalence, consult Schedule 1 to confirm the listed corresponding law for the relevant jurisdiction (regulation 6 and Schedule 1). If a jurisdiction is not listed or its law has changed, seek legal advice and consider applying for an amendment to the Regulations if reliance is necessary.

5. Update governance documents and delegations

• Record in IBAC's governance instruments (delegations, authorisations, policies) who can act as supervisors and senior officers as defined in regulations 8 and 9. Where the Act requires a supervisor’s authorisation, set internal processes that ensure only persons meeting the prescribed criteria sign off.

6. Maintain documentary proof for audit and legal review

• Keep contemporaneous records demonstrating that a person who acted under assumed‑identity authorisation was a prescribed IBAC Officer or a valid supervisor at the time, including HR classification printouts, rank confirmations for police and formal engagement agreements. Such documentation will be essential if legal status is challenged or audited.

7. Monitor legislative change and the sunset date

• Assign responsibility to a legal or regulatory affairs officer to monitor changes in the IBAC Act, Victoria Police Act, and the statutes listed in Schedule 1. Also track the 21 June 2026 sunset noted in the Endnotes and plan to seek extension or remake ahead of expiry to avoid legal gaps.

8. Train operational staff

• Provide training to operational staff and supervisors about who is authorised under the Act and the Regulations. Training should emphasise the classification and rank thresholds and the need for documentary verification before assumed‑identity activity.

9. Plan for transition when internal reclassification occurs

• If IBAC reorganises position classifications or if police rank structures change, ensure that any personnel affected are re‑mapped against the Regulations’ categories and that operational authorisations are revalidated.

10. Legal review before novel operations

• For operations involving interstate personnel or cross‑jurisdictional reliance on corresponding laws, obtain legal advice to confirm that the particular facts fit the Schedule’s mappings and that all prescribed persons are properly appointed and supervised under regulation 8.

Concrete documents and artefacts to keep

• A maintained Prescribed Officers Register with classification evidence.
• Copies of engagement agreements for any police engaged by IBAC.
• Delegations and authorisations showing which persons are authorised supervisors or senior officers.
• Rank confirmation documents for interstate police.
• A monitoring log for legislative change affecting the IBAC Act, Victoria Police Act, and laws listed in Schedule 1.
• Training records and operational checklists used before commencing assumed‑identity activity.

By following these steps and grounding operational decisions in the specific regulatory text (regulations 5-9 and Schedule 1), agencies can show adherence to the precise prescriptions the Regulations make for the Crimes (Assumed Identities) Act 2004.