Candidate Assessment Feedback: What Employers Should Share and Why
A candidate completes an assessment, waits for a decision and receives only: “Unfortunately, your application was unsuccessful.” The message may communicate the outcome, but it does not explain what happened to the assessment evidence or what the candidate could learn from the experience.
A candidate completes an assessment, waits for a decision and receives only: “Unfortunately, your application was unsuccessful.” The message may communicate the outcome, but it does not explain what happened to the assessment evidence or what the candidate could learn from the experience.
At the other extreme, an employer may send an unqualified score report that makes a 72% test result sound like a precise measure of a person's overall ability. That can be equally misleading.
Useful candidate assessment feedback is accurate, job-related, proportionate and understandable. It explains the assessment's purpose, communicates what the results do—and do not—show, and protects confidential information and test integrity.
This guide offers a practical feedback framework for employers using skills tests, work samples, structured interviews and multi-method assessments. It includes original examples, a score interpretation walkthrough, communication templates and safeguards relevant to recruitment across jurisdictions.
Why assessment feedback matters
Candidates invest time in completing assessments. Clear communication can help them understand the process and, where appropriate, identify development priorities.
Employers also benefit from a consistent feedback policy. It encourages better documentation, discourages unsupported claims and helps teams explain selection decisions without improvising.
However, feedback should not promise more precision than the assessment supports. An employer may know that a candidate missed a defined technical standard without being able to infer their long-term potential or personality.
| Feedback objective | Useful approach | Avoid |
|---|---|---|
| Explain the process | State which competency and task were assessed | Generic claims that the test measured “everything” |
| Communicate an outcome | Explain the stage reached and next step | Silence or indefinite uncertainty |
| Interpret a score | State the scale, meaning and limitations | Treating percentages as probabilities of job success |
| Support development | Identify observable strengths and gaps | Diagnosing personality from a short test |
| Maintain fairness | Use consistent, evidence-based language | Different explanations for similar results without justification |
| Protect integrity | Share suitable summaries and examples | Disclosing live answer keys or secure question content |
What should employers share?
The appropriate detail depends on the assessment, stage of recruitment, applicable law, contractual commitments and whether the results support a meaningful interpretation.
A practical baseline includes the assessment purpose, relevant competency areas, outcome status and next steps. More detailed feedback can include appropriately contextualised component scores and observed strengths or development areas.
A proportionate disclosure framework
| Feedback element | Usually useful? | Important qualification |
|---|---|---|
| Assessment purpose | Yes | Describe actual competencies measured |
| Completion confirmation | Yes | Distinguish completed from interrupted |
| Selection-stage outcome | Yes | State whether the candidate advances |
| Competency-level summary | Often | Only when scores support that interpretation |
| Numerical scores | Sometimes | Explain scale, precision and context |
| Cutoff or minimum requirement | When appropriate | Must be established and applied defensibly |
| Detailed answer key | Usually restricted | Protect secure item bank and future fairness |
| Other candidates' results | No | Protect third-party confidentiality |
| Individualised development guidance | Where feasible | Ground advice in observed evidence |
| Appeal or correction route | Where applicable | Follow published policy and legal obligations |
“Usually” is not a substitute for jurisdiction-specific advice. Employers should review legal requirements for automated decisions, access to personal data, disability accommodation and employment selection.
Step 1: Decide the feedback policy before testing
Do not wait until a disappointed candidate asks for a report to decide what can be disclosed.
A written policy should identify:
- Which results candidates receive automatically.
- Whether numerical scores or competency bands will be provided.
- How feedback differs by recruitment stage.
- Who approves individualised comments.
- How quickly feedback is sent.
- How candidates report technical problems or request correction.
- What information remains confidential to protect test integrity.
- How personal data are retained and accessed.
A consistent policy helps avoid arbitrary differences in treatment. It should also allow appropriate exceptions required by law or accessibility needs.
Step 2: Explain what the assessment actually measures
A test title can be broader than the evidence it produces.
For example, a 40-question numerical reasoning assessment may examine calculations, tables and quantitative interpretation. It does not automatically measure accounting ethics, interpersonal communication or every skill required for a finance role.
A candidate-friendly explanation might say:
This assessment sampled numerical reasoning tasks relevant to interpreting figures and identifying quantitative patterns. Your result reflects performance on the questions presented under the stated conditions; it is not a comprehensive measure of your professional ability.
This language is informative without making unsupported predictive claims.
Step 3: Interpret numerical scores accurately
Consider a fictional candidate who answers 29 out of 40 questions correctly.
The raw percentage is:
(29 ÷ 40) × 100 = 72.5%
The employer can accurately report 29 correct out of 40, or 72.5%. But that does not establish that the candidate is “72.5% competent” or has a 72.5% chance of succeeding at work.
A score may be affected by item sampling, difficulty, timing, technical conditions and measurement error. Employers should explain only the interpretation supported by the assessment evidence.
Illustrative feedback scorecard
| Competency area | Correct | Questions | Raw percentage |
|---|---|---|---|
| Numerical reasoning | 9 | 12 | 75.0% |
| Data interpretation | 8 | 12 | 66.7% |
| Analytical reasoning | 8 | 10 | 80.0% |
| Business judgement | 4 | 6 | 66.7% |
| Total | 29 | 40 | 72.5% |
The component percentages are rounded to one decimal place; the total uses all 40 questions. A simple average of the four percentages would be incorrect because the components contain different numbers of questions.
These figures are fictional. Short subscales may not support precise competency claims. The employer should avoid ranking a candidate's strengths from small differences unless score reliability and interpretability justify that level of detail.
Step 4: Separate performance feedback from the hiring decision
An assessment result and a hiring decision are related but distinct.
A candidate can perform well on one assessment and still not progress because the role requires additional competencies or because the overall selection process uses multiple documented methods.
Conversely, a candidate may meet a defined assessment standard without being guaranteed an offer.
A clear message distinguishes:
- What the candidate completed.
- What the assessment result means.
- Whether the candidate progresses.
- Which other stages or criteria apply, where appropriate.
- What happens next.
Avoid suggesting that a candidate “failed” an entire profession because they did not meet the requirements of one specific selection process.
Step 5: Give evidence-based strengths and development areas
Useful developmental feedback refers to observable performance rather than speculation about the person's character.
Too vague: “You lack analytical ability.”
More useful: “In the data-interpretation section, your responses were more accurate on direct comparisons than on questions requiring reconciliation of multiple figures.”
Too personal: “You are not a natural leader.”
More useful: “In the supervisory scenario, your response identified the immediate issue but did not specify a clear delegation or follow-up plan.”
The more detailed the claim, the stronger the supporting evidence should be. A small number of questions may justify only broad feedback, not a diagnostic profile.
Step 6: Protect the integrity of secure question banks
Employers may want to provide explanations while preserving future assessment fairness. Publishing the exact wording, answer keys and detailed solutions for active secure questions can encourage memorisation and undermine retakes.
A balanced approach can share:
- The competency tested.
- A general explanation of the skill involved.
- Non-secure illustrative practice examples.
- Broad development recommendations.
- A route to report suspected question errors.
Where item-level feedback is appropriate, use retired or purpose-built practice items rather than disclosing protected live questions without a controlled release policy.
Test integrity should not be used as an excuse to conceal a confirmed scoring error or deny a legally required disclosure.
Step 7: Explain pass marks and selection thresholds carefully
A pass mark should reflect a documented decision standard, not an arbitrary percentage.
Suppose a fictional employer sets a minimum work-sample score of 70 out of 100 through a suitable job-related standard-setting process. A candidate scores 66.
A defensible feedback statement is:
Your work-sample score was 66 out of 100. The documented minimum for this stage was 70. You therefore did not meet the requirement for progression at this stage.
The employer should not imply that 66 means the candidate is incapable of doing the job in all circumstances. Nor should the threshold be changed retrospectively to favour a particular applicant.
Where disclosure of cutoffs is legally or operationally sensitive, obtain appropriate advice and follow a consistent policy.
Step 8: Address technical issues and accessibility
A candidate who loses connectivity halfway through an assessment may not have a valid completed score. Feedback should distinguish an incomplete session from demonstrated low performance.
An effective process provides a way to report interruptions, request appropriate accommodations and challenge administrative errors.
| Candidate issue | Appropriate response |
|---|---|
| Assessment did not save | Verify session logs and completion status |
| Candidate could not access a question | Investigate accessibility and format |
| Candidate disputes an answer | Review the item and scoring key |
| Candidate requests score correction | Follow documented verification and correction process |
| Candidate needs an accessible report | Provide an appropriate alternative format |
| Candidate requests personal data | Apply relevant privacy and access requirements |
Do not disclose another candidate's results while resolving a complaint.
Step 9: Tailor detail to the recruitment stage
Not every applicant needs a lengthy personalised report. A proportionate policy can balance candidate value, operational effort and evidence quality.
| Recruitment stage | Possible feedback level |
|---|---|
| Initial eligibility screen | Completion and outcome, with concise explanation |
| Standardised skills screening | Outcome and supported competency summary |
| Shortlisted work sample | Scored criteria and specific observed strengths or gaps |
| Final structured interview | Job-related feedback aligned with documented rubric |
| Internal promotion assessment | More detailed development-focused discussion where appropriate |
For internal promotion, feedback may need to support a longer-term development relationship. Employers should keep selection decisions and development planning distinct, even when the same assessment contributes to both.
Step 10: Use respectful, precise communication
Feedback should be written in plain language. Avoid jargon such as “low construct score” unless the recipient is likely to understand it and the report explains the term.
Be careful with absolute statements. “Your response did not include an escalation step” is more defensible than “You cannot manage escalations.”
Candidates should know whether they can request clarification and when to expect further communication.
Example feedback messages
Example A: Candidate progresses
Subject: Assessment completed — next stage
Thank you for completing the assessment for the Reporting Analyst position. Your submission has been reviewed, and you have met the requirements for progression to the next stage.
The assessment covered numerical reasoning, data interpretation and analytical judgement. We will contact you with details of the next stage and any preparation information you need.
Example B: Candidate does not meet a documented standard
Subject: Assessment outcome — Reporting Analyst application
Thank you for taking the time to complete the assessment. The work sample was designed to evaluate reconciliation accuracy and the explanation of reporting discrepancies.
Your result did not meet the documented minimum requirement for progression at this stage. This outcome relates to the specific assessment and role requirements; it is not a judgement about your overall professional potential.
Thank you for your interest and the effort you invested in the process.
Example C: Development-focused feedback
Subject: Your assessment feedback
Thank you for completing the supervisory assessment. Your responses demonstrated clear identification of immediate operational problems. In the delegation scenarios, your proposed actions would have been stronger with explicit task ownership, deadlines and follow-up checks.
For development, consider practising short action plans that specify who will act, what will be completed and how progress will be reviewed.
These examples are templates, not legally sufficient notices for every jurisdiction or selection process.
Feedback for multi-method assessments
When employers combine skills tests, work samples and structured interviews, feedback should avoid treating the composite as the whole story.
For example, a candidate might perform strongly on numerical tasks but less strongly on a structured communication exercise. If the role requires both, the employer can explain the relevant dimensions without suggesting that a single number measures total employability.
Any composite score should use justified weights and documented decision rules. For the design of such models, see How to Combine Multiple Assessment Scores Into a Defensible Hiring Decision.
Privacy, retention and cross-border considerations
Assessment records can be personal data. Employers should limit access, establish retention periods, document purposes and review the legal basis for processing in the jurisdictions where candidates are located.
Where automated scoring or automated decision-making is used, additional transparency, contestability or human-review obligations may apply. Requirements vary, including under data-protection and employment laws.
Do not claim that a standard feedback template guarantees compliance with all global privacy or employment frameworks. Organisations operating across borders should obtain jurisdiction-specific review.
Common assessment feedback mistakes
Sharing a percentage without context. A raw score is not a probability of job success.
Providing unsupported personality judgements. Feedback should reflect observed evidence.
Disclosing secure live answers indiscriminately. Detailed answer keys can compromise future assessments.
Calling every unsuccessful candidate a failure. Not progressing in one selection process is not a global measure of capability.
Giving contradictory explanations. A written policy and scoring audit trail help maintain consistency.
Ignoring technical or accessibility complaints. An invalid or interrupted session should be investigated before being treated as a completed result.
Overpromising development precision. Small tests and short subscales may not support detailed skill diagnoses.
Employer candidate-feedback checklist
- Define what candidates will receive before assessment begins.
- Explain the competencies actually measured.
- Distinguish raw scores from broader ability claims.
- Report completion status and next steps accurately.
- Use documented standards and decision rules.
- Ground comments in observable evidence.
- Protect secure questions and other candidates' data.
- Provide routes for technical complaints and score correction.
- Address accessibility and alternative report formats.
- Apply appropriate privacy, retention and legal controls.
- Review templates for clarity, consistency and respect.
Candidate feedback and Talentrenza Assess
Talentrenza Assess provides structured assessment experiences and results that can inform employer decisions and candidate development. Employers should verify the specific reporting, messaging and disclosure features available in their workspace before promising automatic personalised feedback or item-level explanations.
A platform report does not automatically establish the meaning of a score or satisfy every jurisdiction's disclosure requirements. Employers should set a clear feedback policy aligned with their assessments, hiring procedures and legal obligations.
For related reading, see Pre-Employment Assessment Pass Marks and Scoring Criteria, How to Validate Pre-Employment Assessment Tests, and Fair and Objective Employee Promotion Assessments.
Frequently asked questions
Should employers share assessment scores with candidates?
Often it can be useful, but disclosure depends on the score's interpretability, the employer's policy and applicable law. Explain what the score represents rather than sending an unexplained number.
Must employers reveal the correct answers?
Not universally. Employers may protect secure live question banks, subject to applicable legal rights and obligations. General competency feedback and non-secure examples can provide value without compromising test integrity.
How detailed should unsuccessful-candidate feedback be?
Provide a clear outcome and, where feasible, relevant evidence-based explanation. The level of detail should be proportionate to the stage, the quality of the evidence and legal requirements.
Can a 72.5% score be described as 72.5% competence?
No. It is the proportion of available points earned under defined conditions, not a direct measure of overall professional competence.
Should candidates receive feedback after technical interruptions?
They should receive an accurate status and a route for resolution. Do not represent an incomplete or invalid session as a normal completed score without investigation.
Does assessment feedback need to be the same in every country?
No. A consistent global policy can provide a baseline, but local employment, privacy, accessibility and automated-decision requirements may differ.
Conclusion
Candidate assessment feedback should make the selection process more understandable without exaggerating what the evidence proves. The strongest feedback is clear about the task, accurate about the score, grounded in observable performance and respectful of the candidate's time and rights.
Employers that define their feedback policy in advance, protect assessment integrity and maintain a route for correction can communicate decisions more consistently while preserving high hiring standards.
