Formatting issues cause 23% of ATS parsing failures (Enhancv 2025 study, 25 recruiters across 10+ ATS platforms including Workday, iCIMS, and Greenhouse, corroborated by ResumeAdapter Q1 2026 pipeline analysis). The fix is mechanical: standardize your dates, drop text boxes, use the section headers parsers expect, and ship a text-selectable PDF. This guide covers all six rules. Each one is a five-minute fix. Run a free ATS scan to see which of them your current resume is breaking before you submit your next application.

TL;DR: The 6 ATS Formatting Rules That Decide Whether You Get Parsed

Bottom line: formatting is the easy half. The other 77% of failures are content (missing keywords, weak experience descriptions). Fix formatting first using the rules below, then run a scan against your target job description to see which keywords you are missing.

---

Review My Resume — Free ATS Scan

---

The Technical Logic of ATS Parsing (2026)

Most "ATS advice" online is superstitious guesswork. "Don't use headers!" "Put keywords in white text!" This advice is often wrong and sometimes dangerous.

To beat the ATS, you must understand how Parsers actually work. The major systems (RChilli, Sovren, Daxtra, Workday proprietary) all follow similar logic:

1. Extraction: The system converts your PDF/DOCX into raw text.
2. Segmentation: It identifies blocks of text as "Contact," "Work," "Education" based on specific header keywords.
3. Parsing: It breaks down those blocks into fields: Job Title, Company, Start Date, End Date, Description.
4. Ranking: It calculates your relevance based on the parsed fields, not the visual document.

If step 3 fails (Parsing), step 4 (Ranking) produces a zero.

---

1. The Date Format Rule (MM/YYYY)

This is the single most common cause of parsing errors. When the ATS cannot accurately calculate your years of experience, it ranks your resume below the candidates whose dates parsed cleanly, even when your actual experience matches the role. Recruiters then never see your application in the filtered shortlist.

❌ Dangerous Formats (Do Not Use)

• Just Years: 2022 – 2023. Why: The parser acts conservatively. It might credit you with 1 day (Dec 31, 2022 to Jan 1, 2023) or 365 days. You lose precision.
• Apostrophes: '23 – Present. Why: Some older parsers treat '23 as a typo or garbage character.
• Seasons: Summer 2023. Why: "Summer" is not a month. The robot does not know if that means June, July, or August.
• Vague Terms: Ongoing, Current. Why: Use the standardized term Present or Now.

✅ Safe Formats (Universal Compatibility)

• Standard Numeric: 03/2023 – Present (or 03/2023)
• Standard Text: March 2023 – Present
• Short Text: Mar 2023 – Present (Standard 3-letter abbreviation)

The Golden Rule: Always put the date on the right-hand side, separate from the job title.

Not sure if your current dates are parsing cleanly? Upload your resume to the free ATS scanner and it will flag broken date formats along with every other parsing issue on this page, before a recruiter ever sees it.

---

2. Tables & Columns: The "Reading Order" Problem

The Science of "Left-to-Right"

Parsers read documents like a human reads a book: top-to-bottom, left-to-right.

The Multi-Column Trap: Imagine a two-column resume:

• Column A (Left): Job Titles
• Column B (Right): Job Descriptions

If the parser is "dumb," it might read straight across: Line 1: Senior Manager (Col A) ... Lead a team of 10 (Col B) Line 2: Junior Developer (Col A) ... Wrote code in Java (Col B)

This usually works fine. BUT, if you use Text Boxes to create columns, the parser might read ALL of Column A first, then ALL of Column B. Your job titles get disconnected from your descriptions.

The 2026 Reality

• Modern ATS (Greenhouse, Lever): Generally handles simple columns correctly when they use standard word-processor column formatting (not text boxes).
• Legacy ATS (Taleo, iCIMS): Must struggle with columns.

Recommendation:

• Safest: Single-column layout. It never fails.
• Acceptable: Two-column layout created with proper "Columns" formatting (not tables/text boxes).
• Forbidden: Floating Text Boxes, Sidebars in images, Nested Tables.

---

3. Section Headers (The Anchors)

Parsers rely on "Standard Headers" to know when one section ends and another begins. If you get "Creative" with your headers, the parser gets lost.

If you name your Work Experience section "My Journey," the ATS might think it is a biography block and ignore all the keywords inside it.

---

4. Special Characters & Icons

Icons break parsers. They are often read as garbage characters (&%$#) or cause the line to be skipped.

• Avoid: Icons for phone/email (Use text labels: "Phone:", "Email:", "LinkedIn:").
• Avoid: Progress bars or "skill rating" graphics (e.g., 5/5 stars for Java). The ATS cannot read a visual bar. It sees nothing.
• Avoid: Complex dividers (lines with shapes). Use simple horizontal lines.
• Use: Standard bullet points (•, -, or *). Arrow bullets (➢) are usually fine but standard dots are safer.

---

5. File Type: PDF vs. DOCX

This is the oldest debate in resume writing.

• PDF: Preserves design perfectly. Fonts stay locked. Margins stay fixed. Use this 90% of the time.
• DOCX: The native language of parsers. Use this ONLY if:
  1. The job portal is extremely old/clunky.
  2. The application explicitly says "Please upload Word document."
  3. You are emailing a recruiter directly (they might want to edit it).

Critical Warning: Never use "Image PDF" (scanned document). The ATS is text-based. If you cannot highlight the text with your mouse cursor, the ATS cannot read it.

---

6. Fonts & Typography

• Serif vs Sans-Serif: It doesn't matter for parsing, but Sans-Serif (Arial, Calibri) is generally preferred for on-screen readability.
• Size: Keep body text between 10pt and 12pt. Headers 14pt-18pt.
• Safe Fonts: Arial, Calibri, Helvetica, Roboto, Georgia, Times New Roman, Verdana, Open Sans.
• Unsafe Fonts: Custom fonts downloaded from DaFont, "Typewriter" fonts, Script fonts. If the ATS doesn't have the font installed, it falls back to default, potentially ruining your layout.

---

Summary Checklist: The "Safe Parse" Standard

Before you hit submit, run through this checklist:

1. Format: Single column is safest; simple 2-column is okay. No text boxes.
2. Dates: MM/YYYY format used consistently everywhere.
3. Headers: Standard names (Experience, Education).
4. Fonts: Standard system fonts. No icons.
5. Graphics: No photos, no charts, no skill bars.
6. Hyperlinks: URLs are fully visible (e.g., linkedin.com/in/name) rather than hidden text links (Click Here), just in case parsing strips the link.

---

Related Articles

• ATS Resume Format Guide 2026: Free Template + 5 Rules That Pass - Once you know what breaks, here is the format that works, with a free template.
• Resume Keywords List: 210+ Examples by Industry (2026) - Format gets you parsed; keywords get you ranked.
• Software Engineer Resume Keywords (2026 ATS Data) - Role-specific keyword guide for SWEs.
• How to Optimize Resume Keywords
• Why Your Resume Gets Rejected
• Free ATS Resume Scanner - Test your parsing fidelity.

---

Will Your Resume Parse Correctly?

You don't have to guess. Upload your resume and see exactly what the robot sees. Our tool simulates a strict ATS parser to show you errors before they cost you the interview.

👉 Run a Free Formatting Check

---

Check Your Resume in 60 Seconds

Don't ship a resume without testing it. Run the free ATS scan, paste your target job description, and you'll see every formatting, date, and keyword error on this page applied to your own file, with the exact fixes to make before you hit apply.

Take the Next Step

Ready to apply what you just read? Pick an ATS-safe resume template to start fresh, or Open the ATS Resume Builder to build a clean resume from scratch.