11 min read
Put your name, phone, email, city, and target job title in the document body on line one. Don't hide contact info in Word's header or footer. Most ATS parsers in Workday, Greenhouse, and Taleo read body text top to bottom, so footer phones vanish and decorative taglines waste the only line recruiters search.
Check your resume for free on the file you'll attach tonight. You'll often see contact fields flagged missing even though they look fine on screen. That's usually a header-zone trap, not a mystery rejection.
Below: why parsers skip Word headers, what belongs in the top four lines, when a target title beats a tagline, exceptions for federal and creative roles, and a copy-paste header block you can drop into a single-column DOCX before export.
Job searching is draining enough without losing callbacks because your phone number lived in a zone the machine never reads. This page is about moving lines on the page, not redesigning your whole career story.
Quick Wins
- Move phone and email out of Insert Header into the body under your name.
- Replace your tagline with the exact target title from tonight's posting.
- Export PDF, paste into Notepad, and confirm contact lines appear in order.
- Delete repeated name bands on page two before you re-upload.
Why an ATS friendly resume header must live in the body
Candidates assume the top of the page is the top of the file. Parsers don't. When you use Word's Insert Header or a Canva text band, that content often sits in a separate XML stream from the main body. On plain-text export, the parser may read your Summary or Education before it ever sees your phone number.
The rule recruiters inherit from the upload: first lines in the text stream become name, contact, and headline fields in Workday or Greenhouse. Lines trapped in header/footer zones may import blank, duplicate, or land in the wrong profile slot.
A composite operations analyst whose PDF looks polished still fails when Notepad shows the file opening with Bachelor of Science while the phone sits alone at the bottom. The recruiter never gets a callback number. The ATS profile looks incomplete. You get filtered on a field you thought was obvious.
Decorative taglines make it worse. Passionate storyteller with ten years of impact doesn't match any req title a sourcer types into search. Senior Operations Analyst does. The header isn't branding space. It's the only row some recruiters read before they ctrl-f the posting noun.
Read why your resume looks different after Workday upload when the preview scrambles more than contact. This page is the top-of-file fix that stops half those mismatches before you touch Experience bullets.
Humans and parsers agree on one thing: they want a boring stack of plain lines. Name, how to reach you, where you are, what role you're chasing. Everything else on the page can sell scope. The header's job is to survive export and match search.
Google Docs behaves the same way. A header inserted through Format Headers and footers can vanish on PDF text paste even when Print Preview looks correct. Treat every editor the same: if it's not in the main typing area, assume Workday won't see it on upload.
Scanned PDFs are a separate failure mode. If your header is an image, no parser extracts the phone. Rebuild the file as selectable text before you apply to any corporate portal that runs Greenhouse or Lever behind the apply button.
Build the header block in four body lines
Line 1: Legal name, bold, no nicknames unless you use them on payroll
Use the name that matches your ID and past employer records. If you go by a shorter name, put it in parentheses after the legal name or use it consistently on LinkedIn and the application form. Don't split first and last across a table cell. One line, left aligned, 14 to 16 point bold in the body.
Before: First name in a left column cell, last name in a right column cell inside a contact table.
After: Jordan Ellis on one plain line, bold, no borders.
Line 2: Phone and email on one row, plain text
US format phone with area code, pipe or bullet separator, professional email. No icons. Icons become empty boxes in text export. If the row wraps on your screen, shorten spacing or drop the portfolio link to line four instead of cramming.
Before: Phone icon and mail icon in a two-column header table in Word's footer.
After: (555) 234-8891 | [email protected] on line two in the body.
Line 3: City, state, and remote willingness when the posting cares
City and state are enough for most US corporate reqs. Add Open to remote when the ad is hybrid or remote-first and you're not local. Don't paste the whole street address unless the form asks. Recruiters use city for timezone and relocation screens, not mail.
Edge case: you're relocating and the posting says local only. Put Relocating to Austin, TX on line three instead of your current city if you'll be there by start date. Edge case: fully remote role with no location gate. City line can read Remote | US time zones when truthful.
Line 4: Target job title mirrored from the posting
Copy the employer's title string when you're qualified. Senior Financial Analyst beats Strategic finance leader driving growth. Staff Software Engineer beats Builder of scalable cloud-native platforms. Swap this line per application. Keep the file name dated so you know which title version you uploaded.
Before: Dynamic professional eager to add value on line four under a logo banner.
After: Senior Financial Analyst on line four, plain text, no italics required.
A composite nurse whose header still says Dedicated caregiver with a heart for patients loses ctrl-f to Registered Nurse when the req title is explicit. Same person, different line, different search hit.
Copy-paste header block
JORDAN ELLIS
(555) 234-8891 | [email protected]
Denver, CO | Open to hybrid
Senior Operations Analyst
Paste that stack at the top of a blank single-column DOCX. Replace each line. Export PDF. Open Notepad, paste the PDF text, and read top to bottom once. If your phone appears after Education, you still have a zone problem somewhere else in the file.
Edge case: federal resume builders (USAJOBS) want their own header fields. Fill those forms in the portal and still keep a plain body header on the attachment if the agency accepts a supplemental PDF. Edge case: creative portfolios sometimes use a visual cover page. Submit a plain resume PDF for ATS upload and send the portfolio link in the application URL field or after a screen.
After the header, leave one blank line, then Professional Summary or Experience. Don't put Skills above Experience unless the posting is entry-level and your work history is thin. The parser already spent its first four rows on contact. Give bullet one room to carry gate proof.
For career changers, line four can name the target role even when your last title differs: Target role: Product Manager above a Summary that bridges from your current Analyst title. Keep Target role: as plain text, not a text box. The parser still needs a single stream, not a floating label.
Taglines, sidebars, and tables that break the header
Word header/footer contact bands. They look professional in Print Layout. They often disappear in text export. Move every contact line into the body.
Two-column contact grids with icons. LinkedIn glyphs and phone icons don't survive parsers. Plain characters only.
Decorative taglines instead of target titles. Recruiters search req language, not your motto. Mirror the title when you're qualified.
Repeating the header on page two. Duplicated name rows restart parse loops and can push your latest employer down the profile.
Photo headshots in the header row. Many US corporate parsers ignore images and may shift text order around embedded objects. Save the photo for LinkedIn.
Pronouns or certification strings on line one. She/her belongs on an optional line after contact or in the application form, not before your name. CPR, PMP, or RN can sit after your target title on the same line if short: Senior Project Manager, PMP.
I've opened Workday profiles where the candidate's email imported twice and the current title landed under Skills because a Canva header pushed body text down. The PDF attachment looked fine. The profile the recruiter searched did not.
Verify the header before you upload
Run the exact PDF through the free ATS checker with tonight's posting pasted in. Missing phone or scrambled top lines show up before you wait on portal silence. Fix the header stack first. Tailoring bullet one is step two.
When the title line matches the req, use the cover letter generator to echo the same target title in paragraph one. Recruiters notice when the header, letter, and application form all name the same role. It doesn't replace gate proof in Experience. It stops easy mismatches.
Save a dated file name each time you swap line four: resume_2026-09-08_senior-analyst.pdf. Your spreadsheet log should record which title string went with which req. Generic filenames make it impossible to know which header version failed parse on a rejection you can't explain.
If the checker flags contact missing but you see it on screen, open Word, double-click the top margin, and check whether those lines live in the header zone. Cut, paste into the body, save, export again. That single move fixes more phantom rejections than another round of keyword stuffing in Skills.
What to do now
An ATS friendly resume header is four plain lines in the body: name, phone and email, city, target title. Not a Word header zone. Not a tagline. Paste your PDF into Notepad tonight. If contact lines aren't at the top, move them before you tailor another bullet.
Open the posting you're applying to. Copy the title to line four. Export. Run the checker. Upload the dated file. That's the whole header job.
This won't fix applying to roles where you miss a must-have. It stops qualified files from dying because the parser never saw your phone.
When the header parses clean, spend your energy on bullet one proof. The recruiter finally has a number to call and a title that matches their search.
Re-read your Notepad paste after every template tweak. Headers are the first thing candidates "fix" with a new design and the first thing parsers break again. Boring wins here so the rest of the file gets read.
Read more
Frequently asked questions
Body only. Workday, Greenhouse, Lever, Taleo, and iCIMS parsers read the main document text stream top to bottom. Word header and footer zones often export empty or out of order in plain text. Put name, phone, email, and city on lines one through four inside the page body. You'll see the same order when you paste the PDF into Notepad.
Yes for US corporate apply. Recruiters ctrl-f the posting title or a close variant: Senior Product Manager, Staff Software Engineer, Registered Nurse. A line like Results-driven professional with a passion for excellence wastes the only searchable row under your name. Mirror the req title when you're qualified. Swap it per application instead of keeping a decorative slogan.
One optional link on the same contact row if it fits without wrapping to a second line on export. Full URLs in the header are fine when they're plain hyperlinks, not icons. If the link pushes your phone number to a footer zone in Word, move it below Experience or into the application form field. Parse order beats looking modern.
11-point Calibri or Arial in the body. Bold your name at 14 to 16 point if you want hierarchy. Avoid text boxes, floating shapes, and tables for contact rows. A single-column stack of plain lines survives PDF export better than a two-column contact grid with icons.
No. Repeating name and phone in a page-two Word header restarts parse loops and can duplicate contact fields in Workday while pushing your latest job title down. Page two should start with continued Experience bullets only. If you need a page break, use a simple line break inside the body, not a repeated header band.