Is logging rounds by tap a form of employee monitoring?
A log of who was where and when is data about a worker, whatever it was built for. That does not make it wrong, it makes it a project with a non technical half: what is recorded, who reads it, how long it is kept and what it may be used for are settled before the tags go up.
What the log actually is
A series of times and places attached to a named person for the length of a shift. It was built to show that a round happened, and it also shows when somebody was slow, where they lingered, and when they took a break.
The clocking in page reaches the same place from the entrance door: the technical half is trivial and the half that is not technical is larger.
Nothing about NFC makes this worse or better than a badge reader or an application with a map. The tag is the cheapest way to produce the record, which is exactly why the question arrives with it.
The questions, and who answers them
What is required differs by country and by the form of the employment, and the obligations fall on the employer. The useful questions are these: is a record of this kind permitted here, does it have to be declared, do staff representatives have to be consulted, and for what purposes may it be used once it exists.
The people who answer are inside the organisation or beside it: whoever holds the data protection role, the staff representatives, and the employer's own advisers. The data protection page says the same thing for tags in general and deliberately names no framework, because the answer is national.
Settle it before the hardware. Retrofitting a rule to a system that is already collecting is the expensive order to do this in.
What the design can decide anyway
Record the checkpoint and the time, not a continuous position. A round is a list of points, and a system that also logs where the phone was between them has collected something nobody asked for.
Identify the round rather than the person where the purpose allows it. A device issued per shift, rather than per worker, still shows that the round was walked and does not say by whom, and that choice is available more often than it is taken.
Set a retention period and delete on it. A log that proves a round was done last night has little value a year later, and keeping it is a decision rather than an accident.
Name the purposes, and stop there. A safety record reused for discipline is a second purpose that arrived without being declared, and it is the single thing that turns a workforce against a system like this.
What it does to the round
People who understand why the record exists cooperate with it. People who discover it in a meeting about their performance stop trusting anything the employer installs, including the parts that protect them.
Telling staff in advance what is recorded and what it will be used for costs nothing and changes the outcome. It also produces better requirements, because the person walking the round knows which checkpoints are in the wrong place.
And it keeps the system honest about its limits: the log shows that a device read a tag, not that anyone looked at anything, which the checkpoint page sets out and which matters most when the record is used against someone.
Frequently asked questions
Is a tap log personal data?
A record of who was where and when, attached to a named worker, is data about that person. What that requires of an employer depends on the country.
Who should be asked first?
Whoever holds the data protection role in the organisation, and the staff representatives where they exist. The obligations fall on the employer.
Can the round be logged without naming anyone?
Often yes. A device issued per shift rather than per worker still shows the round was walked, and that option is available more often than it is used.
Can a safety record be used for discipline?
That is a second purpose, and using it without having declared it is what breaks trust in the system. Decide and state the purposes in advance.