Back to solution library
B12

Change-of-User and Change-of-Occupancy Workflow

Change-of-User Workflow

Overview

What This Option Does

Create a fast way to update the account when a user moves, a tenant changes, a stall changes hands, or a service point is subdivided or merged. Many coverage and arrears problems begin when the account no longer matches the current user. Fast change management protects both revenue and user trust.

Most Useful When
  • Arrears are often disputed because they relate to a previous user.

  • Properties, stalls, or service points change hands often.

  • Many users say the bill is not in the name of the person actually responsible.

Legal requirements

The city needs authority to amend customer records on proof of occupancy, control, or service responsibility.

Administrative requirements

Use a short change form, a simple document checklist, a clear service standard for updates, and a full audit trail of every account change.

Usually Not Best First Move
  • There is no practical way to verify who the current user is.

  • The service point itself is not clearly defined in the register.

  • Liability application overviews

  • These cards help the city apply the approved schedule, class, tariff, or usage basis more consistently.

Full details

Overview

Create a fast way to update the account when a user moves, a tenant changes, a stall changes hands, or a service point is subdivided or merged. Many coverage and arrears problems begin when the account no longer matches the current user. Fast change management protects both revenue and user trust.

Practical implementation path
  • Create a simple change-of-user or change-of-occupancy form that can be submitted at service offices, municipal counters, or through a basic digital channel.

  • Decide what proof is sufficient to transfer or update the account and how outstanding balances are treated when a user changes.

  • Make sure the old account is closed or suspended correctly and that the new account starts with the right tariff and service basis.

  • Track the time between occupancy change and account update so the city can see where revenue is being lost during handover periods.

Legal and institutional requirements

The city needs authority to amend customer records on proof of occupancy, control, or service responsibility.

Administrative Setup

Use a short change form, a simple document checklist, a clear service standard for updates, and a full audit trail of every account change.

When this is a strong fit
  • Arrears are often disputed because they relate to a previous user.

  • Properties, stalls, or service points change hands often.

  • Many users say the bill is not in the name of the person actually responsible.

When this is less suitable
  • There is no practical way to verify who the current user is.

  • The service point itself is not clearly defined in the register.

Risks And Design Notes
  • Do not create accounts that cannot be matched to a real service point, user, or occupancy event. Weak account creation can produce a second round of billing disputes later.

  • Where households are vulnerable, explain that better coverage is about fair billing and service continuity as much as it is about revenue.

  • Liability-application full cards

  • These cards are about making sure the city applies the approved class, tariff, band, exemption, or usage basis more consistently.