Step 1: set the legal regime and the purposes
Employee location is another form of monitoring under Article 22(3) § 4 of the Labour Code, and under § 3 Article 22(2) paragraphs 6 to 10 apply to it accordingly. Start by writing down the purpose: location for responding to events, for evacuation lists, for work permits. Do not carry over the purpose 'security' from Article 22(2) § 1, because that concerns video monitoring.
Describe the SOS alarm and motionlessness detection as a separate purpose based on Article 207 § 2 of the Labour Code. Templates of acts for wearable devices contain a separate paragraph on the alarm function, so this is the right place for the entry.
Step 2: assess the risk and prepare a DPIA
GDPR Article 35 requires a data protection impact assessment when processing, especially with new technologies, may cause a high risk. Employee location usually qualifies, so the DPIA is done before the act, not after it. Its conclusions affect the scope of zones and the retention period.
Apply also the principles of GDPR Articles 25 and 32: data protection by design and by default, and technical measures adequate to the risk. In practice this means choosing the minimum scope of data, for example a wearable device instead of a phone, because it collects less data.
Implementation timeline: days before and after announcing the act
Step 3: the internal act and disputes over zones
Article 22(2) paragraphs 6 to 10 require an internal act: regulations, a collective agreement or a notice. Write in it the purposes, the scope of areas, the retention period and the people authorized to access the data. Do not forget a separate paragraph on the alarm.
The most common point of dispute with trade unions is sanitary rooms, smoking areas and canteens. They may be covered by location, because Article 22(2) § 2 does not apply here, but this requires an explicit entry in the act and additional signage. Many plants exclude these places from the scope to avoid a dispute and shorten the path to launch.
Step 4: announcement, 14 days and written information
14 days must pass between announcing the act and launching location. During this time you prepare the written information, which the employer hands over before the employee is admitted to work (Article 22(2) § 8). The content of the information also meets the requirements of GDPR Article 13: the identity of the administrator, purposes and basis, retention period and the rights of the person.
A signed acknowledgement of familiarization is not required by statute, but lists with signatures are recommended as evidence in case of a PIP inspection. For a large workforce, plan several information sessions across shifts, so that the list is complete by the launch date.
Step 5: marking the area and technical tests
You mark the area covered by location no later than the day before launch. The marking should match the scope in the act: if the act covers the hall and plant roads, the signs stand at their entrances. Sanitary rooms covered by location require additional marking.
In parallel the technical team checks coverage. The position is determined from the signals of several beacons averaged on the map and works without GPS; in a building one beacon is installed per 100-200 m2, and on plant roads a beacon about every 100 m. Save the test result as proof that the actual scope matches the act.
Step 6: launch, register and review
On the start day you have the full set: the act, the DPIA, the information and the marking. Enter the activity in the register under GDPR Article 30 and confirm the retention period. After 30 days, carry out a review: number of alarms, complaints, changes of scope. Treat a change of scope as a new announcement with 14 days.
Checklist
Video
Frequently asked questions
Can the 14-day term be shortened?
No. The period results from Article 22(2) paragraphs 6 to 10, applied accordingly to location. What can be shortened is the time needed to prepare documents, not the term itself.
What if a new employee joins after launch?
Written information is provided before admission to work, so the new person receives it on the first day, before starting work in the area covered by location.
Does every change of settings require a new act?
A change of scope, purposes or retention period changes the act and requires a new announcement. Minor technical changes without an effect on scope are documented in the register of changes.
Sources
Let's plan the location launch schedule
Together with your legal and HR departments we will prepare a timeline from the act to the start and a plan for hall coverage tests. Book a conversation with the InnerWeb team.
Let's talk