For municipal utilities, cooperatives and districts
A disconnection in a cold month is a life-safety event governed by protection rules, and an automated hand anywhere near it — including one that merely orders a queue — is unacceptable. That stays entirely with your staff. What can be carried is the assistance programme paperwork that determines whether somebody ever reaches that point, the outage communication, and the regulatory reporting.
Customers cannot leave. That removes the ordinary feedback of a market and replaces it with a commission, a council, or a member vote — so service quality is judged politically rather than commercially, and the judgement arrives in a public meeting.
Rates are set by somebody else, often on a lagging schedule, so cost increases are absorbed before they can be recovered and the recovery itself becomes a public argument.
Arrears are a social problem wearing an operational costume. A household behind on a utility bill is usually behind on several things, and the assistance programmes that exist to help are administered through paperwork the household is least equipped to complete — an income verification, a form from an agency, a certificate from a doctor for a medical protection.
Outages are the visible failure and communication during one is judged harshly. People want to know when power returns, and the honest answer is often unknown, which reads as evasion.
And regulatory reporting is continuous, detailed and unforgiving, produced by an office that also runs billing, customer service and field dispatch.
Households qualify for assistance and do not receive it because the application requires documents they cannot easily assemble on a deadline — so an avoidable disconnection proceeds through a process where every step was correct.
That is the gap worth closing, and it is entirely administrative. Nobody in the utility wants a disconnection; the outcome happens because the alternative path required a household in crisis to complete a document chase.
So the band is completeness and reach on the assistance side. Naming every required document at once. Confirming a received document is legible and is the item requested. Reminding before a protection or programme deadline rather than after. Reaching the household through the channel that actually works and reporting when none does.
The second band is outage communication: telling people what is known and what is not, in the channel they gave, rather than leaving silence to be read as indifference. Saying "unknown" clearly is a communication outcome, not a failure.
The third is regulatory reporting assembled from data the utility already holds.
What never moves, at any tier and under any configuration: any disconnection decision; any ordering, flagging, scoring or prioritisation of accounts for collections or disconnection; any medical or weather protection determination; any payment arrangement decision; and any credit or deposit determination. The exclusion covers ordering explicitly, because a list somebody works down is a decision made by whoever ordered it.
Assistance applications completed on first attempt — measured by count of applications returned for a missing document, before and after.
Households reaching a protection deadline without applying — measured by count who qualified and did not complete an application, and at which step they stopped.
Households with no reachable channel — measured by count where every channel on file failed, which most utilities have never computed.
Time from assistance enquiry to a complete application — measured by elapsed days to completeness, separated from days to a programme decision.
Outage contacts asking only for status — measured by count of contacts whose entire content is a status question during an event.
Time to assemble a regulatory report — measured by elapsed hours from a report becoming due to submission.
Staff hours on assistance paperwork rather than on households — measured by time-on-task sampling across both, taken the same way before and after.
any disconnection decision; any ordering, flagging, scoring or prioritisation of accounts for collections or disconnection; any medical or weather protection determination; any payment arrangement decision; and any credit or deposit determination. The exclusion covers ORDERING explicitly, because a list a person works down is a decision made by whoever ordered it.
It reads the customer information and billing systems for the administrative purposes named. It has no write path into any collections or disconnection workflow, and no read access to one is requested where it is not needed for assistance paperwork — proximity is the risk, so the access itself is absent rather than controlled.
Assistance programme requirement lists come from the programme’s own published rules and from your utility’s tariff as filed. Nothing interprets a tariff.
Outage information comes from your operations, unchanged. Nothing estimates a restoration time — where operations says unknown, the communication says unknown, because a fabricated estimate is worse than silence and is remembered longer.
And household-facing surfaces are built for an old phone with a screen reader, in the languages your service territory actually speaks, because a household in arrears is not a self-selected online population.
Disconnection is excluded completely, and the exclusion is written to cover the versions that are easy to miss: not only the decision but the list, the order of the list, the flag on an account, and any score that could inform one. A vendor that supplied an ordered list would be making the decision while appearing not to.
The reason is not squeamishness. A disconnection in a cold month can end a life, protections exist precisely because that is true, and a household is the least able party to contest a decision made by a process nobody can see.
Household data stays inside your tenancy, on your retention schedule, exportable by you, and is not used to train anything serving another organisation. Medical protection documentation in particular discloses health information and is handled accordingly.
And on assurance: an independent SOC 2 Type II attestation is in progress and no report exists yet.
The general manager should test the disconnection exclusion by asking for the access list rather than the policy: confirm no credential reaches a collections or disconnection workflow at all.
The commission or council will be asked publicly whether the utility automated disconnections. The one-sentence answer needs to be true and complete, and it is: nothing touches disconnection, including the order of any list.
Counsel should confirm the handling of medical protection documentation against your state rules, which frequently attach specific requirements.
And consumer advocates are a legitimate stakeholder here rather than an obstacle. An arrangement whose entire purpose is getting more households through an assistance application is one they may support — and their scrutiny of the exclusion is worth having before it is worth fearing.
One assistance programme’s prior season, measured retrospectively for how many qualifying households did not complete an application and at which step they stopped — with no account data beyond the application process and no household contacted.
Retrospective, application-only, and nowhere near an account’s collections state. It produces a number most utilities do not have: where in the application households stop.
That number is almost always concentrated at one or two document requirements, and it is frequently actionable by changing a form rather than by buying anything. That is a good outcome and it belongs to the utility.
If it continues, the first grant covers completeness and reminders on that one programme, with the disconnection exclusion written into the scope document and the access list confirmed before anything runs.
It will, unless the exclusion is unambiguous and checkable — which is why it covers the list and the order of the list, not merely the decision, and why the correct test is the access list rather than the policy statement. Confirm no credential reaches a collections or disconnection workflow at all. If a vendor cannot produce that list, the concern is correct.
Very often, and that is where the handoff fails — the household is told to go to an agency, the agency needs a document from the utility, and nobody owns the gap between them. The measurement can be run entirely on your side of it: how many households started an application and did not finish, and where they stopped. If the concentration is on an agency-side document, that is a finding to take to the agency rather than a system to buy.
It does when the message contains an estimate that turns out to be wrong. Nothing here estimates anything — where your operations says unknown, the message says unknown, plainly. Saying "we do not know yet and we will tell you when we do" is a communication outcome rather than a failure, and it is remembered far better than a confident estimate that slipped twice.
Then do not touch it. The retrospective measurement reads application-process data rather than driving the billing system, and the first operated scope is completeness and reminders on an assistance programme, which sits beside billing rather than inside it. If even a read against your customer information system is an unacceptable operational risk, the honest answer is that this is not available to you and we would rather say so than design around a system your team is right to protect.