It's 10:17pm. You're half-watching something on your phone, winding down, when the notification appears. A message from your manager — not urgent, just a question that could absolutely wait until morning. You know it can wait. You know it. And yet you reply within four minutes, typing out a complete, thoughtful response like it's 11am on a Tuesday.
You close the app. And somewhere underneath the surface, something sours. Not anger, exactly. More like a quiet, low-grade resentment you can't quite locate. You did nothing wrong. Nobody forced you. And somehow that makes it worse.
That feeling has a name: the availability tax. And most of us are paying it constantly, without ever agreeing to the terms.
What the Availability Tax Actually Is
Availability — being reachable, responsive, reliably there — is not neutral. It's a resource. It draws on your attention, your mental bandwidth, your sense of time as your own. When you're always available, you're not just spending more hours working. You're spending your non-work hours in a state of low-level readiness, which is its own kind of exhaustion.
Think about what "being available" actually requires. Even when you're not actively responding, you're monitoring. Checking. Half-listening for the buzz. Researchers at the University of British Columbia found that just having your phone visible on the table reduces your cognitive capacity — even when you're not using it. The cost of availability isn't just the time you spend responding. It's the ambient tax on every moment you spend not responding but knowing you could be.
And here's the insidious part: when you respond quickly, you don't get credit for responsiveness. You reset expectations. The next message comes with the same implicit assumption of a four-minute reply. You haven't bought goodwill — you've bought a new floor.
How Expectations Calcify
Behavioral economists call this the ratchet effect: once a standard is established, it's nearly impossible to walk back without it feeling like a regression. You replied at 10pm on a Tuesday. Now 10pm on a Tuesday is available time. Not because anyone said so. Just because you made it so.
This is how chronic overavailability happens — not through a single bad policy, but through a hundred small acts of responsiveness that accumulate into an identity. You become "the person who always replies quickly." And once you've been that person for six months, not replying in 20 minutes during office hours starts to feel like a statement.
A 2019 study published in the Academy of Management Journal found that employees who were expected to monitor their work email after hours — even without actually doing much work — reported significantly higher levels of anxiety than those who weren't. The expectation alone was enough to compromise recovery. Not the work. The watching-for-work.
That's what constant availability does. It doesn't just take your evenings. It makes your evenings contingent.
The Way It Changes You Over Time
There's a version of this that's subtle and a version that's not. The not-subtle version is burnout — the kind that forces a break, shows up in sleep, erodes enthusiasm for work you used to care about. That version gets talked about. It has a vocabulary now.
The subtle version is quieter. It's losing the ability to be genuinely off. You go on holiday but you're not really there. You sit through dinner but part of you is monitoring. You start to feel vaguely anxious on the weekends in a way you can't explain, and you've stopped noticing it because it's been the background frequency for so long.
Deep focus — the kind that produces actual creative work, strategic thinking, anything that requires sustained attention — is incompatible with constant availability. Cal Newport has written extensively about this, but you don't need a book to feel it. You know it from experience. Your best thinking doesn't happen when you're glancing at notifications every 12 minutes.
The cost isn't just personal, either. Organisations lose the quality of thinking that comes from people who are genuinely able to concentrate. Everyone's more reachable and less capable. That's a trade most companies have made without realising they made it.
Practical Steps That Actually Work (And Some That Don't)
The standard advice is to set boundaries. Turn off notifications after 7pm. Block focus time. Communicate your hours. All reasonable. All genuinely useful. But let's be honest about the limits.
Turning off notifications doesn't change expectations — it just delays the collision. If your team still expects a same-evening reply and you've silently stopped providing one, the problem hasn't been solved. It's been deferred to a slightly worse moment.
What actually works, in practice:
- Communicate explicitly, not just behaviourally. Tell your manager you're not checking messages after 8pm. Don't just stop checking and hope they notice. Say it. It feels awkward. It's also the only version that works.
- Introduce response latency deliberately, not as avoidance. If you always reply within four minutes, start replying in 45. Not to be difficult — to recalibrate what's normal. Do it consistently, not randomly, so it reads as a pattern and not a signal that something's wrong.
- Use status indicators honestly. Most tools let you set a status. "Focusing until 4pm" is information. It lets people self-serve without creating anxiety about whether you've seen something.
- Have the availability conversation during onboarding, not after a crisis. If you're starting a new role, establish what "responsive" means before the default gets set. It's much easier to define a norm than to renegotiate one six months in when resentment is already part of the picture.
None of this is comfortable. And not all of it will work in every context. Which brings us to the part most articles on this topic skip.
The Honest Part
Some roles genuinely require high availability. On-call engineering, client-facing work with international time zones, crisis communications, anything where the cost of a delayed response is real and measurable — these are not situations where "set boundaries" is a complete answer. They're situations where availability is part of the job description, whether or not it appears there explicitly.
If that's your situation, the problem isn't a boundary problem. It's a negotiation problem. The question isn't "how do I opt out?" — it's "what is this availability worth, and am I being compensated accordingly?" Availability is a premium that should be priced. Extra pay, time off in lieu, reduced load elsewhere, or simply a clear-eyed acknowledgment that you're providing more than a standard role provides. If none of those conversations have happened, that's what needs to happen — not a quiet evening notifications policy that creates friction without solving anything.
There's also a version of this where the problem is you, not the environment. Some people check their messages compulsively not because it's expected but because the checking itself is soothing — a low-stakes activity that provides a hit of agency when everything else feels uncontrollable. That's not a boundary problem either. It's worth naming honestly, because the solution looks completely different.
And sometimes — not always, but sometimes — being highly available is genuinely a career advantage in a specific context, and you're choosing to pay that tax because the return feels worth it. That's a legitimate choice. The goal isn't to convince everyone to be less available. It's to make sure the choice is actually a choice, not a slow erosion you didn't notice until you were already in it.
What You're Actually Protecting
Recovery isn't a wellness concept. It's a performance concept. Athletes know this with extraordinary precision — the quality of training depends on the quality of rest. The same principle applies to cognitive work, and we've collectively decided to ignore it because the degradation is gradual and hard to attribute.
When you protect time that's genuinely yours — phone in another room, no exceptions, actually present in whatever you're doing — you're not being precious about work-life balance. You're maintaining the capacity that makes you good at your job. These aren't in tension. The always-available version of you is not the best version of you. It's the depleted one who's harder to be around, less able to think clearly, and increasingly resentful in ways that eventually surface whether you want them to or not.
That 10pm message deserved a morning reply. Not because you were unavailable. But because you're a person, not a system process. And systems that never sleep eventually crash.
Reply in the morning. The quiet won't kill anyone. The resentment might.
