PlugOp home

Blog

Practical notes from EV charging planning, rollout, and operations

Practical guidance for multifamily EV charging programs, energy management, incentive planning, and policy readiness.

Archive

Recent writing for the next charging decision

The blog is meant to help owners, operators, and project teams move from general questions into better decisions with clearer context.

What we cover

Four subjects most multifamily charging decisions come back to

The archive is organized around the questions that actually stall projects, not around product announcements.

Capacity and load management

How much charging a building service can actually support, when a service upgrade becomes unavoidable, and how sharing capacity across ports changes the answer.

Load management

Program structure and resident experience

Assigned versus shared stalls, what residents pay, how sessions are billed, and which design choices decide whether an amenity gets used or complained about.

Assigned charging

Requirements and incentives

EV-ready and EV-capable rules that vary by jurisdiction, plus the rebate and utility programs that change project budgets and, more often, project timelines.

Incentives

Replacement and operations

Taking over sites where the original provider stopped supporting the hardware, and what it takes to keep stations online once residents depend on them.

Charger replacement

Most published writing about EV charging is aimed at drivers or at public networks along highways. Multifamily charging is a different problem. The vehicles sit for eight to twelve hours instead of twenty minutes, the electrical capacity is fixed by a building service that was never sized for it, and the person answering resident complaints is a property manager rather than a network operator.

What we publish comes out of that setting. Topics are drawn from live projects — capacity discovered during site walks, incentive programs that changed mid-application, charger fleets inherited from a provider that stopped supporting them — and each piece is reviewed by the people at PlugOp closest to that work before it goes out.

Where an answer depends on jurisdiction, utility territory, or code cycle, we say so instead of stating a national rule that does not exist. Where a number depends on site conditions, we give the range and the variables that move it. That makes some articles less quotable and considerably more useful when a budget is being built.

If you are looking for a specific answer rather than a reading list, the resource library covers individual questions directly, and the case studies show how specific properties resolved them.