Guides
Part of Apartment EV charger work orders: how to log a request without diagnosing it
Apartment EV charger routing register: four labels, sources and review dates
An apartment EV charger routing register sets four labels, dated sources, owners and review dates for open charger-service requests.
An apartment EV charger routing register records which route each charger request takes and who owns it next. It is not a set of ranked urgency levels or a finding about the equipment. Nothing in the register decides whether a charger is safe, what caused a fault, or whether work should proceed.
What to take away
- Write the four routing labels down before the first request arrives, not during one.
- Every label cites a dated sourcea provider notice, a resident report, a property walk observation, or a scheduled task.
- The register holds the request ID, label, trigger, owner, and review date. Account data, contact details, and access credentials stay in the restricted system.
- A label change is a new dated line. The earlier label and source stay in the record.
- Review open records on their stated date. If no current source supports a change, the record stays open and the question goes to the named owner.
The four routing labels
What it means in the register
- Standard
- Request entered the usual support queue
- Time-sensitive
- A named source set a response date
- Follow-up
- An earlier response left an open item
- Urgent-process
- The report went to the property's current urgent route
What it does not establish
- Standard
- Anything about cause or condition
- Time-sensitive
- An emergency or a safety finding
- Follow-up
- That the underlying condition is unchanged
- Urgent-process
- A diagnosis by whoever logged it
Choose the label by asking what the dated source says. Use Standard when no source sets a date. Use Time-sensitive only when a named source gives a response date. Use Follow-up when an earlier answer left a question open. Use Urgent-process only when the property has named its urgent route in writing and the report went there.
Keep the definitions short enough that a new property manager can apply them without asking. A label that needs a paragraph of interpretation will be applied two ways by two people. The four labels are this guide's convention, not an industry standard. Adopt them as written or replace them, but define each one once.
Name the source, not the fault
The trigger field is where most registers go wrong. "Critical fault" is a diagnosis the intake owner is not qualified to make. "Provider notice, March 3" is a fact anyone can check.
Acceptable trigger sources
- Dated provider or network notice
- Resident report with time and location
- Property walk observation with asset reference
- Scheduled inspection or maintenance task
- Utility or program notice
Record the charger's serial number or a precise location as the asset reference, so the request reaches the right charger rather than the right building. The serial number guide shows how to read the label.
Keep the register narrow
A shared register is read by board members, managers, and vendors. It should carry the request ID, routing label, trigger, owner, and review date and nothing else.
Resident names, unit numbers tied to accounts, payment details, and charger or network credentials belong in the approved restricted system. A routing decision does not need any of them.
The register template
Five fields, one line per event, and nothing else in the shared file.
| Field | What goes in it |
|---|---|
| Request ID | The next number from the intake log |
| Routing label | One of the four labels defined above |
| Trigger | The dated source, not a diagnosis — for example, "resident report, June 12, 9:40 a.m." |
| Owner | The role that answers next, such as the network provider ticket queue |
| Review date | The day the open record is checked, such as June 19 |
A routing label does not assign cost. When a repair or a service call carries a price, the charging agreement and the service contract say who pays. The record only names the role that answers next.
Change the record, not the history
When new information changes a label, add a dated line. Do not overwrite the old one. A later reader has to be able to tell what was known when the request was routed apart from what a provider found three weeks later. Those are different facts and they belong on different lines.
The National Archives treats records management as control across a record's whole life, from creation to disposition. The same idea applies at property scale: decide retention before the register fills up, and follow the property's record process rather than a folder someone made.
Worked example: a follow-up that stays open
A resident reports a charger that stopped mid-session. The manager logs it as standard. The source is "resident report, June 12, 9:40 a.m." The owner is "network provider ticket queue." The review date is June 19.
The provider replies on June 15 that the session ended normally. The manager adds a dated line: label moves to follow-up, source "provider reply, June 15," owner "regional manager," review date June 29. The original standard label and the resident report stay visible.
On June 29 there is still no answer on why the session ended. The record stays open. The manager routes the question to the provider rather than closing it, because a closed record with no source behind the closure is worse than an open one.
If the same question reaches a regulator's program, use that program's own forms. Public stations in some state programs file maintenance or fee-change notices with a utility commission. The property's internal register does not replace those filings.
Reassess on the stated date
A review date that nobody honors is decoration. Put the open records in front of the named owner on that date and ask one question: does a current source still support this label?
If yes, keep it and set the next date. If no, leave the record open and route the question.
If the property changes network provider or management company, reassess every open record, because the owner field and the routing path both just changed.
Questions about the routing register
Does a routing label decide whether a charger is safe?
No. It is a routing label applied by whoever logs the request. Safety questions go to the authority having jurisdiction and to a licensed electrician or professional engineer, following the property's current process. In most U.S. jurisdictions the electrical code the authority enforces is based on the National Electrical Code (NFPA 70), and Article 625 of that code covers electric vehicle supply equipment.
Who is allowed to change a label?
Whichever role the property process names, and the change has to cite a new dated source. If no role is named, that gap is the first thing to fix.
What if the property has no written label definitions?
Do not invent categories on the spot. Route the request through the current support or management process, note the missing definitions in the record, and raise it at the next board or management meeting.
How long do we keep closed records?
That depends on the property's record process, the association's governing documents, and any state rule that applies. Check those with a qualified attorney. Set retention before the register fills, not after, and write the chosen period into the record process so the next manager does not have to decide it again.
