Guide

Who actually needs time tracking?

Anybody whose income depends on hours, and anybody who wants to know whether a fixed price was a good one. Those are two different reasons and they need different amounts of effort. If you bill by the hour or the day, tracking time is not optional, it is your invoice. If you bill fixed prices, tracking time is how you find out whether the last quote was generous or ruinous, which is the only way the next quote gets better. If neither is true, you can skip it, and plenty of people should.

The three reasons to track time

People conflate these constantly, and then buy a tool that solves the wrong one.

  • To bill. The hours are the invoice. Accuracy matters to the minute because somebody is paying for them.
  • To learn. You want to know what the work really cost so the next quote is not a guess. Accuracy to the half hour is plenty.
  • To prove. A client disputes the scope, or an agency wants a breakdown before it releases payment. What matters here is not precision but a record made at the time, not reconstructed afterwards.

Why "I will remember" costs you money

You will not remember, and the loss is not random. It is biased in one direction.

What you forget is the twenty minutes on the phone, the half hour reading the brief again, the email exchange on Sunday, the call that ran over. What you remember is the block of real work you sat down and did. Reconstruct a week from memory and you will consistently come out low, because the memorable hours are the ones you were paid for anyway.

For an hourly worker that is money handed back. For somebody on a fixed price it is worse, because the number you use to price the next job is quietly wrong in a direction that makes you underquote forever.

The fix is not discipline, it is proximity. Time recorded at the end of the day is roughly right. Time recorded at the end of the week is fiction with good intentions.

What to record, and what not to bother with

The most common mistake is tracking too finely, which produces a system nobody keeps up for more than three weeks.

Record the project, the date, the duration and a short line about what you did. That last part is the one people drop, and it is the one that saves you when a client asks what the eleven hours in week three went on.

Do not record which application you had open, do not chase billing to the minute if you invoice in quarter hours anyway, and do not build a task hierarchy four levels deep before you know what you actually want to compare.

  • Worth it: project, date, duration, one sentence of description, billable or not.
  • Worth it if you have staff: who did it, because that is what turns hours into cost.
  • Usually not worth it: task-level breakdowns, sub-tasks, tags you will never filter by.
  • Never worth it: anything that watches your screen. It changes how people work and it produces data nobody trusts.

Turning hours into an invoice without retyping

This is where most setups leak. The hours live in one tool and the invoice is written in another, so at the end of the month somebody adds up a column and types the total into a line item.

That step is worth naming because it is where the errors are. Not big errors, mostly. A week attributed to the wrong project, a rate from the previous contract, a total that was right before you added the last two days. Small, unglamorous, and each one either costs you money or costs you a conversation.

If the hours and the invoice live in the same place, the step disappears entirely. In Steerd, logged time carries its project and its rate, and an invoice is built from the entries rather than from a number you carried across.

The number worth watching: unbilled hours

One view is worth more than any report: the hours you have worked and not yet invoiced.

It answers a question you probably ask yourself in a vague way every few weeks, which is how much money is currently sitting in the gap between doing the work and asking for it. For most people that number is larger than they expect and older than they expect, and looking at it once tends to be enough to change the billing rhythm permanently.

Steerd has that as a view rather than something you assemble. Alongside it there is a week grid by project and a month view, and time can go straight onto an invoice. What it does not do is run a stopwatch or watch your screen, which is deliberate.

When not to bother

If you sell products rather than time, if you are on a retainer that never gets questioned, or if you genuinely do one thing all day for one client, tracking hours is admin with no payoff. Do not let a tool convince you otherwise.

The moment it becomes worth it is usually the second client. Two projects in the same week is the point where "I will remember" stops being true, and it is also the first time the question "which of these two is actually paying better" has an answer worth having. Working that out properly needs the hours.

Questions people ask

Should I track time if I charge fixed prices?

Yes, but loosely. You are not producing evidence for a client, you are producing evidence for yourself about whether the price was right. Half-hour accuracy and a note about what you did is enough, and it is the only thing that stops you quoting the same optimistic number for years.

Do I need a timer?

Most people do not. Timers work for anybody who switches context constantly, and they are a nuisance for anybody who works in long blocks and forgets to start them. Entering the day at the end of the day is more reliable for most kinds of work.

How detailed should a time entry be?

Detailed enough that you can defend it in three months, which is roughly one honest sentence. "Client call and revisions to section 4" is useful. "Work" is not, and neither is a four-level task tree.

Is billable time the same as working time?

No, and it matters. Billable project time is what a client pays for. A working-time record is a labor-law obligation for employees and covers hours, breaks and rest periods. Steerd records billable project time. It is not a working-time record and does not try to be. If you employ people, that is a separate obligation and separate software.

What counts as billable?

Whatever you agreed, which is why agreeing it matters. Calls, briefings and revisions are the usual gray areas. Decide before the project starts, write it in the proposal, and record the hours either way so that at least you know what the unbillable work cost you.

Hours that already know which invoice they belong on.

Log time against the project, see what is still unbilled, and turn it into an invoice without adding up a single column.

30 days full features · No credit card