Deep Work Interruption Tracker: find what breaks your focus.

Run a focus session, tap to log every interruption — what it was, where it came from, how long it lasted — and get a report: lost minutes, estimated refocus cost, focus score and the fixes that matter.

  • Your session data never leaves the device
  • Live timer + one-tap interruption log
  • Focus score + top sources + fixes
  • History across sessions + CSV export

Start a focus session

Name a single task — a named task is easier to return to after an interruption.

The timer keeps running past the planned length — the plan is a target, not a cut-off.

Live timer, one-tap interruption logging and a costed session report — all in your browser. Nothing is uploaded.

00:00:00

No session running yet.

Pick a task and a block length, then press Start focus session.

Log an interruption

Or type an exact length below (minutes).

Logging does not stop the timer — the interruption's length is recorded as lost time. Log the moment you return to the task, while you still remember it.

Interruptions this session

None logged yet. A clean session is the goal — but an honest log beats a tidy one.

    No session yet. Everything stays on this device. A sample session is available below if you want to see a report first.

    Privacy you can verify, not just trust

    Most focus apps send your sessions to an account on their server — one needs an install, another puts the useful history behind a subscription, and a third is a team tool that reports to your employer. This one can't: your sessions are timed and stored entirely in your browser. Your session data never leaves the device — the only third-party requests are the site's own analytics, which count page views — and it uploads nothing, ever. There is no server to send it to. Don't take our word for it:

    New cross-origin requests during use: 0
    1. Press F12 to open developer tools, then the Network tab.
    2. Run a session and log an interruption above. Watch: apart from the site's analytics, nothing new is requested — no uploads, and no session data ever leaves your device.
    3. Extra credit: disconnect your internet after this page loads — the timer, the log and the report still work.

    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:

    1. 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.
    2. 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.
    3. 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.
    4. 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.

    Frequently asked questions

    Do my sessions upload anywhere?

    No. The timer, the interruption log and the session history live entirely in your browser — your session data never leaves the device, and the only third-party requests are the site's own analytics, which count page views. You can verify it yourself with the network-request counter in the privacy section below the tracker.

    How does the focus score work?

    The score is 100 times the uninterrupted share of your session, minus 2 points per interruption, capped at 0 to 100. A 90-minute session with 25 minutes lost to interruptions scores 66 (Strained); a session with no interruptions scores 100 (Excellent). The bands are 85 and above Excellent, 70 to 84 Good, 50 to 69 Strained, and below 50 Fragmented. It is a heuristic about how broken the session was, not a judgement of the quality of the work itself.

    Where does the 23-minute refocus figure come from?

    It comes from published workplace research by Gloria Mark, who found it takes about 23 minutes on average to fully refocus after an interruption. The tool multiplies that by your interruption count and labels the result clearly as an estimate — your real refocus time will be shorter for a quick glance at a message and longer for a deep context switch. The lost minutes (the durations you logged) are measured; only the refocus cost is estimated.

    What counts as an interruption?

    Anything that pulls you off the task you named: a message, an email, a phone call, a colleague stopping by, a meeting running over, a notification, drifting off to social media or the news yourself, or noise in the room. The log separates what happened (the type) from where it came from (the source), because the fix for Slack is different from the fix for a noisy room. If it did not pull you off the task, do not log it.

    What if I forget to log an interruption?

    Then it leaves no trace in the report — the timer cannot see interruptions that happen away from the keyboard, and it cannot guess what you forgot. That is the honest limit of any self-logged tool. Two things help: keep the page visible while you work so logging is one tap, and log the interruption the moment you return to the task, while you still remember what it was and how long it took.

    How does the history work, and where is it stored?

    Every finished session is saved in your browser's local storage on this device, up to 50 sessions, and the history table shows totals, average focus score and your top interruption source across all of them. You can export the whole history as a CSV file. Nothing is sent to a server, so the history exists only in this browser — clearing your browser data, or switching devices, starts it over. Use Clear history to wipe it deliberately.

    Can I use it for studying, writing or coding?

    Yes — anything with one named task and a block of time: studying, writing, coding, research, design, exam revision, or a report. Pick a block length that fits the work (25 minutes for a short sprint, 90 for a long writing block), name the single task, and log what breaks it. The fixes in the report are written for knowledge work in general, not for one profession.

    What does this tool NOT do?

    It does not block distracting sites or silence your phone — it measures interruptions so you can fix them yourself. It does not watch your screen or track which apps you use, it does not work across devices, and it cannot tell whether the work itself was good — only whether the session was broken. The focus score and the refocus cost are heuristics, not measurements of your ability.

    Why track interruptions instead of just using a timer?

    Because 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 — the work that came out of them is completely different. Logging what broke your focus, and what it cost in lost minutes plus refocus time, turns a vague feeling ("I keep getting interrupted") into a named pattern ("Slack, three times, 25 minutes") with a fix you can actually try tomorrow.