ATS Friendly CV Template: What to Include (and What ATS Software Rejects)

If you've gone looking for an ATS Friendly CV Template, you've probably already downloaded three or four and never found out why the last one didn't get a reply. That's the frustrating part of CV templates: a lot of the ones circulating online were designed to look sharp in a screenshot, not to survive being read by software first. A CV, in the UK, Irish, European, and international sense, isn't quite the same document as a US-style resume, and a fair amount of resume advice floating around doesn't translate cleanly. This piece walks through what actually needs to be in a template that both a parser and a human reviewer can use, section by section, and the specific formatting choices that get an otherwise strong CV rejected before anyone reads a word of it.

CV vs Resume: Why the Template You Pick Matters

In the UK, Ireland, most of Europe, and much of Asia and Africa, 'CV' is simply the word for the document you send when you apply for a job. It's usually one to two pages, chronological, and covers the same ground a US resume does. In the US and Canada, 'CV' means something narrower: a long-form academic document listing publications, grants, conference talks, and teaching history, used mainly for academic, research, or medical positions. If you're outside academia and searching for a CV template, you're almost certainly looking for what an American recruiter would call a resume with a different regional name. We've covered that distinction in more depth in CV vs Resume: What's the Difference and Which One You Actually Need, so this article assumes you already know which document you need and focuses on the part that trips people up regardless of which side of the Atlantic they're on: getting the template through the software before a person ever opens it.

The parsing software doesn't care what you call the file. What it cares about is structure. A CV built for a UK graduate scheme, a CV built for a Dubai-based multinational, and a CV built for a German Lebenslauf-adjacent application all get run through broadly similar applicant tracking systems, and all of them succeed or fail on the same handful of technical points: layout, headings, fonts, and file format. That's the part of CV template advice that's genuinely universal, and it's the part most templates you can download for free get wrong.

What an ATS Actually Does With Your CV

An applicant tracking system isn't one piece of software with one behavior. It's a category, and the market leaders (Workday, Greenhouse, Lever, iCIMS, SAP SuccessFactors, and dozens of smaller regional platforms) each parse documents slightly differently. But the underlying job is the same: extract structured data out of an unstructured document. Workday's own description of the process is useful here, the platform's parsing engine 'reads and interprets document text' and extracts details like education, skills, and work history, then organizes them into structured candidate profiles that recruiters search and filter (see Workday's overview of applicant tracking systems). That structured profile, not your PDF, is usually what a recruiter actually looks at first when they open a requisition with 400 applicants in it.

This is why template design matters more than most people assume. If the parser can't confidently tell which block of text is your job title, which is your employer, and which is your date range, it either mis-files the data (wrong job under the wrong company) or drops it entirely. Neither failure shows up when you look at the PDF yourself, because you're reading it visually, in the layout you designed. The ATS isn't. It's reading the underlying text stream, in whatever order the file's internal structure puts it in, and that order isn't always the order you see on the page.

ATS adoption isn't a fringe concern either. Research from Harvard Business School and Accenture found that roughly 99% of Fortune 500 companies use some form of applicant tracking software, and the same research put a number on the cost of bad parsing and rigid keyword matching: an estimated 27 million people in the US alone who are actively job hunting but getting screened out by automated systems despite being capable of doing the job (see the Harvard Gazette's coverage of the 'hidden workers' study). A template that parses badly doesn't just cost you one application, it can quietly cost you a whole search if you're using the same file everywhere.

The Sections an ATS Friendly CV Template Needs

Every reliable ATS Friendly CV Template is built around a fixed set of sections, in a predictable order, using labels the parser has actually been trained to recognize. Creative section names might read as distinctive to a human, but to a parser they're just unfamiliar strings. Stick to the boring, expected labels. Here's what each section needs to do.

Contact details

Full name, phone number, email address, city and country (street address isn't necessary and, in some regions, is starting to look dated), and a link to your LinkedIn or portfolio. Put all of this in the body of the document, not in a header or footer. Headers and footers are a known blind spot: several parsers skip them by design, which means a CV with contact details tucked into the top banner can arrive at a recruiter's desk with no working phone number or email attached to it at all. The UK's National Careers Service gives essentially the same instruction in its own CV guidance, recommending a clear, professional contact block up top and specifically advising against including age, marital status, or nationality, details that are irrelevant to the role and, in some jurisdictions, illegal to ask for (see the National Careers Service CV sections guidance).

Personal statement or profile

Three to four lines under your contact details, stating your role, your years of experience, and one or two things you're genuinely good at. This section does double duty: it's the first thing a human reads, and it's a natural place to work in a couple of the job description's exact keywords without it reading like a list. If you want a deeper walkthrough of writing this section well, How to Write a Resume Summary That Actually Gets Read (With Examples) covers structure and examples in more detail.

Work experience

Reverse chronological order, always. Each entry needs the company name, your job title, the dates you worked there (month and year is enough, day-level precision isn't expected and just adds clutter), and three to six bullet points describing what you did and what changed because of it. Resist the urge to bury this under a creative heading like 'My Journey' or 'Where I've Been.' Parsers look for standard labels, 'Experience,' 'Work Experience,' or 'Employment History,' and a heading that doesn't match any of those patterns can mean the whole section gets treated as unstructured text instead of being mapped to the work-history field in the candidate profile.

Education (and where academic CVs diverge)

For a standard CV, this section is short: degree, institution, graduation year, and maybe a line about relevant coursework or honors if you're early in your career. For an academic CV, this is where the document genuinely changes shape and grows well past the one-to-two-page range: publications (often in a separate section formatted in a citation style relevant to your field), research grants, conference presentations, teaching experience, and academic references by name rather than 'available on request.' If you're building an academic CV, don't force it into a template designed for industry applications. The sections, and the acceptable length, are different by convention, and hiring committees in academia expect that length.

Skills

A plain list, either comma-separated or one per line, no skill bars, no proficiency dials, no icon grids. Those visual flourishes look nice in a browser preview and turn into either blank space or garbled characters once a parser gets hold of them. Group skills logically (technical skills, tools, languages) if you have a lot of them, but keep the actual list itself as plain text. For guidance on which skills and phrases to prioritize based on the job description, Resume Keywords: How to Pass ATS Screening in 2026 goes into the matching logic ATS platforms use.

References

In most markets, 'References available on request' is standard and sufficient; you don't need to list names and phone numbers on the CV itself. Academic CVs are again the exception, where named references with titles and institutional affiliation are often expected directly on the document.

Formatting Rules That Keep Parsers Happy

Section content is half the job. The other half is layout, and this is where most visually appealing CV templates fall apart. The good news is that the rules are consistent enough across major ATS platforms that you can follow them once and reuse the same template everywhere.

Single column beats multi-column, every time

Two-column layouts, the kind where your skills and contact info sit in a narrow sidebar and your experience runs down a wider main column, are consistently the biggest single cause of ATS parsing failures. Most parsers read a page the way you'd read a book: left to right, top to bottom, line by line. A sidebar breaks that assumption, and instead of reading the sidebar and the main column separately, many parsers slice across both columns at the same height and stitch unrelated fragments together into what parsing researchers have started calling 'word salad,' a sentence from your job title mashed together with a sentence from your skills list, in an order that makes no sense to anyone. Jobscan's research into this exact failure mode found that the underlying cause is a mismatch between a document's visual layout and its actual text structure, design tools that lay content out in visual columns don't necessarily store it in that same reading order internally, so the parser extracts text in an order nobody intended (see Jobscan's breakdown of why tables and columns break ATS parsing). The fix isn't complicated: use a single column, top to bottom, for the entire document. If you want visual separation between sections, use whitespace and bold headings, not side-by-side blocks.

Fonts, sizing, and spacing

Stick to fonts that ship with every operating system and every parser has seen a million times: Arial, Calibri, Georgia, Helvetica, or Times New Roman. The National Careers Service's own guidance lands on the same short list, recommending Arial, Times New Roman, or Calibri at 11 point or larger for readability (again, see their CV sections guidance). Decorative or script fonts might render fine as a PDF on your own machine, but if the font isn't embedded correctly or isn't recognized by the parsing engine, individual characters can get substituted or dropped, turning a clean-looking CV into something that reads as gibberish once it's been through extraction. Keep body text at 10 to 12 point, headings a couple of points larger and bolded rather than a different font entirely, and don't compress line spacing so far that the parser struggles to tell where one line ends and the next begins.

Section headings: boring is correct

Use 'Work Experience,' 'Education,' 'Skills,' and 'Summary' or 'Profile.' Not 'What I Bring to the Table,' not 'The Journey So Far,' not icons standing in for words. Parsers match against a known vocabulary of section headers built from analyzing millions of real CVs and resumes; a heading outside that vocabulary just gets treated as body text, which means the fields under it don't get mapped correctly into the structured profile a recruiter sees. This is one of those cases where creativity actively costs you, and it's worth pairing with a broader look at How to Write an ATS-Friendly Resume in 2026 if you want the equivalent formatting rules laid out for a US-style resume.

File Formats: PDF vs Word for CV Templates

This is the question people ask most and get the most conflicting answers on, mostly because the honest answer is 'it depends on the platform, but one choice is safer by default.' A .docx file is the most universally parseable format because it stores text as, well, text, in a document structure every major ATS was built to read natively. A well-made PDF, specifically one that's genuinely text-based rather than a flattened image or a scan, parses almost as reliably on modern platforms, and it has the advantage of looking identical no matter what device or software opens it, which matters if a hiring manager forwards your CV around internally. What you want to avoid entirely is a PDF exported from a design tool that renders everything as vector shapes or embeds the whole page as one image; there's no underlying text layer at all in that case, and the ATS has nothing to extract. If a job posting or portal specifies a format, follow it exactly; if it doesn't, .docx is the safer default, and a clean, non-flattened PDF is a reasonable second choice for anything you're sending directly to a person rather than uploading to a portal.

One more file-level habit worth building: name the file something a recruiter can find again later, like FirstName-LastName-CV.pdf, not 'Final_v3_USE_THIS_ONE.docx.' It doesn't affect parsing, but it does affect whether the right person can locate your document six weeks later when the hiring manager finally circles back.

What ATS Software Rejects: A Quick Checklist

Before you finalize any template, run it against this list. These are the elements that consistently cause parsing failures, dropped sections, or scrambled text across most major ATS platforms:

• Multi-column or sidebar layouts, including two-column skills-and-timeline templates
• Tables used for layout (even invisible ones with no borders)
• Text boxes, including the kind used to frame a photo or a pull quote
• Headers and footers containing contact details, page numbers are fine there, names and emails aren't
• Graphics standing in for data: skill bars, star ratings, progress dials, icon-only labels
• Scanned or flattened image-based PDFs with no underlying text layer
• Uncommon or decorative fonts, especially script fonts and condensed display fonts
• Non-standard section headings that don't match common vocabulary (Experience, Education, Skills)
• Photos and headshots embedded in the document (also a legal risk in some hiring processes in the US and elsewhere, since it can introduce bias claims)
• Special characters used as bullet points or dividers instead of standard bullet formatting
• Content inside embedded objects, charts, or SmartArt rather than plain paragraph text

Any one of these might not sink an application on its own. A CV with two or three of them stacked together, a two-column layout with a headshot in a text box and a skills section rendered as a bar chart, is a near-guaranteed parsing failure on at least one platform you'll apply through. If you want a second opinion on where your current CV stands before you send it anywhere, ATS Resume Score: How to Check (and Improve) Yours Before You Apply walks through how to test a document against this exact list of failure points.

Academic and International CV Quirks

A handful of conventions vary by country and matter for template choice even when the ATS rules stay constant. Date formats are the most common trip-up: write '03/04/2024' on a CV going to a US-based ATS and it's read as March 4th; send the same string to a UK or European system and it's read as April 3rd. Spell the month out (March 2024) and the ambiguity disappears entirely, and this is worth doing regardless of which system you're applying through. Photos are another regional split: expected or at least common on CVs in parts of continental Europe, actively discouraged in the US, UK, and Canada, where including one can create legal exposure for the employer around discrimination claims and gets your CV auto-rejected by some large employers' intake policies before a person ever reviews it. When in doubt, especially if you're applying across borders with the same base template, leave the photo off and add it back in only for markets where it's the clear local norm.

Length works the same way. A UK CV for a mid-career professional role runs one to two pages; academic CVs run as long as the publication and grant history requires, sometimes ten pages or more for a tenured researcher, and nobody expects otherwise. The general reasoning, relevance over completeness, cut what isn't earning its space, applies to a standard CV. It just doesn't apply to the academic version, where length is a function of career stage, not a stylistic choice.

Testing a Template Before You Trust It

The cheapest way to find out whether a template parses cleanly is to try parsing it yourself before a recruiter's ATS does it for you. Open your finished CV in a plain text editor, or copy the text out of the PDF and paste it into a blank document. If the sentences come out in the right order, with job titles next to the right companies and dates attached to the right roles, that's a good sign. If you get a jumble of fragments from your skills section mixed into your work history, that's exactly the failure mode described earlier, and it means the layout needs to change before you send it anywhere else. A handful of free ATS resume checkers will do a more thorough version of this same test and flag specific formatting issues, which is worth doing once per template rather than once per application.

Where to Find (or Build) an ATS Friendly CV Template

Most free template libraries prioritize visual variety over parsing reliability, which is exactly backwards for this use case. When you're evaluating a template, whether you found it on a design site or you're building your own from scratch in Word, check it against the checklist above before you check whether you like how it looks. Our own CV and resume templates are built single-column by default specifically because of the parsing issues covered here, and they're worth comparing against whatever you're currently using even if you don't end up switching.

If you're managing multiple versions of the same CV for different regions or roles, generating each one from scratch gets tedious fast, and that's really where an ai powered resume builder earns its keep: it can rebuild the same underlying content into a region-appropriate, parser-safe layout in a couple of minutes instead of you manually rebuilding the file every time a new country's conventions apply. It's not a substitute for understanding the rules in this article, but it does remove the repetitive part once you do. For the resume-specific version of this same checklist, ATS-Friendly Resume Templates: What Actually Makes One Pass the Scan is worth reading alongside this one. You can also just create a free account and generate a parser-safe CV directly rather than fighting with a Word template's formatting for the fourth time this month.

None of this is complicated once you've seen it laid out, which is exactly why it's frustrating that so many popular templates still get it wrong. A CV that looks slightly plainer but parses cleanly will out-perform a beautifully designed one that a computer can't read, every single time, because the plain one actually reaches a person. Build the structure right first: standard sections, standard headings, single column, a real font, a real text layer. Once that's solid, there's plenty of room left to make the document distinctly yours in the writing itself, which is the part a machine was never going to judge you on anyway.