License certification data is the part of a career record that carries the most authority and the least standardisation. A credential’s name is often the only part of it that fits in a form field, and the name is exactly the part that is shared by the most unrelated things.
This article explains why a credential title is not an identity, which fields make a record meaningful, why validity and renewal are decisions rather than facts, and how to represent a credential without implying that its holder has one.
What belongs in a credential record?
A useful credential record names four things, and omitting any of them makes the record ambiguous.
| Element | Why it is needed |
|---|---|
| The credential’s name | The starting point, and on its own the least reliable part |
| The issuing body | Two differently-named credentials from one body are usually related; one name from two bodies usually is not |
| The region where it applies | The same words designate different things in different places, and permission normally stops at a border |
| The status claimed | Held, in progress, lapsed or merely listed — a different statement in each case |
A fifth element is worth keeping when the source provides it: the level or grade attached to the credential, where the issuing body distinguishes between them. A credential family often has several tiers, and a record that drops the tier can make the lowest and the highest look identical.
The test of a well-formed record is whether a reader who knows nothing about the profession could tell what the holder is entitled to do. If the answer is that the holder is entitled to nothing, the record is describing an affiliation rather than a permission, and it should say so.
Why does the same credential name mean different things in different places?
Because licensing is a local act. A body that grants permission to practise operates within the boundaries of whoever recognises it, and the names it adopts tend to be descriptive of a general function rather than unique. Two neighbouring jurisdictions can each have a qualification whose name translates into the same English phrase, and holding one has no bearing at all on the other.
Three mechanisms produce the confusion. The first is translation: a well-established local title can be rendered into English in several competing ways, and whoever wrote the CV chose one of them. The second is the awarding body’s own naming habits, where a new body adopts a familiar-sounding name for a scope that is entirely different from the original. The third is the drift of the profession’s vocabulary itself, so that a title written decades ago may describe a role that no longer exists in that form.
The consequence for anyone reading a record is that the credential name is a hint and the issuer plus the region is the identification. A search that matches on the credential name alone will treat unrelated qualifications as equivalent, and it will do so silently, which is the worst way to be wrong.
Does listing a credential mean the person holds it?
No, and the distinction is central rather than pedantic. A record that lists a credential in a candidate’s profile is listing a claim by the candidate about a credential. Whether the credential exists, is current, and belongs to that person are three separate questions, and none of them is answered by the presence of the words.
That matters for how the data is used, not just how it is stored. A list of credentials in a profile is a prompt for verification, not the outcome of one. A design that treats an entered credential as verified has quietly removed a check that existed for a reason, and it will be discovered only when somebody presents a credential they do not have.
There is a second version of the same mistake in generated data. When a set of sample records includes credentials that exist in the real world, a casual reader can mistake the sample for a statement about a person. That is why generated records should use credentials whose presence in the record is obviously illustrative, and why a record should always carry its own disclaimer rather than relying on the reader’s good sense.
Are validity periods fixed or chosen?
They are chosen, and the choice belongs to the awarding body within whatever its jurisdiction permits. Nothing about validity is intrinsic to the skill the credential attests to.
Some credentials are perpetual once granted, with no renewal at all. Some are renewed on a fixed cycle tied to continuing education or fee payment. Some lapse automatically if the holder stops practising, and some lapse only if the holder fails to give notice. Practices also differ within a single credential family, because some issuing bodies maintain several tiers with different rules for each.
Because this varies, a record should never infer expiry from the credential’s type. Where the source provides a validity period, the record should store it along with the issuer that defined it. Where no period is available, the honest record says that the credential was granted and records nothing further, rather than inventing a default horizon. Anyone building a reminder or renewal workflow should read the rule from the issuing body rather than assume it, and treat any single rule as applying to that issuer alone.
For developers: credential fields and their claims
Represent the credential as a claim with an attached source, in the same way you would represent any other assertion that arrives from outside your system.
Five habits keep the model honest. Keep the credential’s identity separate from its display name, so that the issuer and region are part of what identifies it rather than annotations on a string. Keep the claimed status as a field of its own, with values that distinguish holding a credential from expecting to hold one. Never store a validity period without the issuer that defined it. Treat the region as a filter rather than as free text, because a credential that applies nowhere in particular is not usable for anything. And never write a verification result into the same field the candidate wrote into, because once verified and claimed share a column the distinction is unrecoverable.
For test data, the interesting cases are the ones that expose the model: the same credential name from two issuers in two regions, a credential in progress, a lapsed one, and a credential family where the tier is what distinguishes one from another. The credentials named in the generated records on this site are common qualification names used to populate these cases. Listing a name does not mean that anybody holds it, and nothing here is a claim about a person’s right to practise.
Next steps
If your credential field is a single free-text line, check what your search does when two unrelated issuers use the same phrase. The usual result is that both are returned together, and the fix is a second and third field rather than a better search. The relationship between a credential and a self-assessed skill level is taken apart in skills taxonomy levels, and the way a qualification is recorded alongside it is described in education records and degrees. Sample records that include credentials can be produced from the career profile tool.