Guides
Part of Apartment EV charger cost boundaries: six labels for every figure
How to log apartment EV charger estimate assumptions
Apartment EV charger estimate assumptions: track electrical, installation, utility, cost, and payer inputs with sources, owners, status, and review triggers.
Apartment EV charger estimate assumptions are temporary inputs that make an early number possible. They may come from a provider, property contact, public source, or planning model. They are useful only when readers can see that they are inputs, not settled facts about a specific apartment property.
What to take away
- Log each assumption with its source, date, owner, and status before you trust a total.
- Label each input as reported, pending confirmation, assumption, confirmed, or superseded.
- Review an estimate after a material input changes.
- Never hide an assumption inside a round-number total.
- Re-review assumptions quarterly and before a procurement or budget decision.
Build an assumptions log
An assumptions log should be brief enough to update. Give every row a clear statement and avoid technical conclusions that its source does not establish. Do not merge a planning input with a verified site fact.
Assumptions Log Fields
- Inputproposed port count
- Source and dateprovider proposal
- Statusreported, pending, assumption
- Review triggerscope or decision change
- Keep rows brief and updateable
| Status | Meaning | Example input and source | Owner | Required next step | Review trigger |
|---|---|---|---|---|---|
| Reported | A named party supplied the input | Proposed port count: 8, from a provider proposal, dated | Property contact | Keep the dated source | Alternate scope or later decision |
| Pending confirmation | The question is known but unresolved | Parking area, from a property description, dated | Property manager | Name the source owner | Boundary or access question |
| Assumption | The input supports early planning only | Expected use, from a planning input, dated | Planning lead | State what could change it | New resident or operational data |
| Confirmed | A dated source answers the stated question | Equipment type, from a provider-stated option, dated | Provider contact | Record the source date | Changed model or availability |
| Superseded | A later input applies to current work | Prior 8-port count after a revision to 12, dated | Record owner | Retain the older version | Later decision or new proposal |
For an apartment or condo estimate, log separate inputs for planned port count; Level 2 or DC fast charging (DCFC), charger power, and amperage; existing panel and electrical-service capacity; any service upgrade; conduit, trenching, and surface restoration; utility make-ready work and charges; equipment and installation cost per port; recurring network or service fees; expected charging use and energy cost; and who is expected to pay each cost (owner or association, residents, utility, or provider). Record the source, date, owner, status, next step, and review trigger for each. If the proposal does not state a value, write “not stated” and identify who can confirm it.
Use "reported" when a source or property contact has supplied information that has not been independently confirmed. Use "pending confirmation" when the question is known but unresolved. Use "confirmed by [source]" only when a dated source actually answers the point. Do not use "confirmed" to mean "we expect this to be true."
ENERGY STAR's EV charging reference describes estimates that use charger type, usage, and average energy dispensed per session as inputs. Read ENERGY STAR's EV charging model inputs. These are usage inputs, not installed project-cost figures.
The Department of Energy's Alternative Fuels Data Center (AFDC) state laws and incentives directory can help identify state program leads. Check whether a listed program applies to multifamily properties, the project's location, and the specific cost being estimated.
For electrical assumptions, identify the applicable locally adopted National Electrical Code (NFPA 70) provisions, including Article 625 for EV charging equipment, and record the load calculation and service-capacity basis. Confirm local permit and inspection requirements with the authority having jurisdiction (AHJ); do not treat a code edition or utility program from another location as governing. NYSERDA's Permit Process Streamlining guide describes an EVSE load calculation worksheet as useful for checking whether a charger could overload existing service and estimating possible effects on electricity use and customer cost.
Review changes rather than patching totals
When an input changes, retain the prior estimate and create a new dated version.
Example: a 2027 budget cycle starts with 8 ports. A provider revises the proposal to 12 ports. The log keeps the 8-port row as superseded and adds a 12-port row with the revision date.
Illustrative filled log rows from the proposal-change example above—not a real project quote. The example supplies no dates, charger type, electrical capacity, or costs, so those remain open rather than being guessed.
| Input | Recorded value | Source and date | Status | Owner | Next step and review trigger |
|---|---|---|---|---|---|
| Port count, prior scope | 8 ports | Provider proposal; date not stated | Superseded | Property manager, assigned to update the log | Retain the prior scope; compare it with the dated revision |
| Port count, revised scope | 12 ports | Provider revision; revision date not stated | Reported | Property manager, assigned to update the log | Obtain the dated proposal and verify the revised scope before updating the estimate |
This keeps a reader from comparing a new total to an old set of assumptions. A revised total may be reasonable, but it should never look like the original estimate simply became more certain.
Avoid hidden arithmetic
Do not bury a planning number inside a total. If a provider has not stated a cost category, mark it not stated rather than inserting a typical amount. A transparent total is more valuable than an exact-looking number with unknown parts.
When comparing proposals, use the buyer checklist to compare the same logged scope and cost categories. A bid requirement is not, by itself, a confirmed site condition.
Preserve old versions and their limits
Keep the prior estimate, its assumptions log, and the source that changed; retain both versions so a later reader can identify which input changed.
Before a decision meeting, check each assumption for a date, source, status, and named review trigger. Re-review assumptions quarterly and before any procurement or budget decision.
Common questions
Short answers to the questions that come up most when an assumption log is shared with an owner, board, or provider.
Is an assumption the same as a confirmed site condition?
No. An assumption is an input used for planning. Keep it visible until a current, appropriate source confirms or changes it.
Who should own an assumption log?
Name one record owner to update the source, status, and next review. That role does not decide property, technical, or legal questions.
What if a provider does not state an assumption?
Mark it as not stated. Do not add an invented condition to the provider's proposal.
