Legal and organizational documents
The first group consists of documents without which launching location violates the Labour Code or the GDPR. The internal act (regulations, a collective agreement or a notice) must be announced 14 days before the start. The written information reaches the employee before admission to work, and the marking of the area stands no later than the day before launch.
This group also includes the data protection impact assessment. GDPR Article 35 requires a DPIA when processing with new technologies may cause a high risk, and location usually qualifies.
- Internal act with purposes, scope of areas and retention period (Article 22(2) § 6-10 applied accordingly).
- Separate paragraph on the alarm function (Article 207 § 2 of the Labour Code).
- DPIA with conclusions and a risk reduction plan.
- Written information for employees consistent with GDPR Article 13.
GDPR and security documents
The second group documents compliance over time. The register of processing activities under GDPR Article 30 must include location as a separate activity, and for people from external companies as a separate entry based on Article 6(1)(f) GDPR read together with Articles 208 and 304 of the Labour Code.
The principle of data protection by design (Article 25) and the measures of Article 32 have their own proof: a description of the architecture, access control to data and a list of authorized persons. An isolated instance with its own database and its own mail, in Docker containers, also on the client's server, simplifies the description of the place of processing and the scope of access.
- Register of processing activities: location of own employees and location of people from external companies as separate entries.
- Description of architecture and place of processing for the DPIA and the register.
- List of persons with access and the scope of their permissions.
- Contracts with processors, if any.
Checklist items by group
Proof that is most often missing
A signed employee statement of familiarization with the information is not required by statute, but lists with signatures are recommended as evidence in case of a PIP inspection. The inspector most often lacks exactly these lists, or proof that the information was delivered to people who joined after the act was announced.
The second common gap is consistency of the retention period. Compare the value in the act, in the information, in the register and in the system configuration. The third is the change log: the audit trail records changes to permits, rules and patrol routes together with the author and the time, which provides proof of accountability, but only if the administrator knows which objects are audited.
How to use the checklist: order and owners
First the legal bases (act, DPIA), then information and marking, and finally the register and the proof. Assign each item an owner: legal department, HR, DPO, health and safety, IT. Set the date of the final check for the day before launch and record its result. After 30 days return to the list: the scope or the period may have changed during the pilot.
Checklist
Video
Frequently asked questions
Is a DPIA alone enough, without an internal act?
No. The DPIA assesses risk, while the act is a requirement of the Labour Code applied accordingly to location. Both documents are needed.
Does the checklist also cover a request from the inspector?
The data protection officer takes part in the DPIA and the register of processing activities. Record their comments and keep them in the documentation.
How often should the documents be updated?
With every change of scope, purpose, retention period or supplier, and after the review 30 days after launch.
Sources
Let's run a trial review of the documents before launch
In a meeting we will go through this checklist with your data protection officer and point out gaps. Book a conversation with the InnerWeb team.
Let's talk