12 min read
You didn't move cities. You didn't invent a gap year. Yet the Workday preview shows Denver, CO as your employer and your RN license renewal as your start date at the hospital. You're not failing a skills screen. You're failing a field map because location and dates mapping errors in US ATS files are layout problems that look like work-history problems.
Recruiters filter on geography and tenure before they read bullet one. When Greenhouse imports Remote as a blank city or reads 03/2019 as March instead of September, you vanish from the on-site list or show three years short. That's brutal when you're qualified and the req is ten miles away.
Before you rewrite bullets, check your resume for free and open the portal preview. If city, employer, or dates sit in the wrong column, no amount of keyword stuffing fixes the filter you're failing.
This page is a five-step procedure for Workday and Greenhouse location and date field mapping. You'll get quick wins, before and after pairs, two edge cases, and a copy-paste header block you can drop under every role tonight. You don't need a new template. You need the same four lines in the same order on every job block.
If you've already tailored keywords and the preview still shows wrong cities or dates, stop tuning verbs. The file isn't readable yet. Fix mapping first, then compete on fit.
Quick Wins
- Four-line header: Title, Employer, City, ST, Month Year to Month Year.
- Replace every slash date with Jan 2021 style ranges.
- Write Remote, Austin, TX instead of Remote alone.
Why Workday and Greenhouse scramble location and dates
ATS parsers do not see your design. They read plain text in export order. A sidebar with your city, a table with dates in column two, or a header that says Location: Denver pushes fields into the wrong database columns. Recruiters then search Denver as an employer or see a six-month job where you worked four years.
Location and dates mapping errors are silent. Nobody emails you to say your city imported wrong. You just stop appearing in geo filters. I've opened Greenhouse profiles where the candidate's MBA graduation imported as their current role start date because the degree block sat above experience in a two-column template.
Workday and Greenhouse are not identical, but both punish the same habits: cute layouts, inconsistent date styles, and location lines that float away from the employer they belong to. Fix the export order once and every application on those systems inherits the correction.
Read how ATS interprets recency in US resumes when your dates parse but tenure filters still feel off after the layout fix.
Workday and Greenhouse do not share one parser, but they share one habit: they read top to bottom inside the experience block you exported. Sidebars, text boxes, and floating date lines break both. The preview screen is your ground truth. If Denver imports as employer in Workday, assume Greenhouse would scramble the same file the same way until you flatten layout.
Contract and consulting candidates often list Client A and Client B with identical date ranges. Parsers assume job hopping. Stagger headers or note concurrent contract in bullet text so end dates stay honest without looking like three full-time jobs at once.
Fix location and dates mapping errors: five steps
Step 1: Open the portal preview on a draft upload
Upload before you spend an hour tailoring keywords. In Workday, open My Experience or the application preview. In Greenhouse, check the parsed profile after attach. Write down four rows: job title, employer, location, start date, end date. If any row is blank or swapped, stop. Layout fix comes first.
Screenshot the preview next to your Word file. Side-by-side proof saves you from arguing with yourself later about whether the portal changed.
Step 2: Lock the four-line job header order
Every role needs the same stack with line breaks, not tabs inside a table cell.
Copy-paste job header block: Job Title | Employer Name | City, ST | Month Year to Month Year, then bullet one with the top skill from the posting in the first eight words.
Before: Operations Analyst at a logistics firm with NYC and Summer 19 to Present on one line inside a two-column template.
After: Operations Analyst on line one, employer on line two, New York, NY on line three, Jun 2019 to Present on line four, single column, 11-point Calibri.
Step 3: Standardize every date to Month Year
Pick one style and use it on every role, including education if dates sit near experience.
Before: HR Specialist, 01/2017 to 03/18, previous role Jan 2020 to Present.
After: HR Specialist, Jan 2017 to Mar 2018; next role Jan 2020 to Present. Same separator, same four-digit years, spelled months throughout.
Step 4: Label remote work with a parseable anchor
Remote alone often becomes an empty city field. Recruiters running on-site reqs never see you. Hybrid postings still filter on metro area.
Before: Marketing Manager, XYZ Inc., Remote, Mar 2020 to Dec 2021.
After: Marketing Manager, XYZ Inc., Remote, Seattle, WA, Mar 2020 to Dec 2021. Add one bullet that names time zone or travel radius if the posting asks.
Step 5: Notepad test, then one clean re-upload
Copy the experience section from your export. Paste into Notepad on Windows or TextEdit plain mode on Mac. Each employer name should start its own line. Each date range should sit on one line or directly under its role. If lines merge, remove text boxes and re-export.
Re-upload once. Multiple versions without a material fix annoy recruiters and clutter audit trails. Keep the filename Company_Role_2026.pdf so you know which parse passed.
Edge case: overlapping contract roles
Two clients at once is legal; overlapping Month Year ranges confuse parsers. List the primary client with full dates. Note concurrent contract in bullet two: Also supported Beta Corp API migration evenings, Jan 2023 to Jun 2023. Do not stack two employer headers with identical date ranges unless both were W-2 jobs.
Edge case: international city on a US req
Toronto, ON is fine when honest. For US-only reqs, put your US work location on roles performed in the US and note remote from Canada only if true. Mixed Country labels in one block make geo filters guess. Split roles rather than writing USA under every line.
Before and after: clinical role with license line bleed
Before: Registered Nurse block with RN License renewed Apr 2025 above employer; Workday reads Apr 2025 as job start.
After: Registered Nurse, Memorial Hospital, Houston, TX, Jan 2022 to Present on four lines; license on its own Certifications line: Texas RN 1234567, active.
Before and after: table layout breaking Greenhouse
Before: Two-column table with dates in the right cell and titles in the left; Greenhouse pairs dates with the wrong employer.
After: Software Developer, DEF Ltd., Seattle, WA, Feb 2015 to Apr 2019 as plain lines; bullets below, no grid.
See US relocation on resume: how to reduce risk signals when your city line is honest but recruiters still hesitate on distance.
Military and federal candidates: spell out CONUS city when the req is civilian corporate. A PCS line belongs in a bullet, not in the location field of a private-sector role. Veterans often list Fort Bragg, NC correctly but forget to add the civilian metro they target next. Recruiters filtering Raleigh-Durham never see Fort Bragg as a match.
Education blocks deserve the same date discipline. MBA 2020 to 2022 sitting directly above experience with no section header can import as a job. Label Education explicitly and keep degree dates off the same visual row as your current employer unless you want the parser to count school as work.
When a portal lets you type city and dates manually after upload, still fix the resume file. Recruiters compare attachment to profile. Mismatches raise questions you do not need during a tight labor market.
Gig and freelance workers: list the platform or agency as employer when that is payroll truth, then name the client in bullet one with city and dates on the header lines. Parsers handle agency employer plus client site better than three client names with no parent employer row.
Save the corrected Word file and PDF together in one folder. Upload the version the preview liked. Small discipline beats re-fixing the same mapping error every Monday.
Where location and date lines still break
Vague geography. USA or Worldwide without city tells parsers nothing. Recruiters cannot tell if you're local.
Mixing date separators. Jan 2020 to Present on role one and 1/18 to 12/19 on role two splits the parser's brain.
Location inside the employer string. Acme Corp, Denver reads as one employer token in some imports.
Icons and flags for city. A pin emoji is not a city. Parsers skip it.
Degree dates above experience. Graduation lines look like job starts when they sit in the same visual column.
Assuming LinkedIn import fixes Word. Many portals re-parse your upload. Fix the file you attach, not only your profile.
Ignoring end dates on current role. Present is fine. Blank end date on a past role reads as still employed there.
Using state abbreviations wrong. CA means California in US reqs. Write Canada spelled out if that is the country. Ambiguous tokens drop location filters.
Hiding dates inside bullets. Tenure belongs on the header line. Dates buried in prose often never map to start and end fields recruiters sort by.
Uploading a LinkedIn PDF without checking order. Export order differs from a Word file you control. Always preview the exact attachment.
Verify field mapping before the next apply
Run your export through HireFlow's free ATS resume checker and confirm title, employer, city, and dates still sit on separate rows after upload simulation.
When the posting asks for a relocation note, use Generate a cover letter that names your parseable city and start availability without repeating the whole work history.
Give parsers a map they can read
Location and dates mapping errors in US ATS are fixable without rewriting your career. Standardize the four-line header, spell months, anchor remote lines, and paste into Notepad before you trust the preview. Recruiters want qualified people in the right city with believable tenure. Help them find you.
Pick your most recent role tonight. Rebuild the header block. Run the checker. Submit once with the file that survived the Notepad test. That's the whole game for Workday and Greenhouse field mapping.
Keep a folder of preview screenshots named by company and date. When a recruiter asks for an updated resume, you already know which export passed parsing. You are not guessing from memory at midnight before a deadline.
If you relocate mid-search, update city on every role that was truly local to that metro. Do not change historical cities to your new home. Honest geography plus a cover note about relocation beats a file that claims you worked in Austin when payroll was in Boston.
Students and new grads: list city on internships the same way as full-time roles. Campus city alone on the contact line does not tell a parser where your last clinical rotation or co-op placement actually happened.
- Title, employer, city, dates each on their own line.
- Month Year format on every role, no slashes.
- Portal preview matches your plain-text paste.
Run the free resume check on the corrected export before Monday's apply batch. Field mapping is boring work. It is also the work that stops silent rejections you never hear about.
Read more
Frequently asked questions
Workday often reads the first bold line under each job block as the employer. If your city sits on its own line between title and company, or lives in a left sidebar, the parser grabs Denver, CO instead of Acme Corp. Put Job Title on line one, Employer on line two, City, ST on line three, and Month Year dates on line four. Paste the export into Notepad and confirm employer names appear on their own rows before you upload.
Month Year with a spelled-out month and four-digit year: Jan 2021 to Mar 2024 or Jan 2021 to Present. Avoid 01/2021, Summer 2019, and Q3 2020. Slashes flip day and month depending on the parser. Season labels have no month anchor, so tenure math fails and recruiters see fake gaps.
Remote alone often imports as blank city and state. Use Remote, City, ST when you have a home base: Remote, Austin, TX. If the role was fully distributed with no anchor, Remote, US is better than a blank field. Match the posting language when they ask for location eligibility. Recruiters filtering on-site reqs need a parseable city, not a philosophy essay about flexibility.
It fixes whether recruiters can find you at all. Keyword scores assume the parser read your experience block in order. When dates attach to the wrong role or location lands in employer, years-of-experience filters and geography screens drop qualified files before keyword density matters. Fix field mapping first, then tailor bullets.
Try DOCX when the portal allows it. A plain Word file with line breaks usually keeps title, employer, location, and dates on separate rows better than a designed PDF from a template shop. If PDF is required, export from Word after you remove tables and sidebars. Run the same Notepad paste test on both formats before you assume the preview is wrong.