Guides
Part of Apartment EV charger power sharing: write a clear rule
Apartment EV charger power sharing gaps: what to check before you assign
Spot apartment EV power-sharing gaps in 2027 by checking the allocation rule, resident promise, assets, data dependencies, incident route, and recovery evidence.
Apartment EV charger power sharing gaps become visible when a property makes a broad promise but cannot identify the active allocation rule, participating chargers, resident message, support owner, or recovery path. A useful review turns each uncertainty into an evidence request rather than a verbal reassurance.
What to take away
- A claim that power is shared automatically is not a complete operating record.
- Check whether the written policy matches the current configuration, such as circuit-level current limiting or scheduled load management.
- Log missing evidence, incidents, and changes with an owner and due date.
- Separate a charging-session report from a parking, billing, or technical issue.
The pre-assignment checklist
Before a property assigns responsibility for a shared charger group, or assigns capacity to a stall, verify these items:
- Circuit map and panel schedule.Which chargers share a breaker or feeder, the breaker and conductor size, and where the panel schedule is kept.
- Load calculation.The spare capacity available for EV load, calculated under NEC Article 220, with the EV supply equipment itself governed by NEC Article 625.
- Allocation rule.Whether the group limits current at the circuit level or runs scheduled load management, the share assigned to each stall, and the time windows when a charger may draw full current.
- Control baseline.The networked charger's OCPP version, whether it supports ISO 15118 vehicle communication, the SAE J1772 connector in use at each stall, and the firmware and configuration record currently loaded.
- Equipment listing.Evidence that the charger is listed to UL 2594 and that its protective system meets UL 2231.
- Permit, inspection and utility.The electrical permit and final inspection from the local authority having jurisdiction, plus any utility interconnection or service-upgrade approval the added load requires.
- Cost and who pays.Which party pays for panel, circuit and networking work, which pays for each driver's sessions, and the resident notice that states it.
- Service route.The named charging network operator or service provider, the licensed electrical contractor, and the property role that owns each.
Check the promise against the evidence
Ask which charger group is affected, what condition changes a session, what a driver sees, who owns the current setting, and what record proves it. A product-family page or an old demonstration does not answer those questions for the current property configuration.
Warning Sign vs Evidence Needed
Warning sign
- "Fair for everyone"
- Defined allocation and resident rule
- "System handles failures"
- Documented behavior, alert, recovery, retest
- "New charger is equivalent"
- Asset, configuration, policy-change review
- "Staff can fix it"
- Authorized role and support path
Evidence needed
- "Fair for everyone"
- "System handles failures"
- "New charger is equivalent"
- "Staff can fix it"
The Joint Office of Energy and Transportation explains that trustworthy charging transactions depend on consistent measurement and transparent information for consumers. Its charging price-transparency overview is not an apartment power-sharing standard. It supports one narrow review habit: when a property makes a resident-facing allocation or billing statement, the records should identify what the statement measures and who can verify it.
| Warning sign | Evidence needed |
|---|---|
| "It is fair for everyone" | Defined allocation and resident rule |
| "The system handles failures" | Documented behavior, alert, recovery, and retest |
| "The new charger is equivalent" | Asset, configuration, and policy-change review |
| "Staff can fix it" | Authorized role and support path |
Use a small issue log
Record the condition, affected group, missing fact, temporary response, owner, due date, and closure evidence. An issue log lets staff preserve facts without making a technical conclusion during a resident complaint.
| Condition | Group | Missing fact | Owner | Due date | Closure evidence |
|---|---|---|---|---|---|
| Two chargers on one circuit deliver 16 A each instead of 32 A (typical range) | Building A, stalls 4 and 5 | Approved circuit-level current limit setting | System operator | 10 business days from log date | Configuration record showing 32 A limit and a test session log |
The National Archives' basic records guidance describes records as evidence. A property can apply that idea by saving the document, support-case reference, or approved configuration record that closes the question.
Sort gaps before assigning them
Not every open item belongs with the same person. Sort the issue first. A resident who cannot begin a session may have an access, account, station-status, parking, or power-allocation question. The report should not be labeled as an electrical problem until an authorized technical party has evidence for that conclusion.
Sort the Gap First
- Policy mismatch: current notice, effective date
- Configuration uncertainty: approved baseline, asset ID
- Service report: station ID, time, support case
- Safety concern: observation and location, no intervention
- Parking conflict: space, time, posted rule
| Gap type | First useful record | Likely next step |
|---|---|---|
| Policy mismatch | Current resident notice and effective date | Ask the policy owner to confirm or revise it |
| Circuit-level current limiting | Approved baseline, circuit map, and asset identifier | Route to the authorized system owner |
| Scheduled load management | Approved schedule, participant list, and asset identifier | Route to the authorized system owner |
| Service report | Station ID, time, visible status, support case | Follow the documented support route |
| Safety concern | Observation and location, without intervention | Route promptly to the qualified party |
| Parking conflict | Space, time, and posted parking rule | Use the property parking process |
For every gap, record the affected charging group, promise made to residents, missing evidence, likely consequence, and party responsible for the next answer. The Department of Energy's smart-charge management implementation guidance shows that planning, installation, and operations require defined roles and documentation. In a shared charging setup those roles are normally the property owner, the charging network operator, and a licensed electrical contractor, and each one should be named in the record.
Test the recovery story
Ask what happens after a controller restart, lost connection, unavailable account, charger replacement, or a change in the supporting input. If the answer is unknown, record it as open. Do not tell residents that service will resume normally until the responsible party can support that statement.
Before a recovery test, agree on the condition to be observed, the expected resident-facing result, the person conducting the test, and the record to retain. Property staff should gather the basics but should not improvise a technical action. OSHA's electrical safety rules for general industry, 29 CFR 1910 Subpart S, support maintaining a clear boundary between a reported concern and electrical work performed by qualified, authorized people.
Name the roles in the recovery test
A recovery test needs a named conductor and a named record. For apartment charging, that usually means the property manager who schedules the test and posts the resident message, the charging network operator or service provider who confirms the controller setting and connection state, the licensed electrical contractor who confirms circuit and panel conditions, and the authority having jurisdiction when permitted work has to be inspected.
Close a gap only when the evidence matches it
- State the original question in one sentence.
- Identify the document, test result, or accountable response reviewed.
- Record the decision owner and closure date.
- Update the resident message if the confirmed behavior changed. Example message during an open gap: "Charging at stalls 4 and 5 may run at half speed until we confirm the circuit limit. We will post an update by Friday."
- Set a new review date within 30 days, or 90 days if the answer depends on a seasonal load rule, and name the owner who will check it.
Common questions
Is one slowed session proof that power sharing failed?
No. It may reflect the documented rule, a normal condition, a resident-access issue, or a fault. Collect the station and time information, then use the approved support route.
What if the posted rule does not match the current system?
Treat the conflict as open. The responsible party should correct the configuration, the policy, or both before the property expands the promise.
