The commercial reason, not the diversity one. A candidate who can be identified by the client can be hired directly. Anonymising the CV before it leaves the agency is the cheapest way to keep the fee on the table.
Most write-ups about CV anonymisation frame it as a diversity or bias measure. That is a real motivation in some settings, but it is not the motivation in most UK recruitment agencies, and it is not the reason anonymisation is non-negotiable in perm placement. The reason is money.
A UK perm placement fee is typically fifteen to twenty-five per cent of the candidate's first-year salary. On a £60,000 role, that is £9,000 to £15,000 — earned in a few weeks of work by the recruiter, contingent on the candidate being hired through the agency rather than direct. If the client receives a CV with the candidate's name, email and phone number on it, the client can hire the candidate without the agency and pay nothing. The fee is forfeit the moment the candidate's contact details leave the building.
Anonymising the CV — replacing the candidate's name with a reference code, removing the contact details, scrubbing the LinkedIn URL — is the cheapest way to keep the fee on the table. It is not the only way; many agencies also use written terms with their clients. But the anonymisation is the first line, because it works without anyone having to read the terms.
The change is small and visible at the top of the document: the candidate's name is gone, replaced by a short code (often the agency's reference for the candidate). The contact strip — phone, email, address — is removed. The LinkedIn URL is removed. The body of the CV is unchanged: the candidate's experience, education, skills and achievements are presented in the candidate's own words.
The convention in UK perm is that the reference code is internal to the agency and the client refers to the candidate by code throughout the process. The agency holds the mapping between code and candidate. The client does not know who the candidate is until a face-to-face meeting is scheduled, at which point the candidate's identity is shared under the agency's terms.
Anonymisation is not invisibility. A candidate who has a public LinkedIn profile with their current job title and current employer is identifiable from their CV body alone, especially in a niche role. A senior engineer with three jobs in twenty years at known companies can be narrowed to a short list of people by anyone with a search engine. Anonymisation is a friction layer, not a wall; it slows the client down enough that the agency has time to get in the room.
This is why most UK agencies combine anonymisation with a written agreement: the anonymisation handles the casual bypass, and the agreement handles the deliberate one. Both matter.
Blind-CV programmes for diversity typically remove the candidate's name and a small number of demographic markers (gender, age, ethnicity) and ask the reader to focus on the experience. The motivation is to give the candidate a fairer read. Anonymisation for fee protection removes the same identifying markers for a different reason: to keep the recruiter in the commercial chain.
In practice both motivations lead to similar-looking documents, but they imply different obligations. A blind-CV programme asks the reader to ignore what has been redacted; a fee-protection anonymisation asks the client to ask the agency before identifying the candidate. The first is a request; the second is a workflow.
Under UK GDPR, anonymisation is the right concept if the data can no longer be linked to an identifiable person by any means reasonably likely to be used. Pseudonymisation — replacing the name with a code while the rest of the CV identifies the candidate — is not anonymisation in the UK GDPR sense; it is a security measure. UK GDPR still applies to the pseudonymised CV because the candidate is still identifiable.
For fee-protection purposes this distinction does not usually matter. The agency is the controller, the pseudonymisation is a measure the agency takes within its own processing, and the lawfulness comes from the agency's lawful basis (typically legitimate interests for ongoing candidate work). For more on the GDPR side, see GDPR-compliant CV handling for recruitment agencies.
The most common failure modes, in roughly the order they happen:
Venditas anonymises by default: name, email, phone, URLs are replaced before the CV is rendered into the agency template. The replacement is verified on the rendered document — if an identifier would still be visible the request fails, rather than handing back a document with a contact detail still in it. The reference code is added in the document header so it is the first thing the client sees.
What Venditas does not do is write the candidate's content. The CV body is the candidate's own words. That matters for fee protection because a CV the agency has rewritten is a CV the agency cannot sign for; it also matters for compliance with the UK Consumer Protection from Unfair Trading Regulations, which apply to claims made about candidates.
A few questions worth asking before you change anything: