What Is a Focus Score? (And Why One Number Beats a Dashboard)
The first thing most time trackers give you is a dashboard. Pie charts. Bar graphs. A rainbow of app categories. You look at it for ten seconds, think "huh, interesting," and close the tab.
A Focus Score is the opposite. It's one number between 0 and 100 that summarizes how focused your day was. Nothing else. The whole point is that you can glance at it, feel something immediate and honest about how the day went, and decide whether to do anything about it.
Here's what actually goes into that number, and why collapsing the rainbow into a scalar is a feature, not a limitation.
The three things a Focus Score measures
A good Focus Score combines three signals, each of which is easy to cheat on its own but hard to cheat together.
1. Time in productive apps. What fraction of your tracked time was spent in apps and websites you've flagged as productive? If you're a developer, that's your editor, terminal, docs, PR reviews. If you're a writer, it's your writing tool, research tabs, maybe a notes app. Anything you'd actually put on a timesheet.
2. Session length. Deep work isn't just time spent — it's how long you could stay in it before bouncing out. A day with four uninterrupted 45-minute sessions is categorically different from a day with sixteen 11-minute sessions, even though the total "productive time" is identical.
3. Context switches. How often did you jump between apps or tabs? Every switch has a real cognitive tax, and dense switching is the single clearest signal of a day that felt busy but didn't produce anything.
A Focus Score weights these three so that the only way to score high is to be in productive work and stay there and not whiplash between tools. Cheating any one axis drops the number.
Why one number beats a dashboard
Dashboards tell you what you already know. You spent time in Slack. You spent time in your editor. You took a lunch break. What do you do with that information?
A single score does something harder: it forces a verdict. Was today a focused day or not? Was this week better or worse than last week? The act of collapsing the data into one number is what makes it behavior-changing.
This is also why speedometers exist in one dimension instead of a sixteen-chart engine diagnostic. When you're driving, you don't want to reason — you want to know if you're speeding. When you finish a work block, you don't want to cross-reference five charts. You want to know whether the block was focused or not.
Three things get easier once you have the score:
- Daily cadence. Peek at the end of the day, decide if tomorrow needs a different shape.
- Week-over-week. Compare Monday to last Monday, not a blur of categories.
- Cause and effect. Try an experiment — notifications off, a hard start time, a walk at noon — and see the score move.
How to read your score in the first week
Day one, most people score in the 20s or 30s. This isn't because they had a bad day. It's because apps haven't been categorized yet, so most of what you did lands as "neutral," which neither helps nor hurts.
By day three or four, once the top 15 or 20 apps you use are tagged, the score starts reflecting reality. Somewhere in the first week, you'll hit a day where the score is surprisingly low — and you'll remember, oh right, I spent 40 minutes bouncing around Slack before I got into anything. That's the moment the score starts working.
A rough calibration, from watching hundreds of people's early weeks:
- 70+ — a genuinely focused day. Most knowledge workers hit this two or three days a week.
- 50–70 — a reasonable day with some friction.
- Under 50 — a day dominated by meetings, context-switching, or pure distraction.
Scores are relative. The goal isn't a specific number — it's whether your average is trending up over a month. A 55 that you used to rate as "an OK day" feels different when last week's average was 48.
What the score is not
Two things the score is intentionally not:
- A surveillance tool. It runs on your Mac, with your data. Nobody else sees it. Your manager doesn't get a dashboard. You're not being graded.
- A reward system. It's not a streak. Missing a day doesn't break anything. Some days are meetings-heavy by design, and a low score on one of those days is correct information, not a failure.
The job of the score is to make something you already feel — "today was focused" or "today was a mess" — legible and comparable over time. That's the whole trick.
How Focus Meter scores you
Focus Meter computes your Focus Score continuously as you work, using on-device data only. You can see it ticking in the menu bar, open the popover for the breakdown, and watch it trend over days and weeks in Reports.
Same as Screen Time in ease of setup. Nothing like Screen Time in what it tells you.