11 min read
US relocation on resume works when you name the city you're moving to in one calm line under your contact info, not a half-page Summary about boxes and uncertainty. If your lease is signed or your start window is inside eight weeks, list the target City, State. If the move is still fuzzy, keep your current address and add Relocating to Austin, TX | Available June 2026 on its own line. Parsers in Workday and Greenhouse read that strip before they score Experience.
You're not hiding the move. You're stopping the file from reading like a maybe. Recruiters aren't allergic to relocators. They're allergic to timelines that sound negotiable after offer stage. One honest line plus a plain cover letter beats a relocation essay above your first bullet.
Check your resume for free with the city string from the posting pasted beside your export. You'll see whether your header matches what the req filter expects.
Quick Wins
- Replace open to relocation with a target metro and month when the date is real.
- Keep relocation out of your Summary. One header line is enough.
- Mirror the posting's city spelling: San Francisco, CA not SF area.
- Paste your PDF into Notepad and confirm City, State appears before Experience.
Why US relocation on resume wording trips quiet filters
Most corporate reqs still carry a location field even when the role advertises hybrid or remote-first schedules. ATS imports pull City, State from the contact block and compare it to that field. A candidate three states away can clear every skill filter and still rank lower than a local file with thinner bullets. That is not a moral judgment. It is how proximity sorts work when recruiters are staring at four hundred new applications.
Vague willingness reads like flight risk. Open to relocation anywhere tells a hiring manager you have not picked a plan. They picture offer negotiations stalling over moving costs, start dates sliding, or a counteroffer back home. You might be fully committed. The header did not prove it.
Timeline essays belong in the cover letter. Three sentences about your partner's transfer or grad school finish date answer human questions. The same story in a Summary pushes your strongest bullet off page one.
Two-column layouts scramble location. Canva sidebars and icon contact rows often export so City lands under Education. Parsers then think you still live where you went to school. Single-column DOCX or PDF with plain text wins imports into iCIMS and Taleo too.
I've screened relocation batches in Greenhouse where the Skills block looked perfect and the header said willing to relocate globally. The file that moved had one boring line: Denver, CO | Relocated January 2026.
Read should you include address on a resume in 2026 when you're deciding how much contact detail belongs above the fold.
Exceptions: when you should name the target city early
Name the destination city before you physically move when the date is locked. Signed lease, campus hire with a known office, or employer-paid relocation with a start month all qualify. You are not lying. You are aligning the parser with reality the offer letter will confirm.
Keep your current city when the move is more than two months out or still depends on a spouse's offer. Add the relocating line with month and year instead of swapping addresses. Recruiters accept planning language when it includes a metro and a date.
International candidates with visa steps should not claim US residency they do not have. List current country, note work authorization in the application field the employer provides, and put target US metro on the relocating line only when counsel confirms timing. The resume proves skills. Authorization belongs where the form asks for it.
Edge case: you couch-surf in the new city while apartment hunting. List that city if you can receive mail there or start onsite work within days. If you are visiting for interviews only, keep home base honest and say available for onsite interviews in Chicago weekly until move in May.
What to change on your export tonight
Step 1: Pick current city versus target city
Open your master file. Decide whether the move is done, imminent inside eight weeks, or still planning. Done or imminent gets the target City, State in the contact block. Planning keeps current city plus one relocating line underneath your phone number.
Before: Boston, MA (might relocate to Seattle soon).
After: Boston, MA · Relocating to Seattle, WA | Available July 2026.
Step 2: Delete relocation from the Summary
If your Summary opens with passionate about relocating or eager to explore new cities, cut it. Replace with one line about scope: five years building B2B pipelines or RN experience on a 28-bed telemetry unit. Location context already lives in the header.
Before: Summary paragraph mixing career goals with relocation dreams across four sentences.
After: Two-line Summary on revenue impact only. Relocating to Phoenix, AZ | Available March 2026 sits under the phone number.
Step 3: Mirror the posting's location string
Copy how the req spells the metro. Nashville, TN beats Tennessee area. New York, NY beats NYC unless the posting uses NYC. Subtle mismatches do not always break parsers, but recruiters search exact strings when the queue is long.
Step 4: Align employer cities in Experience
Remote roles still list a company HQ. If every job line shows a different state than your header, parsers flag inconsistency. Add Remote or City, ST after the employer name when you worked from that market: Acme Corp | Remote (Austin, TX). Do not invent onsite work you did not do.
Step 5: Move timeline detail to the cover letter
Three sentences max: why you're moving, when you can start onsite, and that you are not asking for relocation assistance unless you are. Plain text. No logo header that strips on upload into Lever.
Copy-paste header lines
Already local: Denver, CO · Relocated January 2026 · Imminent move: Chicago, IL · Relocating from Miami, FL | Available April 2026 · Planning phase: Atlanta, GA · Relocating to Seattle, WA | Available Q3 2026 · Remote while moving: Portland, OR · Remote · Relocating to Austin, TX June 2026
Composite: software engineer targeting Seattle
Before: Header lists Ohio address plus Summary about dreaming of West Coast tech.
After: Columbus, OH · Relocating to Seattle, WA | Available August 2026. Bullet one stays a TypeScript migration with dates intact.
Composite: RN relocating for a partner's job
Before: Skills footer repeats Phoenix six times without license context.
After: Tucson, AZ · Relocating to Phoenix, AZ | AZ RN license active | Available May 2026. Compact license noted in cover letter only if the posting asks.
Composite: marketing manager already in market
Before: Still shows a Charlotte address six months after the move.
After: Raleigh, NC · Relocated February 2026. First bullet opens with campaign scope, not another relocation mention.
Edge case: applying to fully remote US roles while moving
Remote reqs often still filter on state for payroll. List the state you will work from on day one. If that is not decided, name the most likely state and update the file when the lease signs. Silence forces recruiters to guess timezone and tax jurisdiction.
Edge case: company pays relocation
Do not put relocation package sought in the header. That belongs in recruiter conversation after interest is mutual. The resume shows you are already headed to their metro. Negotiation comes later.
Phrasing that still reads like a risk signal
Open to relocation anywhere. Spray-and-pray language without a target metro. Pick one city per application batch or per industry hub.
Fake local addresses. Listing a friend's apartment you have never slept in breaks trust in human review and can conflict with background forms later.
City name stuffing in Skills. Austin, Austin TX, Austin Texas in a footer does not beat one clean header line. Parsers treat that as noise.
Conflicting stories across documents. Resume says Denver, cover letter says still flexible between Denver and Boulder, LinkedIn still shows Chicago. Pick one metro for this application pass.
Relocation in every bullet. You do not need will relocate in your sales achievements. Say it once in the header.
Year-only move dates. Available 2026 is weaker than Available April 2026. Month Year matches how recruiters plan interview loops.
See how to fix location and dates mapping errors in US ATS when your city field imports blank after upload.
Parse your header before the next upload
Export PDF, select all, paste into Notepad. Your name, phone, email, and City, State should appear as plain text before the first employer line. Blank squares mean icons or columns broke the contact strip. Fix layout before you tweak wording again.
Run the same file against the posting you target. You're checking whether the city string survives and whether must-have skills still land in dated bullets after you trimmed the Summary. Location fixes do not excuse a broken Experience block.
Score your job match with the req pasted, then generate a cover letter that states your start month in three plain sentences. Keep the letter single column so Greenhouse imports read it.
Ship one calm location line
US relocation on resume stops raising risk signals when you treat location like contact info, not a career story. One City, State or Relocating to line under your name. Timeline and reason in the cover letter. Bullets stay about work you already did.
Open your file tonight, pick current versus target city using the eight-week rule, delete relocation from the Summary, mirror the posting's metro spelling, and run the Notepad test before you upload into Workday again. That is enough for most screens.
Job searching while you're planning a move is stressful enough without your header sounding undecided. A cleaner location line will not fix every req mismatch. It does stop committed candidates from losing to a vague willing to relocate string before anyone reads bullet one.
And if you're applying to three cities in one week, fork the header per metro instead of sending one generic anywhere file. Recruiters in Dallas want to see Dallas, not a national shrug. Ten minutes of tailoring beats another week of silence.
Read more
Frequently asked questions
List the target city only when your move date is firm, usually within eight weeks or after you sign a lease. Until then, keep your current City, State in the contact block and add one line such as Relocating to Denver, CO | Available April 2026. Parsers read the contact block first. A future address with no date reads like guesswork.
Put one line directly under your name or phone number. Do not bury relocation inside a Summary paragraph or scatter city names through Skills. Workday and Greenhouse map City, State from the header strip. A single plain-text line survives PDF export. Icon headers and two-column sidebars scramble that field.
Open to relocation without a target city gives parsers nothing to match against local filters. Many reqs still carry a location field even when the role is hybrid. Name the metro you are moving to and mirror the posting's city string when it is honest. Vague willingness language ranks below a file that already shows Austin, TX in the header.
Yes for timeline and reason. The resume stays factual: current or target city, availability month, and nothing else. The cover letter can explain lease dates, spouse's transfer, or campus hire timing in three sentences. Recruiters read the letter when the resume already looks local enough to schedule a screen.
Update the contact block before you upload again. Stale state lines fail location filters and raise questions in human review. If your mail still forwards, list the new city anyway and handle logistics in the application notes field. Parsers do not read forwarded mail. They read the City, State string you typed.