Back to Customer Service
Customer Service
Local Government
Updated March 2026

Local Government Customer Data Update

A procedure for processing community member requests to update their personal or account information accurately and securely while maintaining data integrity and compliance.

Purpose

To ensure community member data is updated promptly and accurately upon request, maintaining data quality across all systems while protecting community member privacy and complying with data protection regulations.

Scope

Covers all community member-initiated requests to update personal information such as name, address, phone number, email, payment details, or account preferences across all systems where the data is stored.

Prerequisites

  • Data update procedures documented and aligned with privacy and data protection regulations
  • Identity verification protocols defined for each type of data change
  • Staff trained on data handling, privacy requirements, and system update procedures
  • Audit logging enabled on all systems that store community member data
Compliance Note

Supports Local Government Act compliance, freedom of information requirements, and public accountability standards.

Step-by-Step Procedure

1

Receive the Data Update Request

Accept the community member request to update their information and record the details of the change requested.

  • 1.1Log the request including the community member identifier, the data field to be updated, and the new value
  • 1.2Identify the type of data change and the verification level required
  • 1.3Inform the community member of the verification and processing steps
Customer Service Representative
3 minutes
CRM System, Ticketing System
2

Verify Community member Identity

Authenticate the community member identity using the verification protocol appropriate for the type of data being changed.

  • 2.1Request verification information such as security questions, identification documents, or account credentials
  • 2.2Validate the provided information against the records on file
  • 2.3If verification fails, decline the request and advise the community member on alternative verification methods
Customer Service Representative
5 minutes
CRM System, Identity Verification System
Tips
  • Higher-risk changes such as email, payment details, or name changes require stronger verification
3

Validate the New Data

Check that the new information provided by the community member is complete, correctly formatted, and valid before entering it into the system.

  • 3.1Confirm the data format is correct, such as valid email address format or proper postal code
  • 3.2Check for any obvious errors or inconsistencies in the new information
  • 3.3Ask the community member to confirm the new data by reading it back or reviewing the written submission
Customer Service Representative
2 minutes
CRM System
4

Update the Primary System

Make the data change in the primary community member record system, ensuring the update is applied correctly.

  • 4.1Navigate to the community member record in the CRM and update the relevant field
  • 4.2Double-check the updated record for accuracy before saving
  • 4.3Record the change in the system audit log with the reason and authorisation
Customer Service Representative
3 minutes
CRM System
5

Propagate Changes to Connected Systems

Ensure the data update is reflected in all systems that hold the community member information, whether through automatic synchronisation or manual update.

  • 5.1Verify whether the update propagates automatically to connected systems such as billing, shipping, and marketing platforms
  • 5.2Manually update any systems that do not synchronise automatically
  • 5.3Confirm the data is consistent across all systems
Customer Service Representative
5 minutes
CRM System, Billing System, Marketing Platform
6

Confirm the Update with the Community member

Send the community member a confirmation that their data has been updated, along with details of the change.

  • 6.1Send a confirmation email or message summarising the data change
  • 6.2Include instructions for the community member to contact support if the change is incorrect or unauthorised
  • 6.3If the change affects login credentials, remind the community member of the new details
Customer Service Representative
2 minutes
Email Platform, CRM System
Tips
  • Sending confirmation to both the old and new email address when an email change is made provides an important security safeguard
7

Handle Sensitive Data Changes

For changes to sensitive data such as payment information or legal name, follow the enhanced security protocol and obtain required approvals.

  • 7.1Apply the enhanced verification procedure for sensitive data changes
  • 7.2Obtain supervisor approval if required by the security protocol
  • 7.3Document the additional verification steps taken in the audit log
Customer Service Team Lead
10 minutes
CRM System, Identity Verification System, Approval Workflow
8

Audit and Report on Data Updates

Review data update activity regularly to identify patterns, ensure compliance, and detect any suspicious activity.

  • 8.1Review the data update audit log for completeness and compliance
  • 8.2Flag any unusual patterns such as high-frequency changes or changes to multiple accounts from the same source
  • 8.3Generate monthly reports on data update volume, types, and any compliance findings
Customer Service Manager
20 minutes
CRM System, Reporting Dashboard, Audit Log

Quality Checkpoints

Community member identity is verified according to the appropriate protocol before any data change is made
Updated data is validated for format and accuracy before saving
Data consistency across all connected systems is confirmed after each update
Monthly audit of data update logs is completed with findings documented

Common Mistakes to Avoid

Updating community member data without completing the identity verification step, which creates a security risk
Failing to propagate the change to all connected systems, which causes data inconsistencies
Not sending a confirmation to the community member, which can lead to unnoticed errors or undetected unauthorised changes
Not maintaining audit logs of data changes, which compromises compliance and traceability

Expected Outcomes

Data Update Processing Time

Average time from receiving a data update request to completing the update and sending confirmation.

Data Accuracy Rate

Percentage of data updates processed without errors, measured through quality audits.

Unauthorised Change Detection Rate

Number of suspicious or unauthorised data change attempts detected through verification protocols and audit reviews.

Frequently Asked Questions

How long does it take to process a data update?

Most data updates are processed immediately during the community member interaction. Changes requiring additional verification or approval may take one to two council days.

How does the council ensure data changes comply with privacy regulations?

All data changes are subject to identity verification, audit logging, and periodic compliance reviews. The process is aligned with applicable data protection legislation and the council privacy policy.

What types of data can community members update through community member service?

Community members can update contact details, mailing address, phone number, email address, communication preferences, and payment information. Name changes and other legal data changes may require additional documentation.

What identification is required to update community member data?

The verification level depends on the type of data being changed. Basic changes may require security questions or account verification. Sensitive changes such as payment details or legal name require government-issued identification.

Can data updates be requested through self-service channels?

Yes. Community members can update basic information such as address and phone number through the online portal. Sensitive changes still require identity verification through community member service.

Want this customised for YOUR business?

We'll tailor every step to your exact operations, tools, and team structure.