Classify and acknowledge the concern.
METRO POWERA.M.P.E.R.E. · Annex JComplete Protocol PDF ↗A.M.P.E.R.E. TOOLKIT · ANNEX J
Complaint and Dispute Resolution
Structures intake, service levels, evidence, escalation, mediation and reporting.
ConsumersPhase 10 · Complaint and Dispute Resolution
WHY THIS ANNEX EXISTS
A decision instrument, not a paperwork exercise.
Provide an accountable path for receiving, investigating, correcting and learning from AMI-related consumer concerns.
Start with uncertainty.
Use the annex to make the decision and its missing evidence visible before discussing a preferred product or schedule.
- 01Where can consumers raise installation, privacy, billing or service concerns?
- 02What evidence must be preserved for each complaint type?
- 03Who owns first response, technical investigation and escalation?
- 04How are corrections, explanations and unresolved disputes recorded?
WHAT THE TEAM BRINGS
Required inputs
- Complaint categories and existing channels
- Billing, meter, event, work-order and communication records
- Service levels, authority and escalation rules
- Legal, regulatory and mediation requirements
WHAT THE TEAM PRODUCES
Controlled outputs
- Complaint workflow and service levels
- Evidence checklist by complaint type
- Escalation and resolution register
- Trend and corrective-action reporting
Four disciplined moves.
Preserve the relevant technical, billing and communication evidence.
Assign investigation and decision authority.
Communicate the outcome, correction and escalation options clearly.
IMPORTANT CONTROL BOUNDARY
What this page does not do.
The framework does not replace applicable consumer-protection, regulatory, legal or formal dispute processes. This educational page explains the instrument but does not reproduce its complete working tables. Use the controlled Protocol PDF and the responsible professional or authority for actual project work.
USE THE AUTHORITATIVE VERSION
Open the complete working instrument in Protocol 3.2.
The downloadable publication preserves the full annex, version context and framework limitations.