Guides
Part of Apartment EV charger project authorization recordkeeping
Keep an apartment EV charger approval record current after a handoff
How to update an apartment EV charger approval record when owners, conditions or scope change, with retention notes and where a permit differs.
An apartment EV charger approval record stays useful only if it changes by addition. A decision is dated once, and every later event gets its own dated note, so a new manager or lender can read the file and reach the conclusion the first reader reached.
What to take away
- Add a dated note for every change, and never edit the original decision entry.
- When a decision owner leaves the role, log the new holder and the delegation source.
- Close a condition with the date and the document that closed it.
- When the scope moves, open a new question and mark the earlier decision as superseded.
- Set the retention date when the record is created, not years later.
Events that call for a new entry
Delegations expire, boards turn over, and managers change jobs, so a handoff is a reason to add a note rather than rewrite the earlier entry. The table shows what each event adds and what it leaves alone.
| Event | Add | Leave unchanged |
|---|---|---|
| Decision owner leaves the role | New holder and delegation source | The original decision entry |
| A condition closes | Status note with date and closing document | The condition as first written |
| Scope changes | A new question | The earlier decision, marked superseded |
| Board or manager turns over | Who holds the source file now | Dates and sources already logged |
Four steps to keep the record current
- Check each open condition against its source document and note the date you checked.
- When the decision owner leaves the role, log the new holder and the delegation source.
- When a condition closes, add a status note with the date and the closing document.
- When the scope changes, open a new question and mark the earlier decision as superseded.
Never edit an original decision entry to carry information that arrived later. Add a dated note and connect the two.
A status note points back to the seven fields of the original record: question, decision owner, scope, evidence, conditions, date and next owner. Only the fields that changed get a new line, and each new line carries its own date so the order of events stays readable.
Keep the note short. It says what changed, which document shows it, and who now owns the next step. If a reader needs more than that to understand the change, the source file is missing something and should be fixed there.
Decision record fields
- Questionnarrow action considered
- Decision ownerrole or body
- Scopelocation, parties, activity
- Evidencedated records and gaps
- Conditionsrequired next steps
- Datedecision and review date
- Next ownerresponsible role
Closing a condition without overstating it
A decision may depend on a utility response, a technical review, a local review or a revised scope. Write each as an open condition and never call the project fully approved. The status note that closes a condition names the document, and nothing more.
Open condition / What the closing note names
- Utility response
- The response and its date
- Technical review
- The review result and who issued it
- Local review
- The local decision and its date
- Revised scope
- The new question that replaces the old one
Boards often miss this step, which is one of the mistakes boards keep repeating when charging projects stall.
A handoff note for the next manager
Note who holds the source file, its format, who can retrieve it, and where the backup copy sits. A record nobody can locate is not retained in any useful sense. The National Archives says to take care of records so that information can be found when needed.
The approval itself should stay narrow. An approval to discuss with a vendor is not a vendor selection, and the questions to ask before buying belong in their own record. The board-level side of that sequence appears in condo EV charging planning.
Retention: how long to keep the record and its evidence
Exact periods come from your own documents and your state or provincial rules. Typical ranges: minutes and governing documents stay for the life of the building; contracts run about seven years; warranties last for the equipment's service life.
Ontario's Condominium Act, 1998 sets record-keeping duties for condo corporations. Strata corporations in British Columbia follow separate rules under the Strata Property Act. Charging allocation logs belong in the same plan as the approval.
What to leave out of the shared record
The shared index states the decision, scope, date, conditions and the location of the controlled source file. It should not copy personal contact details, account numbers, payment data or signatures. Those belong in a restricted file.
An approval record is not a permit
A board decision and a local permit are separate records unless the permitting authority says one document serves both. Keep them in separate rows, with separate dates and sources. What follows approval is covered under multifamily installation steps.
The Department of Energy's state laws and incentives directory lets you select a state and see its laws and incentives for alternative fuels and advanced vehicles. It cannot tell you what your property has already approved.
Common questions
How long do we keep an approval record?
As long as the decision still affects the property. Minutes and governing documents usually stay permanently, contracts commonly run seven years, and warranties last for the life of the charger.
Does it replace a permit?
No. Keep the permit result in its own row with its own date, unless the permitting authority states that one document covers both.
Who updates the record when the decision owner changes?
The designated record owner adds a dated status note naming the new role holder and the delegation source. The original entry stays as written.
