Most of what gets written about burnout is about how you feel. Boundaries, mindset, saying no, recovery rituals. Useful to varying degrees, and all of it downstream of a question nobody asks first: how many hours are you actually working, and on what?
Almost nobody knows. Not approximately, in the sense of a job title and a contract, but actually, with the evening catch up and the Sunday hour and the fragmented work that happens between other things.
That number matters because the two possible situations look identical from the inside and need completely different responses.
Two problems that feel the same
The first is genuine overload. You are working more hours than the role can reasonably absorb, and no amount of morning routine fixes an arithmetic problem.
The second is a distribution problem. Total hours are defensible, but they’re badly arranged: fragmented across too many things, with the demanding work sitting in whatever is left after everything else has taken its turn.
Both produce exhaustion. Only one is solved by doing less, and if you apply the wrong remedy you either burn out while optimising your calendar or cut work you didn’t need to cut.
The only way to tell them apart is a record. You can’t settle it by reflection, because memory of time is unreliable in a specific direction: long stretches are remembered, fragments disappear, and the interruptions that make work expensive don’t register at all.
How to track your working hours without it becoming another chore
Four weeks is enough. The method matters more than the tool.
Record as it happens. Reconstructing your day at 10pm reproduces exactly the bias you’re trying to escape.
Use broad categories. Five or six. Focused work, meetings, admin, messages, interruptions, and something for the time that goes nowhere in particular. That last category is often the most revealing.
Don’t improve the numbers while measuring. The temptation to perform a good week is strong and it wastes the exercise.
On tools, free plans are entirely adequate for this and differ more than people expect. This comparison of free time tracking apps covers the user caps, project limits and export restrictions on each, which matters if you want to look at a full month rather than a week at a time.
Method is worth a moment’s thought too, because people often conclude the exercise doesn’t work when really the method didn’t suit them. Timers produce the most accurate record and fail on interrupted days. Manual entry survives chaos but loses precision. Calendar style blocking suits a day already built around meetings. This overview of time tracking methods sets out which works for which pattern, and picking the wrong one is the usual reason a first attempt collapses in week two.
Why people don’t take their leave
There’s a second measurement nobody keeps, and it’s arguably a stronger predictor of trouble than hours: whether time off actually gets taken.
Leave entitlement is not the same as leave used. People defer it because a deadline is approaching, then defer it again, then discover the year ended. In teams where this information lives in individual inboxes, nobody notices that three people haven’t taken a proper break since January, including the three people themselves.
Making it visible changes the behaviour, which is most of the argument for handling it somewhere other than email. A shared calendar everyone genuinely maintains works. So does a leave planner such as actiPLANS, where requests are submitted, approved and shown in one view, so availability is a fact rather than a reconstruction and an unused balance is visible before December.
For anyone managing a team, this is the cheapest intervention available. You don’t have to improve anyone’s resilience. You have to notice who hasn’t stopped.
What to do with the month
Resist redesigning your life. The data supports one or two changes.
If total hours are the problem, the conversation is about scope or headcount, and you now have evidence rather than a feeling, which matters because “I’m overwhelmed” invites sympathy while “this accounts for eleven hours a week and is used once a month” invites a decision.
If distribution is the problem, move the demanding work earlier and protect it structurally, rather than hoping the day leaves room at the end.
And then stop tracking. The point was never the habit. It was finding out which of two very different problems you actually have, and a month settles that for a long time.
