Your license is the first thing a nurse recruiter verifies and the easiest thing to get wrong on a resume. Not wrong as in disqualifying — wrong as in vague, which forces the recruiter to dig, which slows you down in a stack of 80 applicants. Here's the format that answers every licensing question in one line.
The one-line format that works
Put licenses in a dedicated section near the top — "Licenses & Certifications" — not buried under education. Each license gets one line:
Registered Nurse (RN) — Texas Board of Nursing · Compact/Multistate · Exp. 09/2027
That line tells the recruiter your license type, issuing state, compact privilege, and that you're current. Type, state, compact status, expiration: that's the complete set.
Should you include your license number?
Optional, and increasingly the answer is no. Recruiters verify through Nursys in seconds using your name and state; the number adds nothing they can't get, and your resume may pass through many hands (agencies, VMS platforms, shared drives). If a specific application asks for the number, provide it in the application fields, not the resume. Never include your Social Security number anywhere — no legitimate employer asks for it on a resume.
Compact (NLC) status: say it explicitly
If your primary state of residence is a Nurse Licensure Compact state and you hold a multistate license, write "Compact/Multistate" on the license line. Don't assume the recruiter will infer it from the state — plenty of nurses in compact states hold single-state licenses, and recruiters searching for "compact" in an ATS will only find you if the word is there.
If you're in a compact state but hold a single-state license, just write the state and say nothing about compact. Claiming multistate privileges you don't have is the kind of error that surfaces during verification and ends a candidacy.
Multiple licenses: travel nurses and border-city nurses
List each license on its own line, active ones first, and lead with the one that matters for the job:
RN — Arizona · Compact/Multistate · Exp. 05/2028 RN — California (single-state) · Exp. 11/2027
California, notably, is not a compact state — travel nurses who've done the paperwork for a standalone California license should absolutely show it; recruiters filling California contracts search for exactly that. Expired licenses generally come off the resume unless a posting asks for licensure history.
Pending, applied-for, and endorsement statuses
Ambiguity costs interviews; pending status usually doesn't. Use plain, dated language:
- New grad, exam scheduled: "RN, Georgia — license pending, NCLEX scheduled 08/2026"
- Passed, awaiting issuance: "RN, Georgia — NCLEX passed 07/2026, license number pending"
- Endorsement in progress: "RN, Ohio — endorsement application submitted 06/2026 (currently licensed in Kentucky, compact)"
Hospitals hire ahead of issue dates constantly. What they can't work with is silence, because silence looks like either an oversight or something being hidden.
Credentials after your name — the standard order
Your name line is prime parsing real estate: "Danielle Reyes, BSN, RN, CCRN." The convention is degree, then license, then national certification — highest to most job-specific. Keep it to three or four credentials; the full list with expirations lives in the licenses section. And keep license and certification lines distinct: BLS and ACLS are certifications, not licenses, and recruiters notice when candidates blur the two.
Quick mistakes checklist
- No expiration date. Every license line needs one — recruiters must confirm you're current.
- "Licensed in multiple states" with no list. Name each state.
- License buried at the bottom. It belongs in the top third of page one.
- Compact status omitted when you have it — you're invisible to "compact" searches.
- Old certifications mixed in with licenses, padding the section recruiters read most carefully.
The mechanics here are small, but they're checked on every single application, which makes them the cheapest fix on your resume. The Nurse Resume HQ builder stores your license with state, compact flag, and expiration as structured fields and formats the line correctly on every export, so this is a set-once problem.