11 min read
Your bullets might be strong. Your timeline preview might still show a six-month hole you never had. That's what gets you sorted out before a human opens bullet one, and it's more common than missing a keyword.
You can't fix what you don't see. Most candidates never open the employer's preview pane after upload. They assume the PDF they wrote is the record the recruiter sorts on. It isn't.
How resume timelines are scored isn't a mystery box. Portals store employment as structured fields: employer, title, start month, end month, computed tenure. Recruiters sort and filter on those fields. When the parser guesses wrong, you'll look underqualified or unstable on the first screen. Check your resume for free with a target posting pasted in. You're confirming the timeline imported the way you intended, not debating date aesthetics.
Job searching while you're employed is hard enough. You shouldn't lose a callback because Workday assumed January when you meant June. The fixes are boring and specific, which is why they work.
Below: the symptom recruiters react to first, three causes that drive bad timeline scores, how to tell which one is yours, and the fix for each. When dates are clean and you want keyword alignment, 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.
- Label contract, part-time, and consulting in the title line.
- Split internal promotions into separate dated rows.
- Read the portal preview timeline before you assume the file is fine.
The symptom: tenure that doesn't add up on the preview
Recruiters scanning Workday or Greenhouse react to timeline noise before they read accomplishments. The symptom is consistent: employment blocks that don't line up, unexplained white space between roles, tenure totals that look short for the seniority claimed, or overlapping full-time rows with no label.
Timeline scoring starts in the parsed date fields, not in your summary. A posting that asks for five years of SQL ownership runs a filter on computed tenure from start and end months. If the parser guessed December 2019 when you started June 2019, you might miss the cutoff by five months on paper while the real history qualifies.
Humans read the same preview. A recruiter sees a gap between 2018 and 2020 and wonders if you were unemployed for eighteen months. They don't always email to ask. They pass when forty similar files arrived that morning.
Title progression matters on the same screen. Analyst for two years, then Senior Analyst for three, then Manager reads as growth. One block that says Analyst 2016 to 2024 hides a promotion the hiring manager wanted to see in the first eight seconds.
For file-type issues that scramble dates even when months are present, read month-year vs year-only on resume dates . Format dates correctly first, then confirm the export didn't drop them.
Three causes, how to spot yours, and the fix for each
Cause 1: Year-only dates force bad tenure math
How to tell: every role shows years only while your background form lists months. The preview shows phantom gaps between adjacent jobs or inflated tenure on short contracts.
Before: Quality Technician | 2019 to 2021. Next role starts March 2020 in reality. Preview shows overlap or a blank gap depending on the portal guess.
After: Quality Technician | March 2019 to August 2020. Next role | September 2020 to Present. Tenure math matches your actual history.
The fix: spell Month Year on every Experience line. Education graduation years can stay year-only. Never mix formats on one page.
Cause 2: Hidden gaps and unlabeled short stints
How to tell: the preview flags a six-month hole you know you were working contract. Or four roles under ten months each with no contract label reads as job-hopping.
Before: Four employers in two years, no contract labels, year-only date bands stacked to hide length.
After: Each client on its own line. Quality Technician (contract via Apex Staffing) | March 2020 to July 2020. Next client with Month Year range. Gaps labeled: Professional development | January 2021 to April 2021.
I've screened stacks in Workday where year-only dates turned a real six-month contract gap into a phantom eighteen-month hole between two full-time roles. Month Year on both sides fixed the preview without changing a single bullet.
The fix: label contract and consulting in the title line. Address intentional gaps with Month Year boundaries and one honest phrase. Don't blur gaps into year-only blocks that touch adjacent employers.
Cause 3: Dates trapped in tables or wrong order
How to tell: the PDF looks fine but the preview shows blank end dates, swaps employer order, or puts dates on lines without job titles above them.
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 gap labels. Dates in table cells often import without attaching to the employer row. List reverse chronological with no reordering tricks.
Copy-paste block: timeline lines recruiters trust
Employer Name, City ST
Job Title | Month Year to Present
Employer Name, City ST
Job Title (Contract) | Month Year to Month Year
Employer Name, City ST
Analyst | June 2018 to February 2020
Employer Name, City ST
Senior Analyst | March 2020 to Present
Gap line (if needed)
Professional development | Month Year to Month Year
Run a plain-text paste test after you reformat. Copy the export into Notepad. If dates appear without employer names above them, flatten again before upload.
Edge case: overlapping full-time and part-time roles. Month Year makes overlap visible. Add Part-Time or Consulting in the title line. Hiding overlap with year-only creates worse questions on the screen call.
Edge case: internal promotion at one company. List Analyst and Senior Analyst as separate rows with distinct Month Year ranges so progression shows on the timeline filter, not buried inside one vague block.
For how title changes affect search, see how recruiters interpret job titles . Tenure and title filters often run together on the first screen.
Edge cases where a clean timeline still fails the preview
Month Year is the right default. These exceptions explain why a corrected file can still look wrong after upload.
Stale Present on a job you already left. An open end date on a closed role breaks tenure math and background checks. End every closed role with an end month, even when the work was positive.
Future-dated end months from typos. March 2027 on a 2024 role breaks computed tenure. Spell months out so you catch typos spell-check misses.
Seasonal work as one long 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 on the timeline chart.
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 master file you upload elsewhere.
Before: Manager | 2018 to 2020 then Director | 2020 to 2022 with no months on either line.
After: Manager | June 2018 to February 2020 then Director | March 2020 to Present. Promotion month is visible. No phantom gap between February and March.
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.
Recruiters running minimum-experience filters count months, not vibes. A posting that asks for five years in a given function needs a start month that proves you cross the line. How resume timelines are scored depends on those parsed fields matching reality.
Keep the same punctuation between dates on every line. January 2022 to March 2024 beats mixing hyphens and en dashes when your file will paste into plain text boxes. 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 severance paperwork later. The resume isn't the place to round up tenure.
New grads should 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.
Verify the timeline before the next application
Upload your reformatted file and the posting to HireFlow's free ATS resume checker . Confirm each employer row 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
Resume timeline scoring runs on parsed dates, tenure, gaps, and title progression. Month Year on every role, honest labels on contract work, and a flat one-column layout stop phantom gaps from failing filters before your bullets get read.
- Convert year-only roles to Month Year tonight.
- Label contract stacks and intentional gaps.
- Split promotions into separate dated lines.
- Flatten tables so dates sit beside titles.
- Read the preview timeline before you assume the file is fine.
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
Most corporate ATS builds store start month, end month, and tenure as separate fields. A gap of a few months between roles usually passes. Unexplained gaps of six months or more can trigger a flag when a recruiter sorts by continuous employment or when a minimum-tenure filter runs on the parsed timeline. Label intentional gaps with Month Year boundaries and one honest line: Sabbatical, Contract gap, or Caregiving leave.
One six-month stint rarely kills a file on its own. A pattern of four roles under twelve months each reads as instability in both the ATS preview and the recruiter skim. Label contract or project work in the title line. Month Year dates make short stints visible and honest; year-only blocks that hide them look worse when the background check surfaces the real dates.
Yes. Year-only ranges force Workday and Greenhouse to guess start and end months. Those guesses often create phantom gaps or inflated tenure in the preview. Recruiters running five-year experience filters count on parsed months, not the years you typed. Month Year on every role removes the guesswork on both sides.
Real overlap is fine when it's labeled. Part-time, consulting, or concurrent contract roles need that word in the title line and Month Year dates on each row. Two full-time jobs with overlapping dates and no label reads as a data error and lowers trust before anyone reads your bullets.
They read title changes left to right on the first screen: Analyst, then Senior Analyst, then Manager on ascending dates signals growth. Same title for nine years with no scope change raises a different question. Internal promotions should appear as separate lines with updated titles and Month Year ranges, not one vague block that buries the promotion month.