Workplace charging waitlists: handle missed offers, blocked bays, and failed sessions

A posted time limit leaves the handoff unresolved

A Reddit workplace discussion describes five Level 2 stations shared by more than a dozen EVs, with colleagues exceeding a two-hour limit. Comments describe waitlists and notifications, but those experiences do not establish a policy that works for every employer. Once a workplace has chosen a sharing policy, it still needs a reliable handoff from one driver to the next. This guide addresses that operating step: what staff should do when the promised space is unavailable or an offer fails.

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

Separate a queue offer from an available charging bay

A queue position, a software reservation, an empty parking space, and a functioning charger are different states. Write down what the driver is being offered: a particular connector, a parking space, or permission to start at the next available port. The administrator must be able to tell whether a driver accepted an offer but could not reach usable equipment. Do not mark the request fulfilled merely because the app sent a notification.

Use a simple event record: request received, offer sent, accepted or declined, arrival confirmed, session started, and space released. Add a fault or blocked-bay state instead of forcing every failure into a no-show category. The provider must demonstrate which events its platform records; a manual log can cover a pilot without pretending unsupported automation exists.

Define what happens after a missed offer

Set an offer-response window that employees can realistically meet during work. State whether a declined or expired offer removes the person, moves them back, or allows a supported snooze. Decide how repeated missed offers are handled. These are employer choices, not universal charging standards. Apply the same published rule to comparable cases and let staff report a known notification failure.

Employees who cannot leave a customer, production line, or restricted work area need a planned alternative. That may be an agreed break-time handoff or an all-day connection arrangement elsewhere. Do not leave their only option as watching a phone continually. An administrator should resolve operational exceptions without asking employees to disclose unnecessary medical or personal travel details.

Do not treat an occupied bay as a driver no-show

If the offered bay is still occupied, the next driver should have a clear way to report it and preserve the request. Facilities then verifies the obstruction and contacts the current user through the approved process. Do not direct drivers to block another vehicle, move someone else's vehicle, or disconnect another driver's cable without an authorized operating procedure.

If the cable is available but the session will not start, record the port identifier and visible fault, and route the case to support. A failed charger should be removed from the queue until its status is resolved. Keeping a known faulty port available can generate repeated offers, repeated no-shows, and misleading evidence that employees are ignoring the rules.

Illustrative scenario: the offer succeeds but the session does not

Illustrative scenario: an employee accepts an offer during a scheduled break and arrives to find the previous car still parked. The system later labels the employee a no-show. The administrator checks the accepted offer and blocked-bay report, restores the employee's position under the published rule, and handles the obstruction separately. A second user encounters a charger fault; that port is temporarily withheld from new offers. Neither case should automatically count toward a misuse penalty.

This example defines a process to test, not a claim that every network has these functions. Ask the vendor to demonstrate position restoration, a temporary port outage, and correction of any resulting charge. Record the manual fallback when a function is unavailable.

Test the queue with real work constraints

Run a controlled pilot with staff from different work patterns. Test an accepted offer, an intentional decline, an expired offer, a blocked space, and a failed session. Agree on the test accounts and procedure first. Confirm who receives the issue, who can correct the queue, and how the driver learns the resolution. A successful test under an administrator account alone does not validate an employee's notification settings or walking time.

DOE recommends naming responsibility for workplace charging administration and enforcement. For this pilot, give the coordinator authority to correct an operating record while keeping electrical settings outside that role. Maintain a short record of exceptions and the reason for each correction, with access limited to the staff who need it.

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

Use failed handoffs to decide the next correction

Review offers that never became useful sessions by cause: missed notification, unavailable employee, blocked bay, authorization problem, or equipment fault. Compare successful handoffs and administrator effort across shifts. Repeated blocked bays suggest a turnover problem; repeated fault reports suggest service work; usable bays with no viable work-break handoff may require a different connection arrangement.

If employees still cannot receive needed energy after those failures are addressed, use the observed shortfall for a separate capacity review. Buying more power will not repair a notification workflow, and a perfectly administered queue cannot create energy or parking space. Keep this operating playbook with the published policy and update it when the provider or workforce changes.

Put it into practice

A decision table to keep handy