Overall recommendation
Overall Recommendation
Individual scores are the evidence; the overall recommendation is the verdict. Learn how to combine competency scores into one clear, honest, defensible decision — and say exactly what you recommend and why.
Introduction
You have scored each competency against anchors, gathered evidence, and weighed critical versus trainable gaps. Now everything must come together into a single answer: what do you recommend? The overall recommendation is where all your careful evaluation turns into an actual decision.
This step is deceptively hard. It is tempting to simply average the scores, or to let one strong or weak moment dominate. A good overall recommendation is neither a blind average nor a gut call — it is a reasoned judgment that weighs the evidence against what the role truly needs, and states a clear verdict everyone can understand.
Learning Objectives
- Define what an overall recommendation is.
- Combine competency scores into one decision thoughtfully.
- Choose the right recommendation category.
- Weight competencies by what the role needs.
- Justify your recommendation with evidence.
Why This Matters
Individual scores are only useful if they lead to a clear decision. A vague or hedged recommendation ("she was okay, I guess") wastes all the careful scoring that came before and pushes the hard call onto someone else. A clear, well-reasoned recommendation moves the process forward and can be trusted.
Done well, the overall recommendation makes decisions consistent and defensible. Anyone reading it should understand what you recommend and exactly why — grounded in evidence, not impression.
What Is an Overall Recommendation?
An overall recommendation is a single, clear decision — supported by a short justification — that summarizes whether a candidate should move forward, based on the weighted evidence across all competencies.
Think of a Verdict, Not a Tally
A jury does not simply count how many facts were "good" or "bad" — it weighs the evidence and delivers a clear verdict. Your overall recommendation is that verdict: reasoned, decisive, and grounded in the evidence.
Why It Is Not Just an Average
Averaging scores treats every competency as equally important and can hide a fatal weakness. A candidate might average a solid "4" while failing a competency that is critical to the role.
Blind Average
- Treats all competencies as equal.
- Hides a critical low score.
- Ignores what the role truly needs.
- Produces a misleading "okay" verdict.
Weighted Judgment
- Weights competencies by role importance.
- Flags a critical failure clearly.
- Reflects real job requirements.
- Produces an honest verdict.
Common Recommendation Categories
Rather than a vague comment, use clear categories. A common, effective set looks like this:
| Recommendation | Meaning |
|---|---|
| Strong Hire | Clearly exceeds the bar; strong across key competencies. |
| Hire | Meets the bar; solid evidence with no critical gaps. |
| Hire with Reservations | Meets the bar overall, but with a noted, manageable concern. |
| No Hire | Does not meet the bar; a critical gap or weak evidence. |
| Strong No Hire | Clearly below the bar across key competencies. |
How to Form Your Overall Recommendation
Review All Scores
Look across every competency score and its supporting evidence.
Weight by Role Importance
Give the most critical competencies the most weight in your judgment.
Check for Critical Gaps
Ask whether any weak area is a critical, must-have gap that changes everything.
Choose a Category
Commit to a clear recommendation category, not a vague comment.
Write the Justification
Summarize the key evidence and reasoning behind your verdict.
Worked Example: From Scores to Verdict
A fresher software candidate scores as follows:
| Competency | Score | Role Weight |
|---|---|---|
| Problem-solving | 4 | High |
| Communication | 4 | Medium |
| Fundamentals | 3 | High |
| Specific tool knowledge | 2 | Low (trainable) |
Recommendation: Hire
"Strong problem-solving and communication, solid fundamentals, and only a low score on a specific tool — which is a low-weight, trainable gap for a fresher. No critical gaps. Recommend Hire." The verdict is clear and tied directly to weighted evidence.
Writing a Strong Justification
Every recommendation needs a short justification. A good one names the key strengths, any concerns, and why the verdict follows.
Weak Justification
"Seemed good overall, I think we should hire." Vague, no evidence, not defensible.
Strong Justification
"Solved the task independently and explained clearly; fundamentals solid; only gap is a trainable tool. No critical gaps — recommend Hire." Specific, evidence-based, defensible.
Best Practices for the Overall Recommendation
- Weigh competencies by role importance, don't just average.
- Let critical gaps override otherwise strong scores.
- Commit to a clear recommendation category.
- Always include a short, evidence-based justification.
- Treat trainable gaps fairly, especially for freshers.
- Make sure the verdict matches the recorded evidence.
Common Mistakes
Avoid These
- Blindly averaging all the scores.
- Hiding a critical gap behind strong ones.
- Giving a vague, hedged verdict.
- Recommending with no justification.
- A verdict that contradicts the scores.
Do These Instead
- Weight scores by role needs.
- Flag critical gaps clearly.
- Commit to a clear category.
- Justify with specific evidence.
- Keep the verdict consistent with scores.
Real-World Use Cases
Strong Fresher, One Trainable Gap
Weighting shows the gap is low-importance and trainable, so the recommendation is a clear "Hire" despite one low score.
High Average, Critical Failure
A candidate averages well but fails a must-have competency. The recommendation is honestly "No Hire" because the critical gap overrides the average.
Feeding Panel Consensus
Each interviewer's clear recommendation and justification feed a focused panel discussion, rather than a swirl of vague impressions.
Frequently Asked Questions
Can't I just average the competency scores?
No. Averaging treats every competency as equal and can hide a critical failure. Weight the scores by what the role needs, and let critical gaps override the average.
Should I always pick a firm category?
Yes. Even "Hire with Reservations" is a firm, useful decision. Avoid endless "maybes" that push the hard call onto someone else.
What if strong and weak scores are mixed?
Weight them by importance and check whether the weak areas are critical or trainable. That usually clarifies whether the mix still meets the bar.
How long should the justification be?
Short but specific — a few sentences naming the key strengths, any concern, and why the verdict follows. It must tie clearly to the evidence.
What if my verdict doesn't match my scores?
That is a warning sign. Re-check your reasoning. A recommendation should follow logically from the weighted scores and evidence, not contradict them.
Conclusion
The overall recommendation is where careful scoring becomes a real decision. It is not a blind average of your scores, but a reasoned verdict that weights each competency by what the role truly needs and lets critical gaps carry appropriate weight. It turns a page of numbers into a single, clear answer.
Review all the scores, weight them by importance, check for critical gaps, commit to a clear category, and write a short evidence-based justification. Make sure the verdict always matches the evidence. Do this, and your recommendations will be clear, honest, defensible, and genuinely useful to everyone who relies on them.
Key Takeaways
An overall recommendation is a reasoned verdict, not a blind average. Weight competencies by role importance, let critical gaps override strong scores, commit to a clear category, and always include an evidence-based justification that matches the scores.