Use case · Productivity & focus scoring
A productivity score that survives the pushback
One question kills most ratings: where did that number come from. Focus, deep work, idle and app mix roll into one score here, and every score opens into the activity behind it.
Free for two seats, no card.
- Classify the toolsApps and sites are categorised from a shared directory, then overridden by you where your business disagrees with the default.
- Measure focus, not just presenceDeep-work stretches, context switching and idle are measured separately, so the score reflects the shape of the day rather than its length.
- Roll it upPerson, team and org rollups come off one signal, with heatmaps and category breakdowns at every level, so nobody reconciles two versions of the same week.
- Open the breakdownAny score expands into the activity behind it, which is what you take into a one-to-one, a promotion case or a formal process.
Score productivity & focus
Scoring specific enough to manage on
Every line here opens the screen it happens on. Judge the job on what it puts in front of a manager, not on the sentence describing it.
- AKMonitoring & AnalyticsA clear picture of the working week.Search or ask…
- Today
- Insights
- Activity board
- Live screens
- Team
- Agents
- Integrity
- App categories
- Reports & digests
- Capacity
Northlight StudioActivity boardWho is working, on what, right nowPERSONINFOCUSSTATE- AKAria K.Figma92Active
- JMJon M.Terminal78Active
- SDSara D.Slack61Active
- RPRavi P.Notion34Idle 11m
- LMLena M.Teams55In a call
- TVTomas V.Off shift0Off
4 of 6 active · 42 apps seen todayUpdated just now
- Today
- Insights
- Activity board
- Live screens
- Team
- Agents
- Integrity
- App categories
- Reports & digests
- Capacity
- AKAria K.Figma92Active
- JMJon M.Terminal78Active
- SDSara D.Slack61Active
- RPRavi P.Notion34Idle 11m
- LMLena M.Teams55In a call
- TVTomas V.Off shift0Off
How it works
From an app switch to a number that holds up
- 1
Classify the tools
Apps and sites are categorised from a shared directory, then overridden by you where your business disagrees with the default.
- 2
Measure focus, not just presence
Deep-work stretches, context switching and idle are measured separately, so the score reflects the shape of the day rather than its length.
- 3
Roll it up
Person, team and org rollups come off one signal, with heatmaps and category breakdowns at every level, so nobody reconciles two versions of the same week.
- 4
Open the breakdown
Any score expands into the activity behind it, which is what you take into a one-to-one, a promotion case or a formal process.
An activity percentage vs. a score that shows its working
workmonitor.vsActivity-percentage tools
What the number means
With WorkMonitor
Focus, deep work, category and idle, combined into a score whose components you can inspect one by one.
Activity-percentage tools
Keystrokes and mouse movement per minute, which rewards fidgeting and punishes reading.
When someone challenges it
With WorkMonitor
The breakdown opens, and the conversation becomes about the work rather than about the tool.
Activity-percentage tools
There is nothing behind the number to look at, so the conversation becomes a negotiation.
Whose definition of "productive"
With WorkMonitor
Yours. Category overrides and a per-app privacy deny-list mean the classification reflects your business.
Activity-percentage tools
The vendor’s, baked into a category list you cannot change.
Overwork
With WorkMonitor
Shows up as a capacity band running hot and an AI Burnout Guardian warning, weeks before the resignation.
Activity-percentage tools
Shows up as a high score, and gets rewarded until the person resigns.
Evidence for an HR file
With WorkMonitor
A rating the person has already been able to see and query, backed by the activity behind it, which is what makes it usable in a formal process.
Activity-percentage tools
A number in a review that nobody can trace back to anything, which gets argued rather than acted on.
Auditability
With WorkMonitor
A warehouse export plus a hash-chained access log recording every time somebody looked at the data.
Activity-percentage tools
A dashboard you cannot export and cannot reproduce.
- Today
- Insights
- Activity board
- Live screens
- Team
- Agents
- Integrity
- App categories
- Reports & digests
- Capacity
- Product7824131h
- Design476172h
- Engineering14756262h
- Operations271235h
- Support9682168h
- Sales6643108h
Everything behind the score
- Productivity scoring (score, heatmap, category breakdown, rollups)
- Score explainability / breakdown
- App classification & category overrides + per-app privacy deny-list
- Focus & deep-work analysis
- Workload capacity signal (feeds AI Burnout Guardian)
- BI warehouse export (connector in Integrations)
Ask AI
Ask AI what the score is made of
Answers grounded in the same breakdown the score exposes, so the explanation and the number never diverge.
Pick a question above and WorkMonitor AI will answer from your team's real numbers.
- Today
- Insights
- Activity board
- Live screens
- Team
- Agents
- Integrity
- App categories
- Reports & digests
- Capacity
- AKAria K.Figma92Active
- JMJon M.Terminal78Active
- SDSara D.Slack61Active
- RPRavi P.Notion34Idle 11m
- LMLena M.Teams55In a call
- TVTomas V.Off shift0Off
The status meeting, already written
Status is normally assembled by asking. Here it is already: hours, activity, attendance and risk on one board, for one person or the whole company. Set the thresholds once and it tells you who needs you.
Who runs this
Teams that have to defend a rating
Straight answers
The questions we would ask in your position
Every answer here is the one you would get on a call. Open as many as you like; they stay open, so two can be held side by side.
No. Counting keystrokes measures typing, not work: it rewards fidgeting and penalises reading, thinking and pair work. Scoring here is built from app and site categories, focus and deep-work stretches, and detected idle, and the desktop agents are held to counting key events without reading their content.
Yes, and you should. Classification ships with a shared default directory and per-category overrides, so a tool that is core work in your business stops being scored as a distraction. Overrides apply to every score downstream, including historical rollups.
Rollups exist and comparison is possible. The more useful question for most managers is not who is bottom but where the work is piling up, which is what the capacity signal is built to surface, and every score opens into the activity behind it, which is what turns a ranking into something you can act on rather than argue about.
That is what the explainability is for. The score opens into the activity behind it, the person has already been able to see their own record and dispute a capture with a right to human review, and every access to that record is logged. A rating assembled from data the subject has never seen is the one that gets challenged instead of accepted.
Yes. The BI warehouse connector exports the underlying data and the public API exposes it in typed form. A score you cannot reproduce is a score your analysts are being asked to take on trust, and the first executive who asks how it was calculated will find that out.
Keep going
The jobs next to this one
Same record, read for a different question. Each one opens the page written for that job.
- Monitor apps & websitesEvery app and site classified, every day replayable as a timeline. You see which tools are eating the week and which teams they are fragmenting.
- Catch anomalies with smart alertsAnomaly detection against your own baseline, six named agents on specific jobs, evidence-cited summaries, and delivery to a channel your team already reads.
- Manage remote & hybrid teamsOne live board across every zone, attendance in each person’s local day, capacity bands that name who is drowning, and a rollout that never touches a machine.
Take these with you
The software is the easy part of a rollout
Here is what we would send a manager doing one for the first time: how to read a productivity number, what to say to a remote team before anything is installed, and a policy you can adopt as written.
Point it at one team for a week.
Create the account, put the agent on a handful of desks, and leave it alone. On Friday you read the week instead of reconstructing it: hours against their projects, focus and idle per person, and the timesheets already filled in.
Free for two seats. No card, and no sales call to sit through.