The Case That Falls Apart Without Documentation
A raid team documents an unauthorized connection at a commercial premises. The consumer has bypassed the meter and connected directly to the service intake. The team disconnects the supply, issues a verbal notice, and moves on. Three weeks later, the consumer contests the penalty. The field team's recollection is that the connected load was about twice the contracted load. "About" doesn't hold up at a tribunal, and neither does a verbal recollection of what the meter balance showed.
The Sgm Raid Reporting template exists to convert a raid into an evidence package on the same day it happens — while the GPS pin is still accurate, the meter number is still in front of you, and the photos capture the bypass wiring before it gets removed.
Contracted vs. Connected: The Number That Drives the Penalty
The most operationally significant fields in this template are contracted load and connected load. The gap between these two figures is the quantification of the offense. A consumer registered for a 5 kW sanctioned load running 11 kW of connected equipment isn't an ambiguous situation — the delta is the load theft, and that calculation flows directly into the penalty computation.
The irregularity types multichoice field forces the field team to classify the method precisely: Bypass, Unauthorized Connection, Excess Loading, Unrecharged, or Meter Defect. These categories aren't interchangeable. A bypass — where the meter is shorted out entirely — has a different penalty structure and a different legal standing than excess loading, where the meter is intact but the contracted limit is exceeded. Getting the classification right in the field, at the moment of discovery, is what prevents reclassification disputes later.
Meter balance and last recharge date add the financial dimension. For prepaid meter systems, a balance that has been sitting at zero for 11 days while the property continues to draw power is a different offense profile than a meter running negative — the former suggests tampering, the latter suggests a system error or defect. The last recharge amount creates a cross-check: a consumer recharging minimal amounts at irregular intervals while running high-load equipment is a pattern that shows up in the data when you can see both numbers together.
Closing the Case in the Field
The action taken field — Disconnected or Deadline Given — combined with amount received and Resolved? creates a live enforcement dashboard. When a supervisor filters for all raids where Resolved is false and a deadline was given more than seven days ago, those are the follow-ups that need to happen today.
Assigned to links to the technician responsible for the remediation or reconnection work. Reporter ID links into the HR sub-library, tying the raid record to the specific agent who conducted it. If a consumer challenges the report, you know exactly who was on site.
The GPS location field is the one that ends location disputes. When a consumer claims the raid occurred at a neighboring address, the pin doesn't lie.