Guides
Part of EV charging demand charges multifamily: five records, five steps
Multifamily EV demand charge evidence: packets by recipient
Multifamily EV demand charge evidence goes to three readers: the utility, the charging provider, and the owner. Build one packet for each.
Multifamily EV demand charge evidence is only useful when it reaches the party that can act on it. A utility, a charging provider, and a property owner each need a different packet drawn from the same records. Sending everyone the same stack of files slows the answer and invites a question about one account to be answered with material from another.
What to take away
- Build one packet per recipient, each aimed at one question.
- Draw every packet from the same account-and-meter register.
- Ask the receiving party for its request format before assembling the packet.
- Send each reader only the records its question needs.
- Mark every unproven link as confirmed, reported, or unresolved, never as a conclusion.
Match the packet to the recipient
A packet goes to the party that can act on it, and the purpose differs by recipient. The table shows the three common routes, what each reader can answer, and what to put on the first page.
| Recipient | Can answer | Include first |
|---|---|---|
| Utility | A rate or billing question | Service address, account number, meter number, bill period |
| Charging provider or operator | A request for account and charger data | Provider account ID, charger group, support contact |
| Property owner or board | A cost decision | Source records, open items, proposed payer |
Open each packet with one question
The first line of a packet is the question, written so that the reader can answer it without reading the rest. Each recipient gets a different question, because each holds different records.
Utility: Which rate schedule applies to the account and meter on the attached bill page, and how was the billed demand for this billing period set?
Provider: Please export the session and power records for the charger group named below, for the stated period, and confirm which provider account they sit under.
Owner or board: Approve or decline the proposed payer for the demand-related cost line. The open items are listed with owners.
If a packet needs two questions, split it into two packets. A reader who must choose which question to answer tends to answer the easier one.
What goes in each packet
The utility packet is a rate or billing question with the records that identify the account. The provider packet is a data request. The owner packet supports a cost decision and shows which items remain open.
Utility packet:
- The one rate or billing question, stated first
- Service address, account number, meter number, and bill period under review
- The original bill page and the tariff sheet it cites
- The meter map showing which charger groups sit behind the meter
Provider packet:
- The request for account and charger data, stated first
- Provider account ID, charger group, and support contact
- Whether each charger-to-account link is confirmed, reported, or unresolved
Owner or board packet:
- The cost decision being asked for
- The register rows and the source records behind them
- Open items, each with an owner and a follow-up date
- The proposed payer, marked unconfirmed until the board decides
What to leave out of each packet
A smaller packet is easier to answer and exposes less. Each recipient needs only the records behind its own question, and the other two readers' material stays in the property file.
| Recipient | Leave out | Why |
|---|---|---|
| Utility | Resident names, session payment data, provider chat logs | The question is about the rate and the meter |
| Charging provider | Board minutes, the tariff analysis, cost opinions | The provider can answer a data question, not a billing one |
| Owner or board | Raw resident account data | Link to the original in the authorized property location instead |
Ask the recipient how it wants the packet
Ask for the receiving party's request format before you assemble the packet. Utilities commonly name a business account representative or a written-request address on the bill. Charging providers commonly take an evidence request through a support ticket tied to the account.
Where no format is published, ask the account representative which document the reviewer will accept. Ask a provider the same question before buying; the questions for bidders include data access among the items to settle.
Find the rate source for the property's state
State public utility commissions publish the tariffs that set demand charges, and their staff can confirm which rate schedule applies to a property. Examples include the California Public Utilities Commission and the New York State Public Service Commission.
A property in another state can find the equivalent office from the bill or the utility's business representative. The rate and the window come from the utility and the rate schedule.
A demand charge on a multifamily or commercial bill usually appears as a billed demand in kW times a rate per kW that the tariff sets, with the demand window tied to a separate meter reading.
The strongest evidence is the bill page and the tariff sheet that show them, not a figure recalled from an earlier conversation. See what drives multifamily charging cost for the wider cost picture, and the apartment charging cost guide for budgeting.
Draw every packet from one register row
Create one row for every account that may matter. Do not assume that a charging provider account and a utility account refer to the same thing. The row should tell a later reviewer where the original material lives and who can answer questions about it.
Account-and-Meter Register Fields
- Source typebill, notice, export, map
- Obtained datereceived or downloaded
- Account and meterexact identifiers
- Period or timestampbilling or export time
- Charging contextrelevant charging group
- Statusconfirmed, reported, or needs review
The Department of Energy's data guidance tells organizations to match meters with assets and to eliminate inactive accounts. For a charging property, the same habit means every charger group points to a meter, and every meter row points back to a current account.
Log each reply against its question
When a reply arrives, file it beside the packet it answers. Note the date sent, the date answered, who replied, and whether the answer matched the question asked. A reply to a different question is a new open item, not a closed one.
The National Archives describes records as the evidence of the agency's actions, which is the idea behind keeping the original reply. Save it unedited, and put any summary in a separate working note so a later operator can trace a claim back to its source.
For a condo, the board approves the next step, so see condo EV charging planning. A practical guide to testing multifamily charging can follow once the replies are filed.
Common questions
Is a charger-session export enough evidence for a demand-charge question?
No. It may support a record of charging activity, but it does not by itself establish the relevant utility account, meter, rate treatment, or bill result.
Can one packet go to all three readers?
It can, but it should not. Each reader needs a different first page, and a shared stack invites an answer drawn from the wrong account.
What if the recipient answers a different question?
File the reply, and open a new item for the question that is still unanswered. Do not mark the original question closed because a reply arrived.
