The two-hour job gets remembered.

The twelve-minute job does not.

That is not because the small job was less real.

It is because it never felt important enough to become an event.

Big work creates its own memory

Large tasks usually have structure around them.

You plan them.

You block time.

You create a task.

You deliver something obvious.

There are several chances to remember that the work happened.

Small jobs can appear and disappear inside the same conversation.

“Quick” work has weak boundaries

A client writes:

Can you just update the number on that page?

You open the site, make the change, notice another issue, fix that too, reply and return to your original work.

Nothing in that sequence necessarily triggers your normal tracking routine.

The task was too small to feel like a session.

That is precisely why it is easy to lose.

One tiny request is not interesting.

Six of them are.

A client who looks easy in your memory may actually consume a steady stream of short interruptions.

You only see that pattern if the small work is visible somewhere.

You can still decide not to invoice the time.

Maybe that kind of support is included.

Maybe the relationship is valuable enough that you are happy to absorb it.

The record simply gives you the choice.

Without it, the choice has already been made for you.

The solution does not need to be a timer for every ten-minute task.

It can be as simple as making sure the work leaves a trace you can review later.

Small tasks are not hard to bill because they are small.

They are hard to bill because they are easy to forget.