Productivity Score Calculator

Log how many tasks you completed, how many hours of focused work you put in, and how many distractions interrupted you. The tool returns a productivity score that weights completion and focus positively and distractions negatively.

Reach for it as a daily reflection input, not a leaderboard metric. The number is most useful as a trend across weeks — a single day of low score during a meeting-heavy day means nothing in isolation.

The weighting is configurable. If you care more about deep work than task throughput, push the focus-time weight higher. If shipping matters more than how it felt, weight task completion. The defaults try to balance both.

The scoring formula. Score = (tasks_completed × W_tasks) + (focused_hours × W_focus) − (distractions × W_distract). Default weights: tasks_completed × 10, focused_hours × 15, distractions × 5. A typical good day with 8 tasks completed, 4 hours of focus time, and 2 distractions scores 8·10 + 4·15 − 2·5 = 130. The absolute number is meaningless; the relative number across days and weeks is the signal.

Worked example. Monday: 6 tasks, 5 focused hours, 1 distraction → 6·10 + 5·15 − 1·5 = 130. Tuesday: 12 tasks, 1 focused hour, 6 distractions → 12·10 + 1·15 − 6·5 = 105. Tuesday felt busier (more tasks completed) but scored lower because the work was shallow and fragmented. The number captures the difference between a productive day and a busy day, which mental retrospection often gets wrong.

The weights are configurable for a reason. If your role is administrative (high task throughput, low focus requirement), bump the task weight and lower the focus weight. If you're a researcher or writer, weight focus heavily and de-emphasize task count. Make the scoring match what "a good day" looks like for your work — otherwise the number captures the wrong thing.

A contrarian take: tracking your own productivity is itself a distraction unless it leads to changes. If the score never moves your behavior, stop tracking. If you find yourself tracking but not adjusting (skipping a deep-work block to attend a low-value meeting, then logging it without questioning the meeting's value), the data is going to waste. Review weekly. Spot patterns. Cancel one thing the data says doesn't earn its place. That's the value loop.

Distractions are the trickiest input. "Number of distractions" is squishy — a Slack message you ignored isn't a distraction; one you read mid-flow is. The tool's default counts only interruptions that broke focus for >2 minutes; smaller interruptions don't count. Many self-trackers count any context switch and end up with 30+ daily distractions, which makes the metric noise. Discipline the definition.