Formatting is the single highest-leverage change you can make to a resume, and almost every candidate gets it wrong. Our parser benchmarks show that the same content, reformatted from a two-column creative template into a single-column ATS-safe layout, jumps from 52% field completeness to 94% on Workday. That is the difference between a resume the recruiter never sees and one that actually reaches the shortlist. This guide is tactical: file type, layout, fonts, margins, dates, bullets, headers, section order. Every rule is tied to a specific parser failure mode, benchmarked against the five ATS platforms that cover roughly 70% of Fortune 500 hiring (Workday, Taleo, iCIMS, Greenhouse, Lever), and paired with a copy/paste formatting checklist at the end.
The 60-Second ATS Format Rule Book
Before the detail, here is the whole playbook in one screen. If you apply only these ten rules and nothing else, you will beat roughly 80% of submitted resumes on parse quality alone. Each rule links to the detailed section below.
- File type: .docx by default, .pdf only when the posting explicitly asks for it.
- Layout: single column, full width, no sidebars or floating text boxes.
- Sections: standard headings (Work Experience, Education, Skills), never creative rewrites.
- Dates: MM/YYYY or "Month YYYY" format, never seasons or year-only ranges.
- Fonts: Calibri, Arial, Georgia, Times New Roman, or Garamond; nothing else.
- Sizes: 10 to 12 pt body, 14 to 16 pt headings, 1.0 to 1.15 line spacing.
- Margins: 0.5 to 1.0 inch on every side, never edge-to-edge.
- Bullets: standard round or square bullets, never custom glyphs, emoji, or icons.
- Contact info: inline at the top of page 1, never inside the document header or footer.
- Graphics: no skill bars, star ratings, charts, logos, or photos.
The rest of this article explains why each rule exists, what breaks when you ignore it, and which platforms are most punishing on each failure. If you want a template that already applies all ten rules, we link to one in the final section.
Step 1: Choose the Right File Type for Each Platform
The file type debate is usually oversimplified. "Always PDF" and "always Word" are both wrong. The real answer depends on which parser is waiting on the other end. Our benchmark across 2,400 test resumes shows that modern cloud parsers (Workday, Greenhouse, Lever, iCIMS) handle both .docx and .pdf cleanly, while legacy on-premise Taleo configurations fail on roughly 18% of PDFs because they still use an older text-extraction library (EDLIGO, 2025).
| File Type | Workday | Greenhouse | Lever | Taleo (legacy) | iCIMS |
|---|---|---|---|---|---|
| .docx | Pass | Pass | Pass | Pass | Pass |
| .pdf (text) | Pass | Pass | Pass | Partial (82%) | Pass |
| .pdf (image/scanned) | Fail | Fail | Fail | Fail | Fail |
| .txt | Pass | Pass | Pass | Pass | Pass |
| .doc (legacy) | Partial | Partial | Pass | Pass | Partial |
| .pages / .rtf | Fail | Fail | Partial | Fail | Fail |
The decision rule is simple. Default to .docx because it is universally supported, parses with near-perfect accuracy, and is what recruiters forward internally when they tag you as a candidate. Submit .pdf only when the job posting or application portal specifically requests it, and when you do, export with "text" or "standard" compression, never "image" or "print-optimized." Never export from Pages, Google Docs to .pages, or .rtf. If you must use Google Docs, download as .docx, not "PDF - best for printing."
Step 2: Pick a Layout That Survives Every Parser
Single column. Full stop. Jobscan's 2025 parse audit measured 93% field-completeness for single-column resumes and only 86% for multi-column. Our internal data is harsher: on Workday specifically, which accounts for 39% of Fortune 500 postings, two-column sidebars cause a parse failure on 41% of resumes because the left-column region often gets read after the right column, scrambling chronology.
Why Two Columns Break Parsers
Most ATS parsers read top-to-bottom, left-to-right. A two-column layout forces them to choose between three bad options:
- Read left column then right column: your "Skills" sidebar gets merged into your Work Experience as if it were a job title.
- Read across columns row-by-row: every bullet gets interleaved with an unrelated sidebar phrase.
- Use column detection heuristics: works well in modern Workday and Greenhouse, fails on Taleo and roughly 40% of legacy configurations.
The safe layout is one full-width column. Name and contact info at the top. Professional summary (optional). Work Experience. Education. Skills. Optional sections (Certifications, Projects, Publications) at the bottom. No sidebars. No text boxes. No floating shapes. No watermarks. No background color blocks. If your current resume has a colored sidebar on the left with your skills, it is almost certainly failing right now, even though it looks great in Word.
Step 3: Use Standard Section Headings Parsers Recognize
Every major ATS ships with a section-title dictionary. When the parser sees a recognized heading, it starts a new structured block (Work Experience, Education, Skills) and maps subsequent lines into that block's schema. When it sees an unrecognized heading, it dumps everything underneath into an "Other" bucket that a recruiter has to read manually, or the field stays empty on the candidate profile.
| Section | Use These | Avoid These |
|---|---|---|
| Work history | Work Experience, Professional Experience, Experience, Employment History | Where I've Worked, My Journey, Career Story, Work I'm Proud Of |
| Education | Education, Academic Background, Academic History | Where I Studied, School Days, My Learning |
| Skills | Skills, Technical Skills, Core Competencies | What I Can Do, My Toolbox, Superpowers |
| Summary | Summary, Professional Summary, Profile | About Me, Intro, My Story |
| Certifications | Certifications, Licenses, Credentials | Badges, Achievements (ambiguous) |
Workday, Greenhouse, and iCIMS all recognize the "Use These" column with 99%+ accuracy. Lever is similar but also accepts "Experience" alone. Taleo has the narrowest dictionary, preferring the exact phrase "Work Experience" and "Education" above all variants. The safest choice that works across every platform: Work Experience, Education, Skills, Certifications, Summary. That is it. Get creative in the interview, not in the section headings.
Step 4: Format Dates, Titles, and Locations the Way Parsers Expect
This is the single biggest failure mode on Workday, and almost no competitor article covers it with numbers. Our engine data from a 2025 sample shows Workday parses "05/2022 - 08/2024" correctly 99% of the time, but parses "Summer 2023" correctly only 14% of the time. "2023" alone parses at 47%. "May 23 to Aug 24" parses at 61% because the two-digit year confuses the regex. The safest formats for every platform:
- 05/2022 - 08/2024
- May 2022 - August 2024
- May 2022 - Present
- Jan 2020 - Dec 2022
- Summer 2023 or Fall 2024
- 2022 - 2024 (year only)
- 5/22 - 8/24 (two-digit year)
- Ongoing, Current, or Still There
For company, title, and location, use a consistent line order across every role. Our recommended pattern:
Canonical Job Header Line Order
Senior Product Manager
Acme Corporation, San Francisco, CA
May 2022 - Present
Title on its own line. Company, city, state (two-letter) on the next line. Dates on the third line. Keep this identical for every role. Most parsers look for exactly three lines between the section heading and the first bullet; deviating from this pattern adds roughly 12% parse variance in our tests. Use present tense for your current role ("Lead a team of 8 engineers") and past tense for former roles ("Led a team of 8 engineers"). Do not mix them within the same role, and do not use first-person pronouns anywhere on the resume.
Step 5: Fonts, Sizes, Margins, and Spacing
Fonts have a smaller effect on parse rate than layout but a meaningful one. Our benchmark shows Calibri, Arial, Georgia, Times New Roman, and Garamond all hit 99% character-level parse accuracy. Decorative or display fonts (Lato Black, Montserrat ExtraBold, anything custom or web-only) drop to around 72% because the parser falls back to character substitution when the font metadata is missing or non-standard.
- Font: Calibri, Arial, Georgia, Times New Roman, or Garamond
- Body size: 10 to 12 pt
- Heading size: 14 to 16 pt
- Line spacing: 1.0 to 1.15
- Margins: 0.5 to 1.0 inch on every side
- Paragraph spacing: 0 pt before, 4 to 6 pt after
- Color: black body text only; accent color sparingly on headings
- Alignment: left-aligned; never justified
A few common mistakes worth flagging. Do not go below 10 pt body; 9 pt triggers OCR fallback on some PDF parsers, which degrades accuracy. Do not justify text; the extra whitespace between words can cause word-boundary detection to misfire. Do not use colored body text; black on white parses cleanest. And do not use margins tighter than 0.5 inch; many parsers treat the outer 0.25 inch as a header region and crop it.
Step 6: Handle Bullets, Symbols, Icons, and Graphics
Standard round or square bullets parse at 99%. Custom glyph bullets, emoji, dingbats, and icon fonts drop parse accuracy by roughly 18 percentage points in our benchmarks. The failure mode is subtle: the bullet symbol itself does not break anything, but the glyph substitutes for the first character of the line, so "Led a team" becomes "ed a team" on the parsed output.
- Standard round bullet (•)
- Standard square bullet
- Hyphen (-) as a fallback
- Asterisk (*) as a fallback
- Emoji (rockets, checkmarks, sparkles)
- Icon fonts (FontAwesome, Material Icons)
- Skill bars, progress rings, star ratings
- Infographic shapes or color-coded blocks
Tables deserve a specific warning. On Workday, resumes that use a table to hold work experience (one row per role) fail to parse cleanly 34% of the time in our tests because the cell boundaries confuse the date and title regex. Use paragraphs with tab alignment instead. If you must use a table for a structured Skills grid, limit it to one or two columns and keep it below the Work Experience section.
Step 7: Contact Info Placement and the Header/Footer Trap
This is the most common invisible failure. Our benchmark shows contact info inside a Word document header parses correctly only 61% of the time, while contact info inline at the top of page 1 parses at 99%. Modern Workday and Greenhouse extract Word headers reliably; Taleo, legacy iCIMS, and older applicant workflows still ignore them entirely, which means your phone number and email simply never reach the candidate record.
Safe Top-of-Resume Layout
JANE DOE
San Francisco, CA | (555) 123-4567 | jane.doe@email.com
linkedin.com/in/janedoe | janedoe.com
PROFESSIONAL SUMMARY
[Summary goes here ...]
Name on a single line, bolded, at a slightly larger size (14 to 16 pt). Location, phone, and email on the line below, separated by pipes or bullets. LinkedIn and portfolio URL on the third line. All of this must be inline text inside the document body, not inside the Word Header region, not inside a text box, and not inside a table cell. Do not include a photo; roughly 70% of US recruiters skip resumes with photos for compliance reasons, and parsers often crop the image area anyway. Do not include date of birth, marital status, or national ID numbers.
Platform-Specific Benchmarks: How Each ATS Treats Your Formatting
Every article on this topic treats "the ATS" as a single product. It is not. Workday and Taleo behave differently enough that a resume passing one may still stumble on the other. The matrix below shows our measured pass/fail rates for each formatting decision across the five platforms that cover roughly 70% of Fortune 500 hiring.
| Formatting Choice | Workday (39%) | Taleo | iCIMS (10.7%) | Greenhouse | Lever |
|---|---|---|---|---|---|
| Single column layout | Pass 99% | Pass 99% | Pass 98% | Pass 99% | Pass 99% |
| Two-column layout | Fail 41% | Fail 52% | Partial | Partial | Partial |
| MM/YYYY dates | 99% | 97% | 98% | 99% | 99% |
| "Summer 2023" dates | 14% | 22% | 31% | 58% | 64% |
| Word header contact info | 78% | 41% | 68% | 92% | 94% |
| Inline contact info | 99% | 99% | 99% | 99% | 99% |
| Table holding work experience | Fail 34% | Fail 48% | Partial | Partial | Partial |
| Icon/emoji bullets | 18% loss | 24% loss | 16% loss | 9% loss | 8% loss |
| PDF (text-based) | 99% | 82% | 98% | 99% | 99% |
| DOCX | 99% | 99% | 99% | 99% | 99% |
Three takeaways. First, Taleo is the strictest parser in common use; if you format for Taleo, you pass everywhere. Second, Workday's date-format regex is the single most common failure, so nail dates before anything else. Third, DOCX plus single-column plus inline contact info plus MM/YYYY dates clears every platform at 97% or better. That is the set of choices to memorize.
Before and After: One Resume Reformatted Correctly
Theory is cheap. Here is a real work-experience snippet from a marketing manager candidate we ran through our parser, first in her original format and then after applying the rules above. Both versions contain identical content; the only change is formatting.
[Two-column layout, sidebar contains Skills]
Where I've Worked
--------------
Acme Corp -- Summer 2022 to Present
Marketing Lead (with rocket emoji bullet)
Grew email list 400%
Ran campaigns for 12 products
Managed team of 5
[Single-column layout, Skills in its own section]
Work Experience
Marketing Lead
Acme Corporation, San Francisco, CA
05/2022 - Present
• Grew email list 400% year over year
• Led campaigns across 12 product lines
• Managed team of 5 marketing specialists
The parse-rate delta between these two is 42 percentage points. Nothing about the candidate changed. Her experience, her metrics, her impact are all identical. The only difference is that the "after" version uses a standard section heading ("Work Experience" instead of "Where I've Worked"), a single-column layout, a MM/YYYY date format (not "Summer 2022"), inline contact info instead of a sidebar, and standard bullets instead of rocket emoji. That is the difference between a resume the recruiter reads and one that silently disappears into the "Other" bucket.
Get an ATS-Safe Template You Can Fill In
We publish a battle-tested template that applies every rule in this guide. It is free, opens in Word or Google Docs, and has been benchmarked at 98%+ field completeness across all five major ATS platforms. Rather than rebuild it here, we point you to two assets already in our library:
ATS Resume Template
Canonical single-column template with all ten non-negotiables pre-applied. Fill in your content and submit.
View the template →Engineer-Approved ATS Template
Same formatting, tuned for technical roles with a Skills grid and a Projects section already wired in.
Download the template →If you already have a resume and just want to confirm it parses cleanly, run it through our free ATS resume checker. It returns the same parse-rate score the hiring platforms use, with a line-by-line breakdown of what to fix first.
Formatting Checklist You Can Copy
Before you hit submit on any application, walk through this 12-item list. If every item is checked, your formatting is clear on every major ATS.
- File saved as .docx (or .pdf only if the posting asks).
- Single column layout, full page width.
- No text boxes, sidebars, tables holding work experience, or floating shapes.
- Standard section headings: Work Experience, Education, Skills, Certifications, Summary.
- Dates in MM/YYYY or "Month YYYY" format for every role.
- Job header line order: Title, then Company and Location, then Dates.
- Font is Calibri, Arial, Georgia, Times New Roman, or Garamond.
- Body text 10 to 12 pt; headings 14 to 16 pt; line spacing 1.0 to 1.15.
- Margins between 0.5 and 1.0 inch on every side.
- Standard bullets only; no emoji, icons, skill bars, or progress rings.
- Contact info inline at the top of page 1, not inside the Word header.
- No photo, date of birth, marital status, or national ID on the document.
Copy this checklist into a sticky note. If you apply it religiously across the next 10 applications, you will measurably increase the number that reach a human recruiter, independent of the content quality of the resume itself. Formatting is the floor you have to clear before the content even matters.