How do you log a day you spent mostly freelancing?

By ten in the morning you have already done three things that do not belong under one label: finished a layout for one client, chased an invoice from another that is six weeks overdue, and written a quote for a job you might not even get. None of that fits a single button. A time-tracking app wants one task, started and stopped; a freelance day resists that from the first hour, because it was never built out of discrete tasks to begin with — it was built out of whatever needed doing next, for whoever happened to be asking.

The billable clock and the actual day are two different documents

Some of what you do has a real number attached to it, and that number matters: a client is paying by the hour, and a timer run honestly for that block is the right tool, because someone downstream is going to read the figure and act on it. A log will not replace that clock, and it should not try to — if an invoice needs a defensible number, this is not where that number comes from.

But the billable clock only covers the fraction of the day someone is paying for. The quote you wrote for a job that went nowhere, the hour spent politely chasing someone who owes you money, the call with a maybe-client who might hire you in six months — none of that has a clock running on it, and it is exactly the part of a freelance week that vanishes first from memory, because nothing ever marked that it happened. A year in, it is the invoiced hours you can reconstruct from old records. It is everything else that just disappears.

There is no shift to clock out of

Most advice about logging a workday assumes a day with edges: it starts, work happens, it ends. Freelancing rarely offers that. A client message lands at dinner and you answer it, because the relationship is the whole business and an unanswered message at nine feels like a risk. A quiet Tuesday afternoon gets used for laundry because no client is waiting on anything, and then Thursday evening gets eaten by a rush job instead. A timer wants a clean block to attach itself to. A day built this way does not have one, and treating it as though it should is not a discipline problem — it is asking the wrong shape of tool to describe a day that was never shaped that way.

What is actually worth writing down

Not "client work," which could describe two hundred different days. A few lines that would still mean something in a year:

• The actual client or project, by name — not the category. "Redesigned the checkout flow for the bakery site" tells you more, faster, than "design work" ever will.
• Whatever moved: a reply after weeks of silence, a rate you finally asked for and got, a scope that quietly grew, a no that at least closes the question.
• The unpaid hour, on purpose. It is easy to leave out because no one is billed for it, but it is often the biggest single reason a week feels heavier than the invoices at the end of it would suggest.
• How the day actually felt, when it was worth noting — the specific relief of a payment finally landing, the specific dread of an inbox you kept not opening.

A slow week and a full one look the same from inside a single day

Freelance income comes in a rhythm most people only recognise after the fact: a stretch where everything lands at once, followed by a quieter one that, from inside any single day of it, does not announce itself as quiet. You cannot tell from Tuesday alone whether this is a normal lull or the start of a real gap. What tells you is a run of entries you can put next to each other — a slow fortnight against the one that turned around, this quarter against the one before it — showing which clients actually filled the time, which kind of work keeps reappearing, and whether the unpaid admin has quietly started eating half of every week without ever being the thing you meant to spend it on.

TimeMap treats an unpaid afternoon chasing an invoice the same way it treats a paid one finishing a deliverable — one line, one colour, filed by what actually happened rather than by whether anyone was billed for it. Line up a quiet stretch against a busy one and the shape of the work becomes visible in a way no single invoice ever shows you.

None of this needs to happen at the end of a long day. A sentence when something changes — a reply came in, a quote went unanswered, today was mostly the unpaid kind of work — is enough to keep a freelance year from collapsing into "busy" and "slow" with nothing in between.