11 min read
Use Month Year on every US Experience line unless the application form literally won't accept months. Year-only ranges make Workday and Greenhouse guess start and end months, which often shows as a gap you never had. That's the answer. The rest of this page explains why recruiters read year-only as hiding short stints and how to fix each failure mode.
You're not overthinking a formatting detail. You're watching a qualified file get sorted out because the preview timeline doesn't match your actual employment. Before you reformat every line, check your resume for free with a target posting pasted in. You're confirming whether dates imported with employer names, not debating aesthetic preference.
Job searching while you're still employed is hard enough. Date math should not be the reason you get passed over. I've screened stacks where year-only dates made a six-month contract look like a two-year gap in the ATS preview.
Below you'll see the symptom recruiters react to, three causes that drive it, how to tell which one is yours, and the fix for each. When you're ready to apply, generate a cover letter that uses the same Month Year strings as your resume so nothing contradicts on upload.
Quick Wins
- Month Year on every role: January 2022 to March 2024.
- Present for current jobs. Pick Present or Current, not both.
- Same format on every line. No mixing 01/22 with January 2022.
- Contract stints get their own Month Year range, not one year block.
The symptom: phantom gaps and tenure that does not add up
Recruiters scanning Workday or Greenhouse previews react to timeline noise before they read bullet one. The symptom is consistent: employment blocks that don't line up, unexplained white space between roles, or tenure totals that look short for the seniority claimed.
Year-only dates are the most common trigger. When you write 2019 to 2021 for a role that ran March 2019 through August 2020, the importer may assume January 2019 through December 2021. Your next job starting September 2020 now overlaps or leaves a phantom gap depending on which guess the portal makes.
Humans read year-only the same way machines do, just faster. A recruiter sees 2018 to 2019 beside 2019 to 2021 and wonders whether you left in January or December. They don't always email to ask. They pass when forty similar files arrived that morning.
Month-year vs year-only on resume dates is not a style debate. It's whether the reader can reconstruct your timeline without inventing months you never typed. ATS portals store start month, end month, and tenure length as separate fields. Year-only uploads force defaults that you don't control.
For layout issues that scramble dates even when months are present, read how resume file type impacts screening . Format the dates correctly first. Then confirm the file type didn't drop them.
Three causes, how to spot yours, and the fix for each
Cause 1: You used year-only to hide short stints
How to tell: every role shows years only while your LinkedIn or background form lists months. Contract roles stack under one employer logo with 2020 to 2021 covering three clients.
Before: Apex Staffing (various clients) | 2020 to 2021. Three different plants, one date band, no months.
After: Client A Manufacturing, Dallas TX. Quality Technician (contract via Apex Staffing) | March 2020 to July 2020. Client B Assembly, Houston TX. Quality Technician (contract via Apex Staffing) | August 2020 to January 2021.
The fix: split each stint with Month Year. Label contract in the title line when it's true. Recruiters prefer honest short contracts over a vague year block that reads like hiding.
Cause 2: Mixed date formats on one page
How to tell: recent roles spell January 2022 while older roles show 2018 to 2019 or 03/18 to 08/19. The preview imports half the timeline and drops the other half.
Before: Current role: Jan 2023 to Present. Prior role: 2019 to 2021. Earlier role: 03/17 to 11/18.
After: January 2023 to Present. March 2019 to August 2021. March 2017 to November 2018.
The fix: pick Month Year spelled out and apply it to every role on the page. Spell the month to avoid day-first confusion on US reads. Education graduation years can stay year-only.
Cause 3: Dates trapped in tables or sidebars
How to tell: the PDF looks fine but the Workday preview shows blank end dates or swaps employer order. Plain-text paste puts dates before job titles.
Before: Job title in column one, employer in column two, 2021 to 2023 in a narrow right column inside a table.
After: Northline Corp, Chicago IL. Analyst | January 2021 to March 2023. One plain line for title and dates. Employer on the line above.
The fix: flatten to one column before you argue about Month Year versus year-only. Dates in table cells often import without attaching to the employer row. Move every date beside its role on plain text lines.
Copy-paste block: consistent Month Year lines
Employer Name, City ST
Job Title | Month Year to Present
Employer Name, City ST
Job Title | Month Year to Month Year
Employer Name, City ST
Job Title (Contract) | Month Year to Month Year
Education
Degree, University | Year only is fine here
Run a plain-text paste test after you reformat. Copy the Word export into Notepad. If dates appear without employer names above them, flatten again before upload.
Edge case: international candidates with DD/MM resume habits should still spell months for US reqs. Write January 2022, not 01/2022, when the employer is US-based.
Edge case: career gaps you took on purpose belong on the resume as gaps with Month Year boundaries, not as year-only blocks that blur into adjacent roles. A sabbatical line reads cleaner than a fuzzy 2020 to 2021 band with no employer.
For title alignment after dates are fixed, see how recruiters interpret job titles . Tenure math and title search run together on the first screen.
Edge cases where Month Year still fails the preview
Month Year is the right default. These exceptions explain why a corrected file can still look wrong after upload.
Portal caps fields at year only. Some government forms strip months on save. Match the form when you must, but keep Month Year on the resume file you upload elsewhere. Don't downgrade your master file because one portal is limited.
Overlapping full-time and part-time roles. Month Year makes overlap visible. That's correct. Add one word in the title line: Part-Time or Consulting. Hiding overlap with year-only creates worse questions on the screen call.
Future-dated end months from typos. March 2027 on a 2024 role breaks tenure math. Spell months out so you catch typos spell-check misses.
Seasonal work listed as one annual block. Retail or harvest seasons that repeat each fall need separate lines or a clear Seasonal label with Month Year per season. One line that says 2019 to 2023 for summer work reads false.
Exception: roles older than fifteen years where month precision adds no signal can stay year-only if every other role uses Month Year and you stay consistent within that era band. Don't mix 2019 to 2021 with January 2019 to March 2021 on the same page.
This won't fix applying to roles where your tenure genuinely falls short. It stops a qualified timeline from looking broken because the portal guessed months you never entered.
Before: Analyst | 2018 to 2020 then Manager | 2020 to 2022 with no months on either line.
After: Analyst | June 2018 to February 2020 then Manager | March 2020 to Present. Promotion month is visible. No phantom gap between February and March.
Recruiters running minimum-experience filters count months, not vibes. A posting that asks for five years of SQL ownership needs a start month that proves you cross the line. Year-only 2019 to 2024 might mean January 2019 or December 2019. Month Year removes the guesswork on both sides of the screen.
If you recently graduated, keep internships and co-ops on Month Year lines too. A co-op listed as 2024 alone hides whether you worked three months or nine. Hiring managers calibrate new-grad depth from term length, not degree date alone.
After you fix dates, scan for roles that still say Present on jobs you already left. Stale Present lines fail background checks faster than a short contract ever will. End every closed role with an end month, even when the work was positive.
Keep the same punctuation between dates on every line. January 2022 to March 2024 beats January 2022 - March 2024 when your file will paste into plain text boxes. En dashes sometimes survive export. Hyphens always do. Pick one separator and stick with it across the whole document.
When a role ended mid-month because of a layoff, use the actual last day month, not the quarter end you wish it had been. Honest end months prevent overlap fights with COBRA or severance paperwork later. The resume is not the place to round up tenure.
Verify dates before the next application
Upload your reformatted file and the posting to HireFlow's free ATS resume checker . Confirm each employer row still carries distinct Month Year ranges and that no role imported with a blank end date.
When you're rebuilding from a sparse file, build your resume with Month Year fields baked into the template so you don't revert to year-only on the next edit.
Do this now: Spell out Month Year on every Experience line, run a plain-text paste, upload once, read the preview timeline before Submit.
What to do now
Month-year vs year-only on resume dates is settled for US corporate applications: spell the month on every Experience line, keep education as year-only, and never mix formats on one page. Read the preview timeline before you assume the file is fine.
- Convert year-only roles to Month Year tonight.
- Split contract stacks into separate dated lines.
- Flatten tables so dates sit beside titles.
- Run a plain-text paste before export.
- Confirm the preview timeline matches your real history.
Open the req you're targeting. Run a free ATS check , fix any blank or guessed dates, and submit one clean upload.
Read more
Frequently asked questions
Month Year is the default for US corporate resumes unless the application form caps you at years only. Spell the month to avoid parser confusion: January 2022 to March 2024, not 01/22. Year-only ranges force Workday and Greenhouse to guess start and end months, which often surfaces as phantom gaps in the preview.
Use years only when every role spans full calendar years with no contract stints under twelve months, or when the employer's portal literally strips months on upload. Education graduation years are fine as year-only. Early-career roles from the 1990s can stay year-only if adding months adds no signal. Never mix formats on the same page.
Either Present or Current parses cleanly when paired with a Month Year start date. Pick one and use it on every open role. Avoid open-ended dashes with no end label. January 2023 to Present reads complete. January 2023 with a blank end field imports as incomplete in some Workday builds.
List each client or employer on its own line with Month Year start and end. Overlaps are fine when they're real. Year-only blocks that stack 2019 to 2021 for three contracts look like one long job or like hiding hops. Recruiters ask about overlap on the phone. The resume should show it honestly.
Recruiters already assume year-only hides short stints. Month Year reads honest and usually beats getting screened out for a guessed gap. If a contract lasted ten weeks, label it contract in the title line and move on. Hiding months trades one awkward question for a silent pass.