ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Instructions (delete this section before submitting this file):
2
1. Do not rename, reorder, add, or delete columns, except attribute_<name> columns, which can be renamed and added. See the Field definitions tab for column details.
3
2. Each row must be a unique address. hashed_address_line, and postal_code are required in every row. attribute_<name>, and exclusion_reason may be left blank.
4
3. Add up to 10 attribute_<name> columns as needed (for example, attribute_Feeder, attribute_Substation).
5
4. Use the exclusion_reason column to note why an address should be excluded from the ESC program, if applicable.
6
5. Save as a CSV file (.gz optional), named: esc_hashed_addresses.<YYYY_MM_DD>.csv(.gz) — for example, esc_hashed_addresses.2026_07_21.csv.
7
6. Share the file with your Customer Success Manager, or upload it to incoming/program_id=<your_program_id>/ in the shared AWS S3 bucket.
8
* Always upload/share the complete file whenever the data changes.
9
** Files that do not meet these requirements will be rejected.
10
11
hashed_addresspostal_codeattribute_Feederattribute_<name>attribute_<name>exclusion_reason
12
149f17d00cb1cf030a4aefc4f7f73e9d12345Feeder0001OTHER_PROGRAM
← example row, replace with real data
13
58ed404f9f96c22ef0d0ec40e3ad60d112346Feeder0002
← example row, replace with real data
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100