I stopped logging my time. The evidence does it now.
Every consultant hates timesheets, and every consultant leaks billable hours to bad memory. This system reconstructs the workday from evidence the tools already emit, and a human approves every entry before it becomes money.
Time tracking has a dirty secret: nobody actually does it in the moment. You reconstruct it at 5 p.m., or worse, at invoice time, from memory, and memory is generous to whatever happened most recently. For anyone billing across multiple clients and entities, that reconstruction is both a daily tax and a slow leak of real money.
So I stopped doing it. Not the billing, the logging. My workday already leaves a thick evidence trail: AI coding sessions on two machines, git commits, sent email, calendar events, messages, meeting recordings. The system reads all of it and reconstructs the day for me.
What the system does
Every evening, a scheduled job collects the day's evidence and normalizes it into a timeline. To date it has mined more than 400 work sessions, over 21,000 individual tool actions, and thousands of files touched, and distilled them into around 1,900 normalized evidence events. It clusters those events into activity blocks, matches blocks to clients and projects, and drafts time entries.
Drafts. Not entries. The next morning I review the reconstruction, adjust anything it got wrong, and confirm. Only then does anything touch a ledger.
The guardrails
- The math cannot inflate. Overlapping evidence is merged with interval arithmetic, so the total attributed time can never exceed the actual wall-clock span. The guarantee is structural, not a prompt instruction.
- Weak evidence never drafts money. A keyword match alone can suggest context, but it cannot produce a billable draft. Only substantial evidence classes can.
- Separate businesses never mix. Entries for different entities live in different ledgers with different rules, and the automated side cannot write to either. All ledger writes happen in the human review step.
- Billable is decided by agreement, not activity. Time on a flat-fee client defaults to unbillable. The system does not get to promote work into revenue.
What happened
- The daily reconstruction ritual, roughly fifteen minutes of guessing, became a two-minute review of a draft that is usually right.
- Invoice-time archaeology disappeared. The entries were confirmed the morning after the work happened, when memory was still honest.
- The build paid for itself in the first quarter: the ongoing time saved is roughly double what the system cost to build, and it keeps paying every week.
What this means for your business
If your billing depends on humans remembering what they did, you are losing hours you already worked. The pattern here generalizes to any professional-services shop: your tools already know what happened all day. The engineering problem is not capturing the evidence, it is building the guardrails so reconstruction can never quietly become invention.
Details are generalized to protect client confidentiality. The numbers are real. If your team bills time and hates logging it, start with a roadmap session.
