Bulk CV formatting for a shortlist

What "bulk" actually means here

In a UK perm recruitment context, bulk usually means a shortlist of three to twelve CVs for one role, prepared in one session and sent together. It is not "a hundred CVs in a graduate assessment centre", and the workflow is different. The bottleneck on a shortlist is consistency and the final read-through, not throughput.

The advice below assumes a shortlist in that range. For higher-volume workflows (graduate intake, RPO, assessment centres) the consistent answer is the same in principle but different in tooling; that is a separate article.

Before you open the first CV

Have the brief in front of you. The reason a shortlist reads as inconsistent is often that it was formatted without re-reading the brief. A shortlist written against a brief the consultant does not remember looks like six CVs from six searches.
Confirm the agency template. Logo, colour, footer, section order, the reference-code format your client uses. If your team uses a tool with a saved template, confirm it is the current one.
Decide the file naming. Pick the pattern now — role, shortlist position, reference code, date. Saving twelve CVs named CV-Final-v3.docx at 11pm is the path to sending the wrong file to the client.
Decide what is removed. Name, address, mobile, personal email, LinkedIn URL. Write it on a sticky note if necessary. The fastest way to miss an identifier on a shortlist is to have decided five minutes ago and forgotten by the third CV.

Do them all in the same session

This is the single most useful rule for shortlist consistency. The session can be thirty minutes or two hours; what matters is that it is one session, one template, one person. Starting and stopping breaks the consistency in ways that take longer to repair than they save.

If the shortlist is too long for one session, split by role, not by time. Eight CVs for a perm finance role done in one session will look like one agency's work. The same eight CVs done in two sessions on different days will look like two.

What to do for each CV

Open the source. Read it. Note the role title, the start and end dates of each position, the candidate's actual job — not the job title the candidate gave themselves.
Re-render into the agency template. If the source has no text layer (scanned), OCR or re-type first; do not skip this step and hope.
Verify the redaction. Read the rendered document once for identifiers — name, email, phone, address, URLs. Treat it as a check; do not trust that it was done.
Add the reference code in the agreed place (header strip is the convention).
Save with the agreed file name. Move to the next CV.

The check that catches the most mistakes

Before sending to the client, do one read of the shortlist in order, as a client would. The check is not whether the CV is correct — that has been checked per CV — but whether the shortlist reads as one document. Look for:

Heading styles that vary (sizes, weights, colours).
Bullet characters that vary.
Date formats that vary.
Sections that appear in different orders.
A reference code that is in different positions on different CVs.
A CV that is one page while the rest are two, or vice versa, with no obvious reason.

If you spot any of these, fix them in the source template, not by editing individual CVs. Editing individual CVs produces more drift, not less.

Where a tool helps and where it does not

A tool that re-renders and verifies redaction helps with the mechanical part: the typist work and the consistency check. It does not help with the brief, the role-by-role judgement about what to keep, or the final read-through. Those are human steps and stay human.

A tool that rewrites, paraphrases or "improves" the candidate's own wording makes this workflow worse, not better. A CV the consultant did not write is a CV the consultant cannot sign for, and a shortlist that has been quietly embellished is the kind of thing that ends a client relationship.

What to do if the source CVs are a mess

Some shortlists arrive with one CV from a Word template, one from a Canva design, one scanned from a printed page. Three different problems:

The Canva-style CV usually has a text layer and a layout layer; the content is recoverable, the layout is not. Re-render into the agency template; lose the layout, keep the words.
The scanned CV has to be OCR-ed. The OCR result has to be checked against the original — names and figures are the bits that go wrong first. Do not OCR in batch and assume.
The Word CV with tables imports into most editors as a table-shaped block of text. Tables do not survive re-rendering cleanly; expect to flatten them.

When in doubt, the safest move is to use the same source twice and compare outputs. If the outputs match, the pipeline is consistent. If they do not, fix the pipeline before sending either to the client.

Sending to the client

One email, one PDF (or one folder of Word files), a short covering note. Do not send twelve CVs as twelve emails.
Include the reference codes in the covering note so the client can refer to a CV by code without learning the candidate's name.
State the time you sent them and when you will follow up. Hiring managers read shortlists in the gaps; tell them when the gap is.

If you are doing this often

A team that puts more than a hundred shortlists out a year will benefit from a saved template and a documented workflow. A team that puts out a thousand will benefit from a tool that holds the template and the redaction rules in one place and renders every CV through them. The threshold is not "many CVs"; the threshold is "many consultants using the same template".