Why time data goes bad#
Every service business runs on tracked time — it prices the work, proves the retainer, and feeds every profitability number you will ever look at. And in most shops the data is reconstructed on Friday afternoon from memory, calendar archaeology, and guilt. Friday-reconstructed time is fiction with decimals.
The root cause is friction-at-the-moment: the work happens in a task, a ticket, or a meeting, and the time entry lives somewhere else. Every context switch between "doing" and "logging" is a chance to skip it, and people take that chance dozens of times a week.
Rule one: log where the work is#
The timer belongs on the task card. The quick-entry belongs in the ticket, the activity row, the meeting record — a date, a duration, a note, three fields, done in seconds without opening anything. If logging time requires navigating to a timesheet module, you have designed for Friday fiction.
- Start/stop timers on the thing being worked, not in a separate app
- A quick "add time entry" on every work surface — tasks, tickets, activities
- Meetings one click from your calendar: the client is suggested and the length pre-filled
Rule two: the weekly ritual beats daily nagging#
Daily completeness nags train people to resent the system. What works is a weekly rhythm with a real gate: the week's timesheet gets reviewed and submitted once, and someone approves it. Decide whether billing waits for that approval: if it does, approval has to mean something; if it does not, the weekly submit still gives you a clean point to review. People will spend ten minutes on Friday tidying a week that is 90% captured; they will not spend an hour reconstructing one that is 0% captured. The in-the-moment logging makes the ritual short; the ritual catches what logging missed.
Rule three: billable time flows untouched#
The payoff for the discipline is that nobody ever re-keys time. Billable hours become work-in-progress — as soon as they are logged, or once approved, depending on how you bill each client — and work-in-progress becomes invoice lines. And the same entries — priced at each person's cost rate rather than their billing rate — are the labour side of client profitability, read straight from the time rather than from the invoice. If any of those steps involves an export, a spreadsheet, or "let me just adjust this," the chain is broken and the numbers downstream are decorative.
This is also the honest answer to "why do we track time at all" — not surveillance, but the price of every downstream number being real: the effective hourly rate on that retainer, the margin on that client, the utilization picture that says whether you can take the next project.
What not to do#
Do not demand 8.0 hours of logged time per person per day — you will get exactly 8.0 hours of creative writing. Do not make people categorize to three decimal places; billable or not, against the right work item, is enough. And do not weaponize the data in reviews the first month it exists, or the second month it will not exist.
Takeaways#
- Friday-reconstructed time is fiction with decimals — friction at the moment of work is the enemy.
- Put timers and quick-entry on the work itself: tasks, tickets, activities, meetings.
- A weekly submit-and-approve ritual beats daily completeness nagging.
- Billable time should reach invoices and profitability untouched — no exports, no re-keying.
- Demand honesty, not 8.0 hours a day; weaponized time data stops existing.