Should you track internal time, or just client work?
We used to ask everyone to track their whole day, internal work included, and it slowly wore people down. So we made a deliberate call: track client work well, and stop trying to account for everything else. The result was better client records and a habit people actually kept, because the tracking finally had a clear point behind it. We did lose some visibility into where internal time went, and that trade was worth it for us. If you are wondering whether to force full tracking, our answer is to track what you bill by default and reach for internal tracking only when you have a real question it will answer.
Why we stopped trying to track everything
We stopped because tracking everything asked for constant effort and gave almost nothing back for most of it. The majority of a day is not billable - internal projects, admin, planning, the small maintenance that keeps things running - and logging all of it meant a lot of dutiful data entry attached to no invoice. That imbalance is quietly corrosive, because the habit starts to feel like pure overhead, and overhead is the first thing people drop when they are busy.
It also blurred the thing that mattered. When every kind of work went into the same stream, the billable hours we actually cared about got harder to pick out, buried among internal entries that were there for completeness rather than use. We were spending effort to make the important signal harder to read, which is close to backwards.
The deeper issue was motivation. People track willingly when the tracking obviously helps them, and they resist when it feels like surveillance or box-ticking. Asking for a full account of the day tipped it toward the second feeling, and no amount of reminding fixes a habit that people quietly resent. Narrowing the ask was as much about buy-in as about data.
What tracking only client work fixed for us
Narrowing to client work fixed adoption first. Once tracking was clearly tied to getting paid, the reason to do it was obvious, and people kept it up without nagging. A lighter, clearer ask is one people actually sustain, and consistency is worth more than completeness - a billable record everyone maintains beats a full record half the team abandons.
It also made the client records sharper. With effort concentrated on billable work, those entries got more accurate and more complete, which is exactly where accuracy pays off. Reviewing time before an invoice got easier because there was less noise to wade through, and keeping the billed and unbilled hours organized was far simpler when the stream was only work that could be billed in the first place.
And it made billing cleaner end to end. Because everything tracked was client work, tagged to a client and a billable status, the path from tracked time to invoices had no internal entries to filter out first. That is also what to look for in time tracking software for client work - a setup that treats billable status as first-class rather than something you sort out later.
What we gave up by skipping internal time
The honest cost was visibility into where non-billable time went. We could not answer, at a glance, how many hours a month went into internal projects, admin, or a recurring process, because we were no longer capturing it. For a team that wants tight utilization numbers - billable versus total hours across everyone - that gap is real, and pretending otherwise would be dishonest.
We also lost some ability to make internal work visible as work. Untracked time can look like nothing is happening, even when the internal work is genuinely valuable, and that can matter for planning or for justifying where a week actually went. If you need to defend or optimize internal effort, not tracking it leaves you without the evidence to do so.
For us those costs were acceptable, because we did not have live questions that needed the data, and a habit people keep beat a complete dataset nobody maintains. But it is a real trade, not a free lunch, and the right call depends entirely on whether those blind spots would actually cost you a decision. Naming the downside is part of making the choice honestly.
Where we drew the line on what to track
The line we settled on was simple: if a client would be billed for it, or it exists because of a client, track it - otherwise leave it. Client calls, revisions, and setup for a specific client are in, general admin and internal projects are out unless we have a reason. A one-sentence rule matters here, because a rule people can hold in their head is one they can actually follow without deliberating over every entry.
The point was to avoid re-creating the every-task burden under a new name. It would have been easy to slide from "track client work" into "track client work in exhaustive detail," which is its own trap - we learned the hard way that chasing total precision backfires, which is the whole story of when we tried tracking every minute. So the line was not just billable versus internal, it was also useful versus fussy, on both sides of that split.
Getting the structure right underneath helped the line hold. Because entries were tied to a client from the start, they rolled up cleanly at billing without reshuffling, which is the same benefit we describe in our take on reviewing time by client. A clear line plus clean grouping meant the narrowed tracking stayed both light and genuinely useful.
Who should track internal time too, and who should not
Track internal time if you have a specific question it will answer. Whether internal projects are eating into billable capacity, how much a recurring process really costs, or where a team's non-billable hours actually go are all legitimate reasons, and for those you should absolutely capture the data. But do it as a deliberate measurement for a defined stretch, answer the question, and then decide whether the ongoing cost is worth keeping.
Skip permanent internal tracking if you have no live question and mainly need accurate billing, which describes a lot of freelancers and small teams. In that situation full tracking is effort spent producing data you will not use, and the effort is exactly what erodes the habit you actually care about. There is no virtue in tracking hours nobody will ever look at.
The general principle is to let purpose drive tracking, not completeness. Track what you will act on, whether that is billable work, an internal question, or both for a while, and resist the instinct that a full record is inherently better. A focused record you use beats a complete one you maintain out of guilt, every time.
So should you track internal time?
Our take is to track client work by default and treat internal tracking as a tool you pick up for a specific job. Narrowing to billable work gave us sharper client records and a habit people kept, at the cost of some visibility into internal time that we did not actually need. When the payoff is clear, people track, and client work is where the payoff is clearest.
If you are deciding, start by asking what question full tracking would answer for you right now. If you have one, track internal time deliberately until it is answered, and if you do not, keep the tracking focused on what you bill. Let a real question, not a sense that more data must be better, be the thing that expands what you track.