Summary
Most monitoring programs decide the individual-versus-team question by accident. The software collects per person, the dashboard defaults to per person, and managers end up with a ranked list they never asked for. The better default is the reverse: team-level data for everyday management, individual data for the person it describes, and individual detail for managers only in four defined situations. This guide sets out what each level of tracking can answer and what it cannot, the access matrix that follows, the four justified cases for individual detail, the legal weight behind the distinction in Europe, and how to configure a program so the default is the fair one.
E-Monitor shows managers team totals by default and gives every employee their own detail, with individual views for managers switched on per policy. Book a demo →
Two Levels, Two Different Questions
Team-level tracking aggregates activity across a group: total hours, focus time, meeting share, application mix, output, and how all of those move week to week. It answers questions about the work: is the team overloaded, where does the time go, did the process change help, is the launch eating the calendar. Those are the questions a manager needs weekly, and none of them requires knowing who did what.
Individual-level tracking answers questions about a person: is this employee's pattern changing, are they working far more hours than scheduled, did they take their breaks, how does their time split by project for billing. Some of those are legitimately the manager's business. Most of them are the employee's own business first, and the dashboard that serves them best is the one the employee can open.
The design mistake is to use individual data to answer team questions. A manager who looks at seven individual dashboards to find out whether the team is overloaded has seven chances to notice something irrelevant about one person and act on it. The team view answers the question in one screen with no such risk. The team productivity tracking guide covers the team view in detail.
What the Team View Answers
- Capacity: total active hours against planned headcount, and whether the gap is growing
- Overload: after-hours activity across the team, the earliest reliable burnout signal
- Process: where the hours go by application and project, and what a change moved
- Calendar: meeting share and focus-block density by hour, for scheduling decisions
- Trend: whether this week is inside the team's normal range or outside it
Every item on that list is a decision about the work rather than about a person, and every one of them is answered more reliably at team level because individual noise averages out. The baseline guide shows how to establish the normal range the trend question depends on.
What the Individual View Answers, and for Whom
Individual data has three audiences, and the design should serve them in this order.
The employee. Their own hours, breaks, focus pattern, application mix and after-hours time. This is the audience with the greatest use for the data and the strongest claim to it. A self-view dashboard turns monitoring into a tool the person uses rather than a thing done to them, and it catches the misclassified application or missed break before payroll does. The employee's guide is written for this audience.
Payroll and billing. Hours worked and time by client for non-exempt staff and billable roles. A legitimate need for individual records, limited to the fields pay and invoicing require.
The manager, in defined cases. Covered in the next section. Outside those cases, a manager with routine access to every individual's detail has a surveillance tool whether or not it is used as one, and employees assume it is used as one.
Four Cases Where Individual Detail Is Justified
Managers do sometimes need individual data, and a policy that pretends otherwise will be ignored. The defensible position is to name the cases and require a reason to be recorded when the detail is opened.
| Case | Trigger | Scope of detail | Who sees the access log |
|---|---|---|---|
| Workload concern | Individual after-hours or active-hours pattern outside normal range for two or more weeks | Hours and after-hours trend only | HR |
| Pay or billing dispute | Employee or client challenges a record | The disputed period | HR and the employee |
| Formal performance process | A documented process already opened | Fields named in the process, for its duration | HR and the employee |
| Security or compliance investigation | An alert or allegation logged by security | Defined by the investigation | Security and HR |
Two features make the table work in practice: the manager has to state the case to open the detail, and the access is logged where the employee can see it. The role-based access guide covers the configuration.
The Access Matrix
Write the answer down as a grid with roles across the top and data categories down the side. It is the single most useful page in a monitoring policy and the one a works council or regulator asks for first.
| Data | Employee | Manager | HR | Payroll | Security |
|---|---|---|---|---|---|
| Own hours and breaks | Full | Team totals; individual by case | Full, logged | Hours only | None |
| Own application mix | Full | Team totals; individual by case | By case, logged | None | By investigation |
| Own focus and after-hours pattern | Full | Team totals; individual by case | By case, logged | None | None |
| Screenshots, where enabled | Own | None | By case, logged | None | By investigation |
| Security events (file, USB, access) | Own | None | By case | None | Full, logged |
The pattern to notice is that the employee column is the fullest. That is deliberate and it is the arrangement that produces the fewest objections, the fewest workarounds and the most accurate data. The program design guide places the matrix in the sequence of decisions.
The Legal Weight of the Distinction
In the EU and UK the individual-versus-team choice is a proportionality question, and proportionality is the test regulators apply. Team-level data is low-risk processing; routine individual-level access by managers is the kind of monitoring that needs a data protection impact assessment and a demonstrated necessity. Several European works-council agreements require exactly the structure above: aggregate views for managers, individual views for the employee, individual access for others only through a documented procedure. The GDPR guide covers the assessment.
In the US the distinction carries less legal force and more practical force. Routine individual rankings are the feature most cited in surveys of why employees distrust monitoring, and they are the figure most often found to be unreliable when a dismissal is challenged, because active time measures input rather than work. Team-first design is the safer default in both places for different reasons.
Configuring the Default
Four settings produce the arrangement above in most tools. Set the manager's landing view to the team dashboard, not the people list. Enable employee self-view for everyone before launch. Require a reason field, or at minimum a logged event, when individual detail is opened by anyone other than the employee. And switch off individual productivity rankings entirely; they have no use the team view and the four cases do not serve better.
Then tell the team, in the announcement, exactly this: your manager sees team totals, you see your own detail, and here is the list of cases in which anyone else can look. It is the sentence that turns the design into trust. The announcement templates include it.
Related reading: Time Tracking for Remote Employees.
Frequently Asked Questions
1. Should employee productivity be tracked individually or by team?
Both, for different purposes. Team-level data answers questions about the work, such as capacity, overload, process and scheduling, and is the manager's everyday view. Individual data belongs first to the employee, then to payroll for hours, and to managers only in defined cases with a recorded reason.
2. What can team productivity tracking tell you?
Total capacity against headcount, after-hours load, where hours go by application and project, meeting share and focus-block timing, and whether the week sits inside the team's normal range. All of it without identifying who did what.
3. When is it justified for a manager to see individual monitoring data?
Four cases: a workload concern where an individual's pattern is outside normal range for two or more weeks, a pay or billing dispute, a formal performance process already opened, and a security or compliance investigation. Each should require a stated reason and a logged access.
4. Should employees be able to see their own monitoring data?
Yes, and fully. The employee column of the access matrix should be the fullest. Self-view catches errors before payroll, removes most objections, and is the arrangement that produces the most accurate data.
5. Is individual monitoring data a legal problem in Europe?
Routine individual access by managers is higher-risk processing under GDPR and needs a data protection impact assessment and demonstrated necessity. Team aggregates are low-risk. Many works-council agreements require aggregate views for managers and individual views only for the employee or through a documented procedure.
6. Should managers rank employees by productivity score?
No. Rankings rest on activity figures that measure input rather than work, they are the feature employees distrust most, and nothing the team view and the four defined cases cannot do better. Switch rankings off.
Team view by default, your own view for you E-Monitor lands managers on team totals, gives every employee their own detail, and logs any individual access so the policy's access matrix is enforced by the software. Sign up →