04 · Compare
How to evaluate KOL project fit without confusing prominence with relevance
The short answer
Evaluate KOL project fit by comparing evidence against the specific clinical, geographic and activity requirements of the brief. Keep essential conditions separate, use the same criteria for each candidate and explain the reasons behind any score. Professional prominence alone does not establish suitability for a particular project.
What you’ll take away
- A fit score answers a project question, not who is the best expert
- Compare the same evidence categories across candidates
- Use a score breakdown to guide discussion and follow-up
Putting this into practice? Create your KOL Luminary account or compare plans.
Why a prominent KOL may not be the best fit
A well-known researcher may have a strong publication record in a related area while having limited documented experience with the precise subject, audience or geography in your brief. A less visible clinician may contribute the practical perspective the project needs.
This is why the comparison should begin with contribution. Ask what the person could help the group understand, discuss or communicate. Then inspect the evidence for that contribution. Avoid using career visibility as a shortcut for clinical relevance, communication experience or an essential project condition.
Build a comparison matrix before scoring candidates
Use a small number of distinct criteria. Each should represent a real project need, with an agreed way to recognize supporting evidence. The following is an example review framework, not KOL Luminary's scoring formula.
Swipe the table to see all columns.
| Criterion | Question to ask | Evidence that could help |
|---|---|---|
| Clinical relevance | Does the work relate to the precise topic? | Clinical interests and relevant professional roles |
| Research relevance | Does the research address the project's questions? | Topic-relevant studies and publications |
| Activity experience | Is there experience with this kind of contribution? | Relevant speaking, teaching or advisory roles |
| Geographic relevance | Does the professional context match the brief? | Current affiliation and documented practice setting |
| Group contribution | What perspective would this person add? | A comparison with the rest of the proposed group |
How should you interpret a match-to-brief score?
Read the component label, points earned and points available together. A score of 13.3 out of 35 is a result for that component on that scale. It is not automatically 13.3 out of 100, and it should not be presented as a probability that an engagement will succeed.
Ask which parts of the brief are supported, which are supported only partly and which remain unestablished. A score can be lower because the evidence is a weaker match or because relevant information has not been found. The explanation needs to show the difference wherever the research can establish it.
Do not reverse-engineer a score from one visible fact, such as a congress count. Several pieces of evidence may contribute to different components. Use the actual breakdown supplied with the candidate and keep the overall project-fit result distinct from any single component.
What would a perfect project fit look like?
For a defined scoring framework, full marks require meeting the conditions that framework actually measures. In practical terms, imagine a candidate with clearly documented work in the required topic, the relevant professional setting and the experience needed for the proposed activity. The exact combination depends on the brief.
A perfect-fit example is most useful when it names those conditions in everyday language. It should show what stronger supporting evidence would look like, not imply that the person is universally ideal. Availability, interest in the engagement and required approvals still need their own checks.
Turn the comparison into a selection discussion
Review candidates side by side, then look at the proposed group as a whole. Selecting the highest individual scores can still produce a group with very similar experience. Consider what is missing and whether a candidate with a different background could address it.
Record a short decision note for each shortlisted person: proposed contribution, strongest supporting evidence and next question. Keep essential restrictions visible even when a candidate scores well elsewhere. A consistent explanation is easier for stakeholders to challenge or approve than an unexplained ranking.
If the brief changes, revisit the comparison. A score has meaning in the context in which it was produced. Reusing an old score for a different project can hide an important mismatch.
Common questions
Should I always choose the highest-scoring KOL?
No. Review the underlying evidence, essential conditions and the contribution needed from the whole group. A score helps organize the decision; it does not establish availability or replace the team's selection judgment.
Can two KOLs with the same score have different strengths?
Yes. Similar totals can reflect different combinations of experience. Read the component explanations and supporting evidence before treating candidates as interchangeable.
For product, billing and security questions, visit the KOL Luminary FAQ.