Time tracking vs time logging: what is the actual difference?

These two phrases get used as if they were the same thing, and they are not. One measures how long something took. The other records what the thing was. Once you can tell them apart, a lot of frustration with time apps starts to make sense.

Time tracking: the question is "how long?"

Time tracking is measurement. You start something, you stop it, and what you are left with is a number: forty minutes, two hours, three and a quarter. The unit of value is elapsed duration, and everything about a tracking tool is built to protect the accuracy of that number — timers, idle detection, rounding rules, rules about which project a block belongs to.

It exists because certain numbers have consequences. A freelancer invoices by the hour. An agency reconciles a retainer. A studio needs to know whether a fixed-price job actually cost twice what it quoted. A team estimating next quarter wants to know what the last one really took, not what it felt like it took. In all of those cases somebody downstream is going to read the number, and if it is wrong, something material goes wrong with it.

What tracking is good at: proving cost, comparing estimate against actual, splitting effort between clients, giving you an honest answer to "am I spending three days a week on the thing that earns nothing?"

What tracking cannot tell you: what the two hours contained. A tracker will happily tell you that Tuesday afternoon held 2h 10m of "Client A". It has no idea whether that was a good afternoon or a wasted one, whether you solved the problem or went round in circles, whether the call ran long because someone was upset. The duration survives; the substance does not.

Time logging: the question is "what?"

Logging is description. You write down what you are doing, or what you have just finished doing, in a line. No timer runs. The unit of value is the entry: a moment, a few words, usually a time and a category attached to it.

Because nothing is being measured, nothing has to be started or stopped, and nothing breaks when you forget. A gap in a log is simply a gap. A gap in a tracker is corrupt data that quietly ruins the total, which is why people go back and fudge it — and once you have fudged it twice, the numbers are fiction anyway.

What logging is good at: telling you what a period of your life actually consisted of. Which people recur. Which worries recur. What you were doing in April that you have completely forgotten. Whether the shape of your weeks changed after you moved, or changed jobs, or got a dog. It answers the question you tend to ask months later, not the question you ask at the end of the billing cycle.

What logging cannot tell you: precise durations. It will not stand up as an invoice. If your accountant needs a defensible number, a log is not the instrument.

How to tell which one you want

• If someone other than you will read the output — a client, a finance system, a project manager — you want tracking.
• If the output is only ever read by you, later, out of curiosity or as a way of remembering, you want logging.
• If you have started three timer apps this year and abandoned all of them, you probably wanted logging the whole time and were sold measurement.

They are not enemies. Plenty of people track billable work for eight hours and log the rest of life separately, and the two files never need to meet. The mistake is expecting one to do the other's job: expecting a stopwatch to tell you what your year was like, or expecting a diary to survive an audit.

A note on precision

There is a quiet assumption that a measured number is more truthful than a written line. Often it is not. A tracker that ran for ninety minutes while you were half in the room reports ninety minutes with total confidence. A line that says "stuck on the migration, kept getting up to make tea" is imprecise about duration and far more accurate about the afternoon.

TimeMap sits firmly on the logging side: it stores a line, a time and a category colour, and never runs a clock. That is a deliberate limit, not a missing feature — the thing it is trying to preserve is what happened, not how many minutes it lasted.

If you are unsure, start with logging

Logging is the cheaper experiment. It costs one line and it fails gracefully; you can drop it for a fortnight and pick it back up without repairing anything. If after a month you find yourself genuinely needing durations — because you are billing, or estimating, or arguing a case — add a tracker for that specific slice of work, and leave the rest of your life un-metered. Very little of a life needs to be measured. Quite a lot of it is worth remembering.