Calendar shows a full day on site with SummitCare operations. Two mail threads and four hours of deck activity on the same matter. No entry against any of it.
Nobody starts a timer.
The week is already written.
Ambient time tracking across calendar, mail, desktop and browser. Hours flow in from where the work already happens, written in each professional's own voice — so labour cost never lags the work.
What it read
- Outlook calendar 09:00 – 11:30 Gridline CFO — integration scope review Accepted, attended, five attendees from the client side.2.50h
- Outlook mail 11:40 – 12:05 3 threads · RE: revised cutover date Same matter, same counterparties, inside the engagement.0.40h
- Excel · desktop 13:15 – 14:35 Gridline_Budget_v4.xlsx Active editing, not idle. Matched to the engagement folder.1.30h
- Jira · browser 15:10 – 15:28 GRD-412 · Re-baseline reporting workstream Ticket linked to the Phase I workstream.0.30h
Attributed to one engagement 4.50h
The entry it drafted
The problem
Why this goes wrong today.
- 01 The week is reconstructed on Friday
Nobody remembers Tuesday afternoon. The entry that gets written is the one that is easy to write, not the one that happened.
- 02 The gap is never small
Work that goes uncaptured is not evenly distributed. It concentrates in the senior people whose hours are worth the most.
- 03 Chasing it costs more than the time
A delivery lead spends Monday asking eight people for last week, and still submits the timesheet incomplete.
How it works
What it actually does.
- 01 Watch the work, not the clock Capture runs across calendar, mail, tickets, desktop applications and browser tabs. Nobody starts a timer.
- 02 Attribute to the engagement Each block of activity is matched to a project, workstream and task type using the same rules your delivery leads already set.
- 03 Draft in their voice Narratives are written from the professional’s own prior entries, so the language reads like theirs and not like a machine’s.
- 04 They confirm; they don’t compose The day arrives already written. Confirming a drafted week takes minutes instead of the Friday afternoon everyone loses.
When a day goes missing
It found the gap, and stopped.
Thursday was booked and attended, but never logged
Miles had a full-day SummitCare workshop on the calendar. Mail and desktop activity agree it happened. Nothing is logged against it, and he has logged every other day this week.
Inputs and outputs
What it reads, and what it does.
- Calendar events and mail metadata
- Desktop and browser activity, where opted in
- Ticket and issue systems connected to the engagement
- Your project, workstream and task-type structure
- Which engagement it belongs to
- Whether it is billable
- How this person writes
- Drafts the entry in their voice
- Nudges when a day is missing
- Waits for their confirmation
Activity it cannot confidently attribute. Rather than inventing a billable narrative for work it did not do, it leaves the block unattributed and asks the person who did it.
Next step
See it run against one of your live engagements.
Bring an engagement that worried you. We will show you where the margin went, and the week Octayne would have told you.