Recording
your employees

Yes, and it's a different situation from monitoring only entrances or the stockroom: here the camera sits alongside someone's daily work for their entire shift, so the room for justification is narrower. Proportionality stops being an abstract principle and becomes the question you have to answer before installing anything: is there a specific reason (a till position, an area with sensitive stock, a history of incidents) that can't be dealt with any other way? If the answer is generic, "to keep an eye on staff", the installation won't stand up. And even if the reason is good, the framing has to be limited to that reason: the camera watching the till doesn't need to see the chair or the locker next to it. The more hours a camera captures the same person at the same workstation, the easier it is for someone to question later whether it was really necessary, so document the reason before switching it on, rather than inventing one afterwards.

Every person who will be on camera, whatever their contract: permanent, temporary, interns or subcontractor staff working on your premises. If there's legal workforce representation (a works council or staff delegates), them too, and separately from the individual notice: informing only the works council and assuming it reaches everyone doesn't comply. The notice has to explain what is recorded, where the cameras are, for what purpose and what is done with the footage; saying "there are cameras" isn't enough. Anyone who joins after the installation must be given the same information when they start, rather than assuming they know from the sign or from what colleagues tell them. And when you change something significant (add cameras, change the purpose, switch on audio), the notice is repeated: the one given at the outset doesn't cover what came afterwards.

The prohibited areas aren't just changing rooms and toilets in the strict sense: the same logic extends to any corner staff use to genuinely switch off, even if it isn't labelled that way on the floor plan. A small kitchen where staff eat, a corner with a sofa that serves as an informal break room, a storeroom that's also used for changing clothes: if that's its real function, the camera can't point there even if the space is called a "storage room" in the lease. Nor is it an excuse that the camera is "only there to watch the fire exit" if the shot catches the rest area at an angle: you have to move the camera or mask that part. And if a business shares a building with another and the changing room is shared by both workforces, the prohibition doesn't change because it's a shared space: it's still a private space and still off limits to any camera.

Almost never, and it's worth distinguishing two situations that get confused. A camera with a microphone recording continuously next to a workstation captures entire conversations of people who are simply doing their job, and that rarely has a proportionate justification: it's a far greater intrusion than images alone. It's different with an alarm system that triggers brief audio only on a specific event, such as an out-of-hours intrusion; there the situation changes because there's no continuous recording of work conversations. Many recorders come with the microphone switched on from the factory without anyone having decided so, simply because the equipment comes that way, so check each camera's settings and disable audio unless there's a specific, documented reason to have it on. If you're unsure whether your installation is recording sound without your knowing, it's one of the first things worth checking, and it takes minutes.

A hidden camera as such (bought and installed to catch a specific person, without the system having existed before or anyone having been told about it) is the most slippery ground in this area, and it isn't a reasonable shortcut even if the suspicion is well founded. What does work is different: if you already have a system that's installed, notified and with known camera angles, you can use those recordings to prove a specific fact without warning in advance that you're going to review that person's footage on that day; that doesn't make the system hidden, because its existence was already known. The line between the two isn't always obvious on the ground, and getting it wrong has serious consequences: the evidence can be thrown out entirely and the spotlight shifts from the suspect to the business that installed the camera. If you're in this situation, before installing anything new or using a recording for a dismissal, that's the moment to consult a specialist, not to improvise.

It depends entirely on what you stated when you informed staff, and that's where problems usually arise: many businesses install cameras thinking only about theft or intrusion, inform staff of that, and months later someone has the idea of using them to see who arrives late. That use isn't covered by the original notice, so the footage can't justify a disciplinary measure for lateness even if it shows the exact time of arrival. If time-keeping really is an aim, the right thing is to state it from the outset alongside security, not to add it along the way when it's needed for a particular case: that shows, and it weakens any later use. Besides, combining both purposes on the same camera tends to produce wider shots than pure security needs, so consider whether it's really necessary, or whether a dedicated clocking-in system, which records nobody's image, does the same job with less friction and less risk.

Yes, and the problem is almost never the app but who else has access to it. Over time, accounts build up that should no longer be active: an employee who left the business, an installer who commissioned the system two years ago and never had their access removed, a partner who's no longer involved in the business. Each of those accounts is an open door onto footage of people at work, and nobody reviews the list until there's a problem. It's worth regularly clearing out who has remote access, not just protecting it with a strong password and two-factor authentication when it's set up. It's also worth keeping a simple log of who logs in and when, because if you ever have to show that only the right people accessed it, that log is the proof; without it, the answer to "who has seen this footage?" is a guess, and that counts against the business.

Consent not being the legal basis doesn't mean the workforce's opinion can simply be ignored: it's valuable information about how the installation is being experienced, and it's worth taking seriously before it turns into a formal dispute. First, listen to the specific reason for the objection, because it's almost never "I don't want cameras in general" but something more precise: a shot that's seen as excessive, a camera installed without the expected notice, doubts about who sees the footage. Reviewing that exact point is usually enough to resolve the conflict without touching the installation as a whole. If there's legal workforce representation, they're the natural counterpart for this conversation, and keeping a record that it was discussed and what was agreed protects both sides if the matter comes up again later. Simply ignoring the objection, on the other hand, usually ends in a formal complaint that forces you to review the same thing, but in worse circumstances.