Guides
Part of Apartment EV charging pilot evaluation: a practical guide
Apartment EV charging pilot feedback: how to collect comments without overpromising
Apartment EV charging pilot feedback guide for 2027 helps teams gather voluntary comments, record the collection method, protect limits, and route issues correctly.
Apartment EV charging pilot feedback is a dated record of what participants and affected residents reported about the chargers, the start instructions, the parking spaces, and the bills they see. It is not a technical assessment, and it does not settle whether the pilot worked or whether the equipment met its targets. Keep it separate from the operating records the network provider holds — charger logs, session data, error reports — so each source can be read on its own terms.
What to take away
- The deliverable is a dated feedback summary that names the method, the open and close dates, the comment count, the themes, and the unresolved items.
- Ask a few neutral prompts tied to the pilot boundary, and keep the exact prompt wording beside every comment.
- Say the "not representative, not a vote" limit once in these takeaways and once in the summary, and stop there.
- Send complaints about safety, access, billing, or local rules to the group that handles each one: electrical and safety questions to the licensed electrician and the permitting office, accessibility questions to the property's ADA compliance contact, billing questions to the network provider or whoever bills the residents.
- Keep provider records, property facts, and resident comments in separate files.
Set the boundary before you invite comments
Publish a short introduction before the collection window opens. State the pilot dates, who may comment, what kind of feedback helps, and what the feedback cannot decide. Avoid leading prompts such as "How much did the successful pilot help you?"
Neutral prompts that stay inside the pilot boundary:
- Was the start instruction clear?
- Did you find a charging space available when you needed one?
- Were the cable and connector easy to handle?
- Did anything about the parking space make charging harder?
- If you had a question about a charge on your bill, was it answered?
Number the list as version 1, freeze the wording for the whole window, and keep that version number beside every comment you log.
Checklist before the invitation goes out:
Set the boundary
- The prompt list is final and version numbered.
- The open and close dates are fixed.
- The follow-up route for safety, access, and billing issues is named.
- The retention rule for comments and contact details is confirmed.
Feedback boundary checklist
- State pilot dates
- State who may comment
- State what feedback is useful
- State what process does not decide
- Avoid leading questions
Record each comment with the same fields
Use one log with fixed columns, and do not add columns mid-window.
Record each comment
| Field | What goes in it |
|---|---|
| Prompt version | The exact wording the participant answered |
| Date received | The day the comment arrived, not the day it was logged |
| Theme | A plain label such as access instructions or payment question |
| Route | Where a safety, billing, or access issue was sent |
| Status | Open, referred, answered, or closed |
A log with fixed columns survives a staff change better, and this guide to apartment EV charging document control covers how to keep the rows findable.
Example of one completed row
Take a resident who writes that the start instructions in the app are unclear. The row reads: prompt "Was the start instruction clear?", date 2027-03-04, theme "access instructions", route "site manager, information only", status "closed, no equipment check needed". Nothing in that row claims the charger failed.
Show the collection method
Say whether comments came from an optional form, a meeting, an email route, or a direct invitation. Give the dates the window was open and name who was invited. Those details tell a future reader what the comments cover.
Accessibility is its own route. The Americans with Disabilities Act (ADA) sets the accessible parking and reach requirements that apply to shared parking areas, so a comment about a charging space that is too narrow, or a connector that is out of reach, belongs with the property's ADA compliance contact and not with the person writing the summary.
Sorting comments without rewriting them
Keep the original wording where the property's privacy approach allows it. Give each comment one plain theme label. Do not rewrite a complaint into a finding that the equipment failed. Do not rewrite praise into a claim about demand.
A safety, accessibility, billing, or local-rule comment goes to the owner of that process: an electrical or safety question to the licensed electrician and the permitting office, an accessibility question to the property's ADA compliance contact, a billing question to the network provider or whoever bills the residents. The log may say a question was referred. It may not state the answer before the responsible source gives one.
Charger wiring and the permit for it fall under the National Electrical Code (NFPA 70) as the local jurisdiction adopts it, so the equipment record — model, power level, connector type, inspection date — comes from the electrician's paperwork and the provider's account, not from comments. The feedback summary can point to those records; it cannot replace them.
Referrals that never close look like unresolved community concern, so close each item in the log, date it, and carry anything still open into the summary's unresolved list.
Keep feedback separate from outcome claims
A comment about confusion is information about that person's experience. It is not proof of a technical cause, a service-wide result, or future demand. Keep provider records, property facts, and feedback in separate columns or files so the brief can describe each source on its own terms.
A comment about cost is a comment, not a rate. If a resident mentions a charge they saw, record it as a voluntary statement, and take the actual amounts from the property's billing record or the network provider's statements, which are the sources that carry figures. Who pays for a shared charger — the property, the driver, or a mix — is set in those records and in the agreement, not in the feedback log.
If a comment carries a name or a billing detail, store the identifiable record under the property's restricted process. The NIST Privacy Framework is a voluntary resource for identifying and managing privacy risk. It supports collecting only what the stated purpose needs.
Write the dated summary
The summary is the deliverable. It names the collection method, the dates the window was open, the comment count, the main themes, and the unresolved items. The count is a count of voluntary comments, not a share of residents.
Anything still in draft must say so on its face: mark the file "draft," add the date it was written, and make sure no draft count or theme reads as a final one.
| Instead of this | Write this |
|---|---|
| "Residents found the pilot confusing" | "Several voluntary comments asked for clearer start instructions" |
| "The charger failed" | "One participant reported an issue; the record was referred" |
| "Demand is high" | "The record contains requests for more information" |
Lay the summary out in the same order every time, so a reader can compare windows:
- Methodthe routes comments came through, such as an optional form, a meeting, or an email address.
- Windowthe open and close dates.
- Commentsthe count of voluntary comments received.
- Main themeseach theme label used in the log, with the comments behind it.
- Unresolved itemsevery open referral, with its date and owner.
- Limitone line stating that the comments are voluntary, not representative, and not a vote.
The National Archives explains records management as control across a record's whole life cycle in records management 101. Follow the property's retention rule, then keep the source comment, the routing record, and the summary in traceable order.
Share only the summary the property authorizes, and do not name participants unless there is a clear basis for it.
