From niche request to standard practice
Blind CV shortlists used to be a niche request from a handful of public-sector clients. Today they appear in RPO tenders, graduate programmes, diversity commitments and retained search briefs. For many agencies the question is not whether to offer them — it is how to produce them without adding hours of manual redaction to every assignment.
What a blind CV actually is
A blind (or anonymised) CV is a version of a candidate's CV with identifying information removed or masked, so the reader evaluates skills, experience and achievements before they know who the person is. It is not a different CV — it is the same profile with specific fields hidden. That matters, because you should never have to maintain two separate documents for one candidate.
Why clients ask for them
- Reducing bias in early rounds. Names, photos, ages, addresses and school names can all trigger unconscious assumptions.
- Tender and framework requirements. Public-sector and RPO contracts may require anonymised submissions.
- Candidate confidentiality. Currently employed or senior candidates often cannot risk being identified early.
- Protecting the agency relationship. Without contact details, a client cannot easily approach a candidate directly before terms are agreed.
Which fields to remove
| Field | Remove? | Notes |
|---|---|---|
| Name | Always | Replace with a candidate reference such as "Candidate 04". |
| Email, phone, address | Always | Check headers, footers and signature blocks too. |
| Photo | Always | Common on CVs from some regions. |
| Date of birth, age, marital status | Always | Rarely relevant and often sensitive. |
| LinkedIn and personal URLs | Always | A link instantly identifies the candidate. |
| Employer names | Depends | Mask with a descriptor such as "global consultancy". |
| Universities and schools | Depends | Mask for education-blind processes; keep the qualification. |
| Location | Depends | Generalise to region or country. |
Which fields to keep
Over-anonymising is a real risk. If you strip out so much that a hiring manager cannot judge relevance, the shortlist fails for a different reason. Keep:
- Job titles, seniority and scope of responsibility
- Industry or sector context, even if the employer is masked
- Time in each role
- Achievements, projects and measurable outcomes
- Qualifications, certifications and memberships
- Languages and right-to-work status where relevant
Confirm with the client exactly which fields must be hidden before the first CV goes out. Save those rules so every consultant on the account applies them the same way.
A workflow that doesn't slow you down
Manual redaction — opening each Word file, deleting details, checking headers, saving a copy — is slow and fragile. One forgotten email address in a footer undoes the exercise. Treat anonymisation as an export setting instead:
- Format every CV normally into your branded template, so the full profile lives in one place.
- Apply your saved anonymisation rules on export — for one CV or a whole batch.
- Send the blind version as PDF, Word or a secure link.
- Keep the original in your vault, ready to reveal when the client progresses the candidate.
Because the document is rebuilt from structured data rather than edited, stray details in the original file do not carry through. With FormatMyCV's anonymisation this takes one click, and bulk batches can be anonymised at once.
Using candidate references well
A good reference scheme keeps blind shortlists usable:
- Use short, neutral codes ("Candidate A", "C-04") — not initials.
- Keep the same reference for a candidate throughout the assignment.
- Use the reference in file names, email subjects and interview notes.
- Record the mapping from reference to candidate in your ATS, not in the document.
Common mistakes to avoid
- Forgetting file names. "Jane_Smith_CV.pdf" gives the game away.
- Identifying achievements. "Led the IPO of [well-known company]" may identify a senior candidate; generalise where needed.
- Hidden metadata. Author fields in Word and PDF properties can contain the candidate's name.
- Inconsistent rules. If one consultant removes schools and another does not, the shortlist is not truly blind.
- Email signatures. Forwarding the candidate's own email with the CV attached reveals everything.
Revealing candidates at the right time
Agree the reveal point with the client — usually when they decide to interview. At that point, send the named version from the same master profile so the documents match exactly. Keeping the original in a secure vault means no re-uploading or reformatting.
Measuring whether blind shortlists work
If blind shortlists are part of a DE&I commitment, agree what you will measure with the client:
- Diversity of candidates progressing from shortlist to interview, compared with named shortlists
- Time from shortlist to interview decision
- Hiring-manager satisfaction with the quality of information on blind CVs
- Number of anonymisation errors caught before sending (target: zero)
A blind shortlist checklist
- Rules agreed with the client and saved
- Every CV in the same template
- Names replaced with consistent references
- Contact details, photos, links and dates of birth removed
- Employers, schools and locations masked if required
- File names and document properties checked
- Named originals held securely for reveal
