Twelve checks before you buy employee monitoring software

Most buying mistakes in this category happen before the demo, not during it. By the time a vendor is showing you screenshots, the decisions that matter have already been made — or skipped.

Here are twelve checks, in the order the problems usually appear.

Legal and organisational

1. Can you state the purpose in one sentence? If the sentence needs a comma to hold two purposes, it is two projects.
2. Is the notice written before the installation date? A notice written afterwards is a reconstruction.
3. Is the role of employee representatives confirmed? In many jurisdictions there is a consultation or co-decision right. Confirm your own country's rule before ordering.
4. Is there a named person accountable for the data? Not a department. One person who can answer "who looked at this record, and why".

Technical

1. Can each module be switched on independently? Screenshots, keystroke activity, site categories, file access and working time should not be one switch. Otherwise you cannot implement a narrow notice.
2. What happens offline, and where does the data sit? Local recording with later upload is reasonable — but there needs to be a cap and an encrypted or deleted local cache after sync.
3. Is there a real self-service view? Employees seeing their own records changes the tone of the whole deployment. A product that treats this as an add-on was designed for one-way observation.
4. Are uninstall and offboarding documented? Ask for the procedure: removal, the leaver's records, department closure. "Delete the folder" is not a procedure.

Data governance

1. Are access rights granular, and is every view logged? Trust is lost to an unnecessary glance, not to malice. Role-based rights plus an access log make that answerable.
2. Is retention enforced by the system or by people remembering? Prefer the one that deletes on a schedule.
3. Can you export and then leave? You should be able to take your own records out in a usable format, and terminate without losing them.

Vendor

1. Will they say no? The most useful signal in this category: a vendor who explains why a request is disproportionate. If everything is "we can do that", the tool eventually gets configured into a problem.

If you keep only three

Independent modules, granular access with logging, and system-enforced retention. Those three decide whether the rest of your policy can actually be implemented.

General information, not legal advice. The rules differ by jurisdiction; confirm the local position with a professional.