Nursing License Lookup by State (Official Portal Directory + Recruiter Log)

What’s on this page:

Key takeaways

• Use the relevant state’s Board of Nursing or designated licensing agency as the official starting point for a nursing license lookup.
• Confirm the candidate’s identity using multiple matching details before relying on a record.
• Record the exact status wording shown by the portal, along with any displayed dates and the URL used.
• Log search inputs, match points, license type, verification time, and reviewer so the lookup can be handed off or reviewed.
• Escalate ambiguous identity matches, unclear status wording, and discipline or actions entries through the internal credentialing process.

Last updated: August 30, 2026

Ben Argeband, Founder & CEO of Heartbeat.ai — Directory-first, low-risk.

Most nursing license verification problems aren’t about finding a search box. They’re about the fact that every state board runs its own system, uses its own status wording, and updates on its own schedule. That mismatch creates rework right when you’re trying to move a candidate from interest to submittal. This page gives you an official starting-point directory plus a repeatable verification log so your team can confirm license status for RN, LPN, and APRN candidates without guessing at what a portal is actually telling you.

Who this is for

To verify a nurse’s state license, use the official state lookup, confirm that the record matches the candidate, and document the status and lookup details. This workflow is for recruiters verifying nurses or APRNs before outreach or internal credentialing review, with a clear handoff to ops or credentialing support.

• Agency recruiters moving fast and trying to avoid wrong-person errors.
• In-house TA teams validating eligibility before scheduling.
• Ops/credentialing support who need consistent notes and timestamps.

Quick answer

Core answer

Go to the candidate’s state license verification portal, confirm identity and license status, then log the same fields every time so the verification holds up later.

Key insight

Nursing licenses are managed by state Boards of Nursing or a designated licensing agency. Portals and status wording differ by state, so the workflow needs to be standardized even when the source isn’t.

Best for

Recruiters verifying nurses or APRNs before outreach or internal credentialing review.

Compliance & Safety

This method is for legitimate recruiting outreach only. Respect candidate privacy, opt-out requests, and local data laws. Heartbeat does not provide medical advice or legal counsel.

The find-verify-log pattern

1. Find the board. Start from an official source and land on the correct state license verification portal (Board of Nursing or designated licensing agency).
2. Verify. Match the person, not just the name, and confirm what the board record actually shows.
3. Log. Capture a consistent set of fields so anyone on the team can reuse the verification without re-checking.

The trade-off: logging cleanly takes a few extra minutes up front. It saves you the recheck later when a manager asks for proof or a portal’s status wording is ambiguous.

Step-by-step method

Step 1: Confirm state and license type

• State — where the license is issued, not where the nurse currently lives.
• License type — RN, LPN, or APRN (plus specialty/role if the portal shows it).
• Name variants — maiden name, hyphenation, middle initial.

Step 2: Go to the official state portal

Use the directory below to reach an official state lookup. If you have a license number, use it; otherwise, narrow the search with the fields the portal supports, such as city, ZIP, or credential type. Record the exact URL you used.

• Prefer the state Board of Nursing site or the state’s licensing department site.
• Avoid paywalled third-party directories for verification; they’re often stale or incomplete.
• Log the exact URL you used (BON_URL) so the verification can be audited later.

Operational rule: a “no results” screen is not a conclusion. It usually means wrong state, wrong license type, or a name mismatch — not that the license doesn’t exist.

Step 3: Verify identity before trusting the record

Common names can produce wrong-person matches. Look for at least two matching points—for example, full name plus city, or full name plus license type. If a portal returns multiple matches, compare the available details; if identity remains unclear, ask the candidate rather than guessing.

Step 4: Capture status exactly as shown

License status is the board-reported standing of a license — active, inactive, expired, lapsed, suspended, revoked — as displayed in the state record at the time you checked.

• Record the exact status label shown. Don’t translate it into your own shorthand.
• Capture effective and expiration dates if the portal displays them.
• If a discipline or actions section appears, log what’s shown and escalate internally for review.

Step 5: Log the verification

Copy this into your ATS note or CRM activity so the next person doesn’t have to redo the lookup:

• BON_STATE: [State]
• BON_URL: [Official record/lookup URL]
• SEARCH_INPUTS: [Name variant used, license # if used, filters]
• LICENSE_TYPE: [RN/LPN/APRN]
• MATCH_POINTS: [City/credential/other identifiers used to match]
• STATUS_LABEL: [Exact portal wording]
• STATUS_DATES: [Effective/expiration dates if shown]
• DISCIPLINE_FLAG: [Yes/No; portal wording if Yes]
• VERIFIED_AT: [Date/time]
• VERIFIED_BY: [Initials]

Step 6: Decide the next step

• Record is clear: proceed to outreach or submission, verification note attached.
• Identity is unclear: ask the candidate directly. Don’t guess.
• Record is ambiguous: escalate to ops/credentialing with your logged fields and the portal link.

Diagnostic table

Use this to troubleshoot failed lookups and avoid wrong-person verification.

Weighted checklist

Score verification quality before moving a candidate forward. This keeps speed without sloppy documentation.

• 40% Identity match quality
  • At least two match points recorded (MATCH_POINTS)
  • Duplicates resolved and documented
• 35% License record captured
  • LICENSE_TYPE recorded (RN/LPN/APRN)
  • STATUS_LABEL captured exactly as shown
  • STATUS_DATES captured if shown
• 15% Audit trail
  • BON_URL saved
  • VERIFIED_AT and VERIFIED_BY filled
• 10% Handoff readiness
  • DISCIPLINE_FLAG noted (Yes/No)
  • One-line summary added for ops/credentialing

Outreach templates

Template 1: Candidate clarification (identity match)

Subject: Quick license verification question

Hi [First Name] — I’m verifying your state license record before we proceed. Which state is your current license in, and is it under any other last name (e.g., maiden name)?

Thanks, [Your Name]

Template 2: Candidate confirmation (license type)

Subject: Confirming license type for next steps

Hi [First Name] — to line up the right roles, can you confirm your license type in [State]: RN, LPN, or APRN (and specialty if applicable)?

— [Your Name]

Template 3: Internal handoff to ops/credentialing

Subject: License verification logged — please review

Candidate: [Name]. BON_STATE: [State]. LICENSE_TYPE: [RN/LPN/APRN]. STATUS_LABEL: [Exact label]. VERIFIED_AT: [Date/Time]. BON_URL: [URL]. DISCIPLINE_FLAG: [Yes/No + portal wording if Yes].

Directory: official state license verification starting points

This table is a starting-point index, not a complete list of state portals. Use the state link to begin the lookup, record the exact URL you used as BON_URL, and log the standard fields so the verification can be reviewed later.

Fields to capture (short form): BON_STATE, BON_URL, SEARCH_INPUTS, LICENSE_TYPE (RN/LPN/APRN), MATCH_POINTS, STATUS_LABEL, STATUS_DATES, DISCIPLINE_FLAG, VERIFIED_AT, VERIFIED_BY.

Common pitfalls

• Landing on third-party directories. They can be stale or incomplete. Use official state portals and log the BON_URL you used.
• Wrong-person verification. If identity can’t be matched with at least two points, don’t mark it verified.
• Overwriting portal wording. Notes should preserve the exact STATUS_LABEL so ops can interpret it correctly later.
• Missing timestamps. Without VERIFIED_AT, a verification note loses most of its operational value.
• Mixing up agencies. Some states run verification through a broader licensing department portal — Florida MQA and New York’s NYSED are two examples. Log the agency name shown, not just the state.

How to improve results

Speed comes from fewer rechecks and fewer wrong-person errors, not from skipping steps. Improve inputs, logging, and re-verification discipline together.

Standardize what you ask candidates for

• State(s) of licensure
• License type (RN/LPN/APRN)
• Any prior last names
• License number, if they have it handy

Make notes reusable across the team

Use the short-form fields exactly as written (BON_STATE, BON_URL, SEARCH_INPUTS, etc.). Consistency is what makes the next check faster than the last one.

Track the right numbers

Measure rework and ambiguity, not just time spent. A simple spreadsheet or ATS tag keyed by BON_STATE and VERIFIED_AT, with a recheck flag, is enough.

• Verification recheck rate = rechecks required / total verifications, per 100 verifications. Lower is better.
• Identity ambiguity rate = verifications needing candidate clarification / total verifications, per 100. Use it to decide when to ask for license numbers earlier in the process.
• Time-to-verified = median time from “verification needed” to “verification logged.” Use it to spot portal bottlenecks and staffing gaps.

Legal and ethical use

Use this hub to check publicly available board records for legitimate recruiting operations. A lookup documents what the official record displayed at the time of the search; it is not, by itself, a credentialing decision or a guarantee.

• Respect opt-out requests and do-not-contact preferences.
• Collect only what’s needed to match identity and document the board record.
• Don’t treat a lookup as a credentialing decision or a guarantee. Escalate unclear cases to your internal ops/credentialing process.

Evidence and trust notes

For an official directory starting point and board context, use NCSBN. The state Board of Nursing, or the state’s designated licensing agency, remains the source of truth for any record you verify. For how Heartbeat evaluates data quality and sourcing practices, review our trust methodology.

FAQs

What is a Board of Nursing lookup?

A Board of Nursing lookup is the state-run search tool that shows a nurse’s public license verification entry, including license type (RN/LPN/APRN) and license status as published by that state.

What should I log from a nursing license verification?

Log BON_URL, SEARCH_INPUTS, MATCH_POINTS, LICENSE_TYPE, the exact STATUS_LABEL, any STATUS_DATES shown, DISCIPLINE_FLAG, and VERIFIED_AT/VERIFIED_BY.

Why do nursing license searches differ by state?

Each state Board of Nursing operates its own system (or uses a state licensing department portal) and chooses its own search fields, status labels, and publication rules.

Can I use this for RN, LPN, and APRN?

Yes. Always record which license type you verified (RN/LPN/APRN) and don’t assume one type implies another.

Next steps

• Adopt the short-form logging fields as an ATS note template for every verification.
• Use the broader hub for other professions: state license lookups directory.
• If you’re building nurse pipelines and need contact workflows that fit recruiting speed, see: nurse practitioner contact data for recruiting.
• When you’re ready to operationalize sourcing and verification together, start free search & preview data.

About the Author

Ben Argeband is the Founder and CEO of Swordfish.ai and Heartbeat.ai. With deep expertise in data and SaaS, he has built two successful platforms trusted by over 50,000 sales and recruitment professionals. Ben’s mission is to help teams find direct contact information for hard-to-reach professionals and decision-makers, providing the shortest route to their next win. Connect with Ben on LinkedIn.