Applicant Pool Batch Anonymisation with anonym.plus

Anonymise a whole folder of applications in one local run for blind review.

In simple terms, PII redaction is the on-device process of finding and masking personally identifiable information in a document before it is shared.

Applicant pool batch anonymisation is the removal of personal data from many submissions in one run. Equality Act 2010 s.39(1) governs the arrangements an employer makes across every file, not just one, and s.19 catches a criterion that disadvantages one group consistently across the batch even if no single decision looks discriminatory on its own. anonym.plus processes up to 20 files at a time on your device, with a shared map so one person maps to one alias.

When this applies

A vacancy can draw dozens of submissions that all need the same blind treatment for the s.39 arrangements to hold up consistently. One-by-one work risks drift, which is exactly the kind of inconsistency that can turn into an s.19 pattern, so one steady run applies the same rule throughout.

How anonym.plus handles it

  1. Point anonym.plus at the pool folder on your machine.
  2. It scans each submission for names and bias cues.
  3. Built-in OCR reads any scanned pages in the set.
  4. A shared map keeps each person steady across files.
  5. Review the summary and fix low-confidence markings.
  6. Keep the map ON for blind review, or OFF for anonymity.

What you need to provide

PII entity types detected

Categoryanonym.plus entity typeExample
NamesPERSONperson across files → [CANDIDATE_1]
OriginNRPorigin cues → [ORIGIN]
ContactEMAIL_ADDRESSemails → [EMAIL]
ContactPHONE_NUMBERphones → [PHONE]
LocationLOCATIONpostcodes → [ADDRESS]
DatesDATE_TIMEgraduation years → [DATE]

Compliance achieved

Anonymise applicant pools offline — see plans & start free →

Limitations & cautions

A mixed folder of scans and native files leans on OCR for images, so review low-confidence markings. Keeping the map on allows re-linking; turn it off when you need true anonymity for the whole set.

Frequently asked questions

Why does consistency across a batch matter for the Equality Act?

Equality Act 2010 s.19 looks at a pattern, not just one decision, so treating some CVs in the same batch differently from others, even by accident, can create the kind of disparate impact the section targets.

How does batch mode keep one person steady?

A shared map logs each person once, so the same applicant maps to the same alias in every file across the folder, keeping the s.39 arrangements consistent for that person throughout the process.

Yes, if the map stays on. Turn it off when the whole set must be truly anonymous, for example once every candidate in the group has been notified of the outcome.