Guides
Part of Apartment EV charging pilot evaluation: a practical guide
Apartment EV pilot data boundaries: what your records show and what they leave out
Apartment EV pilot data boundaries guide for 2027 helps property teams state what records show, what they exclude, and where a qualified review is still needed.
What to take away
- Attach three things to every pilot figuresource, date range and inclusion rule.
- A log showing five access questions proves five questions were recorded, not five problems.
- A recorded zero, an unavailable source and an out-of-scope gap are three different states.
- Keep technical fields and resident personal data on separate review routes.
- Sharing data outside the property needs a recorded decision from the owner or board.
How a boundary statement reads
A pilot report states its data boundaries by naming, for each figure, the source, the period and the rule that decided what counted. Readers then know whether a number describes the whole property, one log, or one file version.
Put the limit inside the finding sentence. "The maintenance log recorded five access questions between 1 March and 31 May 2027" carries its own boundary. "The pilot had five access problems" claims a condition the log never measured.
If the test is still being designed, the pilot evaluation guide explains how to set the measurement window before a figure is published.
What it covers
- Charger service log
- Tickets opened through the property maintenance line during the pilot period
- Resident survey
- Responses submitted voluntarily
- Provider export
- The session and energy fields in that file version
- Submeter or billing file
- Charges posted under the stated rate schedule
What it leaves out
- Charger service log
- Faults nobody reported, and events outside the period
- Resident survey
- Non-respondents and residents who never charged
- Provider export
- Failed sessions that never reached the network, and manual resets
- Submeter or billing file
- Cost still carried by common expenses
Oregon's ZEV report separates availability indicators from reliability indicators, listing uptime and the interval between a notice and its repair as different measures. See Oregon's metric categories. Those statewide definitions are not requirements for an apartment pilot. They show why two similarly named measures can rest on different records.
Record vs Boundary Statement
Record
- Service log
- Reports received through stated channel
- Participant form
- Voluntary responses, not all residents
- Provider export
- Fields supplied in that file version
- Property notice
- What was communicated, not understood
- Issue register
- Reported items, not every condition
Boundary statement
- Service log
- Participant form
- Provider export
- Property notice
- Issue register
Record the zeros, gaps and conflicts
| Data condition | Wording that holds up |
|---|---|
| Recorded zero | "No items were recorded through this log during the stated period." |
| Source unavailable | "The source was unavailable for the stated period." |
| Outside scope | "This event sits outside the pilot boundary and was not counted." |
| Conflicting records | "The two records disagree and await review by their source owners." |
A blank cell in a provider export is a gap in that file, not evidence that nothing happened. Say which channel residents were told to use, so a later reader knows how wide the net was.
Keep both versions when two records disagree, and note which one the published figure used. The power sharing records guide covers retention periods and who holds the originals.
Example: eight chargers, one uptime number
Illustrative figures, not a real project. A 60-unit building runs eight shared chargers for 90 days. The provider export lists 214 sessions and about 3,050 kWh. The dashboard reports 96 percent uptime.
- 214 sessions means completed network sessions only. It excludes a session a resident abandoned before authentication.
- 3,050 kWh comes from charger-side metering, not from the utility meter at the service.
- 96 percent uptime is provider-defined. It does not count days when a parked car blocked the stall.
Written properly: "The provider export recorded 214 completed sessions across 90 days at eight stalls, at 96 percent provider-reported uptime." That sentence claims nothing about daily usability.
Boundary in the Sentence
Keep
- Access questions
- Log recorded five
- Source named
- Issue log, pilot dates
- Missing field
- Say it is missing
- Conflicting records
- Preserve both, route
Avoid
- Access questions
- Pilot had five problems
- Source named
- No source or period
- Missing field
- Silently omit
- Conflicting records
- Pick one silently
When a figure is still moving, draft status labels keep a working number from being read as final.
Keep technical fields apart from resident data
An event time, a session status or a fault code answers the pilot question. A resident's name, unit number, contact details or payment record usually belongs in a restricted file with narrower access.
The NIST Privacy Framework is a voluntary resource for sorting fields by the risk they carry. Use it to ask one question of each field: does the published finding need this, or only the internal file?
Who approves sharing pilot data
The decision sits with the owner, or with the board of a condominium or strata corporation. The manager prepares the request. Property counsel reviews it against privacy law, the lease or declaration, and any provider contract.
Record the approval as a dated entry: who approved, which fields, which recipient, which purpose. An approval that lives only in a conversation does not survive a staff change.
In Ontario, the Condominium Act, 1998 and its regulations govern how a corporation handles its records and owner approvals, so a board resolution is the document to cite. Read the Condominium Act.
Residents' comments take a different route again. The pilot feedback guide shows how to publish what was said without implying that every resident agrees.
Common questions
Can a provider dashboard be the only data source?
It can be one source. Label it as provider-reported, and show the date range and the fields in that export version. Add the property's own log where the two records answer different parts of the question.
Does an empty issue log mean nothing went wrong?
No. It means nothing was recorded through that log in that period. Say that, and say which channel residents were asked to use.
Who decides whether pilot data can be shared outside the property?
The owner or the board, with property counsel reviewing the request against privacy law and the governing documents. Record the approval, the fields, the recipient and the purpose in the pilot file.
How do I report a figure from a source that later went offline?
State the period the source covered and the date it stopped reporting. Keep the last export with its file date, and mark any figure drawn from it as limited to that window.
