Guides
Part of Apartment EV charger commissioning records: what to keep and for how long
Apartment EV charger precheck record: file by issuer
File the papers in an apartment EV charger precheck record by issuer: building department, utility, provider and contractor, with what each can and cannot show.
A precheck record is easier to read when every document sits under the party that issued it. A permit answers a building-department question, a utility approval answers a supply question, and neither answers the other's. The record keeps those answers apart, so a reader never mistakes one party's paper for another's.
An apartment EV charger precheck record organizes information a property received before a commissioning handoff. It is administrative. It does not inspect electrical work, certify a charger, approve energization, or replace the responsible contractor's or authority's process.
What to take away
- File each document under the party that issued it.
- Note which project step the document belongs to, without re-deciding that step.
- Write what an issuer's document does not show beside what it does.
- Keep a missing document as an open question, not as a guess about project status.
- Hand the next reviewer one document and one question at a time.
Five issuers, five kinds of paper
Five parties produce most of the paper in a precheck record. The table pairs each with its usual document, the question that document answers, and what the record must not infer from it. Each item keeps its own source and purpose instead of being treated as a general sign-off.
| Issuer | Document | What it answers | Do not infer |
|---|---|---|---|
| City or county building department | Building or electrical permit with its number; inspection result or sign-off from the local electrical inspector | Whether the work was permitted and inspected | That the charger is energized or the project accepted |
| Electrical designer or contractor | Load calculation or service capacity study; a document that identifies installed equipment | What supply capacity the installation was sized against | A conclusion about the utility's supply |
| Utility | Service application or interconnection approval for the charger's supply | Whether the supply connection was applied for or approved | Permit or inspection status |
| Charging provider | Service or network agreement, or a network export | Which agreement covers which charger | Who pays beyond what the agreement states |
| Property or contractor | Charger label data (make, model, serial number); site or parking map | Which unit serves which stall | A model number not shown in the source |
Precheck record fields
- Asset referencecharger label, parking location
- Sourcesender, title, date, file reference
- Limited purposeupdate, training, support contact
- Open itemdocument or answer still needed
- Next owner named for each open item
Link each paper to its project step
Most precheck paper traces to a named step, and the record notes which one a received document belongs to without trying to re-decide it. Read the installation stages for where each paper falls.
| Project step | Who acts | Paper to file under it |
|---|---|---|
| Permit and inspection | The city or county building department, as the authority having jurisdiction | Permit, inspection result or sign-off |
| Electrical work | The contractor, under Article 625 of the National Electrical Code (NFPA 70) | Load calculation, equipment identification |
| Supply | The utility | Service application or interconnection approval |
| Service | The charging provider | Service or network agreement, network export |
Each row stays with its own paper. A permit number belongs beside the permit, and a utility reference beside the utility's approval. Copying one into the other's row hides which party said what, and the next reviewer cannot tell which answer to trust for which question.
The Department of Energy's Alternative Fuels Data Center says an electrical contractor should obtain a permit from the local building authorities. It adds that permitting could require a site installation plan and approval from fire, environmental, or electrical inspection entities.
Keep each party's duty with its paper
Where a document assigns a responsibility, the record keeps that assignment. In shared charging, the property usually carries the permit, the electrical work, and the inspection. A provider covers the equipment and service its network agreement names. Residents pay for their own sessions under the plan the property sets.
Cite the agreement or invoice behind each line. The record tracks who pays, not the amount, and the budget models show how such splits can be set. If an issuer's paper is silent on a duty, write "not stated" rather than filling the gap from another party's document.
Make asset references consistent
An organized precheck needs a stable way to tell chargers apart. Match the label in a provider record with the label on the property map or in the service system, and use one identifier per charger in every entry.
If labels do not match, record the difference and request clarification. Do not silently merge them. A wrong asset reference can send a reviewer to the wrong equipment or attach an answer to the wrong work item. A plain-English look at installation helps when contractor labels read differently.
Treat a missing paper as a missing paper
Do not read a missing document as a finding. "The received materials do not identify the current provider support route" is a useful gap. It proves neither that the charger lacks support nor that someone failed a duty, and the record states only what was not received.
Preserve the date the paper was requested and the person or organization asked, so the next reviewer sees a pending request rather than silence. Keep the three kinds of gap apart. A missing document is a documentation gap and stays in the precheck record. A reported equipment event gets its own service record, referenced only when it helps the next reviewer. A construction decision stays with the party that makes it.
The buyer questions show which papers to request at purchase, and an installation checklist shows which to expect at the end.
Send one document and one question
The next reviewer should receive the original item, a concise index, and an answerable question. Avoid forwarding a large folder without context. The handoff might ask whether a named document exists, which current contact owns it, or where a property should request it.
It should not ask the receiver to confirm the whole installation is complete from a partial administrative file. If a document has names, account details, or a resident's device image, include only what the stated question needs, and follow the property's approved handling process.
The NIST Privacy Framework is a voluntary tool to help organizations manage privacy risk. Its relevance here is narrow: before including a detail, such as a resident's account number or a vehicle image from a charging app, ask whether the handoff question needs it at all.
Before the handoff, check the building rules that apply to the property, and preserve any later reply as a new record instead of revising the original entry.
Common questions
Does a precheck prove that construction is complete?
No. It records material received before a defined handoff and identifies questions that still need an owner.
Who should own a missing provider document?
Name the current provider or property role that can obtain or clarify it, and preserve the request date.
Should an equipment problem go in the precheck record?
No. Open a separate service record for a reported equipment event and reference it only when it helps the next reviewer.
