Why do time tracking apps round your time to the nearest 15 minutes?

The call took six minutes. The app logged it as a quarter hour, because a quarter hour is the smallest unit it is willing to hand back. A fourteen-minute call gets the same quarter hour. So does an eleven-minute one. Three genuinely different calls come out of the tool looking identical, and none of them took fifteen minutes. The number is not wrong exactly — it is just not a description of anything that happened. It is what the format was built to produce, whether or not it matches the six minutes it is standing in for.

The rounding was built for invoices, not for you

Fixed billing units — a quarter hour, sometimes a tenth of an hour — come from a specific place: hourly billing, where a client is charged in blocks and nobody wants an invoice line that reads "$4.17 for six minutes of a phone call." Rounding to a clean unit makes the arithmetic simple and the invoice readable. That is a reasonable answer to a real problem, for the person doing the billing. It has nothing to do with a person who is simply trying to keep an honest record of a day, but the convention shipped as the default in most time tracking apps anyway, because the apps were built with billing as the primary use case and everyone else just inherited the same rounding.

A rounded number looks exact but isn't

This is the part that is easy to miss: a number like 0:15 reads as precise. It has a clean, confident shape, the same shape a genuinely measured fifteen minutes would have. But it cannot tell you, later, whether the entry underneath it was six minutes or fourteen — both are gone, replaced by the same digit. The record now carries more certainty than it earned. You are not looking at what happened; you are looking at what happened, passed through a filter that only outputs certain approved numbers, with no way to tell afterward which real value went in.

The gap is small once, and it does not stay small

A single rounded call is a trivial error — a few minutes, nobody would notice. But a day is rarely one call. A day with eight short interruptions, each rounded up to the nearest quarter hour, can show two hours of tracked time against maybe forty real minutes of actual interruption. None of the individual roundings feel dishonest in the moment. Stacked across a day, and then across a week, they produce a total that quietly disagrees with the day you actually remember living — not because you tracked anything incorrectly, but because the tool was rounding up every single time you looked away and back.

Some moments are too short to round up to anything

The opposite failure sits right next to the first one. A task that comes in under the app's minimum unit sometimes does not round up at all — it rounds down to nothing, or the app never prompts you to log something that short in the first place. A two-minute favor for a coworker, a quick message that mattered, a short exchange that changed how the rest of the day went: none of it clears the bar, so none of it makes it into the record. The day did contain it. The tracker simply was not built to notice anything that small, and a record with an invisible minimum size has blind spots exactly where the smallest, easiest-to-forget moments live.

Remove the duration, and there is nothing left to round

Every version of this problem is downstream of the same decision: the tool is measuring a span of time, and a span has to be expressed in some unit, and the unit has to be some fixed size. A record that never measures a span in the first place has nowhere for the rounding to attach. Writing "quick call with the contractor about the schedule change" does not need to fit a fifteen-minute slot, a ten-minute slot, or any slot at all — it just needs to be true, and it stays exactly as true whether the call took two minutes or twelve. There is no unit sitting underneath a written line waiting to round it to the nearest anything.

TimeMap works this way by design rather than by accident: duration is not a field the app tracks at all, so there is no fifteen-minute block hiding behind a line, no minimum length a moment has to clear to be worth writing down. You note what you were doing, give it a colour, and the entry is exactly as valid whether the thing it describes took two minutes or two hours — nothing about it is ever rounded, because nothing about it was ever measured in the first place.

If a rounded number has ever looked more confident than the moment it was supposed to represent, that confidence was borrowed from the unit, not earned by the record. A line that just says what happened does not have that problem, because it was never trying to be a number to begin with.