Proposal & bid ops

How to anonymise CVs for blind tenders and client submissions

What to mask, what to keep, and how to produce anonymised CVs consistently - so a blind submission is not disqualified by a name left in a page footer.

MCMagicCV TeamProduct & bid operations2 min readPublished 27 July 2026

The same CV before and after masking: identity removed, evidence intact.

Blind submissions fail for boring reasons. Not because the redaction was too light in spirit, but because someone's surname was still in the page footer on page three. Here is a method that survives an evaluator looking for exactly that.

Step 1: Decide what identity means for this tender

Read the tender's own definition before masking anything. It usually falls into one of three levels:

Person-blind: name, photo and contact details removed; firm name allowed
Firm-blind: the above plus your firm's name, logo and template branding
Fully blind: also generalise previous employers and named clients

Masking more than required costs you credibility; masking less can disqualify you. Both mistakes are avoidable in two minutes of reading.

Step 1: identity fields masked, capability evidence untouched - the split that makes a blind CV useful.

Step 2: Keep everything that proves capability

An anonymised CV still has to win. Keep the things an evaluator scores:

Remove	Keep
Full name, photo, contact details	Skills, with levels or years
Employer names (if firm-blind)	Project scope, sector, duration, outcome
Named clients	Generalised client descriptors
Personal identifiers in prose	Certifications with dates, languages

If your anonymised CVs feel weak, the problem is usually that redaction removed evidence along with identity.

Step 3: Fix the mechanical leaks

This is where submissions actually fail. Check every one of these in the exported file:

Headers and footers - often set once and forgotten
File name - anna_kowalska_cv_blind.pdf defeats the point
Document metadata - author, company and last-saved-by properties
Image content - a signature or badge in a screenshot
Page numbering blocks that repeat a name

Step 3: anonymisation applied at export, so masking is a property of the output rather than a manual pass.

Anonymized, multilingual CV packs for public tenders used to take days. We turn them around the same morning now.

CRCamille RouxProposal Lead · Meridian Consulting

Get started free - no credit card, no expiry

Step 4: Use a stable reference scheme

Give each consultant a reference that stays constant across the pack and any later correspondence - Consultant A-114, B-207. Keep the mapping in your own records, never in the submitted document. It makes clarification questions answerable and lets you produce the identified version on request.

Step 4: a pack submitted under stable references, with the identity mapping held outside it.

Tenders that mandate their own personnel form: the blind version still has to land in the buyer's layout.

Step 5: Generate, do not edit a copy

Editing a duplicate is how firms end up with an anonymised CV that is three months behind the real one. Generate the blind version from the same profile, so both stay current and neither is authored by hand.

A two-minute pre-submission check

Open the exported file - not the preview - and search it for each consultant's surname, your firm's name, and any client names. Then check the document properties. If all four come back empty, the pack is genuinely blind.

Start free - 10 candidate profiles and 30 CVs, no credit card.

GDPR by design · EU data residency

Get started free

FAQ

Frequently asked questions

What exactly should be removed from an anonymised CV?

Anything that identifies the individual or your firm when the tender requires it: full name, photo, contact details, and often previous employer names. Keep everything that evidences capability - skills, project scope, sector, dates, certifications and languages.

What is the most common reason a blind submission gets disqualified?

Metadata and page furniture. The body text is redacted but the name survives in a header, a footer, the file name, or the document's author property - and that is enough for an evaluator to set the submission aside.

Should we keep client names in project descriptions?

Usually generalise them: 'a Nordic utility' rather than the client's name. It protects your confidentiality obligations and removes an indirect identifier, while keeping the relevance an evaluator needs.

How do we track who is who once CVs are anonymised?

Assign a stable reference per consultant - Consultant A-114 - and keep the mapping outside the submitted pack. It lets you answer follow-up questions and produce the identified version if the client asks after evaluation.

Is anonymising CVs the same as blind recruitment?

The mechanics overlap but the purpose differs. Blind recruitment reduces bias in hiring decisions; anonymised tender CVs satisfy a procurement rule. The same masking applies, but tenders usually also require a specific format and reference scheme.

Do we need to keep the identified version too?

Yes. Evaluation is rarely the end of the process - contract award, onboarding and reference checks all need the real names. Generate both from one profile rather than maintaining two documents.