The ATS resume format that actually works in 2026

Before a recruiter at most mid-to-large companies sees your CV, a piece of software reads it first. That software is an Applicant Tracking System — ATS for short — and it does not read your CV the way a human does. It parses structured data from plain text, extracts entities like your name, dates, job titles, and skills, and then scores the result against the job requirements. A CV that does not parse correctly can score zero even if the candidate is a perfect match.

This guide explains exactly what happens inside an ATS, lists the ten formatting rules that actually affect parse quality, and includes a copy-paste template you can use as a starting point for any application.

What an ATS actually does in 2026

The modern ATS pipeline has three stages: parse, score, and route.

Parse. The ATS ingests your document — most accept PDF and .docx, some also accept .txt — and extracts structured data from it. It is looking for: contact information (name, email, phone, location), work experience (company, title, dates, responsibilities), education (institution, degree, dates), and skills. The parser uses a combination of section header detection, named entity recognition, and pattern matching. Headers like "Work Experience," "Employment History," and "Professional Experience" are all recognised; a creative header like "Where I've been" may not be.

Score. Once the data is extracted, the ATS compares it to the job requirements. This is typically a keyword-match score weighted by the importance of each requirement. Some ATS platforms also consider seniority signals (years of experience, job titles), education requirements, and location. The output is a numeric score that determines how far up the recruiter's stack your application appears.

Route. Applications above a threshold score go to the recruiter queue. Applications below it may be auto-rejected or placed in a lower-priority pile that is only reviewed if the primary queue is thin. The recruiter never decides this — the ATS does.

The implication is clear: parse failure is disqualifying, and score depends on keyword match. Both are directly affected by formatting choices.

The 10 formatting rules that matter

The rules below are derived from how major ATS platforms — Greenhouse, Lever, Workday, iCIMS, Taleo — handle document ingestion. They are not aesthetic preferences. Each one has a documented parse behaviour behind it.

1. Use a single-column layout. Multi-column layouts often cause ATS parsers to read columns in the wrong order, mixing skills from column two into a work experience block from column one. A single-column layout eliminates this risk. It also renders cleanly in plain text, which is the easiest way to verify parse quality.

2. Use standard section headers. The ATS relies on section header detection to classify your experience, education, and skills correctly. Use headers it will recognise: "Work Experience" or "Professional Experience," "Education," "Skills," "Summary" or "Professional Profile." Avoid creative alternatives unless you are applying to a company whose ATS you know for certain handles them.

3. Date format: month and year. ATS systems calculate tenure from date fields. Use a consistent format throughout — "Jan 2022 – Mar 2024" or "01/2022 – 03/2024." Omitting months (just using years) can cause the ATS to overestimate or underestimate tenure. "Present" for your current role is widely supported.

4. Job title on its own line. Keep your job title and company name on separate or clearly delineated lines. Some parsers struggle when job title, company, and dates are all crammed onto a single line with unusual separators.

5. No text boxes or shapes. Text inside Word text boxes, shapes, or drawing canvases is often completely invisible to ATS parsers. If you put your name, contact information, or any skills in a text box, they will not be extracted. This is one of the most common reasons for parse failure in visually designed templates.

6. No headers or footers (in .docx). Word's header and footer regions are rendered separately from the main document body. Many ATS parsers do not extract them. If your contact information is in the document header — which many templates do — the ATS may not capture your email or phone number.

7. No tables for content sections. Tables work for simple two-column layouts where parse order does not matter, but ATS parsers vary in how they handle them. For the experience section specifically, avoid tables. A bulleted list under a clear section header is the safest format.

8. Standard bullet characters. Round bullets (•) and hyphens (-) are universally supported. Fancy Unicode bullets — arrows, diamonds, chevrons — may render as garbled characters or be stripped entirely. Use the standard bullet in Word (the keyboard shortcut in most setups is Alt+0149 on Windows, Option+8 on Mac) or a simple hyphen.

9. Spell out acronyms at least once. If your target role uses "CI/CD" and your CV only says "continuous integration and continuous deployment," you may miss the keyword match. Conversely, if you only use acronyms that the JD spells out, you may also miss. Safe approach: "CI/CD (continuous integration and continuous deployment)" on first mention.

10. Keep file size under 5MB. Most ATS platforms have file size limits. A clean, text-based CV should be under 200KB. If yours is larger, it likely contains embedded images, which also means the ATS cannot read the content inside those images.

Fonts, columns, headers, tables

The formatting rules above have a common theme: anything that makes your CV look distinctive in a PDF viewer often works against you in an ATS. The safest fonts are those with high character recognition rates in text extraction: Calibri, Arial, Helvetica, Georgia, and Times New Roman. Unusual fonts are rarely the parse failure cause, but they can cause character encoding issues in older ATS parsers.

Header and footer regions in Word are the most common source of lost contact information. Before sending any application, copy your CV into a plain-text editor (Notepad on Windows, TextEdit in plain-text mode on Mac) and verify that your name, email, and phone number appear in the body — not only in the document header.

PDF vs .docx in 2026

This debate has run for years. The current state: most modern ATS platforms handle both formats adequately, but .docx is still marginally safer.

Here is why. PDFs are rendered as a visual grid, and text extraction from PDFs depends on how the PDF was generated. A PDF exported from Word with a single-column layout and no special fonts will extract cleanly. A PDF generated from a design tool like Canva or exported from Google Slides will often extract as garbled text or fail entirely — because those tools do not generate text-layer PDFs in the same way Word does.

A .docx file, by contrast, is structured XML that the ATS reads directly. There is no intermediate render step. As long as you avoid text boxes, headers, and footers, the parse is reliable.

The practical recommendation: use .docx when submitting through an ATS portal. Keep a PDF version for emailing directly to a recruiter or hiring manager, where it will be read by a human rather than parsed by software.

RecastCV exports to .docx by default, partly for this reason.

Section order that ATS + humans both like

The section order that performs best across both ATS scoring and human readability:

1. Contact information — name, email, phone, LinkedIn URL, location (city and country, not full address).
2. Professional summary — three to four sentences, keyword-rich, role-specific.
3. Work experience — reverse chronological. Most recent role first.
4. Skills — a clean list, no ratings or bar charts (ATS cannot interpret "4 out of 5 stars" for Python).
5. Education — degree, institution, dates. For candidates more than five years into their career, this moves below skills.
6. Certifications / professional development — optional, relevant only.

This order front-loads the material that ATS systems weight most heavily (experience, skills) while also matching recruiter reading patterns.

A copy-paste ATS-safe template

The following template uses plain-text section markers. Copy this into a Word document, replace the placeholder text, and apply standard formatting (Calibri 11pt body, bold section headers in Calibri 12pt). Keep it to one or two pages.

FULL NAME
email@example.com | +44 7xxx xxxxxx | LinkedIn: linkedin.com/in/yourprofile | London, UK

PROFESSIONAL SUMMARY
[Three to four sentences summarising your seniority, domain, and the value you bring.
Write this after completing the rest of the CV and tailor it per application.]

WORK EXPERIENCE

Job Title | Company Name | Month Year – Month Year (or Present)
- [Outcome-led bullet: what you did, how, and the measurable result.]
- [Second bullet. Prioritise bullets that match the target JD's keywords.]
- [Third bullet. Be specific — numbers, scope, team size where relevant.]

Job Title | Company Name | Month Year – Month Year
- [Bullet]
- [Bullet]

SKILLS
[List skills as a comma-separated sequence or short groups by category.
Example: Python, SQL, dbt, Snowflake | Stakeholder management, roadmap planning, OKR setting]

EDUCATION
Degree Title | Institution Name | Year – Year
[Optional: dissertation title, notable modules, or GPA if high and recent.]

CERTIFICATIONS
Certification Name | Issuing Body | Year

This is intentionally plain. Once you confirm it parses correctly in a plain-text check, you can apply light styling in Word — consistent font, bold headers, left-aligned date ranges — without introducing the elements that cause parse failures.

Test your CV with the free ATS checker

Formatting rules are only half the problem. Even a perfectly structured CV will score poorly if it does not contain the keywords the specific job description is looking for. Keyword coverage is job-specific, which means it cannot be checked once and forgotten — it needs to be checked per application.

The free ATS CV checker does this automatically: paste your CV and the job description URL, and it returns a keyword match score, a list of missing high-priority terms, and a structural parse check. It takes about thirty seconds and will tell you more than a general formatting checklist can.

For the background on why ATS systems work the way they do — including how the parse pipeline handles edge cases — the complete ATS resume guide covers the technical detail. And if you want to start from a verified ATS-safe structure, the templates page has options that have been tested against major ATS platforms.

For the UK/US terminology question — whether to call it a CV or a resume, and whether the formatting differs — the companion post CV vs resume: UK vs US differences explained covers the practical differences.