How many hours do you really work? A one-week measurement
· 6 min read
Probably fewer hours than you say and more than you fear, but the only way to know is to measure for one week. The trouble with the question is that “hours worked” quietly means three different numbers: the hours you were at the desk, the hours a work app was actually in front of you, and the hours you would honestly call work. The method below measures all three so you can stop arguing about which one you mean.
Three numbers that all get called hours worked
When someone says they work fifty hours a week, they almost always mean the first number: the span between arriving and leaving, or between opening the laptop and closing it. It is the easiest to state and the least informative, because it includes lunch, the walk to the kitchen, the ten minutes staring at a wall after a hard call, and the phone.
The second number is the time a work application was in front on the screen. This is what an automatic tracker measures. It excludes the kitchen and the phone but includes the minute you spent with a document open while thinking about something else entirely.
The third number is the part of the second you would defend as work if asked. It is the smallest of the three, it cannot be measured by any machine, and it is the only one that has anything to do with what you produced.
Most frustration about working hours comes from mixing these up: feeling the size of the first number, being paid for the second, and judging yourself by the third. Measuring them separately for a week makes the confusion visible and, usually, more bearable.
The one-week method
You need a notepad or a text file, a fixed closing time, and something to record app time. Five working days.
- Each morning, write down the time you sat down. Each evening, write the time you stood up for good. The difference is number one, desk hours.
- Record which app was in front during the day. The built-in Screen Time report will do it (System Settings, then Screen Time, then App & Website Activity, switched on in advance). For a record that stops at your closing time and arrives on its own, see the next section.
- At the closing time, look at the day’s app total. That is number two, app hours.
- While the day is fresh, estimate number three honestly: of the app hours, how much was actually work? Write it as a fraction (“about two thirds”) rather than a precise figure. Precision here is fake.
- Repeat for five days, then add up each column and look at the three weekly totals side by side.
The order matters. Write the desk hours before you see the app hours, and the honest fraction before you have had time to rationalize.
Recording the middle number automatically
The second number is the one people most often skip because it seems like effort, and it is the one that is easiest to automate. Punchcard is a Mac menu bar app that notices which application is in front during the day and, at the closing time you set, prints a receipt: one line per app with its time, and a day total at the bottom. The day total is number two, ready-made, with no timer to start and no timesheet to fill in.
A few things to know before relying on it. It records app names only; it cannot see what document was open or what you were doing in it, and it asks for no macOS permissions to do its job. It counts whatever is in front, so a document left open while you take a call is counted as the document. And it has no notion of projects or clients, so it cannot tell you how many of the hours belonged to which piece of work. If that is your actual question, a tracker with projects is the right tool, and Punchcard is not it. The first seven receipts are free, which covers this experiment with two days to spare.
Screen Time is the alternative that costs nothing, with the caveat that its totals include evenings and weekends and it does not know when your workday ended. You can make it work by reading the numbers at the same time each day and subtracting, but it is more arithmetic than most people keep up for five days.
What a typical week reveals
The three weekly totals almost always line up the same way, and the gaps between them are the interesting part.
Desk hours are the largest. Forty-five, fifty, sometimes more. This is the number you have been quoting, and it is not wrong, it is just measuring presence rather than work.
App hours are noticeably lower. The gap is lunch, the kitchen, conversations, the phone, and the moments the Mac went to sleep while you did something else. For people in offices the gap tends to be wider; for people at home it can be narrower but includes more household interruptions.
Honest work hours are lower again, and here the gap is the uncomfortable one. It is the time with a work app in front that was not really work: rereading a message thread for the fourth time, tidying files, the long browse that started as research. Nobody’s fraction is one. If you estimated it at nine tenths every day, go back and try again.
The ratio between the first and third numbers is worth knowing once. It tells you how much of your “fifty hours” is production, and for most people the answer is a relief rather than a shock: the long days were not wasted, they were simply never as dense as they felt. There is more on that gap in the-difference-between-time-spent-and-time-worked.html.
The number to care about
Having measured all three, the tempting move is to try to push the honest-work total up toward the desk total, squeezing out every gap. Resist it. The gaps are not all waste. The walk to the kitchen is where the problem gets solved; the conversation in the hallway is where the plan gets fixed. A day with no gaps in it is not a productive day, it is a brittle one.
The more useful move is to look at whether the honest-work total is enough for the work you are expected to produce. If thirty-two real hours a week produces what is needed, then the fifty desk hours are a choice, and you can shorten them without losing anything. If thirty-two is not enough, the question is not how to add more desk hours, which would just widen the first gap, but how to turn app hours into work hours, which usually means fewer interruptions rather than longer days. Either way, you now have a number to argue with instead of a feeling.
If you want to know where the app hours specifically went, by application, how-to-see-which-apps-eat-your-day-on-a-mac.html covers that.
Questions
Should I include meetings in work hours?
Include them in desk hours and app hours (the video app will show up on its own line). Whether they count as honest work is your call, and it will differ by meeting. Being consistent across the week matters more than the rule you pick.
What about work I do on my phone or away from the Mac?
An app tracker on the Mac cannot see it. Add it to the desk hours by hand if it is significant. If a large share of your work happens away from the Mac, the app-hours number will understate you and you should weight it accordingly.
Is one week representative?
One ordinary week is representative of ordinary weeks. If the week had a launch or a holiday in it, run another. Two ordinary weeks that agree are as much certainty as this question needs.