The Cost I Forget to Count

When I weigh whether something is worth doing, my first instinct is always to count the hours it will take. An hour-long class. A two-hour dinner. A weekend trip. That number feels concrete and easy to compare against my calendar, so it’s the number I default to.

The problem is that the hours-spent number is only part of the actual cost, and for me, it’s not even the most important part. The cost that actually determines whether something was worth it is what I’ve started calling the recovery tax: the time and energy it takes me to get back to baseline afterward.

Two things that cost the same on paper

Here’s an example that made this obvious to me. Two activities, both roughly three hours. One is a hike with a friend. The other is a long, unstructured social gathering with people I don’t know well. On my calendar, they look identical. Three hours, one afternoon, gone either way.

In practice, the hike leaves me energized for the rest of the day. The gathering leaves me needing the rest of the day, and sometimes part of the next one, to recover. Same time cost. Wildly different total cost, once you count what comes after.

I had been making decisions for years based only on the first number, which meant I kept agreeing to things that looked equally reasonable on the calendar but were not equally reasonable for me.

How I started tracking it

I didn’t build anything elaborate for this. After anything that took real time or energy, I started jotting one quick note: how did I feel two hours later, and how did I feel the next morning. Not a rating system, just a sentence. Felt fine, went to bed early anyway. Felt wiped out, cancelled the next day’s plans to recover.

After a couple months of these small notes, patterns showed up that I hadn’t noticed while I was just living through them. Certain kinds of commitments consistently cost more afterward than the time they took upfront. Others cost almost nothing extra. Knowing which was which changed how I evaluated new invitations and requests going forward.

The hours on the calendar are the visible cost. The hours it takes to recover are the real one, and they rarely show up until later.

What this changed about how I say yes

Now, before I agree to something, I try to ask not just how long it will take, but what I’ll likely need afterward, based on similar things I’ve done before. If the honest answer is that I’ll need a quiet evening to recover, I factor that evening into the actual cost of saying yes, and I plan around it rather than being surprised by it later.

This has made me more willing to say yes to some things, not less. Once I know a particular kind of commitment has a low recovery cost for me, I don’t hesitate the way I used to, back when every new thing felt like an unknown risk to my week. And it’s made me more careful about the things I know run up a high tab afterward, not because they’re not worth doing, but because I want to actually plan for the cost instead of pretending it isn’t there.

This isn’t about avoiding effort

I want to be clear that this isn’t a system for avoiding anything difficult or tiring. Plenty of things that cost a lot afterward are still worth it to me. A hard conversation with someone I care about might leave me drained for a day, and I’d still choose it every time. The point isn’t to minimize cost. It’s to actually see the full cost, so the decision is an honest one instead of one based on an incomplete number.

There’s also a version of this that runs the other direction. Some things I assumed would cost a lot afterward turned out to cost almost nothing once I actually tracked them. A work trip I’d been dreading for weeks, expecting to need days to recover from, turned out to leave me fairly steady once I actually took it and paid attention to how I felt after. I would have kept avoiding similar trips indefinitely based on a guess, if I hadn’t started checking the guess against what actually happened.

That’s the real benefit of tracking this instead of estimating it. Estimates are shaped by memory, and memory tends to hang onto the worst version of an experience rather than the typical one. A single bad recovery after a certain kind of event can color my expectations for years, even if most instances of that same event were fine. Writing down the actual result, every time, keeps me honest against that bias in both directions.

Applying this to recurring commitments, not just one-off events

Once I got used to tracking recovery cost for single events, I started applying the same idea to ongoing things. A weekly commitment that costs a manageable amount of recovery time once is very different from one that costs the same amount every single week, compounding on top of whatever else that week already holds. The math that works for an occasional trade-off doesn’t automatically work when you multiply it by fifty-two.

This is where the recovery tax matters most, honestly. A single expensive afternoon is easy to absorb. A standing commitment with a high recovery cost, repeated indefinitely, can quietly define the shape of an entire season of my life without me ever making one clear decision about it. Naming the weekly cost, not just the one-time cost, is what finally got me to renegotiate a couple of recurring things I’d been treating as fixed.

Where this has limits

If you notice that almost everything leaves you needing significant recovery time, even things that used to feel easy, that’s worth paying attention to on its own. That pattern can be a sign of something beyond scheduling, like ongoing fatigue or burnout that deserves a conversation with a doctor rather than a smarter calendar. Tracking recovery cost is a tool for making better choices among reasonable options. It’s not a substitute for addressing exhaustion that doesn’t have an obvious cause.

For me, most weeks, the fix really has been this simple: count the after, not just the during. It’s a small change to how I evaluate what’s worth it, and it’s caught more bad decisions than any calendar trick I’ve tried.