Guides
Part of Apartment EV charging pilot evaluation: a practical guide
Apartment EV pilot findings brief: a reporting template
An apartment EV pilot findings brief can document shared-charger use, identify evidence gaps, and separate observed results from the property's next decisions.
Apartment EV pilot findings brief is a short record of what a limited test observed, what its sources do not establish, and what question remains for the authorized decision-maker. It is not a sales presentation or an automatic recommendation to buy, expand, or abandon a charging project.
What to take away
- Lead with the pilot question, dates, scope, and shared-charger setup.
- Put each operating result beside its source, period, and limitation.
- Keep charging activity, participant comments, and decisions in separate sections.
- Present options without suggesting that a choice has already been approved.
Use a five-part brief
Section / Include
- Purpose
- The limited question and pilot boundary
- Record
- Sources reviewed and known gaps
- Findings
- Dated observations stated with their limits
- Open items
- Questions, evidence needed, and next owner
- Options
- Close, revise, extend, or investigate separately
Copy this skeleton and fill the brackets. A typical brief runs one to two pages, about 500 to 900 words.
Section / Filled example
- Purpose
- Test whether two shared Level 2 ports at [property] served [number] residents from [date] to [date].
- Record
- [Source name], [date range], [owner]. Gaps: [what was not collected].
- Findings
- [Dated observation]. Limit: [what the source does not show].
- Open items
- [Question]. Evidence needed: [record]. Owner: [role].
- Options
- Close, revise, extend, or investigate separately. No option is approved.
For a dated pilot, record the program year, charger model year, and firmware version from project records. If a funding program or utility rate changed during the period, name it and record its effective dates from the program or utility documents. Do not assume an older finding still applies.
Report the shared-charging results
Identify the charger make and model, port count, network operator, and firmware version recorded for the pilot. Report charging sessions, kWh delivered, port utilization, uptime, and dwell time only when logs support them; define each measure and date range, and state gaps rather than infer a result.
Pair each cost with its source and scope: installation total, cost per port, and electricity cost. Identify who paid—resident, HOA, property owner, or charging host—only when invoices, bills, agreements, or payment records establish it. If a public funding program or utility rate applies, name the exact program or rate schedule and its effective dates from its documents; do not assume an incentive or tariff applies.
Source notes
- Review the California Energy Commission (CEC) project-report description for an example of a public EV infrastructure report.
- Before circulation, have the evidence owner compare the brief with the source index.
- Use the Department of Energy state laws and incentives directory to identify possible policy or program leads, then verify details in the specific program documents.
- The NIST Privacy Framework is a voluntary resource for identifying and managing privacy risk; use it as background if the brief handles personal information.
- The National Archives records-management overview is general records-management background. Follow the property's own record rules.
Each source is background only. None establishes a pilot outcome or a property's eligibility.
Five-Part Pilot Brief
- Purposelimited question and pilot boundary
- Recordsources reviewed and known gaps
- Findingsdated observations with limits
- Open itemsquestions, evidence, next owner
- Optionsclose, revise, extend, investigate
Write findings carefully
Use "the record shows" only when a dated source is attached. Use "not established" when the pilot did not collect the evidence needed for a conclusion. Keep a separate area for decisions that the property actually adopted, including the date and decision owner. A brief should never make an inferred decision look final.
Weak vs. Better Wording
Weak wording
- Demand
- Pilot proved demand
- Reliability
- Service was reliable
- Expansion
- Residents want expansion
Better wording
- Demand
- Sign-up record shows enrollees
- Reliability
- Issue log entries only
- Expansion
- Feedback log, not nonrespondents
| Weak wording | Better wording |
|---|---|
| The pilot proved demand | The voluntary sign-up record shows the number of people enrolled during the stated period |
| Service was reliable | The available issue log contained the listed entries; reliability requires the defined operational record |
| Residents want expansion | The feedback log contains these voluntary comments and does not represent nonrespondents |
Separate the finding from the next decision
A pilot finding states what the record supports. A next decision states what the property intends to do with that information. They can share a page, but need different labels.
A finding might report what dated charging-session records show for sessions, energy delivered, or charger availability during the pilot period. A decision might authorize a revised instruction or ask for more information. Neither should claim a broader outcome the pilot did not test.
| Brief section | Question it answers | Example limit |
|---|---|---|
| Finding | What does the attached record show? | It covers only the stated dates and source |
| Gap | What did the pilot not establish? | A missing source cannot support a conclusion |
| Option | What could the authorized owner consider? | It is not an approved action |
| Decision | What action was actually recorded? | It may not settle technical or public-program questions |
Give every result a source note
Add a short note under every table or finding, and name the record, date range, source owner, and important limitation.
A feedback result should say comments were voluntary and collected through a stated route. An issue result should identify the log and its reporting period. A source note is more useful than a confident summary with no trail back to the underlying record.
If a brief contains resident questions, contact details, account information, or payment data, place those details in a restricted record rather than the brief.
Use a pre-circulation check
Before sharing the brief, verify the five items below. This check does not require a long review meeting. It asks whether the document can be read without inventing evidence or silently turning an option into a decision.
- Confirm the pilot question and date boundary.
- Check every finding against a dated source.
- Mark a missing or conflicting record as a gap.
- Identify the role that owns each open question.
- Separate options from actions already authorized.
Follow the property's own record rules, then retain the source index and the issued brief so a later reviewer can trace what changed.
Keep the closeout honest
A short brief can conclude that the pilot produced limited observations, that some questions remain, and that the owner has not made an expansion decision. That is a useful result. It gives the authorized decision-maker a clear next question instead of a false certainty.
Common questions
Should the brief include cost estimates?
Include installation, per-port, or electricity costs only when a dated source supports the figure, and state the scope of the estimate. Identify who paid only when the property's records establish it; do not present an estimate as the final cost of a different or expanded project.
Can a findings brief contain recommendations?
It can frame options for the authorized decision-maker, but it should label recommendations, assumptions, and unresolved questions plainly.
How long should a brief be?
A typical brief runs one to two pages, about 500 to 900 words. That length preserves the question, evidence, limits, open items, and next action owner.
