Employee Monitoring: Time Tracker - Overview
Objective. Read the Time Tracker Overview end to end: name every tile, table and chart on it, explain what each one measures, drive the day/date and industry controls, and avoid the three readings that get a customer in trouble.
This is the home screen most managers open first, and the page you will demo most often. It answers one question in layers: for the team I picked, on the day I picked, who was present, how were the hours spent, and where is time leaking. Everything on the page is a different cut of that question.
See it in the demo
What this page answers
The Overview answers for this team and this day, what happened with people and time? A delivery manager opens it each morning to see who started, who is still tracking, how the day's hours split between productive and non-productive activity, and which people need a look (idle, late, on leave, not tracked). It is the first screen in a demo because it tells the whole monitoring story on one page before you drill anywhere.
Controls at the top set the scope the whole page obeys: the Day / Week / Month selector, the date (the demo sits on a fixed fictional date), a timezone (GMT) control, and prev/next arrows. At the bottom is an industry data switcher (IT & Shared Services, Healthcare RCM, Cybersecurity/SOC, Call Center / BPO, Finance & Accounting KPO, Facilities) - it reloads the same screen with a different seeded dataset so you can demo to the prospect's own vertical.
On the page, panel by panel
Read it top to bottom. Five KPI tiles: Average Start Time (when the team began), Team Working Time (total tracked hours across the team, shown as hours:minutes), Average Last Seen (how recently activity was captured), Team Members (people in scope) and Tracked Members (how many of them actually have capture data). The gap between Team Members and Tracked Members is the first thing to read - it is your coverage number.
Top 5 Websites & Applications - a donut of where time went by app/site (Excel, Gmail, LinkedIn, ChatGPT, and so on). Work Hours (Avg) table - columns Name, Man Days, Work Hours (Avg) - average hours per person. Productivity Split table - Name, Man Days, Over Worked, Healthy, Under Worked - classifies each person's load against a healthy band. Productive Activity - a split of the team's time into Productive / Non-Productive / Neutral with hours and a percentage each.
Then six people lists that are really exception queues: Most Productive, Most Non-Productive, Idle Time, Non Tracked, Late, and On Leave users. Work Time Metrics table - Active Time (Avg), Approved Away Time (Avg), Idle Hours (Avg) - separates genuine active time from approved away time and idle. Work vs Life Balance - a chart of Expected Hours against Working Hours over the period. Time Away From System Report - a table breaking away time into reason codes (Testing, Client Call, KT, Meeting, Lunch Break, Tea Break) and an Away Time Report chart of the same. The reason codes matter: they are why away time is not the same as idle time.
How it is used
The morning routine: set the scope (team, day), read the two coverage numbers (Team vs Tracked Members), then scan the exception lists for anyone who is late, idle, not tracked or on leave, and act on those few rather than the whole roster. The Productive/Non-Productive/Neutral split and the Work Time Metrics table tell the manager whether the shape of the day was normal; Time Away From System explains spikes in away time by reason before anyone assumes time was wasted.
The drill path from here: a person who looks off on Overview is opened in Activity (Detailed Activity, Apps & URLs) to see what they actually did, or in Monitoring (Screenshots) where policy allows. Overview is the triage screen; the evidence lives one or two clicks deeper.
How to read it right
Three misreads to head off. One: Tracked less than Team Members is a coverage gap, not proof of no work. A low Tracked count means the agent was not capturing (off, not installed, offline), so the day's totals understate reality - say that before you read any average. Two: Productive/Non-Productive is a configurable classification, not a verdict. The productive label is set per customer against their own app and site list; the demo's classification is illustrative. Never present a non-productive percentage as proof of slacking. Three: away time is not idle time. The Time Away From System reason codes (Client Call, Meeting, KT) are legitimate work off the keyboard; idle in Work Time Metrics is captured inactivity. Conflating them is the classic monitoring mistake. All the figures on the page are seeded demo numbers for one fictional day.
How to demo and sell it
This is the page that sells the product, so lead with the story, not the tiles. Open on the prospect's own vertical using the industry switcher, then say: in one screen a manager sees who showed up, how the hours were spent, and the handful of people to look at today. Land one value point - usually the coverage number (Team vs Tracked) for a remote or hybrid team, because "do you actually know who is working right now?" is the pain. Show the Productive Activity split, then immediately show Time Away From System and make the honesty move yourself: away time has reasons, this is not about catching people. That transparency framing is what wins the room and pre-empts the surveillance objection. Discovery question this page answers for a prospect: today, could your managers tell me in thirty seconds who needs attention on each team?
Honest limits
Overview shows presence and how time was classified - it does not show the quality or output of the work (that is Work Output), and a healthy-looking split does not mean targets were met. The productive classification, the healthy/over/under bands, and the away reason codes are all customer-configured; confirm the real setup with product before quoting any of them to a customer. Whether a given capture (screenshots, specific app detail) is available depends on the customer's policy and plan - confirm with product. Treat every number here as a seeded demo value, not a benchmark.
Interpretation check
Tracked Members below Team Members is a coverage gap that understates every total on the page; and Non-Productive time and Away time are two different things (a configurable classification vs reason-coded time off the keyboard), neither of which is proof that work was not done.
In the field
For a remote-heavy RCM operation like KnackGlobal, the Team-vs-Tracked coverage number is the opening pain: distributed teams where leaders cannot say who is actually working. Lead the demo there, not on the productivity percentages.
Practical task
On the demo Overview, switch the industry to the vertical you sell into, then write the day's reading in four lines: coverage (Team vs Tracked), the productive/non-productive/neutral split, the two biggest exception lists, and the top away-time reason - each with the one honest caveat you would say out loud.
Self-check
Team Members shows 100 but Tracked Members shows 90. What do you say before reading any average on the page?
That 10 people have no capture data today, so the totals understate the real picture - read coverage first, then the averages, and find out why those 10 are untracked (offline, not installed, on leave).
A prospect points at 'Non-Productive Time 21%' and says 'so a fifth of their day is wasted.' Correct it.
Non-productive is a configurable classification against the customer's own app/site list, not a judgement. In the demo it is seeded. It flags time to understand, not wasted time, and it says nothing about output.
Why is the Time Away From System report important for an honest demo?
It breaks away time into reasons (Client Call, Meeting, KT, breaks), proving away-from-keyboard is often real work. Showing it yourself pre-empts the surveillance objection and separates away time from idle time.
A manager wants to act on this screen each morning. What is the efficient routine?
Set team and day, read Team vs Tracked coverage, scan the exception lists (Late, Idle, Not Tracked, On Leave) and act on those few, then sanity-check the Productive split and Work Time Metrics for an abnormal day shape.
Where do you go for the evidence behind a person who looks off on Overview?
Into Activity (Detailed Activity, Apps & URLs) for what they did, or Monitoring (Screenshots) where the customer's policy allows. Overview is triage; the evidence is one or two clicks deeper.
Verified vs demo. Every panel named here is live on the demo Overview at /employeemonitoring/timetracker/overview; the exact tiles, table columns and reason codes were read from the live screen, but all values are seeded demo data and the productive classification, healthy bands and away codes are customer-configured - confirm the real behaviour and entitlement with product.