The 11 formatting mistakes most likely to disrupt ATS extraction are columns, floating text boxes, unlabeled icons, header-only contact details, layout tables, photos and graphics, unusual headings, detached dates, decorative fonts, scanned PDFs, and excessive visual density. Test the final file because Workday, Greenhouse, Taleo, and employer configurations do not parse every document identically.
Formatting does not replace qualifications, and no layout guarantees selection. It removes avoidable friction so your real evidence reaches the candidate record. For a system-wide view, read how to beat an ATS system.
Key Takeaways
- Use one clear reading path.
- Keep required facts in body text.
- Write labels instead of relying on icons.
- Keep dates beside their roles.
- Export selectable text and test it.
How format failures appear in Workday, Greenhouse, and Taleo
Workday can expose extraction errors when it populates candidate-profile experience, education, and contact fields. Greenhouse commonly preserves an uploaded resume for recruiter review while also making extracted content searchable. Taleo has many implementations and conversion paths. None should be treated as one fixed parser across all employers.
The same file may behave differently after an employer update or conversion. Use format principles that reduce dependencies, then test. Workday resume formatting covers that platform in more depth.
| Mistake | Possible extraction symptom | Repair |
|---|---|---|
| Columns | Merged reading order | Single flow |
| Text boxes | Missing sidebar | Body paragraphs |
| Tables | Dates detach | Consecutive role blocks |
| Scanned PDF | No text | Direct export |
Key Takeaway: System brand matters less than building a file with a simple, testable reading order.
1. Splitting the page into two or three columns
Columns save space visually, but they introduce competing reading paths. A parser may read the entire narrow sidebar first, merge each left line with the adjacent right line, or move skills away from the roles that support them. The result can look like a candidate with missing employers, displaced dates, or a summary interrupted by software names.
Workday often maps extracted content into structured profile fields, so mixed order can affect more than the resume preview. Greenhouse may preserve readable text but still index terms without useful context. Taleo implementations vary. Replace layout columns with one continuous flow: contact, summary, skills, experience, education, and credentials. If you keep columns, paste the final file into plain text and read every line in order.
Before: a two-column page with skills stacked on the left and jobs on the right. After: one column with contact, summary, skills, then reverse-chronological experience. Recruiters can still scan quickly, and a parser no longer has to guess which column comes first.
Key Takeaway: One reading path is safer than asking a parser to reconstruct columns.
2. Building content with floating text boxes
Text boxes are separate drawing objects, even when they look like ordinary paragraphs. Export software may place their text at the end, omit it, or insert it between unrelated lines. Resume templates often use boxes for contact information, skills, and job dates, which means the highest-value facts carry the greatest extraction risk.
Open the Word Selection Pane and inspect every object. Move names, phone numbers, credentials, employers, dates, and skills into ordinary paragraphs. Use paragraph borders or shading when you need visual structure. Canva and design-tool exports deserve extra testing because selectable text can still have an unexpected internal order.
If a template uses a boxed header for your name and phone, recreate that look with ordinary body text and spacing. Visual polish is allowed; a separate drawing layer is the problem. Repeat the paste test after every export, not only after the first design change.
Key Takeaway: Keep required information in the main document flow.
3. Replacing words with icons and rating graphics
A phone handset does not necessarily become the word Phone. An envelope does not become Email. Five circles beside Python may extract as five unrelated characters, not an advanced skill level. Recruiters also have no shared definition for stars, bars, rings, or dots, so the graphic adds ambiguity even when it survives parsing.
Write Phone, Email, LinkedIn, Portfolio, and every skill in plain text. Describe proficiency through evidence rather than a meter: built forecasting scripts in Python, or created monthly Tableau dashboards for finance leaders. Decorative icons may remain only when the same information is fully present as text and the plain-text reading order stays clean.
Before: five filled dots beside Excel. After: “Excel: PivotTables, XLOOKUP, Power Query” in Skills, plus a dated bullet showing the workbook and audience. The second version is searchable and discussable in an interview.
Key Takeaway: A symbol is decoration; a written label is searchable information.
4. Hiding contact information in headers or footers
Word headers and footers sit outside the primary document body. Modern systems may capture them, but conversion routes and employer settings differ. If the parser misses a header, the candidate record can lose a phone number, email, credential, or portfolio URL. Footers also repeat on every page and can interrupt extracted work history.
Place essential contact information directly beneath the name in the body. Use body spacing to create a header-like appearance without the Header tool. Keep page numbers or genuinely nonessential marks in the footer. Then test the final DOCX or text-based PDF, because export behavior matters as much as the editable source.
On a second page, repeating the full header block is unnecessary. Keep the name and one contact method in body text if a recruiter prints only page two. Do not hide a LinkedIn URL solely in a footer that some parsers skip.
Key Takeaway: Put contact data in body text where extraction and humans can find it.
5. Putting work history or skills inside tables
Tables can create clean alignment, but their internal cell order may not match the visual page. A parser might read all dates before all titles, combine two employers, or detach a skill from its heading. Merged cells, nested tables, and invisible layout grids increase the risk. The page can look flawless while the extracted profile becomes incoherent.
Turn on Word table gridlines to expose hidden structures. Convert essential sections to paragraphs and use tab stops sparingly for alignment. Keep each employer, title, location, and date in one consecutive block. A simple table may work in a tested workflow, but broad applications across Workday, Greenhouse, Taleo, and iCIMS favor fewer structural dependencies.
If you need a skills grouping, use a labeled paragraph: “Data: SQL, Tableau, Excel Power Query.” That is still one reading path. A nested skills table with merged headers is the layout that usually fails first.
Key Takeaway: Use tables for comparison documents, not for essential resume chronology.
6. Adding photos, logos, charts, or infographic blocks
Images provide pixels, not dependable searchable text. A company logo does not state the employer name. A university seal does not state the degree. A timeline graphic does not establish employment dates. Photos also consume space that could show relevant evidence and may be inappropriate in many United States applications.
Remove photos and logos unless a legitimate local or role-specific instruction calls for them. Replace charts with concise outcomes in text. Write employer, institution, degree, certification, and dates explicitly. If a portfolio role benefits from visual work, link to an accessible portfolio and let the resume remain a readable index of experience.
United States private-sector applications rarely need a headshot. If you are applying internationally as well, keep a US-safe text resume and a separate version only when a market actually expects a photo.
For official hiring-rights information, consult the EEOC. Employer practice resources are available from SHRM.
Key Takeaway: Images should never carry a qualification the application needs.
7. Inventing unusual section headings
Creative labels such as My Journey, Superpowers, Toolbox, Where I Have Made Magic, or Learning Adventures force software and people to infer meaning. Some systems use heading cues when separating experience, education, skills, and certifications. Even when all text extracts, an unusual label can put content in the wrong conceptual section.
Use Experience, Professional Experience, Skills, Education, Certifications, Projects, Publications, or Volunteer Experience. Choose only sections that fit your history. You can express personality through precise accomplishments and project choices without renaming the basic information architecture.
If you want a career-change frame, keep the heading as Summary or Professional Summary and put the transition sentence there. Do not rename Experience as Relevant Superpowers. Parsers and tired recruiters both benefit from familiar labels.
Mid-article check: scan the current version with HireFlow, then inspect the plain-text output instead of relying only on the score.
Key Takeaway: Standard labels help software classify sections and help recruiters scan.
8. Separating dates from titles and employers
Dates placed in a far-right box or left rail can detach from the role they describe. The parser may assign 2022–2024 to the next employer or treat a graduation year as employment. Workday profile imports make these errors visible when an applicant suddenly appears to hold overlapping or implausibly short jobs.
Put each date range on the title line or immediately below it. Use a consistent Month Year format, such as March 2023–August 2026. Do not rely on a vertical timeline, dots, or connector lines. Read the plain-text version and confirm that every date follows or precedes the correct title without needing page coordinates.
Before: a left-rail date column and a right-rail employer column. After: “Operations Analyst, Acme Logistics, Dallas, TX, March 2023–Present” as one block. Workday field mapping is far more reliable when those four facts travel together.
Key Takeaway: Chronology should remain understandable after every visual alignment disappears.
9. Using decorative fonts, tiny type, or symbol bullets
Decorative fonts can substitute characters during PDF export, while tiny text invites keyword stuffing and harms human readability. Complex ligatures, all-cap display faces, and custom icon fonts create avoidable conversion dependencies. Symbol bullets can become question marks or unrelated glyphs, although ordinary bullets are usually harmless.
Use a common readable font at a practical size, with consistent heading hierarchy and spacing. Standard round bullets, hyphens, or simple paragraphs work. Embed fonts when the export process supports it, then test selection and paste. A recruiter should be able to read the document comfortably at normal zoom.
Calibri, Arial, Georgia, Aptos, and Times New Roman are ordinary choices. If a PDF substitutes boxes for letters, the font did not embed. Re-export from the source file instead of printing to a virtual printer.
Key Takeaway: Typography should clarify hierarchy without changing characters or hiding text.
10. Submitting a scanned or flattened PDF
A scan can look exactly like a resume while containing no selectable text. Some systems apply optical character recognition, but accuracy varies with resolution, contrast, alignment, and font size. Names, dates, and abbreviations are especially costly OCR errors. A flattened design export can create the same problem.
Select a sentence in the PDF and paste it into a plain editor. If nothing appears, or the entire page selects as one image, export directly from the source application instead of printing and scanning. Follow the employer request for DOCX or PDF. Never assume a PDF is automatically more compatible.
Phone photos of printed resumes create the same failure. If you must send a PDF, generate it from Word, Google Docs, or a builder that exports selectable text. Then select a middle bullet and confirm it copies as words.
Key Takeaway: A visible page is not necessarily a text document.
11. Overdesigning the page until the story disappears
Formatting can technically parse and still fail the reader. Dense skill clouds, excessive color blocks, repeated side labels, narrow margins, long all-cap headings, and six bullet levels make evidence hard to find. Recruiters ultimately assess whether experience fits the role, not whether every available design feature was used.
Build a restrained hierarchy: clear name and contact line, recognizable headings, consistent role blocks, short paragraphs or bullets, and enough white space to separate ideas. Keep the most relevant recent evidence prominent. Test the result in plain text, but also print or view it at normal size and scan it as a recruiter would.
If shrinking margins and type is the only way to keep a third page of weak duties, cut content instead. Parsing and human review both fail when the page is a wall of compressed text, even if every character extracts.
Key Takeaway: ATS-safe formatting also needs to help a busy human understand fit.
Three before-and-after formatting repairs
- Before: dates in a left rail; jobs in a right column. After: each employer, title, location, and date appears in one consecutive block.
- Before: envelope and handset icons with unlabeled details in a header. After: Email and Phone labels appear under the name in body text.
- Before: five-dot skill ratings inside a table. After: plain skill names are supported by dated accomplishment bullets.
Key Takeaway: Preserve the information hierarchy after visual coordinates and decoration disappear.
Run this final formatting checklist
- Open the final submitted file.
- Select and copy all text.
- Paste into a plain-text editor.
- Confirm contact details appear first.
- Read every role and date in order.
- Search required title, tools, and credentials.
- Reveal Word gridlines and drawing objects.
- Confirm the PDF contains selectable text.
- Check readability at normal zoom.
- Run a job-specific compatibility check.
Use the free ATS compatibility test workflow for detailed diagnostics.
Key Takeaway: Test the attachment the employer receives, not only the editable document.
Make the resume easy to extract and read
Repair the eleven mistakes, then check the result with HireFlow. Improve the substance with stronger outcome bullets. Clean formatting gives those facts a fair path into recruiter review.
Key Takeaway: The best format disappears behind clear, credible evidence.
Frequently asked questions
Use a single column, ordinary headings, body text, simple bullets, and dates beside roles. Follow the employer file instruction.
Not automatically. Some parse and others scramble. Construction and employer configuration matter, so test the exact export.
A simple table may parse, but nested cells and split work histories add risk. Use paragraphs for essential sections.
Keep them in the body because some extraction paths skip or separate headers and footers.
Icons do not reliably communicate meaning. Write Phone, Email, LinkedIn, and skill names as text.
A photo adds no searchable qualification and can complicate layout. It is generally unnecessary in United States applications.
Use Experience, Skills, Education, Certifications, Projects, and similarly standard labels.
Paste into plain text, inspect gridlines and objects, search core terms, and run a job-specific check.