1. Home
  2. Knowledge Base
  3. Privacy & Trust
  4. Should You Monitor the Whole Company or Just Certain People?

Should You Monitor the Whole Company or Just Certain People?

Our recommendation is to deploy mi.team to the whole company, applied consistently to everyone in scope, including leadership. If you want to reduce risk, run a short, openly announced pilot with one team first, then roll out to everyone else.

The option we advise against is choosing a handful of individuals to monitor while everyone else is left alone. It is the most common instinct, and it usually creates the very problems monitoring is supposed to help with.

This article explains why, when a narrower scope is genuinely justified, and how to run a pilot that does not look like targeting.

Why monitoring selected individuals causes problems

It looks like suspicion, whatever the intention

When a business monitors only certain people, those people will reasonably conclude that they are under suspicion. Their colleagues will draw the same conclusion. It does not matter whether the selection was made for a sound operational reason; the message received is that some people are trusted and some are not.

That damages trust with the people being monitored and makes the rest of the workforce wonder whether they are next. Monitoring that is applied to everyone, and explained honestly, is far easier to accept because nobody has been singled out.

It is harder to justify under UK GDPR

Most businesses rely on legitimate interests as the lawful basis for employee monitoring. To rely on it, you need to show that the monitoring serves a genuine purpose, that it is necessary for that purpose, and that it is fair to the people affected. The ICO’s guidance on monitoring workers places particular weight on fairness and transparency.

The difficulty with selective monitoring is that the purpose and the scope stop matching. If your stated purpose is to understand how work is done across the business, monitoring a few individuals does not fit it. If the real purpose is concern about specific people, that is a performance or conduct matter, which calls for a different process and a different assessment.

There is also a discrimination risk to consider. If the people you choose share a characteristic protected under the Equality Act 2010, for example if most of them work part-time, have caring responsibilities or have returned from long-term leave, a selection that seemed neutral can look very different. Applying the same approach to everyone removes that risk at the source.

For a fuller explanation of the legal framework, see Is It Legal to Track Staff Productivity in the UK?

This is not legal advice, and every business should take its own view. In our experience, however, a consistent company-wide policy is considerably easier to explain in a legitimate interests assessment and a DPIA than a selective one.

The data is less useful

Activity data means very little in isolation. Whether 70% productive time is good or poor depends on the role, the team and what normal looks like in your business. Without a wider group to compare against, you have no baseline, and any conclusion you draw about an individual is likely to be wrong.

mi.team’s team views, trends and team-average comparisons are designed to be read across a group. They work best when everyone in the team is included.

Why the whole company works better

When monitoring covers everyone, it becomes part of how the business operates rather than something done to particular people. In practice, that means:

  • One policy, one message. You send a single pre-deployment email, write one disclaimer and complete one DPIA that covers everyone.
  • Leadership is included. When directors and managers are monitored on the same terms as everyone else, it is much harder for anyone to argue that the system exists to catch staff out. We regard this as the single strongest signal of good faith a business can send.
  • Everyone can see their own data. In mi.team, login access is on by default for every user, so people can see exactly what is recorded about them and correct any privacy flags they disagree with.
  • Comparisons are meaningful. Team averages and trends reflect the whole team, not a hand-picked subset.
  • Nobody is left wondering. There is no question about who is included and why.

It is also worth being clear about what a company-wide rollout of mi.team involves. mi.team records app and website usage by duration only. It does not capture screenshots, keystrokes, webcam footage or message content, and Privacy AI redacts personal activity before anyone sees it. Because it records far less than tools that take screenshots or log keystrokes, rolling it out to everyone is much less intrusive than it may first sound. It is worth making that clear to staff when you announce it.

When a narrower scope is justified

Deploying to the whole company is our default recommendation, not an absolute rule. A narrower scope can be reasonable when the group is defined by an objective, business-related reason rather than by who you are concerned about. For example:

  • A whole department or function, where the purpose relates specifically to that work, such as reviewing how time is spent across a customer services team to plan staffing.
  • A contractual requirement, where a client contract requires activity records for the people working on that account.
  • A phased rollout, where you are deploying team by team for practical reasons and everyone knows the rest of the business will follow.

In each case, the test is whether you could explain to any employee, in plain terms, why their group was included or excluded. If the honest answer is “because we were worried about you”, the scope is wrong.

What about investigating one person?

Monitoring an individual as part of a misconduct investigation is a separate matter from a normal rollout. It needs its own justification, should follow your disciplinary process and is an area where we would recommend taking HR or legal advice. It is not a reason to deploy mi.team selectively in the first place.

mi.team is built for transparent monitoring that staff know about. Login access can be switched off for a specific team where there is a genuine exception, such as an active investigation, but this is intended for rare cases, not as a way of running monitoring that people are unaware of.

How to run a pilot without it looking like targeting

A pilot is a sensible way to check that the installation, settings and communication all work before involving everyone. The difference between a pilot and selective monitoring is that a pilot is time-limited, openly announced and followed by the full rollout.

  1. Decide the full scope first. Work out who the final rollout will cover and write your legitimate interests assessment and DPIA for that full scope. The pilot is then the first phase of a plan, not a separate decision.
  2. Choose a team that is willing to go first. Leadership is often the best choice, because it shows that the people introducing monitoring are prepared to be monitored themselves. Pairing Leadership with one operational team gives you a more realistic picture.
  3. Tell the pilot team, and everyone else, what is happening. Explain that this is a pilot, how long it will last, what it is testing and that the rest of the business will follow.
  4. Follow the normal deployment process. Use the same steps you will use for the full rollout: lawful basis, settings, pre-deployment email, DPIA, deployment, enrolment check and follow-up email. Our complete rollout process covers each step.
  5. Keep it short. Two to four weeks is usually enough to confirm that devices enrol correctly, that the Startup Agreement and disclaimer read well and that people understand what they can see when they log in to mi.team.
  6. Ask for feedback. Ask the pilot team what was unclear, which privacy flags needed correcting and which questions came up. Use the answers to improve your wording before the full rollout.
  7. Roll out to everyone. Once you have addressed what the pilot found, deploy to the rest of the business as planned.

Frequently asked questions

Can we monitor only remote or hybrid workers?
You can, but you would need a reason that is specific to remote working, and it can easily appear to be a two-tier policy. Remote and office-based staff generally do similar work and should be treated the same way. In most cases, including everyone is simpler and fairer.

Should directors and managers be included?
Yes. Including leadership is one of the most effective ways to show that monitoring is about understanding how work is done, not about watching junior staff. In mi.team, managers also need to be added as members of their team if their own data is to be shared back with that team. See How to Create Teams, Add Members and Add Managers.

Will everyone be able to see everyone else’s data?
No. What people can see depends on the teams they belong to. Members of the same team see each other’s overview, and team managers can also see their members’ activity logs, which remain privacy-redacted. People who do not share a team see only basic information such as devices and top categories. Deploying to the whole company does not mean opening everyone’s data to everyone.

Does a company-wide rollout cost more?
Yes. Pricing is per user, so covering more people costs more than covering a few. If budget is the main reason for limiting scope, a phased rollout by team is a better way to manage it than selecting individuals.

What about new starters?
Include mi.team in your normal onboarding so that new starters are covered from their first day, receive the same explanation as everyone else and are added to the right team.

Do we need a new DPIA when we move from the pilot to the full rollout?
Not if you wrote the DPIA for the full scope at the start, which is what we recommend. Review it after the pilot and update it with anything you have learned. Our deployment article includes a DPIA template that is pre-completed for a standard rollout.

Was this article helpful?

Related Articles