The difference between time spent and time worked
· 6 min read
Time spent is how long you were at the desk with work in front of you. Time worked is the part of that where you were actually moving something forward. The two are often hours apart, and a lot of frustration about productivity comes from confusing them: feeling exhausted by time spent while judging yourself by time worked, and never quite understanding why the two do not match.
Two clocks
Imagine two clocks on the desk. The first starts when you sit down with work in front of you and stops when you get up or switch to something that is not work. It does not care what you are doing; it only cares that work is there. This is the time-spent clock.
The second clock is stricter. It runs only when something is changing because of you: a sentence being written, a bug being fixed, a decision being made, a problem being understood. It stops the moment you drift, reread, tidy, wait, or wander. This is the time-worked clock.
At the end of a day, the first clock might read eight hours and the second clock four. Neither clock is lying. They are measuring different things, and the gap between them is not waste in any simple sense. It is made of several different things, and it helps to know which.
Where the gap comes from
Some of the gap is the warm-up. You sit down with the document, and for the first ten minutes you are reading what you wrote yesterday, remembering where you were, finding the thread. The first clock is running; the second is not. This is not wasted time, it is the cost of starting, and it is paid every time you start, which is why interruptions are so expensive.
Some of it is thinking. You are looking at the screen and nothing is happening on it, because the problem is being worked on in your head. The first clock counts it; the second, strictly, does not, because nothing has changed yet. This is the most productive kind of time-spent-not-worked, and any approach that tries to squeeze it out is self-defeating.
Some of it is drift. The document is in front, but you are thinking about lunch, or the argument, or the message you should send. Work is present and you are not. This is the gap that people feel guilty about, and it is real, but it is smaller than the guilt suggests.
And some of it is what could be called adjacent work: reorganizing files, rereading a thread, looking up something that turns out not to matter. It feels like work, it happens inside work apps, and the second clock is unsure whether to count it. Usually the honest answer is “a bit”.
Time worked is what remains once all of that is subtracted. It is never the whole day, and a day where it was more than half the time spent was a good day.
Measuring time spent
Time spent is measurable by machine, and this is the part worth automating, because it is the part you cannot estimate. The Screen Time report in System Settings will give you per-app totals for the day, though it includes evenings and weekends and does not know when your workday ended.
Punchcard measures it more precisely for a workday. It is a Mac menu bar app that notices which application is in front and, at the closing time you set, prints a paper receipt: one line per app with its time, and a day total. That day total is the time-spent clock, read off automatically, scoped to your working day, with no timer to start or stop. It records app names only (never window titles, documents or URLs), asks for no macOS permissions, and the first seven receipts are free.
It is important to be clear about which clock it reads. Punchcard measures time spent, not time worked. It cannot tell whether you were typing or staring; “Editor, 3h 10m” means the editor was in front for three hours and ten minutes, and that is all it means. It also has no projects or rates, so it cannot tell you how much of the three hours went to which client. For the first clock, that is exactly the right instrument. For the second clock, there is no instrument.
Estimating time worked
Because no app can read the second clock, you have to estimate it, and the trick is to estimate it as a fraction of the first rather than as an absolute number.
- At the closing time, read the time-spent figure for your main work app from the receipt or the report.
- Before doing anything else, ask: of that, roughly what share was the second clock running? Answer in coarse fractions: about a quarter, about half, about three quarters. Finer than that is invention.
- Multiply. Three hours at about half is ninety minutes of time worked.
- Write it next to the time-spent figure. Two numbers, side by side, every day for a week.
- On the weekend, look at the fractions. They will cluster. That cluster is your normal ratio, and it is the most useful number this exercise produces.
The fraction is subjective, and that is fine. It will be wrong by a bit every day and wrong in the same direction, so it is still a usable gauge of change. If the ratio goes from “about a third” to “about two thirds” after you move your mail to fixed times, the change worked, even though neither number was ever exact. For the wider measurement, including desk hours, see how-many-hours-do-you-really-work-a-one-week-measurement.html.
Closing the gap, or deciding not to
Once you can see the two clocks side by side, the obvious goal seems to be to push the second toward the first. Be careful with that.
Some of the gap should stay. Thinking time and warm-up time are not losses; they are how the work gets done. A day with time worked equal to time spent would be a day with no thinking in it. What you want to shrink is the drift and the adjacent work, and the way to shrink those is not willpower but fewer restarts: every restart brings a warm-up, and every warm-up is an opening for drift.
The other thing the two clocks let you do is stop being hard on yourself for the wrong reason. If the day felt like eight hours of effort and produced four hours of work, that is not failure; that is the ratio. Eight hours of effort really were spent. Understanding that the feeling tracks the first clock and the output tracks the second is most of the way to making peace with it. For why the feeling of a full day can come with nothing finished, why-you-feel-busy-all-day-and-still-got-nothing-done.html goes further.
Questions
Is there any tool that measures time worked directly?
No. Some trackers infer activity from keystrokes or mouse movement, which measures typing, not working, and requires permissions that let the app see far more than it needs. Time worked is a judgment, and the honest approach is to measure time spent by machine and estimate the fraction yourself.
Should I count meetings as time worked?
Count them as time spent (the video or calendar app will be on its own line). Whether they count as time worked depends on the meeting. Apply the same fraction test: how much of it moved something forward? Be consistent from week to week and the number will be usable.
My ratio is low. Is that bad?
Not necessarily. Some days are warm-up and thinking days, and the ratio drops. It matters only if it stays low for weeks while output suffers. A low ratio on a day when the hard problem got understood is a good day, whatever the second clock says.