UK GDPR matters in architecture recruitment because hiring creates a lot of personal data very quickly: CVs, portfolios, contact details, salary expectations, right-to-work information, interview notes and sometimes sensitive context.
This guide is not legal advice. It is a practical reminder for architecture employers to keep recruitment data clear, limited, secure and respectful, then check the ICO guidance or a data protection adviser where needed.
Watch: how architecture recruitment works behind the scenes
This Architecture Social conversation is useful because recruitment data only makes sense when you understand the real flow of candidates, recruiters, clients and hiring decisions.
Why recruitment data needs care
Candidates trust employers and recruiters with information that can affect their career. A CV might include employment history, education, location, contact details and sometimes personal circumstances. Interview notes can be even more sensitive if they are careless or subjective.
The ICO has specific recruitment and selection guidance. Use that as the official reference point for your process.
The principles in plain English
You do not need to become a data lawyer to improve your recruitment process. Start with the principles that shape good behaviour.
- Be clear with candidates about what you collect and why.
- Only collect what you genuinely need for recruitment.
- Keep information accurate and up to date where it affects a decision.
- Do not keep candidate data indefinitely just in case.
- Store CVs, notes and portfolios securely.
- Be able to explain your process if challenged.
Listen: recruitment process and candidate trust
This episode adds more context on how architecture recruitment works behind the scenes, and why trust, clarity and communication matter throughout the process.
What data do you actually need?
Architecture hiring can become messy because portfolios, CVs and project examples travel between hiring managers, directors, HR, recruiters and sometimes clients. Keep the process tight.
- CV and portfolio for assessing role fit.
- Contact details for communication.
- Salary expectation, notice period and location or hybrid preferences.
- Interview notes linked to the selection criteria.
- Right-to-work checks at the appropriate stage.
- References only when needed and handled transparently.
Lawful basis and transparency
You need a lawful basis for processing recruitment data. Consent is not always the neat answer people think it is, especially where there is an imbalance between candidate and employer.
Read the ICO’s lawful basis guidance and make sure your privacy notice explains how recruitment data is used, shared and retained.
Working with recruiters
If you use a recruiter, be clear on what data is being shared, why it is being shared and who is responsible for what. A good recruiter should not spray CVs around the market or send candidate details without a sensible reason.
- Agree what information should be shared at shortlist stage.
- Avoid sending portfolios widely unless the candidate understands the route.
- Keep interview feedback specific and role-related.
- Do not ask for unnecessary personal information early in the process.
- Record decisions in a way that would still look fair if the candidate asked to see them.
Retention and deletion
Recruitment teams often keep CVs because future roles might appear. That can be legitimate if handled properly, but it should not become an endless archive with no retention rule.
- Decide how long unsuccessful candidate data is kept.
- Tell candidates if you want to keep their details for future roles.
- Remove or anonymise data when it is no longer needed.
- Keep interview notes factual and tied to selection criteria.
- Review shared folders, inboxes and downloads, not only the ATS.
Common mistakes
- Keeping every CV forever because it might be useful one day.
- Writing subjective interview notes that do not relate to the role.
- Sharing portfolios around a practice without a clear reason.
- Using vague privacy wording that candidates cannot understand.
- Forgetting that email inboxes and downloaded files are part of the data trail.
Architecture Social view
Stephen’s recruiter view is that GDPR should make recruitment cleaner, not colder. Candidates deserve clarity, and employers make better decisions when their process is structured, factual and respectful.
For the hiring side, pair this with the architecture job advert guide. Clear role criteria usually means cleaner candidate data and better interview notes.
Next step
Before your next hiring round, review where CVs, portfolios, interview notes and recruiter emails are stored. If you need help tightening the brief and the candidate flow, explore Architecture Social recruitment consultancy.
Add a comment