Blind CV: What It Is and How Agencies Produce One at Scale

A blind CV is a candidate CV with personal identifiers removed (name, photo, contact details, age, and anything that signals gender, ethnicity, or background) so the reader evaluates the person on skills and experience alone. It is also called an anonymized CV or a blind resume. The professional history stays fully visible. Only the details that trigger conscious or unconscious bias come out.

For a staffing agency the blind CV is not a diversity slogan, it is a deliverable. More clients now ask for anonymized submissions on the first pass, and the agencies that can produce one in seconds win those briefs. The ones still redacting by hand quietly stop bidding for them. This guide covers exactly what a blind CV removes, what it keeps, when you get asked for one, and how to produce it at scale without adding a manual step to every candidate.

What a blind CV removes and what it keeps

The mistake most first attempts make is treating “blind” as “delete the name”. A name is the obvious identifier, but callback studies replicate across the UK, France, Germany, and Sweden precisely because so many other fields carry the same signal. The scope is wider than it looks.

Removed (identifying)	Kept (job relevant)
Full name, replaced with a candidate reference	Job titles and employers
Photo and profile links (LinkedIn, personal site)	Dates and duration of each role
Address, postcode, nationality	Skills, tools, and certifications
Date of birth and graduation years (age proxies)	Measurable achievements and results
Gender markers and personal pronouns where they signal identity	Industry sector and seniority
University or school name where prestige bias applies	Languages spoken (the skill, not the origin cue)

The rule of thumb: if a field helps a client judge whether the person can do the job, it stays. If it only tells them who the person is, it goes. Keep the redaction consistent across every candidate, because inconsistency is what makes a shortlist comparison meaningless.

When a client asks you for a blind CV

Three situations put this request on your desk, and they are increasingly common.

Public sector and regulated clients. Government employers run anonymized recruitment programs as policy. Canada’s federal Public Service Commission ran a formal name-blind recruitment pilot, and public bodies across the UK and France have tested or adopted the practice. When you supply into those frameworks, an anonymized first submission is often part of the specification, not a preference.

Enterprise DEI requirements. Large corporate clients increasingly hold their staffing partners to diversity reporting, and a growing number ask for anonymized candidate submissions on the initial screen so their own hiring managers judge on capability first. If you cannot deliver that format, you are a harder partner to keep on the panel.

Your own quality control. Some agencies anonymize internally before a consultant shortlists, to keep their own recommendations defensible. It is cheaper to bake fairness into the process than to defend a pattern in your placements later.

How to produce a blind CV at scale

Manual anonymization is where good intentions die. Deleting a name in Word takes a minute, but doing it consistently across fifty candidates a day, catching every pronoun and address and graduation year, then reformatting each one into the client template, is not a minute. It is the whole afternoon. So the practical question is not “how do I anonymize a CV” but “how do I anonymize every CV without adding a step”.

The answer is to let the same engine that already reads and reformats the CV do the redaction, because it already knows which field is the name, the photo, and the date of birth.

This is where anonymization stops being a chore and becomes a byproduct. Because a CV parser already extracts structured fields, it knows the name is a name and the photo is a photo. Removing those is a switch, not a re-read. In Saply the same upload that reformats a CV into your client’s template can drop the identifying fields in the same pass, so an anonymized submission costs no extra time over a normal one. Keep the original on file, of course, so you can reveal identity once the client shortlists.

What blind CVs actually do, and where they stop

Sell this honestly to clients, because overselling it is how the practice gets discredited. The evidence is real but partial.

On the positive side, the strongest demonstration comes from orchestra auditions: when musicians played behind a screen, the share of women advancing rose sharply, a result documented by Harvard Business School. Removing the identity cue changed who got through.

The caveat is just as important. Canada’s federal name-blind recruitment pilot found that anonymized screening actually decreased screen-in rates in some processes compared with full-information review, and published that finding openly in its final report. Blind CVs also do nothing about bias at the interview, where identity becomes visible again, and subtle cues can leak through writing style or career gaps that no redaction catches.

Blind CVs and GDPR data minimization

There is a compliance angle European agencies should not miss. The GDPR requires that personal data be “adequate, relevant and limited to what is necessary” for the purpose. If a client’s hiring manager does not need a candidate’s name, photo, or date of birth to judge fit at the first screen, sending only what the assessment requires is data minimization in practice.

To be precise: GDPR does not mandate blind CVs. It permits and encourages minimizing what you share. That distinction matters when a client’s data protection officer asks why full personal profiles are circulating before anyone has decided to interview. Being able to answer that you submit anonymized first, and reveal identity only when the client engages, is a stronger position than most agencies can claim. It sits naturally alongside the other data questions clients now ask, which is why where and how candidate data is processed belongs in the same conversation.

Frequently asked questions

Is a blind CV the same as blind resume screening?

They are two sides of the same practice. A blind CV is the anonymized document. Blind resume screening is the process of reviewing candidates using those documents. The CV is what you produce and submit, the screening is what the client does with it.

What exactly should be removed from a blind CV?

Name, photo, contact details, address, date of birth, and graduation years, plus any field that signals gender, nationality, or ethnicity. Job titles, employers, dates of employment, skills, certifications, and achievements all stay. When in doubt, keep anything that helps assess the work and remove anything that only identifies the person.

Do blind CVs actually reduce hiring bias?

They reduce bias at the initial screen, which is where identity cues do the most harm, and controlled studies like blind orchestra auditions show a clear effect. They do not fix bias at later stages such as interviews, and at least one government pilot found no screening improvement. Treat them as one control among several, not a complete solution.

Are blind CVs required by law?

No. Neither the EU nor the UK mandates anonymized CVs for private staffing agencies. Some public sector and enterprise clients require them as part of their own recruitment policy, and GDPR data minimization encourages sharing only the personal data an assessment needs, but the practice itself is voluntary for private employers.

How do agencies create blind CVs without slowing down?

By anonymizing inside the tool that already parses and formats the CV, rather than editing each document by hand. When the software has already identified which field is the name or photo, removing those fields is automatic and adds no time to the submission. Manual redaction is what makes blind CVs feel expensive.