How to track what interrupts your deep work
A timer only tells you how long you sat there. Two 90-minute sessions can both show 90 minutes on the clock while one had no interruptions and the other had eight — and the work that came out of them is completely different. This tool turns a vague feeling ("I keep getting interrupted") into a named pattern with a cost attached.
When you run a session here, your browser:
- Runs a live focus timer — name one task, pick a block length (25 to 120 minutes), and start. The timer keeps running past the planned length; the plan is a target, not a cut-off. Pause stops the clock; abandon ends the session without counting it as completed.
- Logs every interruption in one tap — what it was (message, email, call, colleague, meeting overrun, notification, drifting off, noise), where it came from, and how long it lasted. Logging does not stop the timer; the length is recorded as lost time.
- Reports what it cost — interruption count and rate per hour, total lost minutes, an estimated refocus cost (~23 minutes per interruption, the research average, clearly labelled as an estimate), the longest unbroken stretch, a focus score from 0 to 100, the top sources, and practical fixes aimed at the top source first.
- Keeps the history — finished sessions are saved in this browser (up to 50), with totals, average score and top source across all of them, and a CSV export for your own records.
What makes this tracker different
The pages and apps that top the results for this search are mostly installs — an Android timer, a Chrome extension that emails you summaries, an iPad-only app with a paid tier, a Mac-only timer whose history is paywalled — or paid team software that watches employees, or a printable worksheet, or a guide that recommends a paper tally. This page is the only free, no-install, no-account, fully client-side tracker we found that does all four: a live timer, one-tap interruption logging with type and source, a costed report with a focus score and fixes, and history with CSV export — with a live network-request counter so you can verify the privacy claim yourself. It runs entirely in your browser — there is no server to upload to.
When is tracking the right choice — and when is it the wrong one?
Tracking is right when interruptions feel constant but vague: you finish the day tired with little to show for it, and you cannot say what took the time. A week of logged sessions names the pattern — usually one source doing most of the damage — and one fix aimed at it. It is the wrong choice as a surveillance tool: it only logs what you choose to log, it cannot watch anyone else, and a low score is information about the session, not a verdict on you.
Honest limitations
Refocus time is estimated, not measured
The ~23-minute figure is a research average. Your real refocus time varies — shorter for a glance at a message, longer for a deep context switch. Only the lost minutes are measured.
Forgotten interruptions leave no trace
The timer cannot see interruptions away from the keyboard or ones you forget to log. Keep the page visible and log the moment you return to the task.
It cannot block distractions
This tool measures interruptions so you can fix them. It does not silence your phone, block sites, or close your inbox — those fixes are yours to apply.
The score is a heuristic
It measures how broken the session was, not how good the work was. A low score on a hard day is information, not a failure.
History lives in one browser
Sessions are stored in this browser's local storage only. Clearing browser data, or switching devices, starts the history over — export the CSV if the record matters.
One task per session
The tool is built around a single named task. If your work genuinely switches tasks every few minutes, that is a different problem — task-switching, not interruption — and the log will show it as noise.