Billable, non-billable, and the line between them
Every entry is one of three things: billable work you have not invoiced, work you have already billed, or non-billable time you track for your own awareness. The trouble starts when those states live only in your head. You lose track of what is invoiced, you double-bill by accident, or you forget a call entirely.
The fix is to make the state explicit on every entry and impossible to misread. A clear billable marker, a clear billed marker, and a running total of unbilled value does more for your income than any productivity report.
Capturing the short calls
The hours you lose are almost never the long, obvious ones. They are the 10-minute answer, the quick architecture call, the check-in between meetings. They are easy to skip because logging them feels like more effort than they are worth. That instinct is wrong, and it is expensive.
Two habits fix it:
- Log immediately. The path from finishing a call to logging it should be a few seconds, before the next thing pulls your attention. A keyboard shortcut beats opening an app and hunting for a button.
- Bill at your minimum. A short call is not worth its raw minutes. Apply a per-call minimum so a quick call reflects the context switch and the prep around it, automatically.
Seeing unbilled value clearly
The single most useful number for a consultant is not hours worked. It is unbilled, billable value: the money you have earned but not yet sent an invoice for. When that number is always in view, invoicing stops being a monthly archaeology project and becomes a glance. You know what is outstanding, and you know when it is time to bill.
Why this does not need a timesheet suite
Tracking billable hours well does not require accounting software, approvals workflows, or a per-seat subscription built for teams. It requires fast capture, honest billable states, your billing rules applied automatically, and a clean way to show a client the time. That is the whole job, and it is what Billog is built to do. If you want to see how it compares to the heavier tools, the comparison pages lay it out capability by capability.