The Month I Worked Through a Vacation

I took a vacation last July. Five days away. Booked months in advance. Told every client I'd be out of office.

I worked every single day.

Not because of an emergency. Not because a project was falling apart. I worked because I always do, and I hadn't set up any real boundary to stop myself.

What I Told Myself

I told myself it was just thirty minutes in the morning. Checking in. Staying on top of things.

My time tracker told me the truth.

Over five days, I logged just under eleven hours of billable work. Two full working days, scattered across what was supposed to be time off. Plus another three or four hours of email and admin I didn't even log properly because I was telling myself it didn't count.

Fourteen hours of work on a vacation I paid for with money and looked forward to for months.

The Billing Part Makes It Worse

Here's what I'd really like to forget: I invoiced for almost none of it.

The work I did on vacation was catch-up stuff. Responding to messages so things didn't pile up. Reviewing deliverables before I could approve them. Troubleshooting a technical issue that a client flagged on a Thursday.

None of it fit neatly into a billing line. So I absorbed it.

I worked fourteen hours for free while on a trip I was paying for. The effective cost of that vacation, once you count the lost income, was significantly higher than the price of the flights.

The Pattern I Hadn't Noticed

Once I was home and looking at my logs properly, I realized the vacation wasn't an anomaly. It was an extreme version of something I did all the time.

I worked on weekends and didn't bill it. I logged hours on public holidays and called them normal days. I answered client messages at nine at night and never added them to a time entry because it felt small.

The vacation just made it visible because the contrast was so sharp. Five days when I was explicitly not supposed to be working, and I still worked fourteen hours.

My time log wasn't lying. I just hadn't wanted to look at it clearly.

What Consistent Logging Revealed

When I went through three months of time data after getting home, I found that my actual working hours were about twenty-five percent higher than what I was billing. Not because I was undercharging on rates. Because I was simply not logging huge chunks of work.

Small tasks below a mental threshold I'd set arbitrarily. After-hours responses. Prep work before calls. Admin that felt like it shouldn't count.

All of it added up to real hours I was giving away.

What Changed

I set a rule: if I work on a day I wasn't supposed to, it gets logged and it gets billed. No exceptions. If I can't bill it, I don't do it. If it's an emergency worth handling on a weekend, it's an emergency worth charging for.

I also stopped doing the mental math that convinced me tasks were too small to track. A twenty-minute email thread is a twenty-minute email thread. It goes in the log.

The vacation thing specifically: I now set my accounts to auto-responder, turn off notifications on my work apps, and physically close the laptop. Not because I don't care about clients. Because I've seen what the alternative costs me.

The Bigger Point

You can work all the time if you want to. Some people do. But if you're going to work all the time, you should at least know that you're doing it and what it's costing you.

My time logs showed me I was running a freelance business that had no off switch and was billing for maybe three-quarters of what it produced.

That's not sustainable. And it's not visible until you start looking at the numbers honestly.

Track your time, bill every minute.

Time-Trak is a native Mac and Windows time tracker with a floating timer, automatic screenshots, and one-click invoicing.

Free during beta.

macOS + Windows · Floating widget · Auto screenshots