I am very good at doing the work.

I am considerably worse at remembering to write down that I did it.

That seems to be a fairly common freelance problem.

You start the day with something sensible in front of you. Then a client emails. Another one calls. You fix something because it will “only take five minutes”. A meeting runs over. You go back to the original task and eventually finish it.

At some point, somebody expects a timesheet.

That is where things get interesting.

The timer is rarely the difficult part

Starting a timer is not complicated.

Neither is typing `45 minutes` into a form.

The difficult part is remembering to do either of those things while you are concentrating on something else.

Time tracking asks for attention at exactly the moment you would rather give that attention to the work.

If you are about to spend three hours on one clearly defined project, that is manageable.

If your day contains 17 small changes of context, it becomes much easier to miss one.

Freelance work has terrible boundaries

A lot of work does not announce itself properly.

There is no little bell that rings and says:

A new billable activity has now begun.

Instead, a client sends:

Quick question...

You answer it.

Then you check something.

Then you make a small change while you are there.

Twenty-five minutes later, you are back on the thing you were doing before.

Was that a separate piece of work?

Probably.

Did you start a timer?

Possibly not.

This is one reason small jobs are so easy to lose. They do not feel like sessions. They just happen in the gaps.

“I’ll remember it later” is an excellent short-term strategy

At 11:20, remembering the last two hours feels easy.

At 16:45, there are already a few fuzzy bits.

Three days later, you are looking at your calendar, sent emails and browser history like an amateur detective.

You can often reconstruct the broad outline.

The dangerous part is the small work.

The report you spent two hours on is obvious.

The 20-minute revision between two meetings is much easier to forget.

So is the client call that was not in the calendar.

And the task you completed so quickly that it never felt important enough to record.

The work is already scattered across other tools

Very little freelance work actually happens inside a time tracker.

The actual work happens elsewhere.

Tasks live in a task manager.

Meetings live in a calendar.

Communication lives in email and chat.

Documents live somewhere else again.

The time tracker sits beside all of this waiting for you to translate the day into a separate record.

That translation is where things get lost.

It is not necessarily a discipline problem.

Sometimes the workflow simply asks you to duplicate information that already exists in another form.

A timer works beautifully right up until it does not

I do not dislike timers because they are bad at measuring time.

They are excellent at measuring time.

I dislike the part where I have to remember them.

The classic failure modes are familiar:

forget to start it
start it late
forget to stop it
leave it running through lunch
realise it is still attached to the previous client
decide you will fix it later
do not fix it later

This does not mean timers are useless.

For long, focused work, they can be perfect.

The problem is expecting one habit to survive every kind of freelance day.

Small client tasks do not look expensive

A ten-minute job does not feel significant.

Neither does a fifteen-minute call.

That is why they are easy to give away accidentally.

One small forgotten task is probably irrelevant.

A month full of them is not.

The funny thing is that freelancers often spend a lot of energy negotiating rates and almost no energy noticing the work that never reaches an invoice.

A forgotten billable task is, in effect, a tiny discount you did not mean to give.

Fixed-price work does not make the problem disappear

If you do not bill by the hour, it is tempting to decide that none of this matters.

Sometimes that is true.

But if you quote a project at a fixed price, knowing whether it took 12 hours or 30 is useful information.

The client may not care.

You probably should.

Otherwise, a project can feel profitable simply because you never measured how much of your week it consumed.

Time tracking is not only about invoices.

Sometimes it is about finding out whether the price you charged made any sense.

The perfect system is usually another procrastination project

There is a dangerous point where trying to improve time tracking becomes its own hobby.

You design categories.

Create naming rules.

Set up dashboards.

Add automations.

Spend Sunday afternoon building the perfect freelance operating system.

Then on Tuesday you forget to start the timer.

A useful system should survive ordinary behaviour.

It should still work when you are busy, distracted and not particularly interested in maintaining your system.

That is a much higher bar than looking good in a Notion template.

Better memory is probably not the answer

The obvious solution is:

Just remember to track your time.

Excellent.

While we are at it, remember every password, never miss a deadline and always bring a reusable bag to the supermarket.

A better approach is to reduce how much remembering the process requires.

That might mean logging time at the end of each day.

It might mean using a timer only for work where timers genuinely fit.

It might mean reviewing completed tasks and calendar meetings instead of trying to recreate the week from nothing.

The exact method matters less than moving some of the burden away from your head.

Your calendar knows more than you think

A calendar is not a timesheet.

But it is very good at remembering meetings.

If Tuesday contains:

`10:00–10:45 Acme status call`

you already have a useful piece of information.

You do not need to remember that the meeting existed.

You mainly need to decide whether it belongs in your time record and whether the scheduled duration reflects what actually happened.

The same principle applies to tasks.

A completed task does not tell you everything about the time involved, but it is a much better starting point than:

What did I do last Wednesday?

This is why I built Tidst

My own work is spread across tasks, calendar events, calls and the usual interruptions.

I never had a problem understanding why time tracking mattered.

I had a problem wanting to interact with a time tracker all day.

So Tidst started with a fairly simple thought:

The work already leaves clues.

Maybe the timesheet should use them.

Tidst is built around reviewing work after it happened rather than assuming every piece of work begins with a timer.

It does not magically know about everything you did, and it should not pretend to.

The point is simply to give you a better place to start than your memory.

The goal is not perfect time tracking

Perfect time tracking sounds exhausting.

A useful record is usually enough.

Enough to invoice accurately.

Enough to explain the work to a client.

Enough to notice when a fixed-price project is eating the week.

Enough to stop giving away all the little jobs because they were too small to remember individually.

If your current system already does that, keep it.

If Friday afternoon regularly turns into a reconstruction of the previous five days, the problem may not be you.

Your time tracker may simply be asking the wrong question at the wrong time.

Do the work first.

Remember the time before it disappears.

That is probably enough.

See how Tidst works →

[Time tracking for freelancers](/time-tracking-for-freelancers)
[Timer vs automatic vs task-based time tracking](/automatic-vs-manual-time-tracking)
[How Tidst works](/how-it-works)

Why freelancers are so bad at tracking time