Police Complaints and Discipline Regulations 2017

The regulations revolve around a small set of recurring concepts that structure procedural duties.

• Designated officer. The regulations repeatedly address "designated officers" (for example, Schedule 1 item 1, reg 7). The code of conduct in Schedule 3 sets out the substantive standards expected of such officers (honesty, proper exercise of authority, confidentiality, conflict of interest rules and so on). Reg 7(2) converts breaches of that code, or attempts to procure breaches, into disciplinary breaches under the Act.
• IIS and complaint management system (CMS). The IIS is the body responsible for assessment, allocation and recording of complaints and reports. The CMS is the electronic or other record-keeping system; Schedule 2 prescribes the exact kinds of data the IIS must place on the CMS at particular points, and time limits for doing so (see reg 6 and Schedule 2 items 1-17).
• Resolution officer and management resolution. Regulation 4 and Schedule 1 item 1 require resolution officers (those conducting management resolutions under the Act’s section 19) to produce signed reports containing detailed information about the resolution reached, the nature of any remedial training, restrictions, counselling or reprimands, and the resolution officer’s view of impacts and risks.
• Section 21(14) investigating officer. The regulations distinguish (reg 5 and Schedule 1 items 2-4) between investigations conducted by IIS and those conducted by external or other police officers pursuant to s 21(14) of the Act. When a police officer assists or conducts an investigation under s 21(14), the officer must provide the IIS with initial details (within two weeks), fortnightly progress updates, and the final report and recommendations as soon as practicable (Schedule 1 items 2-4). Subregulation 5(2) limits the reporting obligation where the officer is only assisting, not conducting the investigation, to what is reasonably ascertainable in that assisting role.
• Time-critical data flows. The regulations impose a mix of fixed maximum delays and "as soon as reasonably practicable" obligations. Examples include 48 hours for IIS CMS entries on some investigation inputs (Schedule 2 items 5-7), within 7 days for initial complaint entry (Schedule 2 item 1), fortnightly updates for s 21(14) investigating officers after the initial details (Schedule 1 item 3), monthly updates for other investigating officers (Schedule 2 item 10), and the 90-day maximum written communication interval to complainants and designated officers (reg 8).
• Tribunal/Register process flows. The regulations set the procedure and timing for admissions and denials to notices of allegation: an admission or denial must be made to the registrar within 21 days of service (reg 12(1)); admissions are to be forwarded by the registrar to the Commissioner and the IIS (reg 12(2)); an admission triggers the Commissioner’s obligation to consider mitigation (reg 12(3)); denials or non-admission lead the Tribunal to fix a hearing time and place (reg 12(4)). The CMS must record particulars of admissions, Tribunal findings, Commissioner actions and appeals within specified timeframes (Schedule 2 items 12-17, 13-14).
• Discipline sanctions mechanics. The Commissioner’s authority to impose discipline is operationalised: service of a notice of allegation must be in person (reg 10(1)) and the Commissioner may require attendance (reg 10(2)); suspension remuneration entitlement and the manner of calculation is for the Commissioner to determine (reg 11(1)) and withheld remuneration may be denied following a guilty finding unless special circumstances exist (reg 11(2)(b)); fines prescribed for particular disciplinary heads are set at $1 250 and the Commissioner may manage payment and deductions (reg 13).

Those concepts are implemented through prescriptive data fields in Schedules 1 and 2 and through a code of conduct in Schedule 3. The regulations therefore operate at the junction of evidence/information management, time-bound administrative action and internal disciplinary process.

The regulations identify a defined and fairly concentrated set of actors and inform the obligations and entitlements of each.

• Designated officers. Frequently named across the document, designated officers are the primary subject of complaints, investigations and potential disciplinary action. The code of conduct in Schedule 3 sets substantive behavioral obligations that, if contravened or if there is an attempt to contravene, are treated as breaches under the Act (reg 7(2); Schedule 3). Designated officers are affected by operational rules governing notice, service and suspension (regs 10-12), and by the Commissioner’s discretion on remuneration and fines (regs 11, 13).
• Resolution officers. Those conducting management resolutions must produce signed reports containing detailed content (reg 4; Schedule 1 item 1). The report must cover the resolution, any remedial training or restrictions, reasons for no further action, and the resolution officer’s assessment of risks and impact on SA Police and the community.
• Section 21(14) investigating officers. If a police officer is required under s 21(14) of the Act to assist IIS or to conduct an investigation, that officer must provide specified information in specified timeframes (reg 5; Schedule 1 items 2-4). The regulation limits the obligation where the officer is only assisting to what is reasonably ascertainable (reg 5(2)).
• IIS and officer in charge of the IIS. The officer in charge of the IIS, or a delegated member, must ensure that specified information is included on the CMS at prescribed times and in prescribed manners (reg 6; Schedule 2). This places ongoing recording and timetabling duties on the IIS leadership.
• Complainants and witnesses. The regulations impose recording duties when a complaint is made (reg 9; Schedule 2 item 1). Complainants must be kept informed in writing at least every 90 days of progress and resolution (reg 8).
• Commissioner. The Commissioner is given multiple operational discretions and duties: to sanction designated officers (reg 13), to determine suspension remuneration and whether withheld remuneration is payable on revocation (reg 11), to require attendance for service of notices (reg 10(2)), and to consider mitigation after an admission (reg 12(3)). The Commissioner also must be forwarded admissions by the Tribunal registrar (reg 12(2)) and receives IIS reports through the CMS process (Schedule 2 items 13-14).
• Tribunal and its registrar. The registrar is the recipient of admissions or denials (reg 12(1)) and must forward admissions and related papers to the Commissioner and IIS (reg 12(2)). The Tribunal is involved in the course of contested allegations and the regulations prescribe CMS entries following Tribunal determinations (Schedule 2 items 13-14).

Secondary affected groups include police medical officers and other department staff referenced in Schedule 3 (for example, prohibition against making false complaints against such persons in Schedule 3 clause 12), and the public who interact with police officers, as the code imposes standards on interactions (Schedule 3 clauses 6-7).

Overall, the regulations allocate record-keeping and reporting duties primarily to internal actors within SA Police and the IIS. The immediate burdens fall on resolution officers, investigating officers (both s 21(14) and others), the officer in charge of IIS, the Commissioner, and the Tribunal registrar. Complainants are affected principally through the information to be collected and the communication timetable.

The regulations convert several broad duties in the Act into concrete, repeatedly specified obligations and correspondingly define some procedural rights.

Key duties:

• Information content and filing duties. Resolution officers must file a signed report containing the items listed at Schedule 1 item 1 (reg 4). Section 21(14) investigating officers must provide initial details within two weeks, fortnightly progress updates, and final reports and recommendations as soon as practicable (reg 5; Schedule 1 items 2-4). The IIS must enter specified information on the CMS for particular Act sections, within prescribed timeframes (reg 6; Schedule 2 items 1-17). For example, initial complaint intake data must be entered within seven days of the IIS receiving the complaint (Schedule 2 item 1).
• Communication duty. The IIS or the responsible unit must keep complainants and each designated officer informed in writing of progress and resolution at intervals not exceeding 90 days (reg 8). This is a specific duty that creates a minimum frequency for written updates.
• Complaint-taking duty. When a complaint is recorded (reg 9), the person recording it must capture specified data fields (name/contact of complainant, recorder’s name/position, date/time/location of events, details of officers including badge ID, and witness details).
• Service and attendance. Notices of allegation must be served on the designated officer in person (reg 10(1)); the Commissioner may require the officer to attend (reg 10(2)).
• Admission/denial filing deadlines. A designated officer must make an admission or denial to the registrar within 21 days after a notice of allegation is served (reg 12(1)). The registrar must forward an admission and related materials to the Commissioner and the IIS (reg 12(2)). The Commissioner then must consider mitigation submissions attached to an admission before deciding punishment (reg 12(3)).
• Suspension remuneration and forfeiture discretion. If suspension occurs and remuneration is to be paid, the Commissioner determines the calculation method (reg 11(1)). The Commissioner may deduct income received during suspension from withheld remuneration and, on a guilty finding, must generally determine that the officer is not entitled to withheld remuneration or to have the suspension counted as service unless special circumstances justify otherwise (reg 11(2)(a)-(b)).

Key rights or procedural protections:

• Time to admit or deny. Designated officers have a defined 21-day period to admit or deny allegations to the Tribunal registrar (reg 12(1)).
• Consideration of mitigation. If an admission is lodged, the Commissioner must consider mitigation contained in the admission or presented in person before deciding punishment (reg 12(3)).
• Tribunal hearing process. If an officer denies the allegation or does not admit within the 21-day window, the Tribunal must fix a hearing time and place (reg 12(4)). The CMS must then record the Tribunal’s findings and any remittal to the Commissioner (Schedule 2 item 13).
• Payment administration for fines. When the Commissioner imposes fines under s 26, the Commissioner may grant time for payment, permit instalments or deduct the fine from pay (reg 13(3)). The regulations also prescribe the dollar amounts for particular disciplinary fines (reg 13(1)-(2): $1 250).

These duties are mostly administrative in nature: capture and report defined information in specified manners and timelines, preserve written communication with complainants and officers, and ensure a prescribed flow of admissions/denials and outcomes to appropriate decision-makers and records. Rights are chiefly procedural: the 21-day admission window, the Commissioner’s consideration of mitigation, and the Tribunal’s scheduling obligations.

The regulations themselves do not create new criminal offences. Instead they operate as an administrative overlay to the disciplinary powers and sanctioning machinery in the Act. Enforcement occurs through the mechanisms and discretions the Act confers, scaffolded by the regulations.

Monetary sanctions:

• Prescribed fine amounts. The regulations prescribe amounts for particular heads of the Act. Regulation 13 prescribes $1 250 for the purposes of section 26(1)(h) and section 26(1)(i) of the Act (reg 13(1)-(2)). The Commissioner may manage payment by granting time, allowing instalments or deducting from pay (reg 13(3)(a)-(b)).

Suspension and remuneration consequences:

• Suspension remuneration. If a designated officer is suspended and remuneration is to be provided, the Commissioner determines how remuneration is calculated (reg 11(1)). The regulations allow the Commissioner to deduct any income received during the suspension from withheld remuneration payable on revocation (reg 11(2)(a)). If the officer is later found guilty, the Commissioner must, unless satisfied that special circumstances require otherwise, determine the officer is not entitled to withheld remuneration or to have the suspension counted as service (reg 11(2)(b)(i)-(ii)). These provisions convert suspension into a mechanism with potentially significant financial and career-service consequences, subject to the Commissioner’s determinations.

Disciplinary process enforcement mechanics:

• Service and attendance. A notice of allegation must be served in person (reg 10(1)). The Commissioner can require attendance for the purposes of service (reg 10(2)). Personal service and compelled attendance reduce the risk of non-receipt delays but create an administrative enforcement mechanism to ensure the process proceeds.
• Admissions and Tribunal process. Failure to admit within 21 days results in the Tribunal fixing a hearing (reg 12(4)). Admissions, written statements and requests forwarded by the registrar to the Commissioner and IIS (reg 12(2)) feed into the Commissioner’s consideration of punishment (reg 12(3)).

Record-keeping and information obligations:

• Timely CMS entries and updates are required in specific timeframes. While the regulations do not prescribe penalties for failing to enter data on the CMS, these obligations create auditable responsibilities on IIS officers and investigating officers. Non-compliance with these obligations will be visible in records and may be relevant to internal accountability or external review.

Delegated discretions and administrative compliance:

• The Commissioner has a suite of discretions relevant to enforcement and sanction application: to determine remuneration calculation during suspension (reg 11), to deduct suspended-period income from withheld remuneration (reg 11), to require attendance for service (reg 10), to impose fines and manage their payment (reg 13). These discretions are subject to the Act’s limits but are concretely enabled by the regulations.

In short, the regulations support and channel the Act’s enforcement by specifying how discipline is activated (notice and service), how admissions are processed, how suspension remunerations are handled, and how certain fines are quantified and collected. The regulations do not themselves prescribe criminal penalties or express statutory sanctions for non-compliance with the regulations’ information duties.

The regulations sit subordinate to, and operationalise, provisions within the Police Complaints and Discipline Act 2016. The text cross-refers to multiple provisions of the Act and to other statutes.

Direct interactions with the Act:

• The regulations repeatedly refer to and implement duties arising under the Act: for example, reg 4 operationalises section 19(1) of the Act by specifying the content of a management resolution report; reg 5 implements obligations flowing from section 21(14) of the Act by prescribing the content and timing of information from section 21(14) investigating officers; reg 6 prescribes CMS entries for specific sections of the Act (Schedule 2 mapping items to sections such as section 13, 14, 19, 21, 24, 25, 26, 28 and 32).
• The code of conduct is established under section 7(1)(a) and (b) of the Act as applicable to designated officers and police security officers (reg 7(1) and (1a); Schedule 3 codifies required conduct). Reg 7(2) makes contraventions of that code disciplinary breaches under the Act.

Cross-references to other legislation and administrative instruments:

• Schedule 3 clause 1(“Interpretation”) defines "department" by reference to the Public Sector Act 2009, specifically referencing the Commissioner as chief executive under that Act. Thus the code of conduct assumes alignment with public sector administrative structures described in the Public Sector Act 2009.
• Schedule 4 (Savings and transitional provisions) arises from an amendment enacted by the Independent Commissioner Against Corruption (CPIPC Recommendations) Amendment Act 2021. Clause 1 preserves the application of the Act as it was before the commencement of Schedule 1 of that amending Act to certain continuing complaints and complaints made on or before 25 August 2021; it also defines "integrity Acts" which include the Police Complaints and Discipline Act 2016 (Schedule 4 clause 1(2)). This provides transitional continuity between different statutory regimes.
• The legislative history notes that references to other legislation or office titles may be obsolete and are not automatically updated by the legislation publication program. That warning indicates that cross-references should be checked in practice against current titles and provisions.

Administrative and procedural interfaces:

• The regulations require the registrar of the Tribunal to forward admissions and related materials to the Commissioner and the IIS (reg 12(2)). That creates an administrative interface between the Tribunal under its governing legislation and the IIS/Commissioner processes under the Act.
• The correspondence between the IIS and the OPI is implied in Schedule 2 items 3 and 14 which require the IIS to note notifications to OPI under sections 14(4) and 26(4) respectively. The regulations therefore shape how the IIS records interactions with other oversight or prosecutorial bodies.

Limitations and caveats:

• The regulations do not themselves change the substantive jurisdictional boundaries of the Act, nor do they amend other Acts. They operate at the level of procedure, record-keeping and administration. The document’s "Notes" expressly warn that references to other legislation or offices may be obsolete, flagging the need to verify cross-references when applying the regulations.

Taken together, the regulations function as the Act’s procedural companion, mapping statutory checkpoints (sections of the Act) to concrete information fields, timeframes and internal administrative flows, and referencing definitions or roles that lie in other statutes such as the Public Sector Act 2009 and the Independent Commissioner amendment Act 2021 for transitional continuity.

The regulations have been amended several times since their original 2017 commencement. The legislative history section in the text sets out principal variations and the dates of effect.

Key entries:

• Principal regulations made in 2017 as No 261, Gazette 29.8.2017, commenced 4.9.2017 (r 2). That is the instrument establishing these regulations.
• A variation instrument in 2021, No 156, Gazette 7.10.2021, commenced 7.10.2021 (r 2). That instrument inserted Schedule 4 (Savings and transitional provisions); the table shows "Sch 4 inserted by 156/2021 r 4" with commencement 7.10.2021. Schedule 4 implements transitional rules connected to the Independent Commissioner Against Corruption (CPIPC Recommendations) Amendment Act 2021.
• A variation in 2022, No 88, Gazette 29.9.2022, commenced 10.10.2022 (r 2). That variation amended Part 3 heading and substituted reg 7(1), and inserted reg 7(1a) establishing that the Schedule 3 code applies also to police security officers (the table in "Provisions varied" records r 7(1) substituted and r 7(1a) inserted by 88/2022 r 3(2)-(3), effective 10.10.2022).

Other revision notes:

• r 2 was omitted under the Legislation Revision and Publication Act 2002 on 7.10.2021 (as indicated by the "Provisions varied" table).
• The legislative history includes a "Historical versions" note identifying 7.10.2021 as an earlier version available.

What changed substantively:

• The most notable substantive expansion recorded in the variation notes is the explicit application of the code of conduct in Schedule 3 to police security officers via reg 7(1a) inserted in 2022. The substitution of reg 7(1) at the same time likely adjusted cross-references or the text of the principal provision, though the instrument text in this file contains the final wording.
• Schedule 4 addition in 2021 implemented transitional savings relating to the broader reform enacted by the Independent Commissioner Against Corruption (CPIPC Recommendations) Amendment Act 2021, preserving application of the previous Act version to certain continuing matters.

The regulations’ legislative history therefore shows two amendment waves after commencement: one in 2021 adding transitional provisions tied to a separate amending Act, and another in 2022 adjusting the code of conduct’s application to cover police security officers. The legislative history warns that references may not be automatically updated, so practitioners should check the current versions of any external provisions mentioned.

The text of the regulations as provided does not include any reported litigation or case law that interprets them. There are no cases named or cited in the instrument. The "Legislative history" section records statutory amendments and publication details but does not list any judicial decisions.

What the document does record that may be relevant to litigation or review:

• The regulations create time and content obligations that are measurable and therefore potentially subject to administrative review or judicial scrutiny if steps are not taken. For instance, failures to keep complainants informed within the 90-day maximum (reg 8), failures by the IIS to enter prescribed CMS information within specified timeframes (reg 6; Schedule 2), or failure by a registrar to forward admissions to the Commissioner and IIS (reg 12(2)) are all administrative actions that could form part of a complaint or judicial review on procedural fairness grounds if they affect rights or legitimate expectations under the Act.
• The Commissioner’s discretions , for example, to determine calculation of suspension remuneration and to withhold remuneration after a guilty finding except in special circumstances (reg 11(1)-(2)) , create discretionary decision points. Those discretions are potentially reviewable in the usual way under administrative law if exercised unreasonably, without procedural fairness or contrary to statutory limits; the regulations themselves record the mechanics but do not define review remedies.

Absence of case law in the provided text:

• Because the regulations text does not contain decisions or litigation references, practitioners needing case law must search South Australian tribunals and courts for decisions that reference these regulations or the Act. The regulations themselves do not report any decisions or interpretive guidance.

In short, no litigation history is recorded in the instrument as provided. That absence means reliance on primary regulatory text and the Act for interpretation until or unless case law develops; the regulations’ prescriptive entries create operational obligations that could later produce litigation on administrative law grounds.

Several practical pitfalls, operational frictions and compliance traps arise directly from the precise prescriptions in the regulations. These "gotchas" are matters of procedure and project management that create risk of unintentional non-compliance or operational bottlenecks.

1. Multiple, strict and varying timeframes

• The regulations layer multiple deadlines on different actors: 48 hours for some CMS entries (Schedule 2 items 5-7), seven days for initial complaint entry (Schedule 2 item 1), two weeks for initial details from s 21(14) investigating officers (Schedule 1 item 2), fortnightly updates thereafter (Schedule 1 item 3), monthly updates for other investigators (Schedule 2 item 10), 21 days to admit or deny (reg 12(1)), and written updates to complainants and designated officers at intervals not exceeding 90 days (reg 8). A backlog in one part of the chain (for example, late entry by an investigating officer) can cascade into other statutory timeframes and generate compliance questions.
• The frequency differences between s 21(14) investigators (fortnightly updates) and other investigating officers (monthly updates) create a need to track investigator type and ensure different update cadences are respected (Schedule 1 item 3 vs Schedule 2 item 10).

2. Heavy data-field requirements

• The CMS fields required are detailed: names, dates of birth, badge IDs, ranks, postings, dates/times/locations of events, witness contact details, descriptions, supporting documentation, officer identities who assessed the matter, the IIS officer in charge who determined allocation, and more (Schedule 2 items 1-4, 8-11, 13-17). Capturing and validating this data, especially for complaints received in person or by telephone, can be administratively burdensome and time-consuming and requires accurate identity verification.

3. Personal service requirement for notices of allegation

• A notice of allegation must be served in person (reg 10(1)). The Commissioner may require attendance (reg 10(2)). That reduces options for remote service and creates logistical complications if an officer is off-duty, seconded interstate, or otherwise hard to locate. It also creates a potential point of delay if personal service cannot be effected quickly.

4. Registrar forwarding and information flows

• Admissions must be filed with the registrar within 21 days and the registrar must forward admissions, statements and requests to both the Commissioner and IIS (reg 12(1)-(2)). Any failure in this forwarding step can delay mitigation consideration by the Commissioner or CMS entries required under Schedule 2 item 12.

5. Forfeiture of remuneration on guilty finding unless special circumstances

• The default position in reg 11(2)(b) is that withheld remuneration is not payable and suspension does not count as service following a guilty finding unless the Commissioner believes special circumstances require otherwise. The regulations do not define "special circumstances". That creates discretionary risk for officers and potential appeal grounds if the Commissioner’s assessment is contested.

6. Wide-ranging code of conduct with potentially ambiguous terms

• Schedule 3 contains important standards such as "must at all times act with honesty and integrity" (Schedule 3 clause 2), "must not... behave in a manner that reflects or is likely to reflect adversely on SA Police" (clause 3(a)), and prohibitions against being "negligent" (clause 5) and acting in an "oppressive, offensive, abusive or insulting manner" (clause 7(b)). These terms are normatively broad and could produce different interpretations. Because contraventions become disciplinary breaches (reg 7(2)), ambiguity in such formulations may become a flashpoint.

7. Information about third parties and confidentiality risks

• Complaint and investigation records require capture of personal details (DOBs, contact details) for complainants, witnesses and officers (reg 9; Schedule 2 item 1). The requirement in Schedule 3 clause 10 that officers treat information as confidential must be reconciled with the CMS data capture and sharing obligations. Operationally, that creates data-protection and privacy risk: who can access CMS entries, retention periods and information-security controls are not specified here.

8. Different reporting obligations for assisting vs conducting investigators

• Reg 5(2) limits an investigating officer who is only assisting the IIS to provide only information reasonably ascertainable in the assisting role. That creates potential ambiguity about what counts as "reasonably ascertainable", and may require protocol guidance to avoid inconsistent reporting practices.

9. Transitional scope complexity

• Schedule 4 preserves application of previous Act provisions to certain continuing complaints and matters and defines "integrity Acts". Practitioners handling complaints spanning the transition dates must track which statutory version applies to each matter; errors could affect jurisdictional or procedural correctness.

10. Prescribed fines are modest and inflexible

• The regulations fix fines under certain heads at $1 250 (reg 13(1)-(2)). The Commissioner may grant instalments, time or deduction from pay (reg 13(3)), but the fixed quantum may create anomalies where misconduct severity varies. This may prompt parties to press for other sanctions or appeal paths.

Careful process design, role-mapping, CMS access controls and a compliance calendar that maps all the timeframes to responsible officers will mitigate these risks. The regulations themselves do not provide operational templates or technical standards for CMS security or data validation; those implementation details sit with the IIS and Commissioner.

Compliance under these regulations is primarily process-driven: implement information capture, reporting, timetabling and decision protocols aligned with specific regulation clauses and schedule items. Below is a practical compliance checklist and recommended operational measures mapped to the relevant provisions.

1. Governance and role allocation

• Identify accountable officers: resolution officers (reg 4; Schedule 1 item 1), section 21(14) investigating officers (reg 5; Schedule 1 items 2-4), investigating officers other than s 21(14) officers (Schedule 2 items 8-11), officer in charge of the IIS or delegated member (reg 6), registrar of the Tribunal (reg 12), and the Commissioner.
• Ensure delegation instruments exist for the officer in charge of the IIS to authorise members to make CMS entries (reg 6(a)-(b)).

2. Record-keeping and CMS implementation

• Build CMS templates that match Schedule 2 items 1-17 exactly. Include fields for:
  • Complainant name, DOB, contact details (Schedule 2 item 1(a));
  • Event date/time/location, detailed description, officer identifiers (badge ID, rank, posting, DOB, uniformed status), vehicle details where relevant (Schedule 2 item 1(b)(i)-(ii));
  • Witness names and contact details and witness accounts (Schedule 2 item 1(d)-(e));
  • Assessment allocation data: assessing officer, whether sensitive/urgent, reasons, recommended action, officer-in-charge determinations and referrals (Schedule 2 item 3);
  • Investigation updates: actions taken with date/time/outcome (Schedule 2 item 9); monthly updates (Schedule 2 item 10); final report, recommendations and Commissioner determination (Schedule 2 items 11, 14).
• Implement timestamped entry controls so entries can be demonstrated to have been made within the prescribed windows (e.g., within 7 days for initial complaint entry; within 48 hours for s 21(14) investigator entries).

3. Timelines and calendarisation

• Create a compliance calendar that triggers:
  • Within 48 hours: CMS entries for information received from s 21(14) investigating officers (Schedule 2 items 5-7).
  • Within 7 days: initial complaint/report CMS entry (Schedule 2 items 1-2).
  • Within 2 weeks: initial details from s 21(14) investigating officers (Schedule 1 item 2).
  • Fortnightly thereafter: progress updates from s 21(14) investigating officers (Schedule 1 item 3).
  • Monthly: progress updates from other investigating officers following initial entry (Schedule 2 item 10).
  • 21 days from service: design‑ated officer admission or denial filed with the registrar (reg 12(1)); establish registrar processes to immediately forward admissions to IIS and Commissioner (reg 12(2)).
  • Every 90 days: written updates to complainant and designated officer(s) on progress or resolution (reg 8).

4. Complaint intake and recording protocol

• Use a standard intake form matching reg 9 to capture: complainant identity and contact details, recorder details (name, position, place of work), date/time/location of events, officer identifiers (including badge ID), description of events, witness names and contacts, and date/time/location of complaint making.
• Ensure intake staff are trained to collect vehicle descriptions and DOBs when available, because Schedule 2 requires DOBs and vehicle details if known.

5. Investigation reporting templates

• For section 21(14) investigating officers, prepare an initial report template that covers name/badge/rank/posting, complaint summary, investigation scope/objectives, risks/strategies/resources, reporting obligations, projected timeframe (Schedule 1 item 2).
• For subsequent fortnightly updates include intended vs actual progress, reasons for shortfalls, summary actions and intended progress by next update (Schedule 1 item 3).
• Final investigation report must include the investigation report copy, summary of recommendations and IIS determination (Schedule 1 item 4; Schedule 2 items 7, 11).

6. Admissions and mitigation workflow

• Registrar must have an automated or manual process to send copies of admissions, written statements and requests to the Commissioner and the IIS immediately on receipt (reg 12(2)). The Commissioner must be able to access any attached mitigation submissions and to record consideration prior to imposing punishment (reg 12(3)).
• Track appeals: when appeals are instituted, ensure CMS entries for date of institution, appellant identifiers and grounds, and copy of notice (Schedule 2 item 16). On completion or discontinuation of appeal, log outcomes and link to historical CMS files (Schedule 2 item 17).

7. Disciplinary sanction administration

• For fines under section 26(1)(h)/(i) set at $1 250 (reg 13(1)-(2)), maintain accounts and payment plans. The Commissioner should document decisions about instalments or deduction from pay (reg 13(3)).
• For suspensions, the Commissioner must document the method for calculating remuneration and any deductions for income received during suspension; maintain records of determinations about withheld remuneration and whether the suspension will count as service (reg 11(1)-(2)).

8. Confidentiality, access control and privacy

• Map CMS access rights to roles: restrict viewing of sensitive fields to personnel with need-to-know to align with Schedule 3 clause 10 (confidentiality). Implement audit logs to demonstrate who accessed what information and when.
• Align data retention and privacy handling with applicable privacy law and data-security policy; the regulations mandate capture but do not prescribe retention or security requirements.

9. Training and guidance

• Train resolution officers and investigating officers on the content requirements of Schedule 1 (resolution report details and investigation templates).
• Provide interpretation guidance on ambiguous code terms (e.g., what constitutes "negligence", "oppressive" behaviour, "special circumstances" for remuneration decisions) and escalate to legal/compliance unit when uncertainty exists.

10. Transitional matters

• For complaints or reports that straddle the 25 August 2021 date or the commencement of Schedule 1 of the Independent Commissioner amendment Act 2021, consult Schedule 4 to determine which statutory regime applies (Schedule 4 clause 1), and document the applicable regime in the CMS entry.

A compliance programme that transforms the prescriptive Schedule 1 and Schedule 2 fields into templates, automates time triggers, enforces access controls and documents the Commissioner’s discretionary reasons where required will map directly to the regulations’ obligations. Legal oversight should be engaged when drafting templates and when exercising Commissioner discretions that may be reviewable.