Never hand-redact a CV for a tender again.
One-click blind CVs for public tenders and blind recruitment - the same anonymization rules applied to every consultant, every time.
The problem today
The tender annex says CVs must be anonymized, so someone spends an afternoon in Word deleting names, photos, and email addresses from 10 documents. Then the problems start: a name survives in a header on page 3, the document properties still say who authored the file, and one team member's idea of "anonymized" - initials kept, employer names removed - doesn't match another's. In a public tender, one leaked identifier can get a submission challenged; in blind recruitment, it defeats the entire point. MagicCV makes anonymization a property of the export, not a manual editing pass. You configure once what counts as identifying for your process - name, photo, contact details, whatever your evaluations require - and toggle anonymization on any CV. Because the blind CV is generated fresh from the structured profile rather than redacted from an old file, there are no leftover headers, metadata, or missed mentions to worry about.
How MagicCV does it
Start from any CV - standard or tailored
Generate the consultant's CV as usual, including a version tailored to the specific tender. Anonymization is a switch on top of any output, not a separate document you maintain.
Toggle anonymization - your rules, applied automatically
Flip the anonymization toggle and MagicCV removes every detail your configured rules treat as identifying: name, photo, contact details, and anything else your evaluation process requires. The same ruleset applies no matter who on the team generates the CV.
Export clean blind CVs, singly or as a full pack
Export the anonymized version in your brand template as PDF or Word - for one consultant or the whole bid team at once. Because each file is generated from profile data, there's no residue from an original document to slip through.
Outcome
Before: an afternoon of manual redaction per tender, and a low-grade fear that a name survived in a footer. After: the blind version is one click, identical in standard to every other blind CV your firm has ever produced. Anonymization stops being a task and becomes a setting.
“The RFP-to-CV reasoning is the part that surprised me. It surfaces the exact projects that match the brief instead of a generic profile dump.”
Tomas Lindqvist
Head of Delivery · Lindqvist & Co
Frequently asked questions
What exactly gets removed from a blind CV?
Whatever your rules say. Typically name, photo, and contact details; many teams also strip other markers their evaluation process treats as identifying. You configure the ruleset once and it applies to every anonymized export, for every consultant.
Can a name still leak through in a header, footer, or file metadata?
This is the advantage of generating rather than redacting. A blind CV from MagicCV is built fresh from the structured profile with the anonymization rules applied - it isn't an edited copy of an old Word file, so there are no leftover headers, tracked changes, or document properties carrying the original author's name.
Will every team member's anonymized CVs follow the same standard?
Yes. The rules live in the ruleset, not in individual judgment, so the blind CV produced by a junior bid coordinator on Friday evening matches the one a partner would produce. For public tenders where inconsistent anonymization can void a submission, that uniformity is the point.
Can we anonymize a whole proposal team at once?
Yes. Build the CV pack for the bid, apply anonymization, and export - every CV in the pack follows the same rules and the same brand template. A 10-person tender pack is one pass, not 10 redaction jobs.
Does this work for blind recruitment as well as tenders?
Yes. Staffing and recruitment teams use the same toggle to send blind CVs to clients - candidates evaluated on experience and skills before a name or photo enters the conversation. Same mechanism, same consistency.
How does anonymization fit our GDPR obligations?
It's one piece of a data-minimization posture: sharing only the personal data a process actually needs. MagicCV itself is GDPR-first with EU data residency, and Enterprise adds audit logs and a DPA. Blind CVs reduce what leaves your firm; the platform governs what stays inside it.
Do anonymized CVs keep our brand template?
Yes - the blind version exports in the same pixel-consistent template as any other CV, minus the identifying details. If a tender requires a neutral or client-specified layout instead, export in a template set up for that.
Is anonymization available on every plan?
Anonymized exports are generated CVs like any other, counting toward your plan's allowance - 30 CVs on Free, 600 on Pro ($50/month), unlimited on Enterprise. You can test the full blind-CV workflow on the Free plan before a real tender depends on it.
From scattered CVs to a polished, on-brand pack in minutes.
See it on your own consultants, or start free today - no credit card.
GDPR by design · EU data residency · Free plan, no credit card