8 min read
You shouldn't have to choose between legal accuracy and a job application. Most US employers still run parsers built for a single-token surname. Compound names, maiden-name combinations, and Hispanic double surnames stress the same rules.
Check your resume for free before you trust Workday or Greenhouse autofill. If your name line sits in a header the extractor skips, the hyphen debate never starts because half your surname never imported.
Below: a comparison table for hyphen, space, and concatenated spellings, how each fails, and a decision rule for which one you'll standardize tonight.
What to compare before you pick a spelling
Judge formats on identity match, not parser comfort. A spelling that autofills cleanly but disagrees with your Social Security card will delay background checks.
| Criterion | Hyphen (Lopez-Garcia) | Space (Lopez Garcia) | Concatenated (LopezGarcia) |
|---|---|---|---|
| Matches legal ID | Yes when hyphen is on documents | Only if ID uses a space | Rarely matches official records |
| Typical parser split | First token before hyphen, second after | Often keeps final token only as last name | May read as one token or truncate |
| Workday autofill risk | High split across name fields | Medium dropped first surname | Medium mismatch with payroll |
| Greenhouse PDF read | Usually visible in attachment | Usually visible in attachment | Humans may not recognize spelling |
| Background check friction | Low when mirrored everywhere | Low when mirrored everywhere | High if HR cannot match records |
| Manual field fix required | Yes, every application | Yes, every application | Yes, plus explain spelling to HR |
None of the three formats autopills perfectly. The winner is the one that matches your ID, then gets typed the same way in every portal field.
Hyphenated format: when the dash is on your ID
Example legal line: Elena Ruiz-Mendoza. Parsers often assign Ruiz to first name and Mendoza to last name, or stuff Mendoza into a middle name box. The resume should still show the full string on one body line.
Before: Name only in Word header; body starts with Summary.
After: Elena Ruiz-Mendoza on line one of the body, then email and phone on the next lines.
Before: Elena Ruiz–Mendoza with an en dash from autoformat.
After: Elena Ruiz-Mendoza with a standard ASCII hyphen-minus.
After upload, set last name to the full Lopez-Garcia string when the form allows. Do not let autofill keep only Garcia because the hyphen triggered a split.
Space-separated format: when there is no hyphen on documents
Example legal line: Ana Martinez Rodriguez. Tokenizers trained on Anglo patterns may store Rodriguez as last name and drop Martinez entirely from structured fields.
Put the full surname string in the last-name application field even when the portal offers a middle name box. If the form has a single last-name character limit, watch for silent truncation and screenshot the field before submit.
On the resume, keep Martinez Rodriguez together on the same line as the given name. Two-column templates that park contact info in a sidebar can push the name below skills, which is the order parsers read.
Concatenated format: almost never worth it
Some candidates delete spaces and hyphens to beat splits: LopezGarcia. That rarely matches W-2 spelling, passport lines, or prior employer payroll. Background vendors flag inconsistent identity data and pause verification while someone calls you for clarification.
Concatenation is a parser hack, not a legal name. Use it only when you have legally adopted that spelling everywhere, which is uncommon. Otherwise stay with the ID format and fix fields manually.
Hyphenated name on resume: decision rule for US applies
Step 1: Open your state ID or Social Security card. The spelling there wins.
Step 2: Put that exact spelling on one resume body line with standard ASCII characters.
Step 3: Upload, then edit first name, last name, suffix, and preferred name in the portal until they match step 1.
Step 4: Repeat the same spelling on the I-9, direct deposit form, and email display name the recruiter will see.
I've opened Greenhouse next to a PDF where Lopez-Garcia looked perfect on the attachment but the parsed row showed Garcia alone. The coordinator never opened the file because the grid already looked wrong.
Federal contractor flows through structured resume builders still need the legal last-name box filled with the full compound string. Do not let the builder split at the hyphen just because the UI suggests it.
For autofill failures beyond names, see Workday resume autofill wrong fields and why ATS cannot read phone numbers . Same verification habit: never trust the first parse.
Mirror the chosen spelling outside the resume
Recruiters cross-check application data against prior employment verifications. If your resume says Lopez-Garcia but an old HRIS has Lopez Garcia without the hyphen, screening may pause for identity confirmation. That is paperwork friction, not a comment on your name.
Align email display names with legal spelling even when the address omits part of the surname. Calendar invites generated by scheduling tools sometimes strip hyphens. Confirm the invite before the interview.
When a portal truncates your last name, use the free-text comments field only for human reviewers. Comments do not fix parsing. They document that you submitted the full legal spelling elsewhere in the form.
Layout still matters. Single-column contact blocks at the top of the body parse more reliably than names trapped in design-tool headers, same rule as Workday resume format guidance .
Three tests before you click submit
- Copy-paste test: select all resume text, paste into Notepad. Your full name should appear on one line before work history.
- PDF search test: Ctrl/Cmd+F the complete hyphenated string. If search fails, the name may be an image layer.
- Field review test: after autofill, read first, last, and preferred name aloud against your ID. Fix before submit.
Apostrophe names and accented characters add similar tokenizer failures on older Taleo and iCIMS instances. The manual verification rule does not change: type what is on your ID, then confirm every field.
Catch layout issues that hide your name
Name splits are worse when the extractor never saw your contact block. Headers, footers, and two-column sidebars are the usual cause.
Run the free ATS checker on the PDF or DOCX you plan to upload. Fix reading order first, then re-check name fields in the live portal.
Paste the job description into score your job match after contact layout is stable. Identity fields and keyword bullets should not compete for the same repair session.
Do this now: Screenshot your name fields after autofill. If the portal truncates, you have proof you submitted the legal spelling in the attachment.
Pick one spelling, then repeat it everywhere
Hyphenated name on resume ATS parsing fix US applications comes down to format choice plus manual verification. Hyphen, space, and concatenated spellings each break parsers differently. Only the ID-accurate spelling belongs on your file.
- Full legal name on one body line with an ASCII hyphen when your ID has one.
- Comparison table reviewed against your documents, not against autofill guesses.
- Portal fields corrected after every upload.
- Same spelling on payroll, I-9, and resume attachments.
You shouldn't drop part of your name to please software. You should make software failures visible before submit, then type the legal string yourself.
If the role asks for a letter, generate a cover letter with the same legal name line you used on the resume header.
Read more
Frequently asked questions
No. Your legal name includes the hyphen. Removing it creates mismatches with payroll, background checks, and government ID. Format the resume so parsers can read the full string on one line, then manually correct application fields after autofill. Consistency beats parser convenience.
On one plain line at the top of the resume body: Maria Lopez-Garcia. Do not hide the name only in a Word header or footer. Do not break the line at the hyphen. Use a standard ASCII hyphen character, not an en dash from autoformat.
Sometimes parsers keep only the final token as last name, so Martinez Rodriguez can become Rodriguez alone. A hyphenated Lopez-Garcia can split at the dash into two fields. Neither is safe without manual verification. Pick the spelling on your legal ID and fix fields after upload every time.
Not reliably on autofill. Workday often maps tokens before and after the hyphen into separate first and last name boxes. Review every name field after import, even when the PDF preview looks fine. Re-uploading a fixed resume does not always refresh cached name data until you clear the fields.