ATS-Friendly CV Formatting: Guidelines for Recruiters (2026)

When an agency submits a CV, it almost always lands in an ATS — the client's, not yours. What their parser extracts is what their hiring team searches, filters and ranks. A submission that parses badly is a candidate who's invisible for reasons that have nothing to do with ability, and an agency that looks careless when the client opens the record. These are the formatting rules that determine whether your documents survive parsing — written for recruiters, not job seekers.

How parsing actually breaks

An ATS parser reads the document's text layer in sequence and tries to detect structure: contact block, roles, dates, skills, education. It fails in predictable ways:

• Multi-column layouts. Parsers read left-to-right across the page or column-by-column, depending on how the file was built — two-column CVs regularly interleave sidebar skills into job descriptions. The single biggest source of shredded CVs.
• Tables for layout. Cell order ≠ visual order. Dates end up attached to the wrong roles.
• Text in headers/footers. Many parsers skip them entirely — contact details placed there simply vanish.
• Text boxes and graphics. Content in floating boxes, skill-level bar charts, icons instead of labels ("📞" is not the word "phone") — all invisible or garbled in the text layer.
• Scanned images. No text layer at all without OCR. A surprising share of agency inboxes still contains photographed CVs.
• Exotic fonts / ligature encoding. Text that copies out as gibberish parses as gibberish.

The guidelines

• Single column, top to bottom. Boring is parseable. Visual flair belongs in your branding accents, not the structure.
• Standard section headings — "Experience", "Education", "Skills". Parsers key on them; "My Journey" defeats them.
• Reverse-chronological with explicit dates — "Mar 2021 – Present", consistently formatted, on the same line pattern every role.
• Contact block in the body, top of page 1 — never in the header/footer.
• Real text everywhere. No skill graphics, no icon fonts, no embedded images of text.
• Common fonts, real bullets — standard bullet characters, not custom glyphs.
• PDF with a clean text layer (or DOCX where the client requests it). Test: select-all, copy, paste to plain text — if it reads sanely, it parses sanely.
• Sane filename — Lastname_Role_Agency.pdf.

The part job-seeker guides won't tell you

Parsability cuts both ways: the same text layer the ATS reads is where candidates hide things. White-on-white keyword walls, invisible Unicode, prompt injections aimed at AI screeners — none visible on the page, all fully parseable. An agency that submits a manipulated CV inherits the embarrassment when the client's tooling flags it. Before a document goes out, it needs both checks: does it parse correctly, and does it parse only what's visible. Detection techniques: how to spot AI-manipulated CVs.

Reformatting at agency volume

You don't control what arrives: two-column Canva designs, LinkedIn exports, scans, seven-page Word files. Rebuilding each into an ATS-safe house template by hand costs 30–50 minutes per CV — the arithmetic that kills Mondays. The automated version is CVReady: any input format in (OCR for scans, 20+ languages), one clean single-column branded template out, hidden text stripped by construction, in ~60 seconds at $0.95 per CV. The output is designed to survive exactly the parsing failures listed above — and it's the same standardization that makes GDPR minimisation and blind submissions mechanical.

Quick answers

PDF or Word for ATS submissions?

A text-based PDF parses reliably in modern systems and locks your branding; some clients' workflows still ask for DOCX. Send what the client's process requires — CVReady exports both, plus plain text.

Do ATS systems reject CVs automatically for formatting?

Rarely outright — the failure mode is quieter: fields parse wrong or empty, so the candidate never surfaces in searches and rankings. Silent loss, not rejection.

Are "ATS-optimized templates" from CV builders fine?

Often, but they're built for job seekers, not agencies — no client branding, no consultant summary, inconsistent across candidates. What agencies need is one house template applied uniformly: see candidate presentation.