Why Your Office EV Charging Spreadsheet Isn't Working

It usually starts with a single email. Three or four employees got EVs over the same quarter, and someone in facilities notices that two of them are parked in the charging spots every morning while a third circles the lot waiting. A polite all-hands goes out: 'Hey team, please be mindful of charging time so everyone gets a turn.' Problem solved, right?

Not quite. A few months later you have a dozen EVs, six charging stalls, and a situation that no amount of politeness can untangle. At some point (and at nearly every company we've talked to, this moment arrives like clockwork) someone opens a Google Sheet.

The Honor System Phase

The honor system works beautifully for about three months. People are conscious of the new infrastructure, grateful for the benefit, and generally decent to each other. They unplug when they're done and try not to hog the stall all day. Then the initial novelty wears off, summer hits, people stop commuting on the same days, and the first conflict shows up: someone's been plugged in since 7am and it's now 2pm and their car has been full for hours.

The honor system has a structural problem: it requires everyone to remember to do something (unplug and move their car) that has no immediate personal consequence if they forget. The charger is still there. Their car is still charged. The friction is entirely borne by whoever needed that stall next. This asymmetry is what breaks every pure honor-system approach eventually.

The Spreadsheet Phase

Someone creates a shared Google Sheet. It has columns for date, employee name, stall number, check-in time, and expected check-out. This feels like progress. It has structure. It's visible to everyone. For the first few weeks, people actually fill it in.

Then reality sets in. The spreadsheet is only as accurate as the last person who remembered to update it. On Tuesday morning, three stalls show as 'available' in the sheet, but when you walk down to the garage, all three are occupied: two from yesterday, one from this morning by someone who hasn't opened the spreadsheet yet. You walk back upstairs, check the sheet again, look for the person who checked in last, and send them a Slack message asking if they're done. They respond 40 minutes later. You missed the window.

The spreadsheet has a second structural problem: it requires manual updates at both ends of the transaction. Check in, then check out. Real-world processes that require two manual steps have twice the surface area for failure. People are good at the first step (checking in, because they want the stall) and terrible at the second step (checking out, because by that point they've moved on with their day).

The Slack Channel Phase

Someone creates #ev-charging. The intent is good: a single place to ask if a stall is free, announce you're heading down, or let people know you're leaving early. In practice, the channel becomes a low-grade source of ambient anxiety. Messages pile up without resolution. 'Is A2 still taken?' gets answered 20 minutes later with a thumbs up from the person who parked there, which doesn't actually tell you whether the stall is free or not.

Worse, Slack channels reward speed. The first person to see the 'I'm leaving in 10 minutes, grab my spot' message gets the stall. Everyone else who happened to be in a meeting, or who works in a different time zone, or who just doesn't compulsively check Slack, loses out. It's a system that systematically favors the most desk-bound employees and penalizes everyone else.

Why None of These Approaches Scale

The common thread across the honor system, the spreadsheet, and the Slack channel is that they all externalize the coordination problem onto the people who need the stalls. Every person who wants to charge has to actively check, monitor, ask, and follow up. There's no single source of truth. There's no automatic enforcement. There's no way to know, from your desk, whether a stall is genuinely available right now.

As your EV fleet grows (and it will grow; EV adoption rates among white-collar workers have been climbing sharply) informal systems don't just fail, they fail louder. More employees means more edge cases, more missed updates, more resentment when the same people seem to always get the good stalls. At around 10 employees competing for 6 stalls, informal coordination starts producing visible friction. At 20 competing for 10, it becomes a recurring topic in all-hands meetings.

What Actually Works

What works is real-time status. Not a document that represents what someone thought was true an hour ago, but actual live state: which stalls are occupied, which are free, who's in each one, and when they're expected to be done.

What also works is a fair queue system. Instead of whoever-checks-Slack-fastest getting the next available stall, a queue lets anyone join from their desk and get notified when it's their turn. No racing, no favoritism, no ambient anxiety.

The spreadsheet tried to be a coordination tool but couldn't keep up with real-world pace. The Slack channel tried to be a notification system but had no concept of state. What you actually need is software built specifically for this problem: something that knows the current state of every stall, handles the queue automatically, and sends notifications so nobody has to keep refreshing anything.

The good news: this is a solved problem. The infrastructure doesn't need to change. The hardware doesn't need to change. You just need a coordination layer that keeps the state accurate automatically and makes fairness a feature, not an honor.