How to keep multifamily EV charging records usable at handoff and review

Keeping multifamily EV demand charge records usable starts with one practical question: can an authorized person find the current source and identify what it concerns? The record system is not a tariff interpretation or a savings model. It is a durable operating file.

What to take away

Create a source index

The Department of Energy's utility-data access guide covers how customers and their authorized agents get usage data out of a utility. The named standard behind most of that access is Green Button; its companion, Green Button Connect My Data, lets an authorized property pull interval usage and billing line items straight from a participating utility's portal, such as Con Edison's or Xcel Energy's. The guide also notes that utility bills can contain detailed line items and that the method used to collect data affects its availability and quality. The guide is for broad energy-data management, but it supports a simple property rule: retain the original source and record how staff obtained it.

The index needs only enough information to retrieve and understand a record. Avoid a giant spreadsheet that repeats every bill detail. Use the original file for the detail and the index for its context.

Charging-service records live in the network portal that runs the stations. Portals such as ChargePoint, Blink, and EVgo hold session exports showing the kWh delivered, the session start and stop times, and the station or port identifier. Keep the export itself rather than a summary of it, plus the network's invoice number for any transaction or service fee it bills, because those fields are what tie a utility bill back to the sessions on the property.

Preserve snapshots and changes

Do not overwrite a prior map, configuration note, or resident message when a change occurs. Keep the former version and add a new dated version with the reason for the update, approval owner, affected charging group, and related test or communication record. That history helps a later team understand what changed without claiming why a bill changed.

An ordinary source index can link the pieces together by date and identifier. It does not need internal article links or elaborate software. A shared, authorized location with a clear retention practice is more useful than scattered inbox attachments and screenshots.

Use a shared drive for the index and change log. Keep provider portal exports in the portal when the portal is the system of record. Name a property or operations owner for the index.

The National Archives' records-management guide explains that records provide evidence of actions and decisions, and a versioned source index can show which file was current at approval.

Keep personal and operating data apart

The shared record should identify where an authorized person can find the needed information. It should not store passwords, copied payment information, or more resident data than an operations review needs. A station identifier, account reference, time, and controlled support-case number are often enough to open a support case.

NIST's Privacy Framework resource center offers a voluntary approach to managing privacy risk; give every field a defined purpose and keep personal data in the controlled system.

Run a retrieval check at handoff

At least once during a management transition or provider handoff, run a retrieval check. Ask an authorized operator to find the current utility source, identify the account and meter, locate the current charging-service map, read the active resident message, and name the support or review owner. Log anything that cannot be found.

Use the result to update access, not to recreate history. If a provider platform changes, retain the last accessible export and document the new access route. If a staff member leaves, assign the source index and open-items log to a new accountable owner.

Keep questions separate from records

An open-items log is part of the system, but it should not edit the evidence. A good entry says what is unknown, which source could answer it, and who owns the next step. It does not turn an unanswered question into an operational, billing, or tariff conclusion.

This distinction becomes important when a resident asks about a visible session, a staff member finds a new bill, or a provider proposes a setting change. The property can record the question against that source without giving advice beyond the evidence.

The Department of Energy's financial-considerations training discusses demand, rate, and metering factors that may affect charging cost. It does not answer a specific multifamily bill question. It supports preserving separate source records so a team can determine which evidence is relevant before offering a conclusion.

Handoff check

Retention lookback

Typical contractual or utility lookback windows run 3 to 7 years. The period that actually binds a property comes from the utility's filed tariff — look for the record-retention provision in the general terms and conditions of the tariff — and from your state public utility commission's rules on billing records and customer disputes. Confirm the exact period with counsel before you purge. A named recordkeeping standard can help structure the file, such as ARMA's Generally Accepted Recordkeeping Principles or ISO 15489-1.

Common questions

How long should the property keep these records?

Follow the property's approved retention requirements and any applicable contractual or legal obligations. The retention lookback section gives typical windows to confirm with counsel.

Should a property keep screenshots from a provider platform?

Keep the original export or source record when authorized and available. A screenshot may be useful context, but it often lacks the metadata needed for a later review.

What is the purpose of the handoff check?

It verifies that an authorized person can find the current materials and log unresolved questions. It does not certify a tariff, bill, configuration, or engineering conclusion.