Blind CV screening hides details such as name, photo, address and date of birth during the first review, so that reviewers judge applicants on skills and evidence. Public trials show mixed results: it can remove one route for bias, but it does not fix unclear criteria and it can remove useful context. Use it as one control among several, and measure the effect in your own process.
Key takeaways
- Blind screening hides identity details in the first pass. It does not make a process fair on its own.
- Evidence from public trials is mixed. Treat it as a tool to test, not a cure.
- Decide in advance what to hide, who hides it and when to reveal it.
- Hidden details can still leak through proxies such as school names, club membership, and writing style.
- Combine blind review with written criteria, an evidence sheet, two reviewers on a sample and outcome checks.
What blind recruitment is
Blind recruitment, also called anonymised or name-blind screening, removes some or all personal details from an application before the first reviewer sees it. The idea is simple: if a reviewer cannot see a name, a photo or an age, those details cannot trigger a conscious or unconscious judgement. The reviewer scores the work history, skills and evidence against the job criteria. Later in the process, after a shortlist is chosen, the details are revealed.
Blind screening is different from a structured process. A structured process asks the same questions and uses the same scoring for everyone. Blind screening hides some information. You can use both. See our guides on structured screening and how to reduce bias in resume screening.
Does it work? What public trials found
Evidence from public programmes is mixed. Two examples show why you should test the method before you rely on it.
| Trial | What was tested | What was reported |
|---|---|---|
| Public Service Commission of Canada, name-blind pilot, 2017 | 27 recruitment processes, April to October 2017, comparing anonymised and non-anonymised screening | The overall rate of applicants screened in fell from 48.3 percent to 43.3 percent with anonymisation. For visible-minority applicants, the rates were 47.3 percent and 46.0 percent, not significantly different. The report notes limits, including that reviewers knew they were in a pilot. See the PSC report |
| Australian Public Service trial | More than 2,100 public servants shortlisted candidates for a hypothetical role, with some applications anonymised | The summary advises caution before assuming that blind review improves diversity outcomes. See the Australian government report summary |
Do not read these results as proof that blind screening never helps. They show that effects depend on context, on who reviews and on what else changes. They also show that removing details does not remove all bias. A fair process needs several controls.
What you can hide, and what it does
| Detail | Why consider hiding it | Limit |
|---|---|---|
| Name | May signal sex, ethnicity or origin | Sometimes needed to match records later |
| Photo | Shows face, age, sex, ethnicity, disability | Rare in US and UK CVs; common in some countries. Better not requested at all |
| Address or postcode | Can signal class, race or origin | Location may matter for a commute or legal reasons |
| Date of birth and graduation years | Signals age | Years of experience may still show age |
| Gender, marital status, nationality | Protected or sensitive traits | Should not be in an application at all |
| School and university names | Can signal class or background | Qualifications may be a real requirement |
| Hobbies, clubs, volunteer groups | May signal religion, politics or background | Can also show real skills |
| Employment gaps | May relate to caring duties, health or study | Hiding dates can hide useful chronology |
Decide the list for each role. Hide only what you do not need for the first pass. Keep qualifications that are a legal or practical requirement. If a requirement uses a degree, state exactly which one and why.
How to run blind screening in six steps
Step 1: Write the criteria first
Blind review needs clear criteria. Without them, reviewers use their own guesses. Write three to five must-haves that can be checked on a CV. See must-haves vs nice-to-haves.
Step 2: Choose who removes the details
Use someone who is not on the review panel, or software that can hide fields. A person who redacts must work carefully and consistently. Give them a one-page rule list. If you use software, test it on five CVs to see what it misses.
Step 3: Create a clean review copy
Give each applicant a code instead of a name, for example A-014. Keep a private key that links the code to the applicant. Store the key separately and give access only to the person who needs it.
Step 4: Review with an evidence sheet
Reviewers mark each must-have as yes, no or unclear, and note the CV passage that supports it. They do not judge writing style beyond the clarity needed for the job.
Step 5: Reveal at a fixed point
Reveal identity only after the shortlist is chosen. Record the date. Do not go back and change scores after the reveal.
Step 6: Check the result
Compare pass rates by stage with and without blind review where the law allows monitoring. Ask reviewers whether the blind copy gave enough information. Adjust the list of hidden details after the first search.
Redaction checklist
| Item | Done? |
|---|---|
| Name replaced by a code | |
| Photo removed | |
| Address reduced to a general area, or removed | |
| Date of birth, age, graduation years removed (where not needed) | |
| Gender, marital status, nationality fields removed | |
| Names of clubs or groups that signal protected traits removed | |
| Contact details removed | |
| Links to social profiles removed | |
| File name and document properties cleaned (they can contain names) | |
| Key stored separately |
Where hidden details leak back in
- Proxies. A school, a language, an interest or a postcode can still point to a person’s background.
- Writing style. Spelling variants, phrases and format can hint at origin or age.
- Work history dates. A long career shows age even without a birth date.
- Narrative details. “Returned after parental leave” or “managed my disability” tell the reviewer something personal.
- Reviewer familiarity. In a small field, the reviewer may recognise the person from the work.
You cannot remove all of these without removing useful information. Aim for a reasonable first pass and combine it with the other controls. Do not ask applicants to remove factual information about their careers. Do not penalise people who include details.
Legal and data protection notes
Blind review does not replace anti-discrimination law. You must still not decide on protected characteristics at any stage. In the UK, the Acas page on recruitment explains fair process. In the US, the EEOC describes prohibited practices on its page about prohibited employment policies and practices. In the EU, equal treatment is set by directives and national laws; see Directive 2000/78/EC and Directive 2000/43/EC. The key list that links codes to names is personal data. In the UK and EU, apply data protection rules: limit access, keep it secure and delete it on schedule. See the ICO employment guidance.
A worked example (fictional)
This example is invented. A company receives 160 applications for an analyst role. The recruiter writes four must-haves and a one-page redaction rule list. An assistant who is not on the panel replaces names with codes, removes photos and addresses, and deletes graduation years. Two reviewers use an evidence sheet. After the first pass they compare 15 CVs they both reviewed. They disagree on three. The disagreements are all about “uses data tools”, where the CV wording was unclear. They rewrite the criterion to say which tools count, and re-score. They shortlist 18 applicants, reveal the identities, and invite 12 to a screen. The recruiter records the pass rate at each stage. After the search she sees no pattern she cannot explain, but she also notes that two reviewers said they missed the context of university projects. She decides to keep university names visible in future rounds, because the role accepts graduates. The test taught her which details matter for this role.
When blind screening fits, and when it does not
| Situation | Fit | Comment |
|---|---|---|
| High-volume roles with clear criteria | Good | Easier to redact and compare |
| Roles where a licence or degree is mandatory | Partly | Keep the legal requirement visible |
| Small teams where reviewers know the field well | Limited | Reviewers may recognise people |
| Roles that need a portfolio or public work | Limited | Work samples show identity; use work sample review instead |
| Internal moves | Limited | People are known; use structured evidence instead |
Blind screening is easy to explain and cheap to try. Try it on one search and measure. If it removes a source of doubt for your team, keep it. If it adds work with no benefit, drop it and put the effort into criteria, evidence and checks.
Alternatives and additions to hiding details
If hiding details is hard in your setting, other controls address similar risks. They also work well alongside blind review.
| Control | What it does | Effort |
|---|---|---|
| Evidence sheet with a CV passage for each yes | Directs attention to what the CV shows about each must-have | Low |
| Work sample, scored without names | Gives direct evidence of a skill; can be scored anonymously | Medium. See work sample tests |
| Structured interview with the same questions | Makes later stages comparable | Medium. See structured interviews |
| Two reviewers on a sample | Finds inconsistent marking | Low |
| Outcome monitoring where the law allows | Finds patterns you cannot see in single decisions | Medium |
| Clear, job-related criteria | Removes guesswork | Low. See checkable requirements |
Tools that show each job requirement next to the exact CV passage that supports it follow the same logic: they draw the reviewer’s attention to evidence. FastHire is being built on that approach. It is coming soon, it does not rank, score or reject candidates, and people make every decision.
What to tell candidates
Be open about your process. In the job ad or the privacy notice, say whether you review applications without names at the first stage. Explain why you ask for the information you collect and when you will see it. If you collect diversity or monitoring data, say it is separate from the hiring decision and optional where the law allows. Candidates trust a process that is explained, and they can ask for adjustments if they need them.
Do not claim that your process removes bias. Say that you use several controls to reduce it. Overclaiming harms trust if a candidate later finds a gap.
Questions to ask before you start
- What problem are we trying to solve: names, school, age, or something else?
- Which details are not needed for the first pass?
- Who will redact, and how will we check their work?
- How will we reveal the details, and when?
- How will we measure the effect, and what will we do if we see no change?
- Who owns the key that links codes to names, and how long will we keep it?
Write the answers in one page. If you cannot answer them, delay the pilot until you can. A small, well-planned test teaches more than a large, loose one.
Frequently asked questions
What is blind CV screening?
It is a method where identity details such as name, photo and address are hidden from the first reviewer, so that they judge skills and evidence.
Does blind recruitment increase diversity?
Public trials give mixed results. It may help in some settings and not in others. Test it in your own process and combine it with other controls.
Is blind screening legal?
Yes, as a process choice. You must still follow anti-discrimination and data protection laws. This is general information, not legal advice.
What should I hide?
Only what you do not need for the first pass: name, photo, address, date of birth, graduation years and similar details. Keep qualifications that are a real requirement.
Can software do blind screening?
Some tools can hide fields. Test what they miss, and keep people in charge of the decision.
Related guides
- Hiring guides for fair and compliant hiring
- How to reduce bias in resume screening: 15 practical steps
- Structured screening: how to compare every applicant on the same evidence
- Must-haves vs nice-to-haves
- All hiring guides for employers
- Adverse impact and the four-fifths rule explained
- Race, ethnicity and national origin in hiring: what the law says
- How to run an inclusive sourcing process
This is general information, not legal advice.