Licensing and permit issuance: the credential a regulator cannot verify from another state
Fifty states, dozens of boards each, every one with its own lookup page and its own data model. An employer verifying a licence across state lines is performing an integration project by hand, one applicant at a time.
Why can't one state verify another state's professional licence?
Because verification means querying each board's website, one at a time, in whatever form that board provides. Fraudulent licences and lapsed-status misrepresentation persist because checking is optional, slow and inconsistent — and the licensee carries nothing a verifier can test.
- Licensing is jurisdictional and every board maintains its own registry, so verification cost scales with the number of jurisdictions rather than with the number of checks.
- Status is the hard part: a licence valid at hire may be suspended six months later, and nothing notifies the employer.
- This is graded C because verification-rate data is thin; boards can measure their own request volume cheaply.
Part of Public sector identity
Two questions that get conflated
Licence verification is usually described as one task. It is two, with different properties.
- Authenticity: was this licence issued by this board to this person? A historical fact that never changes.
- Status: is it currently valid, unrestricted and in good standing? A fact that changes without warning.
A verifiable issuance artefact answers the first cleanly and permanently. It does not answer the second, and any design that pretends otherwise creates a worse problem than the one it solves — a stale credential that verifies correctly while the licence is suspended.
Why interstate practice made this urgent
Licensure compacts and expanded cross-state practice have multiplied the verification burden. A telehealth clinician may hold licences in a dozen states; a travel nurse may work in five in a year; a contractor may operate across a metropolitan area spanning three.
Each of those relationships requires verification, by each employer, against each board, on a cadence nobody has defined.
Designing for freshness rather than against it
The honest design accepts that status changes and builds around it.
| Design choice | Consequence |
|---|---|
| Long-lived issuance receipt only | Verifies authenticity forever; silently wrong about status |
| Short-validity status receipt | Accurate but requires reissuance and a live relationship |
| Issuance receipt plus a signed revocation list | Authenticity permanent, status checkable against a published list |
| Status receipt on demand | Accurate; requires the board to be reachable, which is the original problem |
The third row is the workable one. A board publishes a signed revocation and restriction list on a defined cadence. A verifier checks the issuance receipt against the current list, offline, and knows both facts.
What the receipt carries
{
"type": "manav-stmt/1",
"action": "professional_licence_issued",
"board": "[board, jurisdiction]",
"licensee": "[name, licence number]",
"profession": "[type] Scope: [endorsements, limitations]",
"issued": "[date] Expires: [date]",
"issued_by": "[board registrar, credential]"
}Why this is graded conservatively
Two gaps in the evidence base, and both are worth naming.
First, nobody publishes how often employers actually verify licences. Practitioner accounts suggest it is low outside regulated healthcare settings, but that is an impression rather than a measurement.
Second, the frequency and cost of unlicensed practice arising from verification failure is not systematically tracked. Enforcement actions exist; a denominator does not.
A board wanting to know whether this matters can measure the cheap proxy: verification requests received per year, staff time spent answering them, and the share arriving from out of state. That number alone often justifies publishing a verifiable artefact on cost grounds, independent of any fraud argument.
Where adoption is easiest
Compacts. A compact commission already coordinates across member boards and has a shared interest in reducing per-verification friction. A compact that published signed issuance and revocation artefacts would cover many jurisdictions in one adoption decision, which is a materially different proposition from persuading fifty boards individually.
What a compact would gain from signing
| Model | Speed | Works across jurisdictions? |
|---|---|---|
| Board-by-board lookup | Slow | Only one at a time |
| Compact data sharing | Faster | Within the compact |
| Issuer-signed licence the holder carries | Milliseconds | Anywhere, with published keys |
Objections and honest limits
“Compacts already solve multi-state practice.” For member states and member professions, with their own data sharing. They do not help a verifier outside the compact, or one checking a profession the compact does not cover.
“Status changes, so a carried credential goes stale.” Correct, and that is what short expiry and published revocation are for. A credential with a two-week validity and a revocation check is fresher than a lookup nobody performs.
What a board can do alone
- Sign the licence facts. Holder, profession, status, scope, expiry.
- Keep the validity short. So staleness is bounded by construction.
- Publish revocations. Signed, cacheable, checkable offline.
- Give it to the licensee. Portability is what makes the check happen at all.
Terms used here
- Licensure compact
- An agreement letting a professional practise across member states under a common framework.
- Primary source verification
- Confirming a credential directly with the issuing body — the gold standard, and the reason checking is slow.
- Status misrepresentation
- Presenting a lapsed, restricted or surrendered licence as current.
Frequently asked questions
Does a receipt tell an employer the licence is currently valid? No, and that limitation is central. Authenticity and status are different questions; the receipt answers the first and must be paired with a published revocation list for the second.
Why not just query the board's website? That works for one licence in one state. It does not scale to an employer verifying hundreds of licences across a dozen jurisdictions on a recurring cadence.
Who would adopt first? A licensure compact commission, because one decision covers many member boards and the shared verification burden is already visible to them.
Why is this filed as frontier? Because verification-rate and harm data are thin. The mechanism is straightforward; the business case has to come from a board's own request volume.
Why is licence verification so inconsistent? Every board is a separate query with a separate format and availability, so at volume the check is frequently skipped.
Do compacts solve it? Within their member states and professions. They do not help a verifier outside the compact.
How do you handle status changes? Short validity plus published, signed revocations. A two-week credential with a revocation check is fresher than a lookup nobody runs.
Where this fits in Manav
Manav binds the authorising official to the exact release, award or record change, and produces a receipt another agency, an auditor or a counterparty can verify without access to the issuing system.
Sources and further reading
- FSMB — state medical board licensure and verification resources
- Published enforcement actions involving unlicensed practice and credential misrepresentation.