The difference between measuring output and surveilling people, and why the employee should see the same dashboard their employer does.
5 April 2026 · 7 min read
There's a conversation business owners have been having since COVID pushed most office work into homes: *how do I know my team is actually working?*
It's a fair question. And there are a lot of tools that promise to answer it, most of them by recording everything your employees do and calling it productivity.
This approach doesn't work. Not because it fails to gather data (it gathers too much of it), but because it destroys the trust that productive remote work depends on. Employees who feel surveilled work defensively. They stop taking initiative, stop experimenting, stop bringing problems forward. They do what the monitoring tool says is "productive" and nothing else.
There's a better way. It starts with a different question.
Ask instead: *do I have the information I need to lead this team?*
The second question is answerable, and honestly, you probably need much less data than you think. For most remote teams, the useful signals are:
You don't need to know whether your senior developer took a fifteen-minute coffee break at 10:47 am. You need to know whether the code shipped, whether the customer was happy, and whether they're overloaded enough that they'll quit in two months.
The good news is that monitoring can actually be designed to answer the leadership question instead of the surveillance question. But it requires you to be honest about what you're trying to achieve, and transparent with your team about it.
Australian law already requires transparency about workplace monitoring under the Workplace Surveillance Act 2005 (NSW) and equivalent state laws. You need written notice, it needs to be specific about what's being monitored, and it needs to be in place before the monitoring begins.
But this isn't just a legal requirement. It's a practical one. Covert monitoring always eventually becomes overt monitoring, because someone always notices. When it does, you lose trust instantly and permanently. The only kind of monitoring that's compatible with a healthy remote team is the kind the team knows about and understands.
Transparency means:
1. A clear, written policy that explains what's captured and why.
2. Employee access to their own data. They should be able to see what the system sees about them.
3. No secret metrics. If you're grading employees on a score, they should know the score and how it's calculated.
4. Opt-outs for private time. Personal breaks, sick time, and after-hours activity should not be captured at all.
If your monitoring policy can't survive being read aloud to the team, it's the wrong policy.
With transparency as the foundation, here's what's reasonable for most workplaces to monitor.
Attendance and active hours. Is the person signed in during their scheduled hours? Not "are they typing every minute". Are they present and available? This is genuinely useful for managers and doesn't require any invasive data collection.
Application and website categories. Not every keystroke, not the content of every tab. Just whether the time is being spent on productive-category tools (the codebase, the CRM, the design tool) or unproductive-category tools (games, shopping, social media). The employee can see the same dashboard their manager sees, and the goal isn't to catch people slacking but to help them notice their own patterns.
Compliance events. If an employee accesses confidential customer data, downloads a file, or sends a message that flags a regulated phrase, that event gets logged. This protects both the business (in case of dispute) and the employee (who has an audit trail proving what they did or didn't do).
Burnout and overload signals. Working very late, working through weekends, skipping breaks repeatedly: these are signs of a problem, not a virtue. Good monitoring surfaces them so managers can intervene before someone quits or crashes.
Focus time. Genuine deep-focus periods, where someone is in a flow state on productive work, are valuable and worth protecting. Good monitoring identifies them and helps teams structure their days around them.
The list of things you shouldn't monitor is shorter but more important:
A simple test: *if your team knew exactly what the monitoring system captured, would they be upset?* If yes, you're monitoring the wrong things.
The business value of monitoring isn't catching the 5% of employees who are slacking. It's understanding the 95% who are working and helping them work better. Done right, workforce monitoring gives you earlier intervention on burnout risk (the number one cause of valuable-employee turnover), insight into which tools and processes are actually productive, compliance evidence that protects both the business and the employee if anything goes wrong, and better resource allocation: knowing where time is actually being spent, not where you *think* it's being spent.
None of this requires treating your team like criminals. All of it requires treating monitoring as a tool for leadership, not a tool for control.
WorkAndGo is built on this philosophy. Transparent monitoring that runs inside the team communication app, with the same dashboards available to employees and managers, and a privacy policy you can show your team without flinching.