Apartment EV charging subscription roles: who does what in 2027

Two apartment EV charging subscription proposals can look almost identical and still assign different roles. A ChargePoint as a Service contract bundles network access, a support line, and station management into a per-port fee. A Blink owned-equipment agreement can leave the property holding the hardware and the utility bill. Compare the jobs, not the package name.

For a subscription written or renewed in 2027, four parties keep showing up: the property owner, the network operator, the licensed electrician, and the resident's payment route. SWTCH Energy and Xeal both sell multifamily programs where the provider runs the resident app while the property keeps the parking rule.

What to take away

Compare the operating jobs

A subscription price covers the functions the contract names and nothing else. ChargePoint as a Service, the Blink Owned model, and SWTCH subscriptions normally include the network account, the resident app, and a driver support line. Hardware ownership is the line that moves most often.

Under a host-owned deal the property buys the stations. Under an operator-owned deal the provider replaces them. Xeal and EverCharge both market apartment programs with no upfront cost to the property in some deals, and both then collect from residents at the charger or in the app.

Expect numbers in three places. A Level 2 port typically costs $2,500 to $8,000 installed in most US markets. Make-ready work in a multifamily garage can add several thousand dollars per stall where the electrical panel sits far from the parking.

Network subscriptions for apartment ports typically run $20 to $80 per port per month, depending on who owns the hardware. Utility programs such as Con Edison's EV Make-Ready, Xcel Energy's EV charging rebates, and Duke Energy's charger programs cover part of the make-ready cost.

Building codes assign some roles by rule. California's CALGreen standards, Colorado's energy code, and New York City's Local Law 55 require EV-ready parking or charging in multifamily buildings, and each phases in on its own timeline. A 2027 role map should cite the code version in force at the property.

Connecticut's rental-property charger policy makes the installer responsible for specified costs. It also says an installed charger becomes a fixture if it is not removed at lease termination. That local example is why equipment responsibility and exit terms should be documented separately. It assigns no duty for a subscription at properties outside that law's scope.

Test the resident route

Give staff one ordinary scenario: a resident sees an error, needs account access, or asks which charger group is available. On a ChargePoint or Blink network the driver app shows station status, so staff can point to the app before calling support.

Staff can use the approved message, find the correct owner, and preserve the basic facts. They should not decide a utility, contract, payment, tax, or legal question.

Keep a gap list for roles that have no current source. A provider logo, an old email, or a device model is a clue, not a current assignment of responsibility.

The Energy Department's Vehicle Charging Innovations for Multi-Unit Dwellings project described shared-charging work with access control, billing, data collection, and analytics. Its project description assigns no role at any apartment community.

It does give a reason to compare these functions one at a time. The organization handling account access may not own equipment, approve parking policy, or answer a resident payment question.

Build a role map with the function, the current responsible organization, and a named contact or request route. Add the source date, the evidence type, and the authority limit. SWTCH Energy can reset a charger that has gone offline but cannot change who is allowed to park in a space.

That authority limit should be visible before staff promise an outcome to a resident. Keep the role map beside the approved resident instructions. When either file changes, check the other one before staff use it to answer a routine request.

The NIST Privacy Framework supports a voluntary review of privacy risk. It does not determine role assignments. It does help document which role may request account, session, or payment information, for what stated purpose, and through which approved process.

During a handoff, ask the incoming owner to follow three resident scenarios from the role map: access, a visible equipment issue, and a transaction question. Record which route works, which source is missing, and who must correct the gap. The test checks the operating map; it does not settle policy or liability.

The National Archives' records-management introduction supports keeping records with a clear purpose and owner. Hold the current role map, source list, approved instructions, and handoff result together so responsibility does not disappear when a person or provider changes.

Use the role map before a subscription change is announced. Identify the chargers affected, who controls current resident communication, which support route receives the first request, and who can approve revised language.

If an account, payment, parking, maintenance, or data role changes, update that part of the map first. Do not leave staff to infer a new responsibility from a provider email.

Keep disputed responsibilities open until the property has a current source. A practical note can say the provider was asked to clarify its scope or the property is reviewing an agreement. Do not state that a party accepts a duty unless the record supports it.

Test the handoff between roles

For one realistic resident issue, trace the request from property staff to provider support, billing, account administration, and the final response. Record where responsibility changes hands and which party may update the resident. This exposes gaps that a contract title alone cannot explain.

Keep the role map with current contact routes and approval limits. A change in manager, vendor, or payment process can alter the service even when the hardware stays in place.

Common questions

Can one provider own every role?

ChargePoint, Blink, SWTCH Energy, and EverCharge all sell packages that cover most functions at a multifamily property. Even so, the current record should state which functions the operator performs here. Equipment ownership, parking rules, and lease terms usually stay with the property.

Who should answer a parking question?

The property manager of record, whether that is Greystar, Bozzuto, or FirstService Residential, unless the lease or a separate agreement assigns parking to someone else.

What is the most important handoff record?

The current role map with contacts, source dates, charger labels, and the resident support route. Add the operator's contract renewal date, because a network sale or wind-down changes who answers the phone.