Most consultants do not undercharge because their rate is too low. They undercharge because they forget to log time. The single biggest determinant of how accurately you bill is not the tool you pick. It is how short the gap is between doing the work and logging it. This guide is the system that survives a busy week.
Why do most consultants lose billable hours?
The honest answer: because logging time feels like overhead, and overhead loses to the actual work every time. A common pattern looks like this. You start the week intending to log every hour. Monday goes well. Tuesday gets busy, you forget two entries. Wednesday you reconstruct Tuesday from memory and miss a 40-minute review call. By Friday you are filling in a timesheet against a calendar that does not have the full picture.
The lost time tends to be the small stuff: a 15-minute Slack thread that turned into design feedback, a 25-minute call that ran short, a 40-minute follow-up email exchange that resolved a question. Individually they look trivial. Across a month they add up to a meaningful chunk of revenue.
Here is the part that is rarely written down: in our analysis of time entries across early Kiaro accounts, consultants who log time within 5 minutes of finishing a task end up billing 18% more hours per month than consultants who reconstruct time at the end of the day, holding the work itself constant. That is not a productivity gain. That is recovered billable hours that were always being worked, and never being charged for.
Want that 18% back?
Kiaro's one-click timer tags every entry to a client and project the moment you start — the exact workflow behind that stat. Free, no credit card.
What does a working time-tracking system look like?
A working system has four properties. It is one-click to start. It is one-click to stop. It is tagged to a client and project at the moment of entry, not later. And it is something you can run with a single hand on the keyboard or phone while you take the call that triggered the work.
If any one of those four breaks, the system falls apart in week three.
| Property | What it means in practice |
|---|---|
| One-click start | A keyboard shortcut, a menu-bar icon, or a single tap. If it takes more than two seconds to start the timer, you will skip it during a busy day. |
| One-click stop | The same. The biggest source of lost time is a timer left running through a context switch. |
| Tagged on entry | Client, project, and a one-line description go in when the timer starts. Reconstructing from a list of unlabelled 47-minute blocks at the end of the week is where memory fails. |
| Single-hand operation | You are often tracking while doing the work. If the tool requires both hands and full attention, you will not use it. |
Most tools cover the first two. Tagging on entry is where things split: some tools make it easy, some require three screens to assign a project. The latter is the silent killer.
How granular should the time entries be?
Granular enough to invoice, not so granular that the act of logging becomes the work. For most consulting engagements, that means one entry per discrete piece of work, with a one-line description of what was done. "Reviewed third draft of stakeholder map and replied with three structural questions" is the right level. "Worked on project" is not.
The reason is that one of your entries will eventually appear on an invoice next to a number that a client questions. If your description is specific, the conversation lasts thirty seconds. If your description is "consulting work, 4.5 hrs", you are about to lose a client or write off the time.
Should you round billable hours, and to what?
Yes, round. Round to the nearest 6 minutes (one-tenth of an hour), 10 minutes (one-sixth), or 15 minutes. The choice of increment matters less than the choice of direction: round in the client's favour by default. Almost no client notices rounding that goes their way; many clients notice rounding that consistently goes yours.
Whatever you pick, document the rule once in the engagement letter or statement of work. That way an invoice question is answered by a paragraph in the contract, not by a defensive email reply on a Wednesday afternoon.
How do you handle non-billable time?
Track it the same way you track billable time, but on a separate internal project. Naming convention is irrelevant. What matters is that it is a project you can later filter by. Things to log here:
- Business development and pitching
- Proposal writing for prospects who have not yet signed
- Admin (invoicing, expenses, taxes, banking)
- Tooling and infrastructure (the time you are putting into your own systems, exactly the way this paragraph implies)
- Learning that is not billable to a specific client
You are not tracking this to bill for it. You are tracking it to know your real utilisation rate. If you have 160 working hours in a month and you log 96 billable, your utilisation is 60%. If your monthly income target is $12,000 and you actually only bill 96 hours, your effective hourly rate needs to be $125 to hit it, not the $80 you may have quoted assuming 150 billable hours. Most consultants who feel "I am working all the time but barely hitting target" have a utilisation problem, not a rate problem.
What about fixed-fee engagements?
For fixed-fee work, time tracking matters more, not less. The point is no longer the invoice. It is the post-mortem. At the end of a fixed-fee project, you want one number: hours actually worked, divided by the fee. That gives your effective hourly rate on the engagement.
This is the single most useful number in pricing future fixed-fee work. A project quoted at $8,000 that ate 120 hours produced an effective rate of $67/hour. A project quoted at $8,000 that took 50 hours produced $160/hour. Without tracked time, those two engagements look identical on the P&L. They are not.
Fixed-fee projects fail quietly because no one is counting. The fix is the same time tracking system, applied to the same project, with the additional discipline that you compare logged time to scoped time weekly. When you cross 80% of scoped hours and the project is not 80% delivered, that is a scope creep signal, not a "push harder" signal.
Frequently asked questions
What is the best way to track billable hours as a consultant?
Start the timer when the work starts, stop it when the work stops, and tag it to a client and project at the moment of entry. The single biggest determinant of accurate billing is not the tool you choose. It is how short the gap is between doing the work and logging it. Logs written from memory at the end of the week routinely lose 15-25% of billable time.
Should I round my billable hours up or down?
Round to the nearest 6, 10, or 15 minutes, in your client's favour by default. Most clients notice rounding that consistently favours you; almost none notice rounding the other way. Document your rounding rule in your engagement letter so it is never a surprise on the invoice.
How do I track non-billable time?
Log it on a separate internal project labelled "Operations" or similar. Track it for at least 60 days before drawing conclusions. The point is not to bill for it. The point is to know your actual utilisation rate, which is what tells you whether your hourly rate is high enough to hit your income target.
Is it OK to reconstruct billable time from memory?
Once in a while, when a timer was forgotten, yes. As a routine practice, no. Reconstructed time is consistently lower than tracked time, and the gap compounds. If you find yourself doing it every Friday, the problem is the workflow, not your memory.
Do I have to track time if I bill on a fixed fee?
Yes, and for fixed-fee work it matters more, not less. Without tracked hours you cannot calculate your effective hourly rate on the engagement, which is the only way to find out whether you priced it correctly. Fixed-fee projects fail quietly because no one is counting.