Employee-only charging: what happens to guests, former staff, and offline access?

Employee-only access needs an actual enrollment process

In a workplace Reddit discussion, one commenter describes employee-only chargers with registration through the company administrator. That illustrates the administrative work behind restricted access; it does not establish a universal technical arrangement. A sign alone does not authorize users, while cumbersome enrollment can prevent legitimate staff from charging. Start with employees, guests, contractors, company vehicles, and any permitted public users, each with defined hours and rules.

Source: What’s your workplace shared-charging policy?

Verify where authorization happens

Networked charging can support different authorization methods, but capabilities vary by provider. DOE's workplace guidance treats access and management as program decisions. Verify the actual method being purchased: account approval, radio-frequency identification card, mobile app, payment card, or another supported arrangement. Ask whether identity is checked locally or through a remote service and how previously authorized users are handled during a communications outage.

Source: Alternative Fuels Data Center: Workplace Charging for Electric Vehicles

Illustrative scenario: cached permission after departure

Illustrative scenario: an employee registers two cars, a visitor arrives without the required app, and a former employee still has an active access card. During an internet outage, the station accepts a cached authorization list. That may preserve employee charging while also delaying access revocation. Alternatively, a fail-closed configuration may stop everyone. Neither outcome should be discovered by trial during the workday. The employer and provider should agree on the intended behavior and its limits.

Assign enrollment, guest access, and revocation

Design enrollment and removal as ordinary administrative processes. A new employee should receive clear instructions, while departures should trigger revocation through an assigned owner. Guests need a supported temporary option rather than a shared permanent credential circulating by email. Define whether one account may start multiple simultaneous sessions and whether company fleet vehicles have a separate priority. Keep personal driving information out of reports unless it is needed for an explicitly defined purpose.

Test the ordinary employee journey

Test the complete journey with someone who has never used the system. Confirm that posted instructions lead to a successful session, the price is visible, the connector can reach the vehicle, and help is available when authorization fails. Repeat the test with a guest account and with the approved offline procedure. A successful installation test using an administrator account does not demonstrate that ordinary employees can use the station.

Test four users instead of one administrator account

Use four deliberately different test cases: a newly approved employee, a recurring employee, a temporary guest, and a user whose access has been removed. For each, verify the actual session-start method and the result expected under the written policy. The test should use supported test credentials and an agreed procedure, with no unauthorized access attempts. A recurring user may succeed because an earlier authorization is cached, while a new user cannot enroll during a communications interruption. Those are different capabilities and should be reported separately.

For a temporary guest, check the whole visit rather than only credential creation. The guest needs to find the correct space, understand any price, start charging, and leave without retaining indefinite access. Determine who can issue the permission, how long it lasts, and how the guest receives help if the app or payment step fails. A receptionist should not have to borrow an employee's permanent credential or distribute an administrator login to make an ordinary visit work. Select a supported process that matches the number and frequency of guests.

For revoked access, ask the provider how quickly the change reaches each station and what happens if a station is offline. Have the responsible administrator record the tested behavior and any delay that the organization must manage. Keep this separate from the electrical fallback: permission to start a session and the safe aggregate charging limit are different controls. Finally, verify who reviews unusual use and what evidence is retained for a legitimate billing or access complaint. An operational handoff should leave facilities staff able to perform normal enrollment and removal without changing protected installation settings. Repeat the relevant user cases after a network migration or a substantial policy change, because an administrator's successful connection alone does not validate the experience of ordinary employees and visitors.

Preserve administration and support responsibilities

At handoff, document who approves users, reviews abnormal use, revokes access, resolves billing issues, and contacts the vendor. Keep emergency electrical isolation separate from routine account administration. If the policy later changes to public charging, reassess payment, signage, accessibility, insurance, and any funding obligations rather than simply removing the employee restriction in software. A small configuration change can materially change the service being offered.

Put it into practice

A decision table to keep handy