Guides
Part of Apartment EV charger sensitivity analysis: how one input change shifts a 2027 decision
How to document apartment EV charger planning inputs for 2027 scenarios
Learn how to label apartment EV charger planning inputs, keep one master worksheet, write scenario questions and version entries for 2027 decisions.
What to take away
- Label every capacity input as source-confirmed, reported, assumed, or pending review.
- Keep one master worksheet, separate from drawings, calculations and permit packages.
- Phrase each scenario as a question about the next information request, not a claim about the building.
- Start now if a 2027 decision matters, because budgets, approvals and utility work run ahead of it.
- Replace a scenario when a material input changes, and keep the earlier version.
Before planning capacity for 2027, an apartment team should be able to hand a reviewer a single page. It lists the inputs the team holds, where each came from, and the question each one raises next.
Build one master worksheet
Four columns carry everything. Older sheets that repeat the same inputs and next steps split a reader's attention, so merge them into one table and update rows in place.
| Input | Label | Source | Next request it raises |
|---|---|---|---|
| Proposed port count, for example 12 stalls | Planning input | Draft scope from the property team | Does the provider scope change if the count moves? |
| Parking area proposed for charging | Reported condition | Dated site walk note | Is the boundary still current? |
| Provider product option | Provider statement | Vendor sheet | Does the property need its own condition check? |
| Existing service claim | Pending review | No source attached yet | Who holds the current electrical record? |
| Charging approach, shared or assigned stalls | Planning input | Resident survey draft | Which usage rule applies? |
A row is a planning entry, not a finding. Confirm that the label column is filled for every row before the worksheet leaves the property office.
[figure 1]
Planning Inputs vs Conclusions
Input
- Proposed port count
- Planning input
- Provider product option
- Provider-stated option
- Property-reported info
- Reported condition
- Utility response
- Dated source
Correct label
- Proposed port count
- Capacity to serve it
- Provider product option
- Suitability for property
- Property-reported info
- Verified electrical fact
- Utility response
- Answer for changed scope
Not a conclusion about
- Proposed port count
- Provider product option
- Property-reported info
- Utility response
Add a dated source for anything labeled source-confirmed or reported. Rows without a source stay at pending review, and that status is useful information on its own.
The Department of Energy's EVI-X Toolbox models electrical demand from user-defined adoption scenarios. The AFDC scenario-tool description explains what it does. Treat its output as an assumption with a stated input, never as a property condition.
If the charging approach is shared rather than assigned per stall, the worksheet should point to a usage rule residents can follow without calling the office. How to write an apartment EV power sharing rule covers wording that survives a complaint.
Ask a scenario question, not a technical question
A scenario question names an input and the request that depends on it. It never asserts a building condition.
Scenario question: If the proposed port count rises from 8 to 12, does the provider scope and the request for site review change?
Technical question: Can this building support 12 chargers?
Change one input at a time and record whether the next request changes. If several inputs move together, label the result a new scenario rather than a comparison against the old one.
Testing how far one number must move before a 2027 decision flips is a separate exercise. Apartment EV charger sensitivity analysis shows how to structure that test.
Why 2027 sets the planning clock
A 2027 target sits inside the current planning window rather than beyond it. Apartment capital budgets and reserve studies typically look two to three years ahead. Board approvals, resident votes and utility coordination add months after that.
Electrical codes move on their own schedule. NFPA 70, the National Electrical Code, is revised, then adopted by states and local jurisdictions at staggered dates, so the edition in force in 2027 may differ from the one an older worksheet cites. NFPA 70 is the reference to track.
Rebate and incentive programs often require code-compliant work, which strengthens the case for noting the edition you are designing against.
Authority is the other pre-2027 item. Apartment EV charger project authorization sets out what a board should settle before it commits to a scope.
Example: one labeled scenario entry
A complete entry reads like this.
One labeled scenario entry
- Scenario ID and dateCS-2027-03, drafted in the current planning year.
- Area and scopenorth garage, charging proposed at the west bank of stalls.
- Input and label12 proposed ports, planning input, from the draft scope.
- Question it answersif the port count moves, does the provider scope and the site review request change?
- Question it does not answerwhether existing service, panel or feeder capacity supports that load.
Write the final line inside the entry. A reader then sees the boundary without searching another document.
Keep versions and route the technical question
When a material input changes, create a later entry and name the changed field. Keep the earlier version. The property's own records process governs retention, so match it rather than inventing a schedule.
If charger safety items land in the same file, what to keep and what to skip helps hold the two sets apart.
If residents will pay for charging, document the billing method as an input. State rules on submetering and billing in rental housing vary, and the AFDC summary of submetering and billing laws is a starting point.
Send the electrical question to whoever holds current site evidence. The worksheet's only job is to make that request precise.
