GDPR applies to any organisation processing personal data of EU and UK residents, regardless of sector. Construction organisations face a specific configuration of obligations shaped by the personal data they collect, the regulatory environment they operate in, and the systems they use to do it.
This page covers the GDPR obligations specific to Construction, the lawful bases that apply, and the implementation approach that survives supervisory authority scrutiny.
Regulatory context
Supervisory authority: National supervisory authorities
Key personal data categories: employee H&S records, subcontractor personal data, client project contacts, site access logs
Special category data present: Yes — requires Article 9 lawful basis in addition to Article 6
Primary lawful bases: Legal Obligation (H&S), Contract (employment and subcontracts), Legitimate Interests (site security)
Health and safety records are special category data under Article 9 where they contain health information. The lawful basis is typically Article 9(2)(b) — obligations in the field of employment law — combined with national implementing legislation. Ensure the specific national provision is documented in the ROPA.
The hard part
Mapping personal data across project management tools, site systems, HR platforms, and subcontractor systems — many of which are operated by third parties not under direct IT control.
This is the implementation decision that most Construction GDPR programmes get wrong. It is also the issue most likely to appear in a supervisory authority audit or a data subject complaint.
Required controls
- Article 28 processor agreements with all subcontractors handling personal data
- H&S records classified as special category with explicit lawful basis documented
- Retention schedules tied to project close-out plus statutory limitation periods
- DSAR workflow spanning HR, project management, and finance systems
- Site access log retention limited to security purpose with defined deletion schedule
GDPR gap assessment framework for Construction
A gap assessment for a Construction organisation covers five areas:
1. Data inventory and ROPA
Map every system that holds personal data specific to Construction operations: employee H&S records, subcontractor personal data, client project contacts, site access logs. Document the purpose, lawful basis, retention period, and third-party recipients for each. The ROPA must be current — a snapshot taken at implementation and not updated is not compliant.
2. Lawful basis audit
For each processing activity, confirm the lawful basis is documented and appropriate. Construction organisations frequently find that processing that was assumed to be covered by legitimate interests has not had a Legitimate Interests Assessment completed. Where special category data is present, Article 9 requires a separate documented basis.
3. Consent management
Where consent is the lawful basis, verify that consent records meet GDPR Article 7 requirements: freely given, specific, informed, unambiguous, and withdrawable. Legacy consent from before the current privacy notice version should be assessed for adequacy.
4. DSAR readiness
Test the DSAR workflow with a synthetic request. The test should cover: intake, identity verification, data discovery across all systems identified in the data inventory, response assembly, and delivery within the 30-day deadline. Most Construction DSAR gaps are discovered at the data discovery stage — systems that hold personal data but are not connected to the DSAR workflow.
5. Breach preparedness
Verify the incident log, the severity classification matrix, and the 72-hour notification workflow. The Construction-specific question is: which data categories, if breached, trigger notification to individuals (not just to the supervisory authority)? Notification to individuals is required where the breach is likely to result in high risk to their rights and freedoms.
Implementation priority order
For Construction organisations starting a GDPR programme:
- Data inventory — identify all systems holding personal data before configuring any controls
- Lawful basis documentation — stop processing for which there is no documented basis
- DSAR workflow — rights requests can arrive at any time; the workflow must be operational before launch
- Consent remediation — address legacy consent before running any marketing to the affected population
- ROPA — live, connected to source systems, reviewed quarterly
- Breach procedure — tested annually; DPO and legal team both trained on the 72-hour obligation