
Reviews
Part of EV charging demand charges multifamily: five records, five steps
Multifamily EV demand charge reviews: how to compare evidence before you decide
Compare multifamily EV demand-charge review paths by evidence quality, meter context, decision scope, data access, ownership, resident impact, and next actions.
Compare review methods by what each one can establish, not by a predicted bill outcome. An account-record review, a meter-map reconciliation, and a provider-configuration review may all be necessary.
What to take away
- A complete review identifies its exact decision question before it gathers data.
- Metering, rate design, charging controls, and customer-facing service are separate topics with different sources.
- A blank field in a comparison sheet is a useful finding, not a reason to guess.
- Choose the next evidence action when the record cannot support a decision.
Compare scope before comparing data
Lawrence Berkeley National Laboratory's EV Retail Rate Design 101 describes metering configurations, energy and demand charges, charging controls, and load flexibility as distinct rate-design subjects. Use it to keep evidence categories separate before comparing review paths.
Review paths and evidence
Review path
- Account-record
- Which bill and meter
- Meter-map
- Which service is connected
- Provider-record
- What configuration exists
- Resident-service
- What property tells users
Question it answers
- Account-record
- Complete bill and account
- Meter-map
- Current map and identifiers
- Provider-record
- Account access and export
- Resident-service
- Approved signs and app text
Evidence needed
- Account-record
- Charger configuration
- Meter-map
- Tariff interpretation
- Provider-record
- Utility billing conclusion
- Resident-service
- Rate or savings claim
Cannot settle
- Account-record
- Meter-map
- Provider-record
- Resident-service
Use a comparison sheet that asks what the review is for. Do not compare a platform setting against a bill as though they answer the same question.
Question it can help answer
- Account-record review
- Which bill and meter are under discussion?
- Meter-map review
- Which physical service is connected to the question?
- Provider-record review
- What configuration or session record is available?
- Resident-service review
- What is the property currently telling users?
Evidence it needs
- Account-record review
- Complete bill, account, and billing period
- Meter-map review
- Current map and verified identifiers
- Provider-record review
- Account access and dated export
- Resident-service review
- Approved signs, app text, and support script
What it cannot settle alone
- Account-record review
- A charger configuration result
- Meter-map review
- A tariff interpretation
- Provider-record review
- A utility billing conclusion
- Resident-service review
- A rate or savings claim
Worked example. A property asks why a July demand charge rose. Fill one row like this:
- Bill
- account number, service address, rate schedule, billing period, billed demand in kW, and energy in kWh.
- Meter map
- meter number, charger group, and service address.
- Provider export
- session start and stop, charger ID, energy delivered, and maximum kW for the same period.
If billed demand is more than 10 kW above the provider export peak, a typical review threshold, request a meter-map review. If the bill lists demand but the provider export peak is lower, request a utility service-account confirmation. It should contain the utility name, account number, service address, meter number, rate schedule, and confirmation date.
A typical US commercial demand charge ranges from about $10 to $25 per kW-month, but the bill and tariff determine the actual figure.
Test the evidence quality
For every path, record four checks: source date, accountable owner, missing context, and next action. A recent export with no account or meter relationship is incomplete. A complete bill with no charging-service map is also incomplete for a charging question.
Use direct labels. "Confirmed" means the source supports the connection. "Reported" means a party stated it but the file still lacks verification. "Needs review" means the property has identified the gap and assigned it. Those labels give decision makers a more honest picture than a single pass-fail score.
The Department of Energy's financial-considerations training notes that charging costs can be affected by demand charges, time-of-use periods, and metering approaches. Use that list to check whether a cost question needs a bill, a meter record, or a provider export before assigning an owner.
Assign the right review owner
The comparison works best when it names who can resolve each gap. A property manager may gather a resident report and current notice, while an account holder may retrieve a bill.
A provider administrator may export a setting or session record, and a qualified technical or utility contact may clarify a meter relationship. The worksheet should route a question, not imply one person decides everything.
The Federal Energy Regulatory Commission's energy-markets page explains that FERC oversees wholesale and interstate matters, while retail service is generally regulated by state authorities. That separation supports routing a retail account question to the local utility and applicable regulator rather than treating a national source as a property-specific answer.
| Unresolved question | First owner to contact | Record to request |
|---|---|---|
| Which account was billed? | Authorized account holder | Original bill and service reference |
| Which meter serves a charger group? | Technical or utility contact | Current map or verified connection record |
| What did the platform do? | Provider administrator | Dated configuration or event export |
| What was communicated? | Policy or support owner | Current approved message |
| What changed recently? | Change-process owner | Approved change and verification record |
Decide the next action by question type
A provider question may require access to a configuration record. Use this table to turn a question type into the next action. Set a first-artifact deadline of 5 to 10 business days, a typical review window, and assign an owner.
| Question type | Next action | Artifact to request |
|---|---|---|
| Billing or account | Ask the authorized account holder to retrieve the bill. | Utility service-account confirmation with utility name, account number, service address, meter number, rate schedule, and confirmation date. |
| Meter relationship | Ask the technical or utility contact to verify the map. | Current meter map with meter number, charger group, and service address. |
| Provider configuration or session record | Request access to the configuration record and a dated export. | Provider session export with session start and stop, charger ID, energy delivered, and maximum kW. |
| Resident message | Ask the policy owner to confirm the approved text. | Current approved message and support script. |
| Cost or savings claim | Request the bill and tariff instead of forecasting. | Utility service-account confirmation plus current tariff sheet. |
Common platforms include ChargePoint, Blink, and SWTCH. The export fields to request do not change by brand. If the record does not establish an outcome, take the narrower next action. Do not score a path by supposed savings, a universal rate, or a generic charger specification.
Record the decision that was actually made
End the sheet with one action that the evidence supports. Examples include asking the utility to confirm a service-account question, asking a provider to identify its monitored point, or scheduling an approved configuration review. State what remains unanswered. The next reviewer should be able to tell the difference between a completed document request and a completed billing conclusion.
The National Archives' records-management guide explains why records preserve evidence of actions and decisions. Keep the selected path, source packet, owner, and response together so a future review does not mistake an open request for a confirmed answer.
Comparison closeout checks
- Does the selected path answer the stated question and no broader one?
- Are account, meter, provider, and resident-service records kept distinct?
- Is every missing relationship assigned to an owner and next action?
- Is the resident message unchanged until a responsible decision supports an update?
- Can the team retrieve the source behind the comparison result?
Common questions
Can a property compare providers by their demand-charge savings claims?
No. A property should first compare the evidence, scope, installed configuration, and decision authority relevant to its own service. Savings claims require separate current verification.
What if two records name different meters?
Preserve both records, mark the conflict, and send the specific relationship question to the owner who can verify it. Do not select the more convenient record without evidence.
Does this comparison select a tariff?
No. It organizes review paths and missing evidence. A tariff decision requires current, property-specific material and appropriate utility or qualified review.







