Jurisdictional licence
A Licence Is Authorization, Not a Skill Level
Licensing can protect the public by setting entry, accountability and scope-of-practice rules. It is still not a universal measure of what a person can do outside that legal context.
What the wrapper says
A licence is issued by a regulator in a particular jurisdiction for a protected occupation, scope, or practice context; an occupation describes the work and its entry characteristics.
The all-clear
Occupational licensing provides public protection, accountable practitioners, enforceable scope rules, and a way to verify current authority.
What is durable
The demonstrated capability to perform defined work safely and competently under stated conditions.
The request is modest.
Add a licence field to your skills graph.
Fine.
Great.
A field.
We have fields.
By Tuesday, capability_model_FINAL_final_v16.xlsx contains a column reading licensed = yes. It sits beside critical thinking, manual dexterity, and the ability to get a meeting cancelled before it becomes a steering committee.
Then somebody moves jurisdiction.
Somebody else’s renewal date passes.
A third person has a foreign qualification.
And your talent marketplace, seeing a familiar title, recommends all three for regulated work.
That is not a metadata issue.
A licence is authorization. A skill level is evidence of capability.
They can be related.
They are not the same claim.
An occupational licence is a regulatory grant.
It is issued by a particular authority, for defined work, in a particular jurisdiction, under a particular scope of practice.
A capability is the demonstrated ability to do that work safely and competently under stated conditions.
Those are different sentences.
They are also different objects.
One is a current legal permission.
The other is the durable object underneath it.
The distinction matters because a licence can expire, be limited, or refuse to cross a border. Nobody becomes incapable at midnight because an administrative cycle ended.
It matters in the other direction too.
Demonstrated capability does not permit a person to do work that a local practice act reserves to licensees.
The first mistake creates unnecessary blocks.
The second creates unlawful recommendations, which is a slightly more serious failure mode than a poor learning-path suggestion.
The licence field has started telling stories
Take the ordinary route into physical therapy.
A Doctor of Physical Therapy programme runs about three academic years and includes months of full-time clinical rotations.
That is substantial preparation.
It is still not the licence.
The regulator does not accept a photograph of a diploma attached to an email called dpt_proof_REAL.pdf. The university registrar sends a sealed transcript directly to the board.
That is a provenance control.
It establishes where the entry requirement came from.
Nothing more.
The applicant then supplies an application record, disclosures, and a criminal-history check. The board reviews the file and decides whether the applicant may test.
None of that measures whether the person can manage every future clinical situation. It establishes whether the regulator will allow the next step.
The National Physical Therapy Examination is another object again.
It sets a scaled threshold for entry competence.
A real threshold, seriously built.
Measured on one day.
It is not a proficiency scale for every task, setting, patient population, or moment in a career.
Once the board grants eligibility, the candidate receives an Authorization to Test, valid for a fixed window.
The name is unexpectedly honest.
It is authorization to sit an examination.
Passing the examination is one requirement inside a longer authorization process.
Then there is the state jurisprudence examination, which makes the point outright.
Its subject is local practice law, administrative rules, reporting obligations, consent and discipline.
30 to 50 questions.
80 percent to pass.
Pass it and you have shown that you know the rules in one state.
Your skills model should not quietly translate that into “advanced legal judgment” and send it abroad.
O*NET already keeps the objects apart
This is not a plea for a philosophically ambitious HR system.
The O*NET Content Model has already done the filing.
Entry licensing sits under Experience Requirements, beside experience and training. Skills, knowledge and education sit somewhere else entirely, under Worker Requirements. Occupational Requirements hold the work activities and the context.
The regulatory wrapper and the occupational description are in different drawers.
The drawers are there for a reason.
Somebody thought about it.
O*NET’s skill and ability ratings are scales built to describe occupational demands.
Importance.
Level.
Behavioural anchors.
A licence number is not one of those scales wearing a lanyard.
The same model can describe the work, the conditions, and the consequence of an error. It does not ask a current licence status to carry all of that meaning by itself.
Neither should your workforce platform.
Licensing has a public-protection job, and it does it
None of this is an argument against occupational licensing.
Practice acts establish two separate controls, and both matter.
Title protection restricts who may use a protected professional name.
Practice exclusivity restricts who may deliver defined services.
They carry enforcement, too.
Boards issue subpoenas and cease-and-desist orders, levy civil penalties, and in many U.S. healthcare and structural-trade contexts unlicensed practice is a criminal offence.
There is no version of your workforce design in which a recommendation engine improvises around that boundary because a profile looked strong.
Licensure also makes current status checkable.
A public register carries the licensee’s name, licence number, issue date, expiration date and disciplinary standing.
Renewal runs on a 24-month cycle, with continuing competence units attached.
That is accountability infrastructure.
Keep it.
Just do not treat it as a permanent numeric representation of a person.
Scope is the payload, not the badge
The operational issue is scope.
A licence is not a badge saying somebody passed a difficult exam last quarter. It says who may perform which work, under which authority, and under which conditions.
Nursing makes this deliberately awkward for anyone building a global field.
In full-practice states, Nurse Practitioners may evaluate, diagnose, order diagnostic tests, prescribe, and manage treatment under the authority of the nursing board.
In reduced and restricted states, a career-long collaborative agreement or a supervisory contract can be required. Some rules cap a single physician at 4 to 6 supervised practitioners, or require 2,000 post-graduate hours before prescriptive authority begins.
Same occupation.
Same label.
Different authorized work.
The title does not contain the jurisdiction.
The licence record has to.
This is also why the occupation field and the licence field should not collapse into each other.
Registered Nurses, Nurse Practitioners, and Licensed Practical Nurses have different occupational boundaries: care-plan evaluation, diagnostic and prescriptive authority, and supervised execution.
A statistical occupation describes work and entry characteristics.
A regulator determines local authorization.
That distinction looks fussy right up until a system recommends a task with consequences. Then it looks like the minimum viable data model.
A border is not a skills assessment
Portability is where your licensed = yes column starts producing fiction at scale.
A foreign-educated physical-therapy candidate goes through formal educational equivalency review by an approved service, which compares course content against a U.S. coursework tool before the board will open the file at all.
That is a process.
It takes months.
It is not a database join.
And even where you hold excellent evidence of education, examination history, supervised practice and demonstrated work, the destination regulator has its own current requirements.
A model can identify experience relevant to an application.
It cannot declare that an authorization transferred.
Renewal behaves the same way.
Codes run on annual or biennial cycles and specify contact hours, sometimes down to the subject: jurisprudence, ethics, infection control, opioid prescribing.
Those requirements do not measure the whole person.
They do create a current regulatory condition.
So a licence record needs status and effective dates, not a timeless Boolean waiting to disappoint everyone after a migration.
AI turns the shortcut into a decision
For years these distinctions lived in the heads of licensing specialists, recruiters, and the one operations manager who knew which regulator page to check.
Imperfect.
But context existed.
Now workforce systems infer skills, match people to roles, recommend learning and shortlist candidates at volume. They ingest occupation codes, job titles, credential records and licence fields, because those records are tidy.
AI is unusually good at treating tidy records as settled meaning.
If the model reads a current licence as a skill level, it will block a capable person from adjacent lawful work the moment the licence lapses.
If it reads a foreign licence as permission, it will recommend regulated local work before any regulator has authorized it.
If it reads an occupation title as scope, it will miss the difference between full, reduced and restricted practice.
None of that is the model overreaching.
That is a data contract failure with an attractive interface.
The remedy is admirably unglamorous.
Store the regulator, jurisdiction, protected title, scope, status, issue date and expiration date as authorization data.
Store capability evidence separately: assessment, supervised work, project outcomes, validated practice, whatever actually supports the claim.
Then give the model two honest questions instead of the one convenient one it currently has.
Can this person demonstrate the capability this work requires?
Is this person currently authorized to perform this work here?
The answers may both be yes.
They may not.
That is information, not a defect.
The regulator gets the final noun
You can maintain a canonical role, an occupation classification and a serious skills record.
You can keep every date, document and evidence relationship that makes the decision auditable.
You should still route the authorization question to the regulator’s register, scope rules and reciprocity process.
Not to the LinkedIn title.
Not to the old credential attachment.
And not to a hopeful cross-border match with a reassuring confidence score.
The regulator’s answer is authoritative inside its jurisdiction.
The capability record stays useful across all of them.
The occupation record stays useful for describing and comparing work.
Three objects.
Three fields.
Not one.
And if your system has one field for all three, that field is not simplifying the problem.
It is hiding it.
What the record establishes
- Store the regulator, jurisdiction, occupation and scope of practice as separate fields.
- Distinguish evidence of capability from legal authorization to perform regulated work.
- Record licence status, issue date, expiration date and effective dates rather than a permanent licence flag.
- Model reciprocity and foreign-education recognition as an application process rather than an assumed transfer.
- Keep title protection and practice exclusivity as different regulatory rules.
- Route authorization decisions to the relevant regulator's current register, scope rules and reciprocity requirements.
Asked in the review
- Is a professional licence the same thing as a skill level?
- No. A professional licence is a regulator's current authorization for defined work in a particular jurisdiction, occupation, and scope of practice. A skill level describes demonstrated capability under stated conditions. The two can be related because licensing may require education, examinations, or supervised practice, but a licence status does not create a universal capability score and a capability record does not grant legal authority.
- What information belongs in a licence record?
- A licence record stores the issuing regulator, jurisdiction, occupation or protected title, authorized scope, licence number where appropriate, status, issue date, expiration date, and the effective dates of any relevant conditions. It does not replace evidence of capability. Keeping those fields separate lets a system distinguish an active authorization from expired status, an authorization elsewhere, and a person's demonstrated work history.
- Why should title protection and scope of practice be stored separately?
- Title protection restricts use of a protected professional designation, acronym, or commercial title. Practice exclusivity restricts performance of defined services or interventions without the required licence. A person can encounter one restriction without the other. Separate records prevent a title rule from being mistaken for a complete work authorization, or a work restriction from being reduced to a naming convention in an HR system.
- Does an active licence prove that someone can do every task in the occupation?
- No. An active licence shows that the relevant regulator currently authorizes work within its defined scope and conditions. Occupational capability still varies by task, setting, recency of practice, responsibility, and evidence. O*NET treats entry licensing as an Experience Requirement while separately describing abilities, skills, knowledge, work activities, and work context. That structure reflects different claims rather than one universal skill level.
- What happens when a licence expires?
- An expired licence changes the person's current authorization status; it does not by itself establish that the person's underlying capability disappeared. Licensing rules commonly require annual or biennial renewal, continuing education, fees, and possible audit before practice authority remains active. A workforce system records the expiration and status accurately, preserves separate capability evidence, and routes any current authorization decision to the issuing regulator.
- Can a licence from another jurisdiction be treated as local authorization?
- No. A licence issued elsewhere is evidence of a regulatory history, not automatic authority in a new jurisdiction. Recognition can require an application, primary-source verification, education review, examination, or a jurisdiction-specific law assessment. Foreign-educated physical-therapy candidates can undergo an approved evaluation that compares course material through the U.S. Coursework Tool before board intake. The local regulator determines the current path.
- Why does a licensing application ask for more than training and an exam score?
- Licensing is an administrative public-protection process, not a single assessment. A physical-therapy licensing pipeline can include registrar-to-board transcript verification, criminal-history clearance, a national examination, state-specific jurisprudence testing, board adjudication, and public registry enrollment. These steps establish identity, eligibility, accountability, and legal compliance alongside evidence of entry competence.
- How is a licensing exam different from a skills assessment?
- A licensing examination can test a regulator's threshold for entry competence within a defined profession, but it does not by itself describe every capability or the person's current performance in every context. The National Physical Therapy Examination uses a scaled score from 200 to 800 with a passing score of 600. O*NET, by contrast, rates skills and abilities using separate Importance and Level measures.
- Why do nurse practitioner permissions vary so much?
- Nurse practitioner authority depends on the governing jurisdiction's scope-of-practice rules. Full-practice regimes can allow a nurse practitioner to evaluate, diagnose, order tests, prescribe medicines including Schedule II–V substances, and manage treatment under nursing-board authority. Reduced or restricted regimes can require a collaborative or supervisory arrangement. A job title alone cannot safely represent those different legal permissions.
- What should an AI matching system do with licence data?
- An AI matching system keeps authorization separate from capability evidence and checks the regulator, jurisdiction, scope, status, and effective dates before recommending regulated work. It should treat reciprocity as a process and direct current decisions to regulator sources. Otherwise it can falsely treat a foreign licence as local permission or treat an expired licence as proof that demonstrated capability no longer exists.
- Why is a public licence register useful to an employer?
- A public licence register provides a current regulatory record of a licensee's name, licence number, issuance date, expiration date, and disciplinary standing where the regulator publishes those fields. It supports verification of legal authorization without asking an employer's skills database to invent it. A registry check answers a current authorization question; it does not replace assessment of the capability required for a particular assignment.
- What should happen when the system cannot verify authorization?
- The system marks authorization as unverified or pending rather than inferring permission from a title, credential, prior role, or foreign licence. The decision is routed to the relevant regulator's current register and scope-of-practice or reciprocity requirements. That preserves an auditable boundary: a matching system can identify relevant experience, while the regulator remains the authority on whether regulated work is permitted.