
How to run a team time audit that leads to a useful change
The point of a time audit is to change a decision. Start with a question, keep the categories clean, and measure whether the resulting change helped.
Getting people to track time without making the place miserable.

The point of a time audit is to change a decision. Start with a question, keep the categories clean, and measure whether the resulting change helped.
Every one of these is genuinely useful and every one of them regularly produces the wrong decision. What each actually measures, and what to read alongside it.
One page, eight decisions. Most agencies have none of this written down, which is why their billable percentage measures interpretation rather than work.

Nobody is lying. Human recall of a working day decays within hours, and every agency's data quietly reflects that. What to change so the numbers describe the week that happened.

Approvals exist to protect the invoice, not to police the team. The difference shows up in what the approver is actually looking at.

The four arguments every agency has about what counts as billable, why the answers matter less than the consistency, and what a healthy non-billable split looks like.

Most time tracking advice assumes the problem is discipline. It usually is not — it is that the system asks for more precision than the work can supply.
The first ninety days decide whether you get useful data or a compliance exercise. A practical sequence, and the three mistakes that poison it on day one.

Several tools in this category will photograph your team's screens every ten minutes. We have decided not to build that, and it is worth saying why rather than leaving it as a gap in a feature list.
Utilization, effective hourly rate and project margin, straight out of tracked time.
Request an invite