Online Tool Store
Single-Tasking Session Logger
Single-Tasking Session Logger separates interruptions you caused from ones you received — only the second kind is solved by a closed door.
🔒 This tool runs entirely in your browser. Your files are never uploaded to a server.
Productivity
Single-Tasking Session Logger
Frontend preview — no upload or external service.
Session log
Session: "Draft migration plan", 53 minutes, 2 interruptions (5 min Slack, 3 min email). Total focus time: 45 minutes.
How the Single-Tasking Session Logger works
- Name one specific task, not a category of work.
- Log every interruption as it happens, marking whether it came from outside or from you.
- Review the pattern after a week. Self-initiated switches and external interruptions need completely different responses.
FAQ
Why distinguish self-initiated interruptions?
Because they have a different cause and a different fix. External interruptions need boundaries with other people; self-initiated ones usually mean the task is unclear, unpleasant, or blocked — and closing a chat client will not help.
How long should a session be?
Long enough to reach depth and short enough to sustain. Twenty-five minutes suits fragmented work; ninety suits anything requiring a complex model held in your head. The right answer differs by task.
Does logging interruptions cause more?
Recording takes a few seconds and can reduce them, because noticing an urge to switch is often enough to override it. If the logging itself becomes the distraction, count them instead of describing them.
How we compare
| Feature | Online Tool Store | A notes app | A project suite |
|---|---|---|---|
| Interruption source tracking | ✓ | ✗ | Paid |
| Pattern over sessions | ✓ | ✗ | ✓ |
| Data stays on device | ✓ | ✗ | ✗ |
| No account needed | ✓ | ✓ | ✗ |
Single-Tasking Session Logger separates interruptions you caused from ones you received — only the second kind is solved by a closed door.