Starting point: a plant, one hall and the DPIA question
The scenario concerns a concept for a mid-sized manufacturing plant where management wants to start employee location tracking in one hall, as a limited pilot. We do not describe a completed rollout here, but the path a sensible team takes before the system collects its first data on where people are.
The data protection officer asks whether this operation requires a data protection impact assessment under Article 35 GDPR. The provision requires a DPIA where processing, especially with new technologies, may cause a high risk to the rights and freedoms of individuals. Systematic tracking of employees, who are in a subordinate relationship with the controller, is a situation in which a careful officer assumes a DPIA is needed, because a missing assessment is hard to defend later.
That is why the DPIA in this scenario is a gate before launch, not a document filled in afterwards. Its result decides which data the system collects, how long it keeps them and who can see them.
Stage 1: description of the processing and legal basis
The officer starts with a description of the processing, because without it no risk can be assessed. The description covers the purpose, categories of people, categories of data, recipients, place of processing and retention period. In the InnerWeb system every client has an isolated instance with its own database and its own mail service in Docker containers, also on the client's server, which simplifies answers about the controller, the place of processing and the scope of access.
The legal basis comes from the Polish Labour Code (Kodeks pracy). Location tracking of employees is a form of monitoring covered by Article 22(3) § 4, and under § 3 Article 22(2) §§ 6-10 applies to it accordingly. In practice this means an internal act (work rules, a collective agreement or a notice), 14 days from announcement to launch, written information before the employee is admitted to work, and marking of the area no later than the day before the start.
Purposes split into separate activities
In the DPIA it is worth splitting the purposes: work organisation and permits, evacuation, and an SOS alarm with motionlessness detection. The purpose 'safety' is listed in Article 22(2) § 1 for video monitoring, not in Article 22(3) § 1, so the alarm function is described as a separate purpose based on Article 207 § 2 of the Labour Code. Model acts for wearable devices contain a separate paragraph on the alarm function.
DPIA stages in the hall scenario: working time
Stage 2: necessity and proportionality assessment
The second stage of the DPIA asks whether the purpose can be achieved at a smaller cost to privacy. The principle in Article 5(1)(c) GDPR says data must be adequate and limited to what is necessary for the purpose. In practice the officer checks three things: whether location is needed for the whole shift or only in higher-risk zones, and whether the employee's name must appear on the map or an identifier is enough.
The technology helps limit the scope. The position is calculated from signals of several transmitters averaged on the map and works without GPS. In a building one transmitter is installed per 100-200 m2, so the scope of location can be narrowed to the hall and its entrances, without extending it to the whole plant. A wearable device, an active card or a watch, collects less data than a phone, which supports the proportionality argument.
In the DPIA documentation the officer records the alternatives considered and rejected, for example only the entry points to a zone from the access control system, or location only in case of an alarm. Such a record shows the supervisory authority that the choice was not accidental.
Stage 3: risk register and mitigating measures
The third stage is a concrete table of risks for the people whose data is processed. For the hall scenario the officer lists five risks that appear most often and assigns each one a technical or organisational measure consistent with Articles 25 and 32 GDPR.
- Risk of monitoring beyond the purpose: the measure is limiting visibility of the history to the roles that need it, and recording the purposes in an internal act.
- Risk of storage for too long: the measure is a fixed retention period set in advance and automatic deletion once it expires.
- Risk of unauthorised access: the measure is roles in the system and an audit log that records changes to selected data, with the author and the time.
- Risk of employees not knowing: the measure is written information before admission to work and marking of the hall.
- Risk of location covering intimate places: the measure is an explicit decision on toilets, smoking areas and canteens, described in a separate section of the act.
Evidence that the measures work
A DPIA without evidence is only a declaration. That is why for each measure the officer indicates where the trace is: an entry in the work rules, an entry in the audit log, a retention setting, a signed list. A signed employee declaration is not required by statute, but a signed list is a recommended proof for a Labour Inspectorate (PIP) inspection.
Stage 4: consultation, decision and pilot
The fourth stage is consultation. The officer's opinion is recorded in the documentation, and the position of trade unions or employee representatives is taken into account before the act is announced. The model set for an employer includes a legal opinion on location monitoring, an implementation guide, a guide for the employer and a guide for the employee, and a data protection audit carried out by a law firm, so the plant does not start from a blank page.
The management decision follows the DPIA and may be conditional: a pilot in one hall, a review after a set period, and extension only after a new assessment. The legal opinions describe the variant with an app on a company phone; for wearable devices they apply by analogy, and the risk assessment in the DPIA should record this explicitly.
After the decision the order set by the Labour Code applies: announcement of the act, 14 days, written information, marking, start. The officer enters these dates in the schedule and makes sure the system does not start earlier than the act allows.
Conclusions for a plant planning a DPIA
Three practical conclusions follow from this scenario. First, the DPIA is done before the pilot and covers a specific hall, not the whole company. Second, the purposes are split into separate activities, because the SOS alarm has a different legal basis than work organisation. Third, every measure should have evidence that can be shown to an inspector.
On the system side, InnerWeb provides elements that make this evidence easier to produce: an isolated instance, roles and an audit trail. The legal assessment and the decision on scope remain with the controller.
Checklist
Video
Frequently asked questions
Does employee location tracking always require a DPIA?
Article 35 GDPR requires an assessment where processing may cause a high risk. Tracking the location of employees usually meets this condition, so a careful controller assumes a DPIA is needed. The final assessment is made by the controller together with the data protection officer.
Who should carry out the DPIA?
The controller is responsible, and the data protection officer advises. The model set for an employer includes a data protection audit carried out by a law firm, which can be used as a starting point.
Does the DPIA cover the whole company?
It does not have to. In the pilot scenario the assessment covers one hall and its purposes. If the scope is extended, the assessment is updated.
Is a technical description of the system from the vendor enough?
No. The vendor's description helps with the technical measures, but the controller describes the purposes, the legal basis and the proportionality assessment.
Sources
Plan the DPIA before the pilot
Let's talk about the scope of location tracking in your hall and about which data the system must collect and which it must not.
Let's talk