Employee Monitoring: Activity - Current Activity
Objective. Read the Current Activity live board end to end: name every status tile and every column of the live table, explain what 'right now' means here versus a historical report, drive the auto-refresh and filters, and avoid presenting a live status as a judgement on a person.
Current Activity is the live 'who is doing what right now' board for the whole in-scope population. It answers one real-time question in two layers - a strip of status count tiles across the top, then a per-person table underneath showing each employee's current activity this instant. It is the page a team lead glances at during the shift, not an end-of-day report, so everything on it is a snapshot that keeps refreshing.
See it in the demo
What this page answers
Current Activity answers right now, across my teams, who is online, who is idle, who is away, and what is each person actually on this moment? A team lead or shift supervisor opens it live during the working window - not to review history but to see the current state of the floor. It is the real-time cousin of the Time Tracker Overview: Overview summarises a whole day, Current Activity is this instant and it moves.
Controls at the top set scope and freshness: a Filters control (team/person scoping) and a Refresh every control (seen set to 1 min) that re-pulls the live state on an interval so the board stays current without a manual reload. Because the numbers refresh, any figure you read is a moment-in-time count, not a stable total.
On the page, panel by panel
Status count tiles (top strip). A row of live counters, each a running headcount in that state right now: Overall (everyone in scope), Logged In, Online, Offline, Productive, Non-Productive, Neutral, Idle, and Away from system. Read them as a funnel: Overall is the population, Logged In and Online tell you presence, and the Productive / Non-Productive / Neutral trio splits whoever is active right now by how their current app or site is classified. Idle and Away from system are the two 'present but not typing' states - keep them distinct from Offline (not logged in at all).
Live activity table. One row per employee, columns: Employee Id, Employee Name, Team Name, Current Activity (the live status - for example Active, Idle, Offline, Leave), Activity Detail (the exact app or site in focus this instant, e.g. 'dropbox.com - Dropbox', 'zoom.us - Zoom', 'Minutes.docx - Microsoft Word'), Current Activity Time (how long they have been in the current activity, as hh:mm:ss) and First Login (the timestamp they first started today). A person on Leave shows the status with no live detail; an Offline person shows no current app. The pairing that matters is Current Activity plus Activity Detail - the status word plus the actual thing on their screen right now.
How it is used
This is a glance-and-act board, not a study screen. The intraday routine: leave it open (it refreshes on the interval), watch the Online versus Idle versus Away tiles for the shape of the floor, and if a number looks off, scan the table for the specific people. A lead uses it to answer live questions - 'is the team actually on shift?', 'who just went idle before a deadline?', 'is anyone still offline after start time?' - and to nudge in the moment rather than after the fact.
The drill path: a person who looks off here is opened in Detailed Activity or Apps & Urls to see the history behind the live snapshot, or in Monitoring (Screenshots) where the customer's policy allows. Current Activity tells you the state this second; the evidence and the pattern live on the history pages.
How to read it right
Three misreads to head off. One: a live status is a snapshot, not a verdict. 'Idle' right now means no captured input in this moment - someone reading on screen, on a phone call, or thinking still reads as idle. Never treat one live status as proof a person is not working; it is a prompt to look, not a conclusion. Two: Idle and Away are not Offline. Idle and Away from system are present-but-not-at-keyboard states (a call, a break, a meeting); Offline means not logged in. Conflating them overstates 'nobody is working'. Three: the Productive / Non-Productive / Neutral tiles are a configurable classification of the current app, not a value judgement. The labels come from the customer's own app and site rules; in the demo they are illustrative. Finally, because the board auto-refreshes, every count is a moving moment-in-time number and all values here are seeded demo data.
How to demo and sell it
This is the single most visceral screen in the product for the 'do you actually know who is working right now?' pain, so demo it live. Open it, point at the status tiles and say this is your floor this second - online, idle, away, offline - refreshing on its own. Land one value point: for a distributed or hybrid team, a supervisor normally has no live view of the shift at all, and here it is one glance. Then make the honesty move yourself - open one 'Idle' row and say idle is a live signal, not an accusation; the point is to see the floor, not to catch a person. That framing pre-empts the surveillance objection before it is raised. Discovery question this page answers for a prospect: right now, could your shift leads tell me who is online, who is idle, and who never logged in - without pinging anyone?
Honest limits
Current Activity shows live state, not productivity or output - a full 'Online' board says nothing about whether the right work got done (that is Work Output), and a live status is only as complete as agent coverage allows: a person whose agent is not reporting simply will not appear as online. The Productive/Non-Productive/Neutral classification and what counts as Idle versus Away are customer-configured; confirm the real setup with product. Whether live monitoring at this granularity is enabled, and the refresh behaviour, depend on the customer's policy and plan - confirm with product. Treat every tile count and row here as a seeded, moving demo value, never a customer result.
Interpretation check
A live status on this board (Idle, Away, Offline, or a Non-Productive classification) is a moment-in-time signal about the current app and input, not a verdict on whether a person is working - and it is only as complete as agent coverage, since an unreporting agent never shows as online at all.
In the field
For a remote-heavy RCM operation like KnackGlobal, the live board is the sharpest answer to the displacement pitch's core doubt - distributed shift leads who cannot see their floor. Demo it live on their vertical and lead with presence (online/idle/offline), not the productivity classification.
Practical task
On the demo Current Activity board, write the floor's live state in four lines: the presence picture (Overall vs Logged In vs Online vs Offline), the live productive/non-productive/neutral split, how many are Idle or Away versus Offline, and one person whose Current Activity + Activity Detail you would glance at - each line with the one honest caveat you would say out loud.
Self-check
The Idle tile jumps up for a few minutes. Before you act, what do you remind the lead?
Idle is a live signal that there was no captured input just now - a call, reading, or thinking all read as idle. It is a prompt to glance at who and why, not proof anyone stopped working, and it will move on the next refresh.
A supervisor says 'Offline and Idle are both people not working, so add them up.' Correct it.
No. Offline means not logged in; Idle and Away from system mean logged in but not at the keyboard right now (break, meeting, call). They are different states and adding them overstates 'nobody is working'.
What do Current Activity and Activity Detail together tell you, and why read them as a pair?
Current Activity is the status word (Active, Idle, Offline, Leave) and Activity Detail is the exact app or site in focus this instant. Read together they say not just that someone is active but what they are actually on right now.
Why is this a 'moment-in-time' page and what follows from that?
It auto-refreshes (seen at every 1 min), so every tile count and row is a live snapshot that changes - you read the current shape of the floor, not a stable daily total, and you go to the history pages for patterns.
Someone looks off on the live board. Where do you go for evidence?
Into Detailed Activity or Apps & Urls for the history behind the snapshot, or Monitoring (Screenshots) where the customer's policy allows. Current Activity is the live glance; the pattern and evidence are on the history pages.
Verified vs demo. The status tiles (Overall, Logged In, Online, Offline, Productive, Non-Productive, Neutral, Idle, Away from system), the live table columns (Employee Id, Employee Name, Team Name, Current Activity, Activity Detail, Current Activity Time, First Login) and the 'Refresh every 1 min' control were read from the live demo at /employeemonitoring/activity/currentactivity; all counts and rows are seeded demo data, the productive classification and idle/away definitions are customer-configured, and whether live monitoring at this granularity is enabled depends on the customer's policy and plan - confirm with product.