How-To Guide

CV Redaction Software for Staffing Agencies: How to Test It Before You Trust It With Client Submissions

November 20, 2026iReformat Team10 min read
cv redactionblind resumecandidate anonymizationstaffing agencies

Quick Summary

TL;DR

Test redaction on 10 of your hardest CVs, in your own template, against a written rule. Check the filename, headers, hyperlinks, photos, and document properties. Keep the full CV in the ATS and create the redacted copy when you submit.

Key Facts

Test set

10 hard CVs

Check

Links, files, photos

Workflow

Redact at submission

Pricing

Shared in the demo

Key Takeaways

  • Write the redaction rule before the demo, then score every output against it.
  • A clean header can still leak a name in the filename, a hyperlink, or the file properties.
  • Keep the full CV in the ATS. Create the redacted, branded copy per client submission.
  • iReformat works one submission at a time, in the template we set up for you.
  • Pricing is custom and volume-based, with unlimited users, and shared in the demo.

Short answer: Good CV redaction software for a staffing agency does three things reliably: it removes the identifiers you choose (name, contact details, LinkedIn, personal sites, photo) from every place they appear in the document, it puts the result into your client-ready template without breaking the layout, and it fits the point in your workflow where submissions actually go out. The only way to know whether a tool does all three is to test it on your own messy CVs, in your own template, before you sign anything. This guide gives you that test.

If you're still deciding what to redact, start with our guide to blind resume formatting and GDPR. If you're deciding whether to offer blind submissions at all, read how blind resumes fit a DEI recruiting program. This piece assumes you've made those calls and now need a tool you can trust.

Why agencies buy redaction software in the first place

Most agencies come to redaction for one of three reasons, and it's worth knowing which one is yours, because it changes what you test.

  1. Fee protection. You don't want a client finding your candidate on LinkedIn and hiring them around you. Here the critical items are the name, phone, email, LinkedIn URL and anything else that makes the person searchable. (Our candidate anonymization use case covers the backdoor-hiring problem in more detail.)
  2. Client-requested blind screening. A client wants first-round CVs without names or photos. Here consistency matters most: every CV in the shortlist has to be anonymized the same way, or the exercise falls apart.
  3. Data minimization. You're sending CVs to clients, tender panels or partners and want to share only what the reviewer needs. Here you care about what leaves the building. What your obligations actually are is a question for your own legal or compliance advisor, not your software vendor.

Write down which one applies before your first demo. A tool that's fine for reason 1 can still fail reason 2.

Where redaction quietly fails

Removing a name from the top of a CV is easy. The failures happen everywhere else. These are the places I'd check on any tool, including ours.

  • The filename. "Jane_Smith_CV_final.docx" undoes a perfect redaction. Check what the output file is called and whether your team renames it.
  • Headers, footers and text boxes. Many candidate CVs put contact details in a Word header or a floating text box. Some tools read the body text and miss these.
  • Hyperlinks. The visible text says "LinkedIn profile" but the link underneath still points to the candidate's URL. Click every link in the output.
  • Body-text mentions. "References available from Jane's manager", a portfolio URL in a project description, a personal email inside a cover note pasted into the CV. Find out exactly where the tool looks. iReformat, for example, documents that names are removed from headers and contact sections while company names and job titles stay, so a name buried in a paragraph is something to test, not assume.
  • Photos and logos. Especially on CVs from markets where headshots are common.
  • Document properties. The original author's name can sit in the file's metadata. If you send Word files rather than PDFs, check File > Info on the output.
  • Indirect identifiers. A rare job title at a small, named company can identify someone as clearly as a name. Software won't decide this for you. Your recruiter has to judge it per role.

None of these mean a tool is bad. They tell you where your recruiters still need a 30-second check.

A redaction test you can run in one demo

Here's the test I'd run. It takes about an hour of prep and turns a sales demo into an actual evaluation. (The resume formatting software demo checklist covers the rest of the evaluation; this adds the redaction-specific part.)

1. Build a "nasty ten" test set. Pick ten CVs your team has actually struggled with: a two-column PDF, a scanned PDF, a CV with contact details in the Word header, one with a photo, one with a portfolio link in the body, one with a reference name, a long executive CV, and a couple of ordinary ones. Use CVs you're allowed to share for evaluation, or redacted/synthetic stand-ins with the same structure.

2. Write the rule before you run it. For each of your three reasons above, write the exact rule: "First submission to Client X: remove name (replace with Candidate reference), email, phone, address, LinkedIn, personal sites, photo. Keep employers and titles." If the tool lets you choose what to remove per submission, configure it to your rule, not the vendor's default.

3. Run all ten and check every output against a list: name anywhere, email, phone, address, LinkedIn (text and hyperlink), personal URLs, photo, filename, document properties. Score each output pass or miss on each item. A simple grid is enough.

4. Check the formatting, not just the redaction. A redacted CV that comes out with broken spacing still goes back to a recruiter for fixing, which is the work you were trying to remove. Look at it in your client template exactly as the client will see it.

5. Time the full step, end to end. Upload, choose the redaction level, review, download, attach. That's the number that matters to your recruiters, not the processing time on its own.

6. Ask what happens to the original. You'll need to reveal identity once the client wants an interview. Confirm where the full CV lives (usually your ATS record) and how the recruiter links the anonymized version to it, for example a candidate reference number used as the placeholder.

A hypothetical example of how this plays out: an agency submitting IT contractors to a client that asks for blind first rounds runs its nasty ten. Eight come out clean. One keeps a GitHub link in a project description, and one has the candidate's name in the filename because the recruiter saved over the original. Neither is a deal-breaker, but now the team knows to add "check body links and filename" to the submission checklist, and they know it before go-live rather than after a client spots it.

Questions to ask the vendor

Bring these to the demo. They're plain questions, and good vendors answer them plainly.

  • What exactly can be removed, and can we choose per submission? You want specific items (name, email, phone, address, LinkedIn, personal sites, photo), not "all personal data."
  • Where in the document does detection look? Header and contact block only, or body text, footers, text boxes and links as well?
  • What replaces the name? A fixed placeholder, a reference number, or nothing? A reference number makes the reveal step easier.
  • Is redaction done in our template? If the tool redacts but outputs its own layout, you'll be reformatting afterwards.
  • What happens to the files we upload, and who can see them? Get the answer in writing from the vendor's own documentation or contract. Don't rely on a sales slide, and don't let anyone (including us) substitute a badge for a straight answer.
  • What does it cost at our volume? Per-CV pricing and per-seat pricing behave very differently once every recruiter is redacting.

Where it should sit in your workflow

Redaction belongs at the moment of submission, not at intake. You want the full CV in your ATS for search and compliance, and a redacted, branded copy created per client submission.

A pattern that works for most agencies (a hypothetical, simplified flow):

  1. The recruiter shortlists the candidate in the ATS as usual.
  2. They download the original CV, run it through the formatting tool with the client's template and the client's redaction level.
  3. They do the 30-second check (filename, links, photo) and attach the redacted file to the submission.
  4. When the client asks to interview, the recruiter sends the full, branded CV, referenced by the same candidate number.

If you run several clients with different rules (one wants fully blind CVs, one only wants contact details removed, one wants everything), set those rules up once per client rather than leaving them to each recruiter. The client-ready submissions use case shows how per-client templates work in practice.

Manual redaction vs. software: when each makes sense

Manual redaction is fine if you send a handful of blind CVs a month and one careful person does them. It breaks down when several recruiters redact in different ways, when volume rises, or when a single missed phone number would cost you a fee.

Software makes sense when blind or contact-free submissions are routine, when consistency across recruiters matters to a client, and when the redacted CV also needs to arrive in your branded template. Agencies that already use iReformat for formatting describe anonymity as part of the same step: the TIR Energy Services case study notes that users can automatically remove a candidate's name, contact information and photos whenever they need anonymity.

Who redaction software is not for

Be honest with yourself about fit. This category, and iReformat specifically, is probably not right if:

  • You need to redact documents other than CVs (contracts, case files, scanned records). That's a general document-redaction problem; use a tool built for it.
  • You need to redact large archives in one go. iReformat works one submission at a time.
  • Your real problem is search or matching. If you need better data in your ATS, look at parsing tools; our comparison of resume parsing vs. resume formatting explains the difference.
  • You need a vendor to certify your legal compliance. Software can make redaction consistent. It can't decide what your obligations are.
  • You send very few blind CVs. A written checklist and a careful coordinator may be enough.

How iReformat handles this

iReformat is resume formatting software for staffing agencies, with anonymization built into the formatting step. Based on our published product pages:

  • You choose what to remove for each submission: name, email, phone number, address, LinkedIn URL and personal websites, plus photos when anonymity is needed.
  • The name can be replaced with "Candidate A", a "Candidate [Reference Number]" placeholder, or removed entirely.
  • Names are removed from headers and contact sections; employers and job titles stay so the client can still judge experience. Test body-text mentions in your own files.
  • The output is your agency's (or your client's) template, which we set up for you. It isn't a generic layout.
  • Uploads can be PDF, DOC or DOCX.

Pricing is custom and volume-based with unlimited users, and we walk through it on the demo. We'll also set up a free trial before you buy, with no credit card required.

Run your redaction test in your own template

The fastest way to know whether redaction will hold up for your clients is to watch it run on your hardest CVs. Book a demo, bring your "nasty ten" and tell us your client's redaction rule. We'll set up your template and show you every output, including the ones that need a human check.

Frequently Asked Questions

  • Blind Resume Formatting: GDPR-Compliant Guide

    Blind resume formatting removes identifying information (name, photo, age, gender indicators) from resumes before client submission. It serves two purposes: reducing unconscious bias in hiring and ensuring GDPR/data privacy compliance. Manually anonymizing resumes takes 15-20 minutes each. Automated tools do it in seconds while maintaining formatting quality.

  • DEI Recruiting: How Blind Resumes Reduce Bias

    Blind resume formatting removes names, photos, age indicators, and other personal details before a client sees the resume. Research on blind hiring suggests anonymization can reduce bias in screening. Many enterprise clients ask for anonymized submissions or some form of DEI reporting, so agencies that can produce a consistent blind version are easier to work with.

  • Resume Formatting Software: An Agency Demo Checklist

    Judge resume formatting software by running your own template against resumes your team actually sees, then timing the work until you'd send the file to a client. A polished demo file isn't enough. Check the facts, the branding, the workflow, and the full prep time, including review and corrections.

Bring your 10 hardest CVs

We'll set up your template and show every output, including the ones that need a human check.

One resume at a timeWe set up your templateNo credit card required