Apartment EV power sharing records: an organizing guide

Apartment EV power sharing records answer four questions: which stations share a power budget, which allocation policy version governs them, what a resident was told, and who holds the provider account. A former board member should not be the only source for any of the four.

What to take away

The sharing-group record has two spines

The first spine is membership: which station IDs draw from one shared capacity, where they sit, and what boundary separates that group from the next. The second is the allocation policy version, the dated document that says how the shared capacity is divided when demand exceeds it.

Everything else hangs off those two. A test result means nothing without the policy version it was run against. A resident complaint means nothing without knowing which group the station belongs to.

Confirm panel capacity and circuit details with a licensed electrician or professional engineer, and confirm any code question with the authority having jurisdiction. The record stores their findings; it does not replace them.

Keep the resident rule separate from the setting

A configuration sets a current limit. A resident-facing rule says what a driver may expect: how long a session runs, whether idle fees apply, how a queue works, what happens during a demand event.

These are two documents. The setting changes when an engineer changes it. The rule changes when the owner or board approves a new version, and it carries an effective date and an approver.

When a resident says the chargers slowed down, the first useful question is which document moved. If the policy version is unchanged and the configuration is unchanged, the event is a fault. If either moved, the event is a policy question.

Write events as observations

For each report, capture the date and time. Capture the station ID and visible status. Capture what the driver described and what was done immediately. Also capture who was notified and the next action. Leave out conclusions.

"The station stopped mid-session" is usable. "The system failed" is a finding, and findings belong to whoever verified them, with a name and a date attached.

The National Archives' records-management introduction makes the point that records exist as evidence of decisions and activity. An event log with a final unchecked comment gives a future manager nothing to verify against.

Keep access and personal data out of the asset file

The group record should point to an authorized account process, never hold credentials. It should point to a support case, never copy payment details or identity documents into a shared folder.

NIST's Privacy Framework resource center describes a voluntary approach to identifying and managing privacy risk. For a property file, the working version is narrower: keep the minimum needed to route an event, and keep the rest in the restricted process that already exists for resident data.

A station ID and a timestamp usually carry a technical review. A copied receipt rarely does.

Name owners on both sides of a handoff

A provider change, a management change, or a new board is a handoff event, and it needs a record of its own. Fill in both columns before the outgoing party leaves.

The Department of Energy's smart-charge management implementation guidance links operational planning to asset information and defined roles. That is the same list, applied to a handoff instead of a launch.

NREL's multifamily charging research shows that charging patterns follow building and use assumptions. Its apartment-load profile report is a modeling resource, not an operating requirement. It supports keeping the reasoning behind an allocation decision, not just the number that came out of it.

Run a retrieval drill, not a reading

Once a quarter, hand the file to someone who did not build it and give them a task: a resident reports that a specific station charged slowly last Tuesday night.

Ask them to produce the group that station belongs to. Ask for the policy version in force that night. Ask for the configuration reference. Ask for the last test. Ask for the open items. Ask for the name of the person who can change the setting.

Time it. If the drill takes an afternoon, the file is the problem, not the charger.

A drill also surfaces the quiet failures: a group owner who left, a provider contact that bounces, a policy version with no approver recorded.

Version every policy change

When a group, an allocation setting, a resident rule, or a support path changes, keep the prior version. Include its date, the reason, the approver, the equipment affected, and the notice sent to residents.

A future manager needs to know whether a complaint came from the current rule or from a stale notice, account, or setting. Without versions, that question has no answer.

Common questions

Does a policy revision always change the technical record?

Not always, but check both. A policy can describe behavior that a configuration produces, so a change in either one may require the other to be reviewed and retested.

How much detail belongs in an event log?

Enough to identify the station, the condition, the response, and the next owner. Personal and payment details stay in the restricted process, not in the shared asset file.

What makes a provider handoff complete?

Every row in the handoff table filled with a name on each side, plus a retrieval drill the incoming operator passes without help from the outgoing one.

Who should own the sharing-group record?

One named person with a named backup, usually the property manager or the board's charging liaison, with the provider holding the account and the association holding the policy versions.