Portfolio replacement rollout
National REIT Charger Replacement
84 chargers replaced across 4 states in 8 days, with escalated site-level complaints dropping to zero.
Procurement Checklist
A strong RFP should make vendors explain more than charger price. Use this checklist to compare the infrastructure plan, resident experience, support model, commercial terms, data access, and your options if the provider changes later.
01
Before asking vendors for equipment, define what the charging program must accomplish. A single-property pilot, a new-development requirement, and a portfolio-wide replacement need different operating standards even when they use similar chargers.
Give bidders enough site and portfolio context to recommend a defensible first phase. Require them to identify assumptions instead of hiding them inside a lump-sum proposal.
List the properties, parking types, unit counts, existing chargers, known electrical capacity, and anticipated rollout phases.
Define the intended users: assigned residents, shared resident parking, guests, employees, or limited public access.
State the owner's goals for resident experience, cost recovery, uptime, reporting, sustainability, and future expansion.
Require site-specific alternatives when existing drawings, utility information, or field conditions are incomplete.
02
Proposals become difficult to compare when one bidder includes engineering, utility coordination, trenching, networking, signage, commissioning, and permits while another prices only charger hardware and installation labor.
Ask each bidder to separate base scope, allowances, exclusions, alternates, and assumptions. The RFP should also require a phasing plan that protects future expansion without forcing the owner to build every charger immediately.
Site assessment, electrical engineering, utility coordination, permits, ADA review, civil work, restoration, signage, and striping.
Panel, transformer, conduit, wiring, make-ready infrastructure, cellular or network equipment, and load-management controls.
Installed, EV-ready, and EV-capable stall counts for the first phase and future phases.
Commissioning, test records, as-built documentation, warranties, training, and final owner handoff.
03
Hardware and network software may be bundled, but ownership should still understand the responsibilities, limitations, and replacement path for each layer. A low initial price can become expensive if proprietary equipment, unclear credentials, or a closed network makes future migration difficult.
Require the bidder to identify the exact charger model, supported protocols, software platform, communications method, payment flow, firmware process, warranty, spare-parts plan, and compatibility claims.
Charger ratings, connectors, certifications, environmental limits, cable management, mounting, warranty, and replacement-part availability.
OCPP version and implementation details, network ownership, firmware control, credentials, and the process for moving compatible hardware to another platform.
Access control, reservations, notifications, pricing options, payment processing, refunds, taxes, and resident account management.
Load-management behavior, fail-safe operation, reporting, API or export access, cybersecurity responsibilities, and software release practices.
04
Multifamily charging creates two support audiences: the resident trying to charge and the property team trying to keep the community running. The RFP should prevent either group from becoming the default troubleshooting desk.
Ask bidders to describe the full support workflow, including who receives the first call, what can be resolved remotely, when a technician is dispatched, how parts are sourced, and how ownership sees open issues.
Resident support hours, channels, languages, escalation rules, refund handling, and communication during outages.
Remote monitoring, preventive maintenance, uptime measurement, severity levels, response targets, dispatch targets, and service coverage.
Property-manager onboarding, launch materials, support signage, issue visibility, and the tasks that remain with onsite staff.
Portfolio reporting for charger status, utilization, revenue, energy, sessions, support cases, and maintenance history.
05
The RFP should make every bidder show the total cost of ownership, not just the equipment and installation number. Recurring network fees, cellular costs, payment processing, maintenance, support, warranty extensions, revenue shares, and annual increases can materially change the comparison.
Require a pricing schedule that separates one-time, recurring, usage-based, and optional charges. Ask bidders to explain who controls driver pricing and who receives charging revenue.
Hardware, design, installation, commissioning, software, cellular, payment processing, maintenance, support, training, and replacement parts.
Contract term, renewal structure, annual escalators, minimums, early-termination costs, service-level remedies, and insurance requirements.
Revenue ownership, settlement timing, transaction detail, refunds, taxes, idle fees, subscription options, and revenue-sharing terms.
Incentive responsibilities, application timing, documentation, prevailing-wage requirements, reimbursement risk, and treatment of incentive value in the proposal.
06
A vendor relationship should begin with a clear answer to what happens if the owner later changes providers. That question affects hardware value, resident continuity, historical reporting, contract leverage, and the cost of a future replacement.
Put data access, credential ownership, transition support, and termination deliverables in the RFP before bidders propose contract language.
Owner access to session, revenue, energy, utilization, charger-status, support, maintenance, and resident-account data in usable formats.
Retention periods, API or scheduled exports, role-based access, data security, breach notification, and deletion requirements.
Ownership or transfer of charger credentials, networking information, configuration files, pricing rules, documentation, and administrative access.
Transition assistance, final data export, resident communications, hardware de-networking, account migration, and fees charged at termination.
07
Before proposals arrive, assign weights to the outcomes that matter. A scoring model keeps a compelling demo or low equipment price from overshadowing weak support, costly contract terms, or limited portfolio visibility.
Ask finalists to walk through one real property, one resident support scenario, one charger outage, and one future provider transition. Those exercises reveal more than a generic product presentation.
Technical and infrastructure approach: 20–25%.
Operations, maintenance, and resident support: 20–25%.
Commercial model and total cost of ownership: 20–25%.
Portfolio reporting, data, integration, and migration flexibility: 15–20%.
Relevant multifamily experience, implementation plan, references, and team: 15–20%.
Proof
If this guide matches the question you are working through, these case studies show how PlugOp handled the same issue in live multifamily work.
Portfolio replacement rollout
84 chargers replaced across 4 states in 8 days, with escalated site-level complaints dropping to zero.
National portfolio operations
127 charging ports replaced across 17 assets, with one centralized program live within 2 months.
Explore PlugOp
Use these PlugOp pages to connect the RFP checklist to provider replacement, portfolio standards, and real transition outcomes.
Next read
See how PlugOp audits an underperforming charging program and plans the hardware, network, resident, and operational transition.
Next read
Define the shared charger, support, reporting, and expansion standards that should carry across a multi-property procurement.
Next read
Understand how bundled and decoupled hardware and software models affect flexibility, integration, and future provider choice.
Next read
See the operating, support, and commercial outcomes produced by an eight-day multi-state replacement.
FAQ
Only when there is a defensible portfolio, compatibility, incentive, or service reason. Otherwise, define required performance, certifications, protocols, warranty, serviceability, and operating outcomes, then require bidders to explain their recommended equipment.
They can be combined, but the pricing and responsibilities should remain separable. Ownership needs to see who is accountable for design, installation, commissioning, software, support, maintenance, and long-term program management even when one bidder coordinates the full scope.
Require a common base scenario plus clearly priced alternates. Ask every bidder to show the assumptions behind charger count, electrical capacity, utilization, load management, and future phases so the owner can compare strategy rather than unrelated totals.
Focus on contract length, renewal, termination, data export, administrative access, hardware and software credentials, transition assistance, network migration, resident-account handling, and every fee triggered when the relationship ends.
Yes. PlugOp can review the scope, assumptions, total-cost model, support responsibilities, data access, contract structure, and replacement risks before ownership selects a provider or finalizes an award.
RFP And Proposal Review
Bring a draft RFP, bidder response, comparison sheet, or existing contract. PlugOp can help identify missing scope, hidden operating costs, support gaps, and terms that may limit the portfolio later.