The day keeps changing shape

You begin a task for Client A.

Client B calls.

You answer a quick question from Client C.

You return to Client A.

Then the task becomes blocked, so you switch to something else while you wait.

A timer can still handle this, technically.

You can stop, switch, restart and correct entries as often as needed.

The question is whether you actually will.

Timers are strongest when boundaries are clear

For a two-hour writing session, a timer is excellent.

For a workshop, same thing.

For development, design or research in long blocks, starting a timer may feel completely natural.

The trouble begins with fragmented work.

Small tasks have weak beginnings and endings.

They sneak into the day instead of arriving as planned sessions.

A tool can be simple and still depend on behaviour that does not fit you.

If you repeatedly forget to start a timer, the obvious answer is not always to become more disciplined.

Maybe the timer is simply not the best first step for that kind of work.

You can still use it where it fits.

The rest can be recorded another way.

A completed task tells you something happened.

A calendar meeting tells you when something was scheduled.

A sent deliverable, note or message can provide context too.

None of these are perfect substitutes for a running timer.

They solve a different problem: remembering the work well enough to record it afterwards.

The sensible position is not “timers are bad”.

It is “timers are one method”.

Use them for the work that suits them.

Use other evidence for the work that does not.

A flexible record is often more realistic than pretending every freelance day can be chopped cleanly into stopwatch-shaped pieces.