Guides
Part of Apartment EV charging waitlist: what a policy must cover
EV charging waitlist: how to set a trigger that starts a feasibility review
Turn a verified EV charging waitlist into expansion triggers with a named measurement period, a validator and a decision for feasibility, electrical review, budget, construction and the next phase.
An EV charging waitlist expansion trigger turns sustained, verified demand into a named next step. The trigger may start a feasibility review, a budget request, a design decision, or a qualified electrical assessment.
What to take away
- Validate the queue before using it as a demand signal.
- Define the evidence, owner, and decision for every project gate.
- Size a service option using parking and electrical constraints, not queue length alone.
Clean up the demand record first
Verify current residency, remove duplicates, close withdrawals, and separate present vehicle requests from expected-delivery or planning-interest entries. Add offer outcomes, shared-port use, failed sessions, and resident feedback. A queue can overstate demand when it is stale and understate demand when residents believe there is no point applying.
Clean Up Demand Record
- Verify current residency
- Remove duplicate entries
- Close withdrawals
- Separate present from expected requests
- Add offer outcomes and feedback
The project gate table maps each stage to the decision it can start.
| Project gate | Evidence needed | Decision made |
|---|---|---|
| Feasibility | Verified demand and a defined parking question | Start a technical and operating review |
| Concept | Viable location and service options | Choose options for cost and capacity work |
| Budget | Preliminary scope and operating assumptions | Request funding or owner approval |
| Delivery | Approved scope and current constraints | Move to utility, permit, procurement, and construction work |
| Enrollment | Available service and adopted allocation rule | Make offers and measure actual use |
Write the trigger as a rule
A usable trigger is one sentence with four parts: the measurement period, the request type it counts, the person who validates the count, and the decision that follows. Every part must be specific enough that two board members would reach the same answer from the same data.
Illustrative trigger (hypothetical numbers). "If, in any 90-day period, at least 12 verified applicants with an EV and an overnight parking assignment remain active after the cleanup, the property manager validates the count and the board receives a feasibility request at its next meeting."
The example uses invented numbers. Each property should set its own threshold from its parking count, its service capacity and its budget. A count alone does not show whether a site can carry the load.
Size options before announcing a port count
An electrical assessment may show that a lower-power option, shared service, load management, a later infrastructure phase, or a site upgrade fits the building better than an immediate one-for-one assignment. Parking access and the resident's typical dwell window matter as much as the number of names on the list.
Costs depend on electrical service capacity, trenching distance, permitting, and whether load management is used. A qualified contractor can give a property-specific range. No single figure applies to every building, so the trigger should require a written estimate before the budget gate.
The Department of Energy's multifamily EV charging guide covers electrical capacity planning for multifamily buildings. Read its assessment steps before you set the electrical-review gate. A waitlist is an input to that technical planning, not a complete project design.
Publish the current blocker
Residents do not need a speculative completion date. They do need the current stage and the next decision. A plain update can say that the property is validating demand, reviewing parking, seeking a budget decision, waiting for utility information, or preparing an approved construction scope.
When a trigger does not advance a project, preserve the reason. It may involve capacity, parking, cost, a required approval, or a question for qualified local review. The record helps management revisit the decision when the input changes.
Choose evidence that can change a decision
An expansion trigger should be more specific than "the list is long." Define the measurement period, which request type it tracks, how withdrawals are handled, who validates the data, and what decision follows.
A useful trigger can begin a site survey or a budget request. It cannot approve construction by itself, because the electrical, permit and budget gates still apply.
The signal table below tracks demand evidence that can start or stop a gate.
| Signal | Useful question | Possible next action |
|---|---|---|
| Verified applications | Is demand sustained across review periods? | Start feasibility work |
| Shared-port conflicts | Do current hours match resident need? | Review operating model |
| Offer declines | Do residents reject the price, location, or terms? | Adjust service design |
| Failed sessions | Are current ports reliable enough? | Plan maintenance or upgrades |
Keep the decision record current
Record the demand data used, the validator, the technical question, the decision, and the next review date. Keep the record for as long as the project's own rules and the association's records policy require. If the board has not adopted a records schedule, adopt one before the first trigger fires.
Separate the planning record from each resident's individual waitlist entry. The planning record can hold counts and decisions. Individual entries stay with the property manager and follow the privacy terms residents accepted. Set a review date at least every six months, or after each phase fills.
Measure the result after capacity opens
Make offers under the published policy, record acceptances and declines, and compare actual use with the original demand record. Set the next review point before the new phase fills. Expansion planning works best when the property learns from each operating phase instead of resetting the process each time.
Revisit parking, electrical service, billing, equipment ownership and operating policy after capacity opens. Actual use may show that the initial service model needs adjustment.
Common questions
How many requests should trigger expansion?
There is no universal number. The property should set the threshold from its own parking count, service capacity, price and available funding. The illustrative trigger above uses 12 verified requests in 90 days for a hypothetical building only.
Does a feasibility trigger mean construction is approved?
No. It starts the next review.
Why track declined offers?
They help distinguish demand for a general charging option from demand for a specific price, location, or service model.
