From credentials to capability evidence

A credential is a claim about the past made by an institution. Capability evidence is a record of work someone did, read against a written standard, on a known date. Both are useful. They are not the same thing, and clinical research hiring currently treats them as if they were.

The three questions a credential does not answer

Ask what a certificate or a degree tells a reviewer, and the honest answer is narrow: someone met an institution's requirements at some point. Three questions remain open.

• Recency. When was this capability last demonstrated, rather than last certified?
• Specificity. Which domains does it cover, and which does it leave untouched?
• Application. Can the holder make the judgement call under the conditions of the role?

Those three gaps are why two people holding the same certificate can perform very differently on the same study, and why a hiring team that reads only credentials is surprised by the result more often than it should be.

Who the gap removes

The gap is not neutral. It removes specific people, and it removes them quietly, before anyone reads their file.

An internationally trained physician who has decided not to pursue local clinical licensure carries protocol comprehension, consent conversations and adverse event judgement that a screen reads as an unrecognised degree and a career change. A pharmacist trained outside the reviewer's market carries investigational product handling and SOP discipline that a keyword filter reads as dispensing. A site coordinator carries source documentation and deviation judgement, from the side that creates the source, and is filtered out of monitoring roles for not already holding the monitoring title.

None of those people lack capability. They lack a readable record of it.

A qualification earned in one country is not automatically equivalent to a credential in another, and nothing here suggests otherwise. Licensure, work authorisation and employer requirements are real and they are not TRUVAN's to waive. The narrower point stands: where a role does not require a licence, capability that a filter cannot see is being discarded anyway.

What capability evidence is made of

Evidence is only worth the discipline behind it. Four properties make the difference between a record a hiring manager can act on and a badge that means nothing.

• A published rubric, versioned, that the candidate could read before starting.
• Role-realistic work: a casebook or scenario drawn from the conditions the role operates in.
• Identity and context confirmation, plus an AI-use disclosure, recorded with the submission.
• Structured human review by a qualified reviewer, with the date and rubric version attached.

Remove any one of them and the record degrades. Without a rubric version, an older result cannot be interpreted later. Without a date, recency is unknowable. Without human review, the result is a machine's opinion about work it did not watch being done. Without realistic work, it is a quiz.

Gaps belong in the record

The most useful line in a capability record is often the one describing what was not demonstrated. A record that reports only strengths is marketing. A record that names the domains still to develop tells a hiring manager exactly what the first ninety days need to cover, and tells the professional what to work on next.

This is also where development and hiring stop being separate conversations. The same map that tells an employer which domains are thin across a team tells an individual which practice to do. The difference is only who is reading it.

The workflow, end to end

• Define the capability domains a role turns on, and what good looks like in each.
• Build or select role-realistic work that exercises those domains.
• Publish the rubric before the work is attempted, and version it.
• Confirm identity and context, and record how assistance was used.
• Review every scored submission with a qualified person against that rubric.
• Issue a dated record naming what was demonstrated, what was not and which rubric applied.
• Reassess after development, so a change in capability is visible rather than assumed.

Nothing in that sequence is exotic. It is what a careful hiring team already tries to do informally, written down so it happens the same way for every candidate.

A modest conclusion

Credentials will not disappear, and they should not. They carry information no assessment can reconstruct, and in regulated work some of them are non-negotiable. What they cannot do is answer the recency, specificity and application questions, and pretending otherwise costs employers time and costs capable people access.

Capability evidence sits next to the credential and answers those three questions directly. Read together, they are a better basis for a decision than either alone.