Bay Availability and Lighting
Most complaints at a charging site are not about charging. They are about a driver who could not find a free bay, drove to one that was occupied, or gave up in a dark basement. Those are wayfinding problems, and they are solved with information and light rather than with power.
Availability at the three distances a driver experiences it, keeping one truth about availability across systems that each hold part of it, lighting driven by charger state, and the occupied-but-not-charging state that causes most of the arguments.
Discuss bay availabilityFor An operator or property owner whose complaints are about finding and reaching a bay rather than about charging speed.
Availability at three distances
- 1
Before setting off
In an app or a map. Decides whether the driver comes at all. Being wrong here sends someone on a journey for nothing, which is the worst version of the failure.
- 2
On arrival
At the entrance or the level. Decides whether they enter and where they go. A count of free bays per level is worth more than per-bay detail at this distance.
- 3
At the bay
A light or an indicator visible from the aisle. Decides which bay they take, and it is the only one that works when the app is wrong.
Most sites do the first and skip the other two, which puts the entire burden on the app being correct in a basement where the driver has no signal to refresh it.
One truth about availability
Availability is frequently held in several systems that each know part of it and disagree at the edges.
- The charging platform knows whether a vehicle is connected and whether the unit is faulted
- A parking system, where one exists, knows whether the bay is physically occupied
- Signage and lighting may be driven by either, or by their own sensing
- The app may cache, and a cached availability is a stale availability
One system has to own publishing availability, and everything else must consume rather than compute. Where several systems each derive it independently, they will disagree, and the driver will experience the disagreement as the site being unreliable.
Occupied but not charging
This is the state that generates the arguments, and it is not one state but three.
Swipe to compare
| State | What is happening | Reasonable response |
|---|---|---|
| Finished, still parked | Charging completed, vehicle remains | Notify the driver, then idle fee after a grace period |
| Parked, never plugged in | An EV or otherwise, using the bay as parking | Enforcement. This is a parking matter, not a charging one |
| Connected, not drawing | Vehicle is full, or has refused, or is scheduled | Nothing. It is charging correctly and may resume |
Treating all three the same produces an idle fee charged to a driver whose vehicle was charging correctly on a schedule, which is a complaint the operator will lose.
Lighting driven by charger state
Lighting at a charging bay does three jobs at once, and driving it from charger state makes it do all of them better.
- Wayfinding: a free bay that is visibly free from the aisle, without the driver approaching each one
- Status: charging, complete, faulted, distinguishable at a glance rather than by reading a small screen
- Security and comfort: a lit area is safer to use and less attractive to interfere with, particularly in a basement at night
The energy question is worth taking seriously in a large facility, and it points the same way: presence-triggered or state-driven lighting is both more useful and cheaper to run than lighting an entire level continuously.
Basements, where all of this matters most
Underground parking is where charging is most needed, where signal is worst and where light is scarcest, so it is where availability information fails most and matters most.
- Assume the driver has no signal from the moment they enter the ramp
- Availability has to be visible physically, because the app will not refresh
- Signage at the ramp with a per-level count does most of the work for very little
- Bay indication visible along the aisle finishes the job
- The charging system itself must work without connectivity, or the bay is unusable regardless of how well it was signposted
Want this applied to your own site?
Discuss bay availabilityTechnically reviewed by Deepu Joy, Director of Products and Delivery. Last reviewed 2026-09-10.
Frequently asked questions
Why do drivers complain about charging speed when the problem is availability?
Because speed is the only variable they know the name of. The underlying complaint is usually that the bay was occupied or that they could not find it.
Which system should own availability?
One of them, and everything else should consume it. Where several systems each compute availability independently they will disagree, and the driver experiences the disagreement as unreliability.
Should we charge idle fees?
Only after distinguishing the three occupied-but-not-charging states. A vehicle connected and not drawing may be charging correctly on a schedule, and billing that driver is a complaint you will lose.
Is bay lighting worth the cost?
It does wayfinding, status indication and security at once, and state-driven lighting costs less to run than lighting a whole level continuously.
What matters most in a basement?
Assume no signal. Availability has to be physically visible, because the app will not refresh, and the charging system has to work offline or the bay is unusable anyway.
Complaints about finding a bay rather than about charging?
Tell us what a driver sees at the ramp, at the level and at the bay today. The gap is usually at the second one.
Discuss bay availability