The Regulations rely on a small set of core concepts which frame obligations and discretionary choices.

• Customer service code and customer charter. The principal device is the "customer service code" which must set mandatory elements; within that code each regulated entity must publish a "customer charter" (reg 4(1)). The charter is a specific document the codes must require and that the regulated entity may not contravene in its dealings with customers (reg 4(2)). Reg 5 requires both to comply with the Act, these Regulations, any Regulator guidelines and the customer service code itself.

• Regulated entity and customer. The duties in the Regulations fall primarily on "regulated entities" and protect "customers". The instrument repeatedly frames requirements as obligations on the regulated entity to set standards in its customer service code, to publish information, and to act in particular ways where customers have specific circumstances (eg special needs customers under s 3(1)).

• Meter reading and special meter reading. "Meter reading" is defined broadly (reg 3(1): actual reads, estimates based on an equivalent period, or estimates based on comparable properties). "Special meter reading" is a read at a different time than usual (reg 3(1)). The Regulations create customer protections around special meter reads (customers may request them and they are not liable for the charge if the meter has inaccurately measured , reg 17(1)(b)-(c)).

• Special needs customers and Regulator determinations. The Regulations define "special needs customers" in three ways: dialysis customers, those with medical-condition-determined special requirements, and classes determined by the Regulator (reg 3(1) and (2)). The Regulator has express statutory power to determine classes and their special requirements that must be reflected in customer service codes (reg 3(2)).

• Planned versus unplanned interruptions. The instrument distinguishes planned interruptions (maintenance, augmentation, upgrade) from unplanned interruptions (not caused by the regulated entity or due to an event beyond its control) (reg 3(1)). Customer service codes must set policies to minimise effects of both and restore service as soon as practicable after unplanned interruptions (reg 11).

• Overpayments/underpayments; fraud; arrears and payment plans. Definitions and minimum procedures for refunds, recovery, and limits on charging fees or interest on undercharging (except for fraud) are set out (regs 20-23). Payment plans must be detailed and renegotiable where circumstances change, and must be confirmed in writing (reg 26).

Conceptually the Regulations do not themselves set prices, disconnection powers or criminal offences. They set content and process obligations for customer service codes; enforcement and the outer powers (eg power to disconnect without notice under sections 56K-56M of the Act) are referenced rather than rewritten (reg 9(1)). The rules are a content‑prescription model: they require regulated entities to enshrine particular procedures, notice and disclosure practices in the codes and charters and to publish those instruments for customers (eg reg 14(3)).

The Regulations affect three principal groups and several secondary stakeholders.

• Regulated entities. All obligations are worded as duties on a "regulated entity" to include specified matters in its customer service code, to publish a customer charter, and to act consistently with those documents (eg regs 4(1)-(2), 5, multiple subsequent regs). The regulated entity bears the compliance, documentation, publication and procedural burdens: drafting and updating customer service codes and charters, publishing materials on its website (reg 14(3)), responding to special meter reading requests within the maximum period to be specified in the code (reg 17(2)), implementing payment plans with specified content (reg 26) and operationalising financial hardship policies (reg 28).

• Customers. The Regulations create information and procedural rights for customers. Customers can expect published charters (reg 4), the ability to request separate accounts for individual properties (reg 16(1)), the right to request special meter readings (reg 17(1)(b)) with particular protections if meters have misread (reg 17(1)(c)), protections during disputes and Ombudsman complaints (reg 27), access to information contained in accounts and to additional service information on request within the time specified by the customer service code (reg 18(2)), and a financial hardship policy to apply to them (reg 28).

• The Regulator and the Department. The Regulations explicitly give the Regulator an active role in determining classes of special needs customers and their special requirements (reg 3(2)). Reg 5 requires charters to comply with guidelines issued by the Regulator under the Act. Administratively, the Regulations are administered through the Department of Primary Industries, Parks, Water and Environment (final paragraph), which indicates the government body that will oversee implementation and point-of-contact matters.

• Ombudsman and dispute resolution bodies. Reg 27 references the Ombudsman as a dispute-resolution forum with procedural consequences: if a customer makes an Ombudsman complaint and the disputed amount is not due that day, the customer is not liable to pay the disputed amount until the Ombudsman dismisses the complaint or finds the customer liable (reg 27(2)).

• Other parties indirectly affected. Property purchasers, landlords and tenants are affected by obligations on notification of change in ownership or occupation (reg 33(3)), and parties that provide or maintain meters may face increased special meter read requests or audits as regulated entities implement frequency requirements (reg 17(1)(a)).

Who pays and who decides. Customers ultimately bear the direct costs where regulated entities lawfully pass through fees and charges defined under applicable price determinations, subject to the limits the customer service code imposes (eg treatment of fees and interest on underpayments, reg 23(1)). Regulated entities decide the content of their customer service codes, within the floor set by these Regulations and the Act; the Regulator determines classes of special needs customers and issues guidelines that the codes and charters must comply with (reg 3(2), reg 5). The Department administers the Regulations.

The Regulations set out a catalogue of duties for regulated entities and corresponding rights for customers, mostly implemented via customer service codes and customer charters.

Duties on regulated entities (selected, with section references):

• Publish a customer charter and ensure dealings with customers do not contravene it (reg 4(1)-(2)).
• Ensure charters and codes comply with the Act, these Regulations and Regulator guidelines (reg 5).
• Include connections information consistent with price and service plans (reg 6 and section 56U of the Act).
• State circumstances for requesting, holding and returning security deposits and obligations on deposit handling (reg 7(1)-(2)).
• Specify circumstances and permissible days/times for disconnection or restriction of water and sewerage services; include consideration of health, safety and environment before disconnecting (regs 8(1)-(4)).
• Provide notice for disconnections or restrictions where practicable, and give notice where disconnection results from non-payment (reg 9(1)-(3)).
• Specify circumstances for restriction/disconnection due to debt and rules for restoration upon entry into a payment plan (reg 10).
• Develop policies to minimise customer impacts from planned and unplanned interruptions and restore services as soon as practicable after unplanned interruptions (reg 11).
• Provide special provision for special needs customers to maintain services during interruptions (reg 12).
• Optionally specify minimum water flow rates (reg 13).
• Provide minimum notice periods for imposing or varying fees, and make fee schedules and calculation methods available on websites and on request (reg 14).
• Specify minimum and maximum billing periods for non-contract customers (reg 15).
• Issue separate accounts on request for each property or where separate meters exist (reg 16).
• Specify minimum meter-reading frequency, rights to request special meter readings and non-liability for special meter reading costs if the meter has mismeasured (reg 17(1)(a)-(c)); also set the maximum response time for special meter reading requests (reg 17(2)).
• Specify account content and the customer’s right to request service and payment information and the time within which it will be provided (reg 18).
• Set acceptable payment methods, possible discounts for payment methods and recovery for dishonoured payments (reg 19).
• Provide processes for refunding overpayments (reg 21).
• Be entitled to recover undercharges, except where undercharging results from customer fraud (reg 22(1)-(2)).
• Generally not impose fees or interest on undercharged amounts except where undercharging was caused by customer fraud (reg 23(1)); specify the method and amounts recoverable in fraud cases (reg 23(2)).
• Specify permitted interest and fees on overdue accounts, if any (reg 24).
• Limit debt recovery to remedies specified in the customer service code; send reminder notices within the period the code specifies before pursuing a remedy; do not pursue a remedy before the reminder notice is sent (reg 25(1), (3)-(4)); notify customers in writing when pursuing a remedy (reg 25(5)).
• Implement payment plans that include calculation, duration, instalment amounts, renegotiation rights for changed circumstances and written confirmation (reg 26).
• Ensure customers are not required to pay disputed amounts while arbitration, mediation or negotiation is outstanding, and protect customers who complain to the Ombudsman so long as the amount is not due and payable the day the complaint is made (reg 27).
• Have and apply a financial hardship policy consistent with the customer service code and the Act (reg 28).

Rights for customers (selected, with section references):

• Right to access and view fee schedules and policies on the regulated entity’s website and obtain copies on request within the time the code specifies (reg 14(3)-(4)).
• Right to request separate accounts per property (reg 16(1)), and an entitlement to separate accounts where meters are separate (reg 16(2)).
• Right to request special meter readings and protection from costs if the meter has inaccurately measured (reg 17(1)(b)-(c)).
• Right to information on account contents and related service/payment history at request within the time set out in the code (reg 18(1)-(2)).
• Protections while disputes are being resolved: a customer is not liable to pay the disputed amount while arbitration, mediation or negotiation is outstanding (reg 27(1)); if an Ombudsman complaint is lodged and the disputed amount is not yet due, the customer does not need to pay until the Ombudsman dismisses or finds liability (reg 27(2)).
• Right to a financial hardship policy and to seek renegotiation of payment plans upon changed circumstances (reg 26(2)(d); reg 28).

The Regulations also create procedural duties that shift practical burdens onto regulated entities: for example, the duty to specify the maximum response period for special meter readings (reg 17(2)) and to confirm payment plans in writing (reg 26(2)(e)). Many duties are specified as requirements to set out further rules in the customer service code rather than as directly prescriptive operational rules, which leaves detail-setting to regulated entities but inside the mandatory envelope established here.

The Regulations themselves do not create criminal offences or specific monetary penalties within the text provided. Instead they operate by imposing mandatory content requirements on customer service codes and charters, which are instruments that regulated entities must have and apply. The Regulations reference the Act and Regulator powers several times (eg reg 5 requires compliance with the Act and any Regulator guidelines; reg 3(2) gives the Regulator a role in determining special needs classes). Enforcement mechanisms and penalties for non‑compliance with these Regulations are therefore likely to be situated in the Water and Sewerage Industry Act 2008 and in any enforcement framework administered by the Regulator or the Department, but the Regulations do not themselves specify sanctioning tools, penalty amounts, or criminal offences.

Procedural enforcement levers and practical consequences follow from the way obligations are structured:

• Duty to adopt and publish charters and codes (reg 4(1), reg 14(3)) creates transparency. Non-compliance would be visible and may attract Regulator action or administrative interventions under the Act or under Regulator guidelines (reg 5).
• References to the Act for exceptional disconnection powers (reg 9(1) citing sections 56K, 56L, 56M of the Act) indicate that the Act contains the backbone of disconnection power and exceptions; the Regulations do not override or replicate those powers.
• The requirement to not pursue a remedy before issuing a reminder notice (reg 25(3)-(4)) and to notify customers in writing when pursuing a remedy (reg 25(5)) impose pre-action procedural steps that regulated entities must document and follow. Failure to follow them would be a failure to comply with the customer service code; consequences for such a breach will depend on the Act and any Regulator disciplinary or enforcement policies.

Administrative oversight. The Regulations are administered in the Department of Primary Industries, Parks, Water and Environment (final paragraph). The Regulator is given specific roles (reg 3(2), reg 5), which creates a two-tier oversight architecture: the Regulator sets guidelines and may determine classes of special needs customers; the Department manages administration. The Regulations therefore shift enforcement and supervisory burdens to existing institutions under the Act rather than embedding sanctions in the Regulations.

Practical enforcement risk for regulated entities arises from transparency and consumer complaint channels. Regulated entities must provide written reasons for complaint decisions (reg 32(3)) and must ensure their codes limit remedies to those specified in the code (reg 25(1)). This creates documentary obligations that regulators and external ombudsmen can review. While the Regulations do not list fines, failure to meet the mandatory content and process requirements is likely to be actionable under the Act or through regulatory oversight procedures referenced by reg 5. Parties seeking redress for breaches of the codes have a procedural path: internal complaints policies (reg 32) and recourse to the Ombudsman (reg 27(2)).

The Regulations are expressly designed to sit under and interact with the Water and Sewerage Industry Act 2008 and any guidelines or instruments made under that Act. Multiple cross‑references indicate that these Regulations are not standalone but rather specify minimum content that must be consistent with the Act and existing statutory frameworks.

• Direct cross-references to the Act. The Regulations require customer service codes to include connection-related information that aligns with section 56U of the Act (reg 6). Reg 9(1) disallows disconnection except where allowed under sections 56K, 56L and 56M of the Act. Regulation 15 cross-refers to customers without a contract under section 61 of the Act. These references mean that the operational powers governing connections, disconnections, and contractual status are set in the Act, and the Regulations slot into that framework by describing the customer-facing procedures and safeguards that must accompany those Act powers.

• Regulator powers and guidelines. Reg 5 requires customer charters to comply with "any guidelines issued by the Regulator under the Act." Reg 3(2) empowers the Regulator to determine classes of special needs customers and to require the regulated entity to specify their special requirements in customer service codes. This gives the Regulator an active role in shaping the content that the Regulations require, and creates an interaction where non-statutory or subordinate guidance (guidelines under the Act) will inform what is required in codes and charters.

• Ombudsman and dispute resolution. Reg 27(2) directly involves the Ombudsman. The Regulations defer to the Ombudsman’s process and decision-making for disputed amounts, affecting when a customer is and is not liable to pay. This links the regulatory requirements to administrative dispute resolution mechanisms that are external to the water Act framework.

• General administrative law and consumer law. The Regulations impose duties to provide written reasons for complaints decisions (reg 32(3)), to confirm payment plans in writing (reg 26(2)(e)), and to provide information on request within specified timeframes (eg reg 18(2)). These duties produce administrative recordkeeping and procedural fairness obligations that intersect with general administrative law principles. They also operate in the broader consumer-protection landscape: for example, prohibitions on charging fees or interest for undercharging except in fraud cases (reg 23(1)) create consumer-friendly limits that must operate alongside any general consumer law obligations or contracting arrangements.

• Local government or other statutory instruments. The Regulations do not mention local government powers or land law directly. However, obligations affecting notification on sale, lease or vacation of property (reg 33(3)) will interact with property transaction processes and possibly conveyancing practices. They also may affect tenancy practice when regulated entities must provide separate accounts (reg 16) or when a customer must notify change of circumstances (reg 33).

• Fees and price determinations. Where a price determination applies that does not require notice to customers, reg 14(2) makes the notice obligation in reg 14(1) inapplicable. This clarifies that the Regulations are designed to operate compatibly with statutory pricing frameworks, and that price determinations under the Act may override certain notice requirements in the Regulations.

In practical terms, regulated entities must read the Regulations alongside the Act, any Regulator guidelines, and any price determinations or contracts. The Regulations set minimum content and procedural standards; the Act supplies the primary statutory powers, and Regulator guidelines will often supply further interpretive content that the Regulations require compliance with (reg 5). The Regulations therefore operate as subordinate, code‑content rules that must be implemented consistent with higher-order statutory instruments.

The instrument as provided records a short, explicit amendment and publication history:

• Short title: Water and Sewerage Industry (Customer Service Standards) Regulations 2019 (reg 1).
• Commencement: These Regulations take effect on 25 November 2019 (reg 2).
• Gazette notification: Notified in the Gazette on 21 November 2019 (final paragraph).
• Administration: These Regulations are administered in the Department of Primary Industries, Parks, Water and Environment (final paragraph).

No subsequent amendments, repeals, or modification dates are contained in the text provided. The Regulations therefore took effect from the single commencement date noted above and were in force as of 25 November 2019. The instrument repeatedly references the Water and Sewerage Industry Act 2008 for interaction and cross‑validation of content; any later amendments to the Act, price determinations, or Regulator guidelines after 25 November 2019 could affect compliance obligations, but such later changes are not recorded in the provided text.

Practical implication: compliance obligations were effective from the commencement date, and regulated entities were required to ensure their customer service codes and customer charters complied with the new content requirements from that time. For practitioners advising regulated entities, it is necessary to check for any post-2019 amendments to either the Regulations, the Act, Regulator guidelines, or price determinations that might alter or displace requirements in these Regulations. The instrument itself does not present an amendment chronology beyond its initial notification and commencement metadata.

The text of the Regulations provided contains no references to judicial or administrative decisions, and it names no cases. There is therefore no litigation history recorded in the instrument itself. The Regulations do cross-reference the Ombudsman (reg 27(2)) and the Act (multiple regs), but there are no named legal proceedings, appeals, or case law citations contained in the Regulations.

For practitioners researching litigation risk or precedent, two notes follow from the instrument’s structure:

• Because the Regulations require detailed customer-facing processes and documentation (for example, requiring written reasons for complaint decisions, reg 32(3)), disputes about compliance are likely to be resolved through administrative or regulatory processes first, and through Ombudsman complaints in certain circumstances (reg 27). Where those processes do not resolve matters, affected parties may seek judicial review or other remedies under the Act or general administrative law,however, the Regulations themselves do not supply any case law or litigation references to guide interpretation.
• Any legal challenge to a regulated entity for failure to comply with its customer service code or charter would depend on the enforcement and sanctioning regime in the Act and any Regulator policies (reg 5), and on administrative law standards such as procedural fairness, reasonableness and statutory interpretation. Those sources, not the Regulations themselves, will provide litigation precedent.

In practice, legal researchers and litigators will need to consult the Act, Regulator guidelines and any Ombudsman determinations or administrative tribunal decisions that involve these Regulations to build a litigation history. None of that material is included in the instrument text provided.

The Regulations include multiple provisions that create compliance traps or operational ambiguities for regulated entities. These are concrete points where regulated entities, advisers and auditors should pay attention.

• Delegated detail and potential for variation. The Regulations require a customer service code to "specify" matters across a wide range of areas (eg regs 4-33). They rarely set fixed time periods or precise formulae themselves; instead they force regulated entities to set those details in their codes (eg reg 14(1) leaves the "minimum period of notice" to be specified in the code). This design permits variation across regulated entities. The result is that a regulated entity could have a code materially different from a neighbour's code while still complying with the Regulations. That variation may create regulatory arbitrage, comparative consumer confusion and increased compliance costs for customers and third parties (eg conveyancers, tenant advocates) who must navigate differing standards.

• "Where practicable" qualifier for notice. Reg 9(1) says a regulated entity must not disconnect or restrict a regulated service unless, "where practicable, the regulated entity has given notice." The "where practicable" standard is context-dependent and not defined in the Regulations. Regulated entities must translate this into operational procedures and records to show when notice could not reasonably be given. That will create judgement calls that the Regulator or Ombudsman may scrutinise.

• Undefined key terms. Several operationally material words are left undefined: for example, what constitutes a meter "inaccurately" measuring (reg 17(1)(c)); what qualifies as "special requirements" for special needs customers outside dialysis or medical determinations (reg 3); and "as soon as practicable" for restoring service after unplanned interruptions (reg 11(3)). The absence of definitions shifts interpretive burden to regulated entities and to the Regulator, and increases exposure to complaints and disputes.

• Regulator discretion on special needs. Reg 3(2) gives the Regulator the power to determine classes of special needs customers and to require regulated entities to specify special requirements in their codes. That centralised discretion can produce binding obligations that regulated entities must reflect in their codes. Regulated entities should therefore maintain active engagement with the Regulator to anticipate or influence such determinations.

• Dispute suspension mechanics and timing. Reg 27(1) provides that if the parties agree to resolve a billing dispute by arbitration, mediation or negotiation, the customer is not liable to pay the disputed amount during the resolution period. Reg 27(2) supplements this by protecting customers who complain to the Ombudsman where the amount is not due on the complaint day. The gotcha is that these protections hinge on procedural timing and characterisation of the billing item. Regulated entities must track whether an amount is "due and payable" on the complaint date; otherwise they risk prematurely pursuing collection remedies in breach of reg 27.

• Limits on recovery for undercharging except for fraud. Reg 23(1) prohibits imposing fees or interest on undercharged amounts unless there was customer fraud. Reg 22(1) allows recovery of undercharged amounts, but the inability to add interest or fees (except for fraud) may be financially material for regulated entities that discover long‑running undercharges and expected interest income. The practical consequence is that regulated entities have incentives to monitor billing accuracy proactively, but may face unrecoverable losses where undercharging arises from their own systems or staff error.

• Reminder notice requirement before remedies. Reg 25(3)-(4) requires a reminder notice within the period specified in the code, and forbids pursuing remedies until that notice is sent. If a regulated entity's code sets short reminder periods to reduce administrative delay, that may be challenged as insufficiently protective; if it sets long periods, the entity will experience delayed debt recovery. Entities must calibrate codes and demonstrate reasoned policy choices.

• Publication obligations and website maintenance. Reg 14(3) mandates that fees, methods and policies may be viewed on the regulated entity's website and reg 14(4) requires provision on request within a specified period. Regulated entities must therefore maintain accurate and current web pages, plus service processes for requests. Failures of website availability or outdated documents could be treated as non-compliance.

• Disconnection exceptions under the Act. Reg 9(1) references sections 56K-56M of the Act as exceptions to the notice rule. Entities must understand and apply those Act provisions in conjunction with the Regulations; a failure to do so risks either illegal disconnection or failure to act under lawful exceptions.

• Administrative burden of written reasons and recordkeeping. Regulated entities must provide written reasons for complaint decisions (reg 32(3)), confirm payment plans in writing (reg 26(2)(e)), and notify in writing when pursuing remedies (reg 25(5)). These generate document production obligations and may lead to greater Ombudsman and Regulator scrutiny.

• No statutory penalties in these Regulations. The Regulations do not themselves contain penalty clauses; enforcement will depend on the Act and Regulator actions. Regulated entities should not assume an absence of penalty risk because the Regulations omit explicit fines.

Each of these points imposes concrete operational choices. Regulated entities should document the rationale for each choice in their codes to withstand Regulator or Ombudsman review.

A practical compliance roadmap for a regulated entity to align with these Regulations should be documented, implemented and periodically reviewed. Below are the actions to take, mapped to the controlling Regulations and with implementation tips.

1. Inventory and legal mapping

   • Map each regulation clause to an internal policy owner. The Regulations require explicit content across multiple domains (eg connections, disconnections, fees, meter readings, billing, arrears, payment plans, disputes, hardship). Assign responsibility for each bucket (eg operations, billing, customer service, legal, compliance).
   • Identify any applicable price determinations, Act provisions (sections cited in regs 6, 9, 15), and Regulator guidelines (reg 5). Ensure the code will be consistent with those instruments.

2. Draft or revise the customer service code

   • Ensure the code contains each matter the Regulations mandate. Use the Regulations’ phrasing as a checklist: publication of a customer charter (reg 4), compliance with the Act and guidelines (reg 5), connection information per section 56U (reg 6), security deposit policies (reg 7), disconnection/restriction circumstances and timing (regs 8-10), interruption policies (reg 11), special needs arrangements (reg 12), billing periods (reg 15), separate accounts (reg 16), meter-reading frequency and special meter reading response times (reg 17), account contents (reg 18), payment methods and dishonour recovery (reg 19), overpayment/underpayment processes (regs 21-23), arrears collection and reminder notices (reg 25), payment plan content and renegotiation rules (reg 26), dispute handling (reg 27), hardship policy (reg 28), information and complaint handling requirements (regs 29-33).
   • For all places where the Regulations require the code to "specify" a period, fee, procedure or maximum, set explicit values or processes in the code. For example, set a maximum response time for special meter reading requests (reg 17(2)); set minimum and maximum billing period lengths for non-contract customers (reg 15); set the minimum notice period for fee changes if price determinations do not apply (reg 14(1)-(2)).

3. Draft the customer charter and publish

   • Prepare a customer charter consistent with the customer service code and the Act (reg 5). The charter should be a concise, accessible statement of customer rights and key procedures (eg how to request a special meter reading, how to apply for hardship assistance).
   • Publish the charter on the regulated entity’s website and ensure it is available in hard copy on request (reg 14(3)-(4)). Maintain an administrative process to provide copies within the times specified by the code (reg 14(4)).

4. Establish operational procedures and scripts

   • Meter-reading program: document the meter-reading frequency (reg 17(1)(a)), processes for special meter reading requests, technical criteria for determining whether a meter has "inaccurately measured" (reg 17(1)(c)), and the customer communication process.
   • Disconnection and restriction: record the circumstances when disconnection is permitted, the days/times when disconnection is prohibited (reg 8(2)), how health/safety/environment considerations will be assessed before disconnection (reg 8(4)), and how to apply exceptions under sections 56K-56M of the Act (reg 9(1)).
   • Payment and arrears handling: build reminder notice templates, timelines, and pre-remedy checklists to ensure a reminder is sent before any remedy (reg 25(3)-(4)). Create written notification templates for when a remedy is pursued (reg 25(5)).
   • Payment plans: standardise payment plan templates that include calculation methodology, total amount, duration, instalment amounts, renegotiation procedures, and written confirmation processes (reg 26(2)(a)-(e)).
   • Dispute management: implement an internal dispute escalation system that supports suspension of liability for disputed amounts during arbitration/mediation/negotiation (reg 27(1)), and handles Ombudsman complaints as per reg 27(2).

5. Policies for special needs and hardship

   • Engage with the Regulator to identify any existing determinations on special needs customers (reg 3(2)). Ensure codes specify how special needs customers will be identified, registered, and provided with service continuity during interruptions (reg 12).
   • Draft a financial hardship policy consistent with the customer service code and the Act, with clear eligibility, treatment, and monitoring mechanisms (reg 28).

6. Communications and publication controls

   • Keep an up-to-date website repository of fee schedules, calculation methods and policies (reg 14(3)). Implement version control and a public changelog for fee or policy variations.
   • For fee or method changes, apply the minimum notice period specified in the code (reg 14(1)). Where a price determination makes notice unnecessary, document the legal basis for omitting notice (reg 14(2)).

7. Training, recordkeeping and audit

   • Train customer-facing staff on the requirements to provide written reasons for complaint decisions (reg 32(3)), to confirm payment plans in writing, and to supply account/service information within the code’s timeframes (reg 18(2)).
   • Implement records retention for notices sent, payment plans agreed, special meter reads undertaken, and complaint decisions. These records will support compliance reviews and potential Ombudsman or Regulator inquiries.

8. Internal and external compliance checks

   • Conduct an initial legal review and an annual compliance audit of the customer service code against these Regulations, the Act and any Regulator guidelines (reg 5).
   • Monitor Ombudsman determinations and Regulator guidance for interpretive developments, and update codes and operational manuals accordingly.

9. Liaise with stakeholders

   • Communicate the code and charter to customers via bills, website, and customer service channels. Ensure contract templates (where applicable under section 61 of the Act, reg 15) align with the code.
   • For landlords, conveyancers and tenancy services, clarify processes for notification when properties are vacated, sold or leased (reg 33(3)) and offer separate billing options (reg 16).

10. Contingency for disputes and enforcement

• Prepare a compliance playbook to respond to Ombudsman complaints and Regulator inquiries. The playbook should include timelines to produce documents, to implement corrective actions, and to report remediation to the Regulator and affected customers.

Timelines and prioritisation. Immediate priorities on initial implementation are: publish a compliant customer charter (reg 4(1)); ensure payment plan templates meet reg 26 content and written confirmation requirements; implement reminder notice and pre-remedy processes required by reg 25; and ensure website publication of fees and policies (reg 14(3)). Entities must pay particular attention to Regulator determinations about special needs customers (reg 3(2)) and to any price determinations that interact with notice obligations (reg 14(2)).

Record evidence. Because the Regulations set process and disclosure duties rather than criminal sanctions, documentary evidence demonstrating that the regulated entity has incorporated the required matters into its codes and is applying them operationally will be the primary defence against complaints or regulatory action.