Management software or surveillance: where is the line?

Management software becomes surveillance software when employees do not know what is recorded, cannot see what it is for, get nothing out of the data, and the data is used to judge them. The technology is the same in both cases. What changes is the stated purpose, the transparency, who can see what, and what leadership rules out.

The day the tablet ended up in a cupboard

In one restaurant, a tablet is installed in the kitchen for temperature logs and checklists. In the first month, everything gets ticked. In the second, a chef de partie notices that his first name appears in an export sent to the owner with the word "late" next to several tasks. Nobody told him that kind of export existed. The following week, the tablet is "charging" in the office, and the logs are back on paper.

No software was hacked. What broke was trust: the tool was really there to record delays, not to help hold a standard.

Why the drift is so easy

• The data exists, so it gets used. A clock-in time or a task sign-off lends itself to a ranking as soon as there is a table. Nobody decided to monitor anyone: it is simply the easiest reading.
• Access was never discussed. When everyone can see everyone's actions, attention shifts toward people rather than processes.
• The employee gains nothing. A tool that does not serve them (a clear instruction, help with training, a record of what they did) is seen only as a data-entry cost for the benefit of management.
• No written limits. Without a red line, each manager decides alone what to do with the data, and whoever is in the biggest hurry sets the usage.

Five questions to know which side you are on

Question	Execution aid	Surveillance
Does the employee know what is recorded?	Yes, it is said and written	They find out by chance
What is the data for?	Reminding, training, fixing a process	Spotting who does badly
Who can view it?	The people involved in the decision	The whole chain of command, no rules
Does the employee get a benefit from it?	Yes: instructions, history, training	No
What do we rule out?	Ranking, scoring, automatic sanctions	Nothing is said

If even one of your answers falls in the right-hand column, the problem is already there, even if nobody complains out loud.

How to hold the line over time

1. Write a one-page usage charter. What is recorded, by whom, for what, and what is off limits. The owner signs it first.
2. Present it to the team before launch. In a meeting, not by message, with time for questions.
3. Limit access by role. A chef de partie sees their own tasks and logs, a manager sees their site, the owner sees the summary they need.
4. Look at the process before the person. A task that is always late raises the question of the schedule, the training or the instruction.
5. Show employees what they get out of it. Their typical day, up-to-date instructions, the list of what they have completed in their training.
6. Review usage every quarter. Ask the teams whether anything feels out of place, and correct it.

Common mistakes

• Announcing that "this is not surveillance." It is better to show what is recorded and what is refused.
• Keeping a "ranking" feature because it is available. It will end up being used.
• Putting individual data on a meeting slide. A name next to a delay, in front of colleagues, destroys in one meeting what a charter took months to build.
• Using the tool to justify a decision already made. Teams see it, and the tool loses all credibility.

What teams actually hear

An owner presents the tool as a way to "get visibility." An employee hears: "they'll be able to see what I do, when, and for how long." The word visibility is neutral for the one looking and unsettling for the one being looked at. So translate each feature into the team's language: "this checklist saves you from hunting for the instruction," "this history proves what you checked if a doubt comes up." Then ask two or three employees to restate what they understood. Their version, not yours, tells you whether the line is being held.

Three signals to watch

• The number of workarounds: logs redone on paper, tasks ticked in bulk at the end of service, the tablet "forgotten."
• Recurring questions about what the tool "knows" about each person. They signal doubt about transparency.
• The number of times an individual's data is quoted in meetings, compared with the times the process is discussed.

Where Tsuno comes in

Tsuno is built on a doctrine: it connects the facts, it never judges a person. It does not rank employees, does not grade anyone, does not infer motivation or mood, does not predict resignations and triggers no sanctions. Each fact keeps its source (measured, declared, proven, observed, inferred) and, when data is missing, Tsuno says so. If something is wrong, the answer points to the process, the training or the schedule. The commitments are detailed on the trust page.

Read next

On the same subject, see why AI should not judge your employees and why restaurant checklists often change nothing. The manager-side approach is in managers do not need another dashboard.

Key takeaway

The line between support and surveillance does not run through the technology but through its use: what is said, who sees, what it is for, what is ruled out. Write those limits before day one and hold to them, or the tablet will end up in the cupboard.