
Guides
Part of Apartment EV charger power sharing: write a clear rule
Apartment EV power sharing methods: what to assess
Learn how to assess apartment EV power sharing methods by comparing allocation behavior, equipment, resident experience, operations, and test evidence.
Apartment EV power sharing methods differ in the rule used to allocate a limited shared resource. A property should compare the rule a resident sees, the technical inputs that support it, and the evidence that proves the quoted configuration, rather than treating every shared-capacity feature as interchangeable.
What to take away
- Compare what starts, slows, pauses, or resumes a session.
- Ask for the exact assets and inputs behind every method.
- Score resident information and recovery alongside technical features.
- Keep the selected method tied to a recorded test.
Put allocation behavior first
Compare fixed, queue, rotation, and dynamic approaches by the action a driver experiences. A method may spread available power across every active session, hold a session until a rule permits it, rotate access, or alter power in response to documented inputs. A product can combine methods, so ask for the active configuration.
Name the method behind each category before you score it.
Allocation behavior
| Allocation type | Named method or product |
|---|---|
| Fixed | Wallbox Power Sharing on a shared circuit; load-control devices such as RVE's DCC-9 and the NeoCharge Smart Splitter |
| Queue | A software waitlist on a networked platform; ask ChargePoint, Enel X, or an OCPP backend whether the queue exists and who configures it |
| Rotation | A schedule or access policy, set on the platform or run by on-site staff |
| Dynamic | Wallbox Dynamic Power Sharing and ChargePoint power management, both driven by a current meter |
Allocation Methods vs Driver Action
Fixed
- Driver action
- Power spread
- Key input
- Set limit
- Evidence to ask
- Written config
Queue
- Driver action
- Held until rule
- Key input
- Rule permit
- Evidence to ask
- Input map
Rotation
- Driver action
- Access rotates
- Key input
- Time slot
- Evidence to ask
- Status message
Dynamic
- Driver action
- Power varies
- Key input
- Documented inputs
- Evidence to ask
- Condition map
Joint Office material explains that charging power can be managed with information about grid constraints, driver preferences, and desired departure times. Its managed-charging webinar transcript is industry education, not an apartment design rule. It supports asking what input a power-sharing method actually uses before a property names its resident service.
Method questions
| Method question | Evidence to request |
|---|---|
| How is available power allocated? | Written configuration description |
| What can change a session? | Input and condition map |
| What does the driver see? | Example status and resident message |
| Who can alter the rule? | Authorized administrator roles |
| What happens after a disruption? | Recovery path and test record |
Compare the operating burden
A simple method can be easier to explain but less flexible. A dynamic method can react to more conditions but may require additional equipment, communications, data, software, administrator access, and recovery planning. Record those dependencies with the feature comparison. A system should not be treated as low effort merely because its allocation occurs automatically.
Operating Burden to Record
- Additional equipment and communications
- Data and software dependencies
- Administrator access roles
- Support responsibilities
- Recovery planning
- Routine review process
The Department of Energy's implementation guidance for smart charge management separates goals, inventory, site assessment, procurement, installation, and operations. That framing helps an apartment owner compare the whole operating burden. A method is not ready for selection if the proposed equipment is clear but the account roles, support responsibilities, and routine review process remain vague.
These considerations can conflict, so rank them. Put safety and code compliance first, then the resident service promise, cost, and support burden. Cap added capability at what the site contact and budget can sustain.
Score the resident experience separately
Feature sheets often focus on technical options. Score the resident experience separately.
For each method, ask how the station shows a paused or reduced session, what a resident sees when data is missing, how a session resumes, and who can explain an unexpected result. A method that is technically acceptable but hard to describe can create avoidable support work.
Resident experience
| Resident-service check | What a comparison should capture |
|---|---|
| Status visibility | The documented message or indicator during normal sharing |
| Delay explanation | A plain description that does not promise a finish time |
| Support route | Who receives a report and what information they need |
| Recovery message | What staff can say after a service interruption |
| Policy fit | Whether the method matches the property's written access rule |
Do not treat a driver report as permission to change equipment or override a control. OSHA's electrical guidance supports sending electrical concerns to qualified, authorized people.
Preserve the comparison decision
At the end of the review, save documents supporting the selection, not just a purchasing conclusion. Include options considered, evidence received, site assumptions, and owner decision.
Include conditions that require a new review and the person responsible for the acceptance test.
That file lets you revisit the decision when an additional charger, a software change, or a new resident policy changes the facts.
The National Archives' records-management introduction treats records as evidence of decisions, so a short decision record keeps a vendor presentation from becoming an approved operating rule.
Test the property scenario
Ask each provider to demonstrate the proposed allocation at a representative level of simultaneous demand. Use the same scenario for every option. Preserve the settings, expected behavior, observed result, alerts, resident message, recovery path, and unresolved condition. The comparison should finish with observed evidence, not only a generic feature table.
Worked example: scoring two methods for one property
Take a 30-unit building with eight shared ports on a 200 A house panel and no budget for a service upgrade. Two candidates go head to head: a fixed cap that sets every port to 16 A, and dynamic sharing that holds the group at 40 A using a current transformer.
Score both against the same comparison criteria: allocation rule, equipment and inputs, resident information, support burden, recovery, and evidence.
Worked example
Fixed cap on a shared circuit
- Allocation rule
- Every port runs at the same set current
- Equipment and inputs
- Stations, one breaker, no meter
- Resident information
- Fixed speed, no extra message
- Support burden
- Site contact only
- Recovery
- Restart returns to the set current
- Evidence
- Load test at full simultaneous draw
Dynamic group limit with a meter
- Allocation rule
- Group total follows measured load
- Equipment and inputs
- Stations, current transformer, network link
- Resident information
- Variable speed, needs a status message
- Support burden
- Account roles, firmware, alerts, review
- Recovery
- Needs a fallback when the meter drops
- Evidence
- Same test plus a meter-failure test
Fixed wins on support burden and recovery. Dynamic wins on flexibility and headroom. The decision turns on whether the property can staff the account roles that the dynamic method adds.
Budget the two options differently. Fixed sharing is mostly a one-time cost: equipment, circuit work, and commissioning. Dynamic sharing adds metering hardware and may add a recurring network fee per port per month.
Ask each bidder for the monthly rate, the term, what happens at renewal, and which party owns the meter. Many utility make-ready programs cover the service, conduit, and panel work up to a defined point, so ask what the program pays for.
The federal alternative fuel refueling property credit is 30% of qualifying cost, capped at $100,000 for each item of business property. Confirm current eligibility with a tax adviser.
Common questions
Is rotation always more fair than equal sharing?
Not necessarily. Fairness is a property policy question that must be defined in terms residents can understand. The technical method only implements a documented rule.
Can a platform select a method without owner input?
It may offer defaults, but the property should identify the active setting, its owner, and the resident service it creates before relying on it.
What belongs in the final comparison record?
The allocation behavior, assets, dependencies, administrator roles, test result, resident message, support route, and decision owner.







