Guides
Part of Apartment EV charging document control: a practical filing method
Apartment EV charger file names for utility, permit, rebate and board records
Name apartment EV charger project files for the utility application, load calculation, permit, rebate, warranty, board approval, resident agreement and commissioning record, so each one stays findable.
An apartment EV charger project creates a long paper trail: utility forms, load math, permit packets, rebate applications, warranties, board votes, resident agreements and commissioning reports. A clear file name lets the property find the right version without opening every folder. The name should show the topic, date, document type and status, and nothing more.
Name the records a charger project creates
Each record type below gets its own document-type label. The examples use the project label oak-view and a submission date of 2027-03-08. They are illustrations for a property folder, not a required standard.
- Utility interconnection application
2027-03-08_oak-view_utility-interconnection_submitted_v01- Electrical load calculation
2027-03-08_oak-view_load-calc_draft_v02- Building permit application
2027-03-08_oak-view_permit-application_submitted_v01- Utility or state rebate form
2027-03-08_oak-view_rebate-form_submitted_v01- Charger specification and warranty
2027-03-08_oak-view_charger-spec-warranty_received_v01- Board or condo approval
2027-03-08_oak-view_board-approval_adopted_v01- Resident charging agreement
2027-03-08_oak-view_resident-agreement_draft_v01- Invoice and commissioning record
2027-03-08_oak-view_commissioning-record_received_v01
The load calculation label matters because the calculation draws on NEC Article 625 for EV supply equipment and the service and feeder calculations in Article 220. A file named load-calc should say which inputs it uses in its index entry, so a reviewer knows what was assumed.
Match each label to the rule behind it
Some records have a legal source, so the name must not claim more than the record shows. The commissioning record shows that a test was done, not that the work was approved.
In California, a homeowners association or condominium board reviews a charger request under Civil Code section 4745. The approval file should show the date the written request was received and the date of any written decision, because the statute's timing rules run from those dates.
For a California renter, the request falls under Civil Code section 1947.6. Name the tenant's written request and the landlord's reply as separate files, so the record shows which step is complete.
A rebate form needs a status too. Federal Section 30C credit ended for property placed in service after June 30, 2026, so a file for a charger installed later should not be named as a 30C claim. Name the actual program the application went to, and check its current window with the administrator.
Filename fields to define
- Date2027-03-08
- Project labeloak-view
- Document typeutility-question
- Statussubmitted
- Versionv02
- Exclude resident names, unit numbers, account numbers
Choose the fields first
Field / Example
- Date
2027-03-08· Sorts the record and shows its currency- Project label
oak-view· Connects it to one property file- Document type
utility-question· Explains what it is- Status
submitted· Shows its current stage- Version
v02· Distinguishes a revision when needed
Start with a small controlled vocabulary. Decide once how the project writes the property label, document type and status, then list those terms in the folder index.
A person who sees utility-question should not have to guess whether utility-inquiry, utility-email and utility-request mean the same thing. If they differ, define the difference before files accumulate.
Ask the people who create and retrieve the files what they look for before imposing a complicated pattern.
Apply the status labels carefully
Status labels describe a record. They do not decide the project. Use draft for a document still under internal revision. Use received when an outside party has sent material to the property. Use submitted only after the authorized sender has actually transmitted a request. Use adopted only for a decision that the property has recorded through its own authority.
Use it when
- Draft
- The property is still revising the record
- Received
- The file came from another party
- Submitted
- An authorized person sent an application or question
- Adopted
- The authorized decision maker recorded its action
- Superseded
- A later record replaces it for current work
Do not use it when
- Draft
- A vendor has merely sent a proposal
- Received
- The content has been accepted or approved
- Submitted
- The team prepared a form but did not send it
- Adopted
- The group only discussed an option
- Superseded
- The older record remains the only decision record
Cost files need the same discipline. Name the invoice or bid by its issuer and date, then label each figure using the cost approval status so a quoted price is not mistaken for an approved budget line.
Keep source files easy to trace
Save a source page with a filename that says what it is, not what the team hopes it will prove. For example, 2027-03-08_doe-afdc_state-incentive-directory_accessed.pdf records the issuer, subject and access date.
The Department of Energy's state laws and incentives directory helps a team find state-level leads. The saved file should still point to the agency page and must not be labeled as an approval or a confirmed benefit.
Use the same approach for email. Name a city office message by date, issuer, subject and received status. Keep the complete message and its attachments together under the property's approved records process.
If a later message changes the answer, create a separate row in the index and mark the older message as superseded for current work. That preserves history without inviting reliance on an outdated response.
Keep private details out of names
Do not include a resident's name, unit number, email address, payment detail or account number in a filename. Store resident agreements and payment records through the property's approved process, not in a broadly visible project folder.
Test and maintain the system
Run a short retrieval test at the start of the project and after any staff change. Ask someone who did not create the files to find the latest utility application, the load calculation draft and the board's latest decision record.
Note where the search failed. The fix may be a better document-type label, a clearer folder name or a simple index entry. Review the convention when the project moves to a new stage, since permits and installation records often need different labels from resident notices. Confirm who is allowed to decide what the labels mean, using the representative authority guide.
Common questions
Should every file have a version number?
No. Add one when multiple versions of the same document are active or likely to be compared.
Is "final" a useful status label?
Only when the property defines what final means. "Adopted," "published" or "superseded" is often more specific.
Who approves the naming pattern?
Use the person or role responsible for the property record system, with input from the people who will maintain the files.
